Search results

  1. dimasites

    Feature Request: HTTP-Early-Hints header

    This is a very relative concept... I'm afraid when you achieve DocumentComplete in 150-250 ms, the additional 50ms will become up to +30% speed for you. This is the reason why I switch to HTTP 3 from HTTP 2 (minus ping time thanks to Zero-RTT), and Early Hints can give a much greater increase...
  2. dimasites

    Feature Request: HTTP-Early-Hints header

    For more readability, as i said: You are right, i new user for litespeed, however, I have enough experience (10+ years, but not enough to stop learning) to see that performance depends on many factors, and you cannot rely only on a web server if you need realy high speed for UX and SEO. It...
  3. dimasites

    Feature Request: HTTP-Early-Hints header

    Its mean, i recommend you split to separate files js-libraries which glued now together in one file. Like a CSS-sprites, it is old practice and antipattern on HTTP2 and 3, as like as CSS-sprites which you are not using and it is ok. You can use it slight better: see the screenshot. I am about...
  4. dimasites

    Feature Request: HTTP-Early-Hints header

    I agree that it loads fast, but I also assure you that it will be even faster if you get rid of unnecessary font files using modern VFS and decompose the bundles, because there are no restrictions on the number of connections in HTTP2 (this is cool feature of protocol → try it now). And with...
  5. dimasites

    Feature Request: HTTP-Early-Hints header

    If we started talking about what and how to write in tags, then by this point both Push and Hints have already worked. Fetch priority in html tags — too late feature for our discussion! Waterfalls from my screenshots is formed from real browsers, this is not a simulation! So you can trust the...
  6. dimasites

    Feature Request: HTTP-Early-Hints header

    Ohh... Thank you for an additional explanation that is never superfluous, but I think I understand perfectly how both EH and Push work. And even show it for you (and others) my own rest results (not from manuals or ads): please see new example and screenshot (now from WPT) about parallel...
  7. dimasites

    Feature Request: HTTP-Early-Hints header

    Ok :) Let me give you the confirmations. As I said above, I am not a theorist, and I have used server push with NGINX perfectly in the past (and yes, I used setting cookies to prevent push resending) and I also generated a list of resources for Push on the PHP side (and this was a good fit for...
  8. dimasites

    Web developer. OpenSource contributor in MODX CMS related projects. Web perfomance expert.

    Web developer. OpenSource contributor in MODX CMS related projects. Web perfomance expert.
  9. dimasites

    Feature Request: HTTP-Early-Hints header

    In my opinion (based on tests), the kill feature of Early Hits is that they allow you to provide links to related resources (CSS, Fonts or LCP image etc.) even before the body (html) of the page is loaded. And then they will be loaded in parallel, not sequential! It gives not only downloading...
  10. dimasites

    Feature Request: HTTP-Early-Hints header

    Thanks for answer! At least, on/off will be great, for real... But for get full power of 103 headig, i see two ways (and best together): Server must cache "Link" headings for each uri and return immidiately in 103 response (unlike Server Push when where it was not so important, because Push...
  11. dimasites

    Feature Request: HTTP-Early-Hints header

    Hi @serpent_driver , may be i missed any good news about 103 headers? In many cases use CDN or cache proxy not a best way and we need on-board Early hints soluton! P.S. Why LiteSpeed team cant apply this feature? It's about perfomance, and that is feature, LSWS made for... Apache support this...
  12. dimasites

    Feature Request: HTTP-Early-Hints header

    Of course, i using not only <link rel="preload"... tag, i even send HTTP Header "Link" with list of resources for preload from my backend, because its faster (browser dont need parse html for searching <link> tags), but this is not same compare with early send HTTP 103 code before send 200 code...
  13. dimasites

    Hi, thanks i dont use wordpress, use MODX Revo instead. Good idea with crawler for warming cache!

    Hi, thanks i dont use wordpress, use MODX Revo instead. Good idea with crawler for warming cache!
  14. dimasites

    Feature Request: HTTP-Early-Hints header

    You're right! There were nuances with the Server Push, but now it's in the past (in fact) and now I don't even have the tools to check if I can make a replacement for it. May be 103 header is only hints, but in Chrome dev's blog written about alternatives, and i want to check how chrome actually...
  15. dimasites

    Feature Request: HTTP-Early-Hints header

    Hi, i am not a theoretician. On my projects first page load (and CWV metrics) slowed down now (because Server Push not working). I am not sure how big will the benefits be (but they will), which can give 103 header because i cant use it, and that is problem!
  16. dimasites

    Feature Request: HTTP-Early-Hints header

    Hi all! We're laggards now! Crome remove server push and we lost about 30% page load time! https://developer.chrome.com/blog/removing-push/ we need 103 Early Hints emergency!
Top