← All guides
Performance budgets: thresholds, not impressions
Request count, document weight, JavaScript and CSS volume, third-party domains. Hard numbers, compared against explicit thresholds.
- Weight in the score
- 2/100
- checks in this category
- 11
Why it matters
A performance budget turns a vague sense of heaviness into a number above or below a limit. That is what lets you catch a regression before a visitor feels it, and discuss a third-party integration on facts rather than impressions.
The checks that run
The list below is the audit's own, generated from its catalogue — it follows the product rather than describing it from memory.
- Reasonable number of resource hints (preconnect/preload)
- Number of iframes within budget
- Number of images within budget
- Number of third-party domains within budget
- Number of JavaScript files within budget
- Number of fonts within budget
- Number of network requests within budget
- Inline CSS weight within budget
- HTML document size within budget
- Inline JavaScript weight within budget
- Transferred document size within budget
Check your site against these
A free scan runs these checks and those of the other 10 categories, and returns the detail of every failure with its fix.
Scan my site for freeOther categories
- Website security: what an audit actually checks
- Website performance: what an audit really measures
- Technical SEO audit: the foundations before the keywords
- Content quality: readability, structure and intent
- Design and accessibility: what can be measured objectively
- Visibility to generative AI (GEO)
- Tech stack: what your infrastructure gives away
- Business information: what a visitor looks for and cannot find
- Mobile friendliness: beyond responsive layout
- Web analytics: knowing what happens on your site