WEB PERFORMANCE · LIGHTHOUSE EVIDENCE
Page Weight & Asset Bloat Audit
Find where one page spends its transferred bytes. Review HTML, scripts, stylesheets, images, fonts and the largest measured resources without treating file counts as page weight.
Automatic measurements: setup required
The public page is available, but measurements are not connected. The anonymous Google PageSpeed quota was unavailable during preparation. The administrator can configure a PageSpeed Insights API key under Web Performance → Page Weight Audit, or explicitly enable anonymous attempts.
No measurement is fabricated and no payment is required by this plugin. A successful provider lookup must still be verified.
How to read the report
Transfer bytes and resource bytes are separate fields, not numbers to add together. Totals may exclude unknown requests; cache and incomplete records matter. Summary totals and third-party summaries overlap the resource categories.
Review flags use adjustable thresholds. They are a starting point for checking resource purpose and delivery—not proof of wasted code, a speed score or a reason to delete files automatically.
Questions and limits
Is this an HTML file counter?
No. Automatic checks request a remote Lighthouse navigation from Google PageSpeed Insights. Only returned network and resource measurements are used; markup references are not counted as downloaded bytes.
Why does the page say setup required?
The anonymous Google quota was unavailable when this tool was prepared. The site administrator can add a PageSpeed Insights API key or explicitly enable anonymous attempts. A stored key alone does not prove quota or successful source access.
Does a large file prove asset bloat?
No. Review flags compare observed byte counts with configurable thresholds. They do not measure unused code, business necessity, execution time or causal slowdown. Review a resource before removing it.
What can a single run miss?
Later interactions, scroll-triggered assets, logged-in content and different consent states can change requests. Cached, incomplete and missing evidence stays visible. This is not a whole-site or real-user measurement.
What is sent or stored?
The submitted public URL and strategy are sent to Google. This module does not retain the raw report or report history. Downloads are generated in your browser; paths can still contain personal information, so review them before sharing.
Measurement engine: open-source Lighthouse through the PageSpeed Insights API. No Lighthouse source is bundled or executed on WordPress.