Live data from Hacker News

We rendered a million web pages to find out what makes the web slow

itnext.io

61–70 of 124 posts

Re: We rendered a million web pages to find out what makes the web slow

#61
post #19

I can guess without reading: 1 ads 2 client side rendering. Youtube nowadays is 400-1000 kilobytes of Json + ~!8! megabyte of javascript(1). Pre Polymer (YT client side rendering engine update) you would receive 50KB of pre rendered pure HTML that would display instantly. Nowadays scrolling comments results in seeing them appear one by one while browser struggles with constant DOM updates. 1) >7MB desktop_polymer_inl…

> I can guess without reading:

Can you not.

Re: We rendered a million web pages to find out what makes the web slow

#63
Pages with rocket-lazy-load are generally faster.

AFAIK Rocket is a Rust framework and my guess is that the average Rust dev cares more about perf. Which would imply that perf could be more about mindset than technology.

But that's just my humble interpretation...

Re: We rendered a million web pages to find out what makes the web slow

#64

Earlier quoted context omitted.

And you'd be wrong. SPA frameworks are almost entirely absent from this list. HN discourse would have you think single-page apps are pervasive, but they're only on a tiny fraction of websites: https://css-tricks.com/how-the-web-is-really-built/

Given that most public-facing websites want to benefit from SEO, it doesn't make sense to build a SPA for those websites. I'd bet the majority of developers working on SPAs are doing so for internal dashboards/tools.

You can render SPAs before the page loads, which eliminate any potential issues with SEO. This is how it should be done and the approach frameworks like Next.js take.

Re: We rendered a million web pages to find out what makes the web slow

#67
post #63

Pages with rocket-lazy-load are generally faster. AFAIK Rocket is a Rust framework and my guess is that the average Rust dev cares more about perf. Which would imply that perf could be more about mindset than technology. But that's just my humble interpretation...

It is the name of a Rust web framework, but this is referring to a Wordpress plugin.

(Also, the Rust Rocket is not primarily focused on perf, but developer ergonomics.)

Re: We rendered a million web pages to find out what makes the web slow

#68
post #34
post #30

Earlier quoted context omitted.

uBlock is what's keeping me from switching to Safari (which is so much nicer to use on a Mac) It seems like most people who use Safari use full system-level ad blockers like Wipr. But I was also Googling around and found some complaints about Wipr, like it taking forever to be updated to block YouTube ads when they switch how they're displayed, or not being as good at getting around ad-block detection on certain site…

I've recently switched to macOS and Safari with Wipr. I don't see much difference to my Firefox setup with AdNauseam (uBlock Origin) before. More on the contrary - my selected lists were very aggressive and I had various sites where I had to disable uBlock to see them properly. With Safari and Wipr, everything seems to just work.

> I don't see much difference to my Firefox setup with AdNauseam (uBlock Origin)

AdNauseam is not uBlock Origin, you can not use AdNauseam's results to judge uBlock Origin.

Re: We rendered a million web pages to find out what makes the web slow

#70
post #32

https://catchjs.com/Blog/PerformanceInTheWild — actual link to the people that did the study. Itnext.io just ripped it off with a small credit at the bottom.

That is not what "originally published at" means. The author is providing the canonical home of his own article.
Post reply on HN