Live data from Hacker News

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

itnext.io

71–80 of 124 posts

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

#71

Seems like jQuery is a big cause of slowdowns - anybody have suggestions for how to provide similar functionality without it?

Have a local instance of it [1] to keep the functionality.

[1] - https://addons.mozilla.org/en-US/firefox/addon/localcdn-fork...

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

#72
post #53
post #17

Earlier quoted context omitted.

fwiw there's almost nothing on the dom in this article. I'm quite tired of the hot air pointless uneducated uninformed web bashing. I don't know why the web attracts such angry angry people but for all the complaining the grandparent post is about as real of a counter-idea to the dom as I have ever seen. what we do with the web is often bad. fully agreed there are terrible experiences everywhere. but starting fresh,…

I'd be interested in some people expanding on what they think is so "wrong" with the DOM, especially from the point of view of performance, and (emphasis on this!) what would be so much better. It's not that different than any other widget toolkit anymore, which have all largely converged on the same sort of model for the same reasons. I can't think of very many things that affect performance in big ways. An explicit…

It's not so much there being something "wrong" with it, it's more that there are trade-offs. Look, for example, at https://tc39.es/ecma262 (the JS spec) and try to jump around the page: you'll notice that it takes quite a bit of time for some things to render simply because the document is absolutely humongous. BUT, once it does load completely, you can insta-search it with ctrl+f, it reflows/wraps correctly in a mobile browser and and if you throw your iphone's accessibility feature at it, it'll read the document for you. Being able to google the thing in the first place is also due to ability to programmatically crawl the document and analyze its contents. These are important features that are usually forgotten by the people proposing that everything should be a thin bitmap buffer on top of raw hardware.

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

#73
>If we were to believe this, we would conclude that moving requested resources from HTTP 1.1 to 2 gives a 1.8x speed-up, while going from HTTP 2 to 3 causes 0.6x slow down. Is it really true that HTTP 3 is a slower protocol? No: A more likely explanation is that HTTP 3 is rare, and that the few resources that are being sent over HTTP 3 (e.g. Google Analytics) are things that have a larger than average effect on dominteractive.

If you wanted to measure the effect of protocol, you could compare requesting with support HTTP/N to requesting with support for HTTP/N+1. Since this is all synthetic testing it shouldn't be too hard to run a controlled experiment instead of a correlational one.

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

#75
post #57
post #25

Earlier quoted context omitted.

I spend a lot of time on Youtube, and their recommendations are addictive, so I blocked the sidebar that recommends next videos. I block scripts on news sites since they serve no purpose.It removes things like popups, autoplaying videos and comments. And I have so many custom filters set up to block cookie prompts, annoyances and other stuff.

> I block scripts on news sites since they serve no purpose https://outline.com/ is also fantastic for this purpose.

Never works for me. Tried with dozens of links and multiple browsers.

Plus paywalls aren't really a problem. 2/3 clicks and they're gone

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

#76
post #31
post #4

Use an adblocker. I save about 25 gigs and hours of my time every month. * https://www.ublockorigin.com * I block much more than ads.

If you can afford it, I'd suggest switching to AdNauseam ( https://adnauseam.io ). They're using the same uBlock Origin engine, but ads are downloaded and clicked on in the background. This way you still generate revenue for site owners. But since this extension is banned from the Chrome Web Store, you'll have to install it manually there. On Firefox it's available from their add-on store.

I specifically choose not to use this. Do not use forks of uBlock Origin. They might sell anytime. It has happened before, it will happen again.

Plus I do not like ad fraud. I get lots of captchas. I also don't wanna give money to Google and Facebook.

If uBO sells out (I don't think gorhill will, but I don't know him) it'll be the top link on HN

https://www.lowyat.net/2020/224264/chromium-versions-nano-ad...

https://arstechnica.com/information-technology/2020/10/popul...

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

#78
post #31
post #4

Use an adblocker. I save about 25 gigs and hours of my time every month. * https://www.ublockorigin.com * I block much more than ads.

If you can afford it, I'd suggest switching to AdNauseam ( https://adnauseam.io ). They're using the same uBlock Origin engine, but ads are downloaded and clicked on in the background. This way you still generate revenue for site owners. But since this extension is banned from the Chrome Web Store, you'll have to install it manually there. On Firefox it's available from their add-on store.

This is based on a misunderstanding of how ads work and does harm.

If this silently clicks ads in the background the click rate goes up but the goal action (buying, signing up) remains at 0 which smartprices the ads and tanks the value of the ads for the real clickthroughs.

If you must block ads just use uBlock Origin so you are treated like your visit doesn't exist.

A deeper question is it moral to consume content and block the ads. Wouldn't that be the same as pirating a movie? (not that there is anything wrong with pirating). Are there people who would block ads and complain about people pirating, or even stealing from a store if you can get away with it.

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

#79
post #27

It seems web performance is one of the least understood topics, even for engineers. Unfortunately even this author makes the mistake of confusing DOM Interactive[0] with Time to Interactive[1]. And yet this is a better analysis than what I often see repeated backed with no evidence. For example, the myths about page weight and big SPA JS websites being the source of web performance issues is one I see so frequently h…

> the problem isn't page weight or JS frameworks, it's network latency[3].

if that was the case electron apps with content available locally would not be so slow

Post reply on HN