Page Load Timing — The Waterfall Behind Your Score
This loads a page in a real browser and records every request that results — scripts, stylesheets, fonts, images, third-party calls — each with its own timing. A score out of a hundred tells you there is a problem. The waterfall tells you which resource is causing it, which is the only form of the information you can act on.
When it helps
Because the answer is nearly always specific and nearly always surprising. A font loading late and blocking text. A hero image several times larger than the space it occupies. Two versions of the same library, because a dependency bundled its own. A tag manager that has quietly grown to a dozen scripts, each added by someone who reasonably assumed one more would not matter. None of these are visible in the source; all of them are obvious in a waterfall.
Worth running automatically
Page weight only ever grows, and it grows one defensible decision at a time. Nobody ships a change that makes the site twice as slow; twenty people ship changes that each make it two percent slower. Capturing the waterfall on every deploy and diffing it turns "the site feels slower than it used to" — a claim nobody can act on — into a named resource that appeared or grew on a specific date, which is a conversation with an obvious next step.
What you get out of it
Converts a performance score into a list of specific things to change. Run per deploy, it attributes a regression to the change that caused it while that is still cheap to reverse.