4 ms·
It’s a propos that this article took ~10 seconds to load for me the first time, but <1 second the second time and <1 second again with the cache cleared. Unfort
by divbzero 6y ago
It’s a propos that this article took ~10 seconds to load for me the first time, but <1 second the second time and <1 second again with the cache cleared. Unfortunately I didn’t have dev tools open to figure out why.
- randomchars 6y agoProbably 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.
- pjc50 6y agoDNS lookups?