For teams with a performance budget
Catch the deploy that doubled the page weight
Get a page's resources with their sizes and lab load metrics from one capture, and compare them across deploys.
The problem
Nobody decided to make the home page twice as heavy. A hero video went in uncompressed, a new tag brought its own copy of a framework, and a font family arrived in nine weights. Each change was reasonable; together they make a slower page, and nobody can say which deploy did it.
How domscout handles it
diagnostics lists every resource the page loaded with its type and transfer size, and analysis.diagnostics.summary.transferBytes adds them up. Browsers report the size of a resource from another origin only when its server allows it, so treat the total as a floor. performanceOverlay measures first contentful paint, largest contentful paint, cumulative layout shift and time to first byte, returns them in performanceMetrics and draws them onto the screenshot. Record both on every deploy and a jump has a date and a list of suspects. These are lab numbers from one load in one place, good for spotting a change, not a substitute for what real visitors experience.
Where it shows up
- A CI step that fails when a page's resources cross a budget.
- A weekly record of the heaviest resources on key pages.
- Before and after numbers for an image or font optimisation.
The request
POST /screenshot. performanceOverlay works on every plan at 1 credit. diagnostics, for the resource list, starts at Pro and brings the request to 2 credits.
Go further
More in SEO and site health: SEO regression checks · Link preview checks · Find every page on a site · Website migration checks · JavaScript SEO checks · Backlink checks · JSON-LD structured data checks · hreflang checks · Website audits for prospects · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.