5 ms·
On my first load of this page, it took 4.85 seconds to get meaningful content and the whole page took 8.09s. The vast majority of the delay seems to be from ass
by Shank 6mo ago
On my first load of this page, it took 4.85 seconds to get meaningful content and the whole page took 8.09s. The vast majority of the delay seems to be from assets like the PNG images and the fonts, which don't seem to be on a CDN. I am located in Tokyo, Japan, with a 1Gbps symmetric connection, so while I am regionally quite distant from the site, I assume, I still think there are ample CDNs available that would speed this up.
- 6031769 6mo agoLucky you. Blog.js fails for me with a TypeError and I'm disinclined to debug someone else's javascript on a whim, so I don't get to see any of the content at all. To the OP: JS is for enhancements. If you are using it in such a way that it becomes a potential blocker for all of the content then you are not going to reach the audience that you otherwise would. If you are on somebody else's platform/framework then by all means pass this up the chain.
- taspeotis 6mo agoMobile is particularly bad https://pagespeed.web.dev/analysis/https-lubeno-dev-blog-reinventing-the-pull-request/12a9907gmb?form_factor=mobile https://pagespeed.web.dev/analysis/https-lubeno-dev-blog-rei...
- bkolobara 6mo agoSorry about that! Performance is really important to me, I just didn't get around to configuring CDN caching and optimizing the assets. All the HN traffic hitting our server also didn't help.
- widdershins 6mo agoI signed up and I'm finding browsing a repo quite snappy. Good job.