Page load speed tool: documentation

├── README.md ├── LICENSE.txt ├── pageloadspeed-details.html └── pageloadspeed.html /README.md: -------------------------------------------------------------------------------- 1 | # pageloadspeed 2 | A simple benchmark tool to measure page load speed: . 3 | -------------------------------------------------------------------------------- /LICENSE.txt: -------------------------------------------------------------------------------- 1 | DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE 2 | Version 2, December 2004 3 | 4 | Copyright (C) 2004 Sam Hocevar 5 | 6 | Everyone is permitted to copy and distribute verbatim or modified 7 | copies of this license document, and changing it is allowed as long 8 | as the name is changed. 9 | 10 | DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE 11 | TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 12 | 13 | 0. You just DO WHAT THE FUCK YOU WANT TO. 14 | -------------------------------------------------------------------------------- /pageloadspeed-details.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 12 | Page load speed tool: documentation 13 | 14 | 15 |

Randomly ordered details to mind when benchmarking a page load time:

16 |

The averaged timing is valid if and only if it is labelled valid. 18 |
If comparing two or more blockers: 19 |
- Be sure the benchmarked blocker is the only active extension. 21 |
- To benchmark another blocker, disable the current one, enable the other blocker, then ... 22 |
  - Chromium: open the page load speed tool in a new tab. 24 |
  - Firefox: restart the browser. 25 |
  26 |
- Configure them in a similar way. 27 |
28 |
Clicking the Benchmark button will launch an automated benchmark session which will end when the average page load time is marked as "valid". 29 |
If you want to bypass the browser cache, open de developer console and check the "disable cache when dev console is opened" setting of your browser. 30 |
- Bypassing the cache can lead to more erratic results though, as the measurements become more sensitive to arbitrary network latency. 32 |
33 |
There is a timeout for when a page never completes loading: 30 seconds. 34 |
- The result will be discarded in such case. 36 |
37 |
This page load speed tool works only for web pages which accept to be embedded in a frame. 38 |
Since the web page to measure is inside a frame, it may not rendered correctly if you block 3rd-party cookies (a good idea in general). 39 |
This tool can also be used to compare different configurations for the same blocker. For examples: 40 |
- Adblock Plus with "acceptable ads" enabled versus "acceptable ads" disabled. 42 |
43 |
When you share the results, you should provide all the information: 44 |
- Browser, version, relevant settings (click-to-play, block 3rd-party cookies, etc.) 46 |
- Blocker, version, filter lists, settings. 47 |
- Which URL was benchmarked. 48 |
- Disclose the whole average result of the benchmark, for example: Average (valid): 832.01 ms (10/13 iterations). 49 |
- Etc. 50 |
51 |
Keep in mind uBlock Origin disables pre-fetching by default -- most other blockers do not modify this browser setting. 52 |
- I haven't confirmed so far that this makes a significant difference in page load speed. 54 |
55 |
The page load speed tool is completely self-contained, just look at the page source to see how it works. 56 |
- Being self-contained means you can save a local copy onto your computer and launch from there. 58 |
- There is a prototypical feel to the code, I emphasized on it working, not being elegant. I may work more on it as time allows. 59 |
60 |

61 | 62 | 63 | -------------------------------------------------------------------------------- /pageloadspeed.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 70 | Page load speed tool 71 | 72 | 73 | 86 | 87 | 323 | 324 | 325 | --------------------------------------------------------------------------------