4 ms·
Because there's no way to measure when the page is "usable", and the load event firing is a good enough measurement of the worst case.
by jlarocco 11y ago
Because there's no way to measure when the page is "usable", and the load event firing is a good enough measurement of the worst case.
- emn13 11y agoIt's not a good enough measurement - it's a ridiculously poor measurement. You're trying to measure how fast an adblocker is by measuring how long it takes... to load the ads. How is that in any way helpful? If anything, the proper, comparable load time for the adblocked version is infinite - they never complete loading the ads. If you're going to run this comparison, you need to at least compare the same set of resources being loaded - after all, if you're willing to omit ads entirely, you clearly don't care how long it takes for them to load. We don't need a perfect measurement, but this measurement is extremely biased. DOMContentLoaded would be better, but still far from good - you want to measure the load time of the resources the adblocker would not have blocked.
- jlarocco 11y agoKnowing the time saved by removing the ads is a useful number to know, IMO. I'm willing to give the benchmarker the benefit of the doubt that he used the same block lists for each blocker, although spelling it out would have been a good idea.