SiteAuditLab
Free tool · No sign-up required

Free Website Performance Test

Check Core Web Vitals and page speed instantly

Test any URL for Core Web Vitals, TTFB, compression, caching, CDN usage, and render-blocking resources. Get a performance grade with actionable recommendations.

Results in ~10 seconds · Sign up free to save history & set up monitoring

This tool uses the same scanner as the full SiteAuditLab audit — pre-filtered to this category. Run a full scan to see Security, Performance, SEO, Accessibility, Privacy & more together.

What gets checked

Core Web Vitals (LCP, FID/INP, CLS) from Chrome UX Report
Time to First Byte (TTFB)
Gzip / Brotli compression detection
Browser caching headers (Cache-Control, ETag)
CDN presence (Cloudflare, Fastly, CloudFront, etc.)
Render-blocking scripts and stylesheets
HTTP/2 or HTTP/3 protocol usage
Redirect chain length
Response size analysis
Image optimization signals
DNS resolution time
SSL handshake overhead

Frequently asked questions

What are Core Web Vitals?

Core Web Vitals are Google's official page experience metrics: Largest Contentful Paint (LCP) measures loading performance, First Input Delay / Interaction to Next Paint (FID/INP) measures interactivity, and Cumulative Layout Shift (CLS) measures visual stability. Good thresholds are LCP < 2.5s, INP < 200ms, CLS < 0.1. These metrics are a Google ranking factor.

How do I improve my website speed?

The highest-impact improvements are: enable Brotli compression (saves 15–20% over gzip), add a CDN to reduce TTFB globally, set proper Cache-Control headers for static assets, remove render-blocking scripts with async/defer, and optimise images with WebP/AVIF and lazy loading.

What is TTFB and why does it matter?

Time to First Byte (TTFB) is how long the browser waits before receiving the first byte of page content. A high TTFB (>800ms) indicates server slowness, poor hosting, or lack of caching. Google considers TTFB as part of Core Web Vitals. A good TTFB is under 200ms.

Does this test from multiple locations?

The performance data comes from the Chrome User Experience Report (CrUX), which aggregates real user measurements from Chrome users worldwide. This gives you actual field data rather than synthetic lab tests.

How often should I test performance?

After every significant deployment and at least weekly in production. Performance can degrade silently when adding new third-party scripts or after infrastructure changes. Use our scheduled audit feature to automate this.

Want history, scheduled audits, and uptime monitoring?

Sign up free — no credit card