Free tool guide
Free Site Speed Test
Measure loading and interaction signals, then connect slow metrics to the resources causing them. The test combines Core Web Vitals with practical diagnostics for images, scripts, fonts, caching, and server response.
How to read the report
Start with the signals that change your next decision.
- Core Web Vitals: read LCP, INP, and CLS separately because each points to a different user-experience problem.
- Lab diagnostics: use resource timing and recommendations to locate likely causes, not just the score.
- Device context: prioritize mobile results and verify important fixes on real pages and repeat visits.
When to use it
It is most useful in these situations.
- Before and after a release, redesign, or third-party script change.
- When mobile conversion, engagement, or rankings decline.
- Creating a measurable performance backlog for developers.
Common questions
What people ask before they act on the report.
What are good Core Web Vitals targets?
Aim for LCP within 2.5 seconds, INP within 200 milliseconds, and CLS at or below 0.1 at the 75th percentile.
Why does the speed score change between tests?
Network, server load, cache state, device simulation, ads, and third-party scripts vary. Run several tests and look for repeated bottlenecks.
Should I optimize the score or the metric?
Optimize the user-facing metrics and their causes. A perfect headline score is less important than stable, fast behavior for real visitors.
Unlock premium features for better results
Remove the daily limit, export your results and start risk-free.
- Unlimited daily scans
- 40+ SEO & content tools
7-day free trial · cancel anytime