Considerations on http/2 push implementation

  • Resolved titsmaker

    (@titsmaker)


    3 years, 1 month ago

    It’s great that your plugin offers such an option to push CSS and JS files, but I suppose it needs more refinement to be useful.
    Pushing all the assets is often too much and can lead too performance decrease instead of increase.
    So we should have an options to:
    – push only selected resources
    – exclude some resources from being pushed

    Also having ability to preload resources instead of pushing would be great also as in some cases preloading would make more sense.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support qtwrk

    (@qtwrk)

    3 years, 1 month ago

    Hi,

    Actually Google is going to remove the HTTP2 push out of Chrome and we are evaluating this that if we should drop the HTTP2 push alone with it

    Best regards,

    Thread Starter titsmaker

    (@titsmaker)

    3 years, 1 month ago

    OMG, that’s quite surprising. I can’t get Google logic here (https://groups.google.com/a/chromium.org/g/blink-dev/c/K3rYLvmQUBY/m/vOWBKZGoAQAJ?pli=1), they say too few sites are using http/2 push but that can be said about any new technology. E.g. despite all Google efforts webp is used by merely 1,5% of websites now but that does not make Google drop webp support.
    Anyway thank you for that information and please consider implementing selective resources preloading instead of push.

    Plugin Support qtwrk

    (@qtwrk)

    3 years, 1 month ago

    Hi,

    thanks for the info , we will evaluate it

    Best regards,

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Considerations on http/2 push implementation’ is closed to new replies.