Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

15ms to who? I’ve never had that kind of latency on a cold connection. My pages have an LCP of around 600ms, and it’s hard to push it much lower because even static pages on a CDN end up taking 400ms to connect and download.


15 ms to anyone in the same city or on the same local network in an office setting.

50 ms to anyone in the same country, ideally lower.

Global reach is a different problem because of physics.

However, front pages of web pages tend to be largely static and can be staged in various geo-distributed regions. In other words, distributed via a CDN..

> even static pages on a CDN end up taking 400ms to connect and download.

Only if you stuff them full of megabytes of Javascript and pull down megabytes of JSON in order to display that static content.

The fact that my comment -- a factual statement about real-world performance I've achieved regularly -- is voted down and your off-by-an-order-of-magnitude reply is voted up speaks volumes about the state of the industry.

It's like a bunch of fat people being flabbergasted about the mere concept of mountain climbing. With what... your legs!? Up there!? Madness!


My site is a static page hosted on a CDN with less than 80KB of JavaScript.

If you’re testing local network times, you’re just fooling yourself. None of your visitors are seeing that time, so it’s irrelevant.

What’s your URL? I’d love to throw it into webpagetest.org and take a look.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: