|
|
|
|
|
by bialpio
3651 days ago
|
|
> Server sends an HTML and browser fetches what it needs. Not fetching content is simply an advanced form of caching. I didn't understand this part. Caching is basically "not fetching content that you already have", and I don't see how it is relevant here. I assume that when using adblocks the browser will not even issue a request to fetch the data (be it HTML, JavaScript, flash videos, images, etc.) that is ad-related, so it is not the same as caching. And even if it did choose to fetch the data but then skip rendering, it boils down to the same thing: browser engine has different (presumably smaller) input in case when you use adblock. By telnetting I will get a response, but this is only a first step. HTML will have references to huge amount of other content that also needs to be fetched (unless everything is embedded in the HTML - possible, but unlikely for any bigger website). Open developer tools in any browser and go to network tab and see for yourself how the amount of fetched data (and number of requests / number of fetched files) differs when you use adblock and not. This is the difference in the input for the browser. Opera mentions mlive.com - with uBlock, FF fetches 2.5MB of data (caching disabled), without uBlock I get 5MB (caching disabled). We can even take the example to the extreme - let's go to the website that has only ads. Of course Opera will be better there - it will have to render nothing, everything will be blocked by adblock. |
|
As to downloading you can try it you self your talking fractions of a watt savings from not downloading a few Meg's.
In terms of other downloads from a page, most of that is things like tiny images which you can mostly skip. The Amazon homepage sends lots of junk but all you actually care about is the search bar and links to other areas.