3 ms·
Probably service workers. If the site has a service worker the traditional cache-busting hard refresh is just a normal refresh.
by randomchars 6y ago
Probably service workers. If the site has a service worker the traditional cache-busting hard refresh is just a normal refresh.
- divbzero 6y agoThat’s an interesting theory. I checked though and didn’t find service workers on this page [1] so it could just be something with the server itself. I caught another slower load just now and server timing showed a long wait for the first byte. [1]: https://devdocs.io/dom/serviceworkercontainer/getregistrations https://devdocs.io/dom/serviceworkercontainer/getregistratio... "navigator.serviceWorkers.getRegistrations()"
- SquareWheel 6y agoTTFB includes DNS lookup, server generation of the page, and actual sending of the data. I'd guess it's one of the first two at fault.