Start with request count and resource weight
Large scripts, oversized images, heavy fonts, and third-party tags often explain why a page feels crowded before you run a broader lab test.
Performance workflow · HAR evidence
Analyze HAR request waterfalls without rerunning the page
Import a real browser network export to review request count, transfer size, resource mix, third-party origins, response errors, redirects, compression evidence, HTTP protocol labels, cache lifetimes, and slow wait phases.
HAR ENTRIES5,000 RETAINEDINPUT15 MiBLIVE TESTNOT RUN
HAR
Ready for a real request waterfall.
No sample waterfall, synthetic request count, Core Web Vitals result, Lighthouse score, cache grade, or ranking claim appears before you supply a HAR file.
Performance review workflow
Turn browser network evidence into a practical cleanup list
Separate delivery policy from page design
Cache-Control, protocol, compression, and redirects are server or CDN evidence. Keep those findings distinct from content, layout, and search-result changes.
Confirm changes after deployment
Use the header checker, resource inspector, PageSpeed report, and fresh HAR exports after each release so the request ledger stays tied to what actually shipped.
Inspect declared resourcesCheck live headersRun PageSpeed evidenceMinify source assets