Skip to content
Skip to content

Website Speed Test — Core Web Vitals

Measure your website's loading speed and get Core Web Vitals scores. We analyze LCP, CLS, TTFB, FCP and provide actionable optimization tips.

What we measure

  • LCP — Largest Contentful Paint
  • CLS — Cumulative Layout Shift
  • TTFB — Time to First Byte
  • FCP — First Contentful Paint

Why speed matters

Google uses Core Web Vitals as a ranking factor. A slow site loses search rankings and conversions.

PerformanceOverall speed score 0-100
📈
Core Web VitalsLCP, FID, CLS — Google metrics
📦
Page SizeSize of HTML, CSS, JS, images
🚀
RecommendationsSpecific tips for improvement

Why Does Site Speed Matter?

Page load speed directly impacts conversion, SEO rankings, and user satisfaction. Google uses Core Web Vitals as a ranking factor. Every extra second of load time can cost up to 7% in conversions.

📊

Lighthouse Analysis

Google Lighthouse-based analysis: Performance, Accessibility, Best Practices, SEO.

📈

Core Web Vitals

LCP (rendering), FID (interactivity), CLS (visual stability) — key Google metrics.

📦

Resource Analysis

Breakdown by type: HTML, CSS, JavaScript, images, fonts. Size, request count, blocking resources.

💡

Actionable Advice

Specific recommendations with savings estimates: image compression, caching, minification, etc.

Mobile vs Desktop

Mobile
  • Tested on Moto G Power emulation (slow CPU)
  • Network: 4G (1.6 Mbps, 150ms RTT)
  • Stricter speed scoring
  • Google indexes mobile-first
  • Priority for SEO optimization
Desktop
  • High CPU performance
  • Fast connection without throttling
  • Scores typically 20-40 points higher
  • Important for B2B and corporate sites
  • Use for baseline comparisons

Common Mistakes

Unoptimized imagesImages can be up to 70% of page weight. Use WebP/AVIF and lazy loading.
Render-blocking JS in <head>Scripts without async/defer block rendering. Move to end or add attribute.
No static asset cachingWithout Cache-Control, the browser reloads CSS/JS on every visit.
Too many HTTP requestsEach request adds latency. Bundle files, use sprites, or inline critical CSS.
Missing compression (gzip/brotli)Compression reduces text resource size by 60-80%. Enable brotli on the server.

Best Practices

Optimize imagesWebP for photos, SVG for icons. loading="lazy" for images below the fold.
Enable brotli compressionBrotli is 15-20% more efficient than gzip. Configure in nginx: brotli on;
Set up cachingStatic: Cache-Control: max-age=31536000, immutable. HTML: max-age=0, s-maxage=60.
Preload critical resources<link rel="preload"> for fonts and CSS. Reduces LCP by 200-500ms.
Test regularlySpeed degrades over time. Check after each deploy and monthly.

Frequently Asked Questions

How to improve LCP?

Optimize images (WebP, lazy loading), use a CDN, minimize CSS/JS, enable server caching.

Is the speed test free?

Yes, completely free.