Skip to content

PageSpeed

Speed analysis: Core Web Vitals, performance metrics, recommendations

TL;DR:

Site speed analysis using Google PageSpeed Insights methodology: measures Core Web Vitals — LCP, CLS, INP, FCP, TTFB. Returns a 0-100 performance score (Mobile + Desktop), with improvement opportunities (lazy-loading, compression, minify, image optimization). Includes field data (real-user metrics) from CrUX.

Analysis may take 15–30 seconds (data from Google Lighthouse)

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

Why teams trust us

Lighthouse
analysis engine
CWV
Core Web Vitals
4
Lighthouse categories
Precise
recommendations

How it works

1

Enter page URL

2

Lighthouse analyzes

3

Get CWV scores & tips

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 cancost 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

Who uses this

SEO

Core Web Vitals for rankings

Developers

performance optimization

Marketers

speed = conversions

DevOps

performance regression

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.

Get more with a free account

Speed check history, competitor comparison and PageSpeed monitoring.

Sign up free

PageSpeed Performance Analysis

Analyze website performance using Google PageSpeed Insights API. Get Core Web Vitals metrics (LCP, FID, CLS, INP), performance score, accessibility audit, and actionable optimization recommendations. Test both mobile and desktop versions. Essential for SEO, user experience optimization, and meeting Google ranking requirements.

The speed test analyzes Core Web Vitals (LCP, FID, CLS), total page weight, number of requests, and server response time. Results include actionable recommendations for improving load time, such as image optimization, script deferral, and cache configuration.

Run speed tests from Russia to check performance for CIS audiences. Compare results before and after optimization to measure improvement. For server-side issues, check security headers and DNS configuration. Set up monitoring to track performance over time.

Learn more

Frequently Asked Questions

What is PageSpeed?

PageSpeed is a metric for web page loading performance. It includes Time to First Byte (TTFB), First Contentful Paint (FCP), Largest Contentful Paint (LCP), and other metrics. Fast sites get advantages in SEO and conversion.

What are Core Web Vitals?

Core Web Vitals are three key Google metrics: LCP (speed of main content loading, target < 2.5s), INP (responsiveness to interaction, target < 200ms), CLS (visual stability, target < 0.1). They affect search ranking.

How to improve page load speed?

Key methods: image optimization (WebP, compression), CSS/JS minification, enabling Gzip/Brotli, using a CDN, caching (Cache-Control), lazy loading images, preloading critical resources (preload).

What is LCP, FID, CLS?

LCP (Largest Contentful Paint) is the time to load the largest element. FID (First Input Delay) is the delay of first interaction (replaced by INP). CLS (Cumulative Layout Shift) is the total layout shift during loading.

How does page speed affect SEO?

Google uses Core Web Vitals as a ranking factor. Slow sites lose positions, increase bounce rate, and reduce conversion. According to Google, a 1-second loading delay reduces conversion by 7%.

What is TTFB and how to improve it?

TTFB (Time to First Byte) is the time from sending a request to receiving the first byte of the response. Target: under 800ms. Improve with: fast hosting, server-side caching, CDN, optimizing DB queries, Redis/Memcached.

Why is Gzip/Brotli needed?

Gzip and Brotli are compression algorithms that reduce transferred data size by 60-90%. Brotli is 15-25% more efficient than Gzip for text content. Both are supported by all modern browsers and servers.

Continuous Core Web Vitals monitoring

Track LCP, INP, CLS from real visitors (RUM) — catch regressions before SEO impact.