Skip to content
Pricing RU Sign In
RU

Core Web Vitals in Runet 2026: A Performance Benchmark

By · Updated
Key idea:

Enterno.io measured Core Web Vitals for the 500 most-visited Runet sites (Yandex Metrica + SimilarWeb rankings) in March 2026. Results: only 38% pass all three thresholds (LCP ≤2.5s, INP ≤200ms, CLS ≤0.1). Median LCP = 2.9s (200ms worse than 2025), INP = 218ms (Google replaced FID in March 2024). Worst — e-commerce on 1С-Bitrix (52% fail), best — SPAs on Next.js (67% pass).

Below: key findings, platform breakdown, implications, methodology, FAQ.

Try it now — free →

Key Findings

MetricPass-rate / ValueMedianp75
LCP (Largest Contentful Paint)48%2.9s4.2s
INP (Interaction to Next Paint)61%218ms380ms
CLS (Cumulative Layout Shift)72%0.050.18
All three (good)38%——

Breakdown by Platform

PlatformSharePass / Detailavg LCP
1С-Bitrix31%28%3.6s
WordPress18%34%3.2s
Next.js/React SPA12%67%2.1s
Tilda/Wix/no-code9%42%2.8s
Custom / unknown30%39%2.9s

Why It Matters

  • Every extra second of LCP cuts conversion by 7% (Google/SOASTA 2017)
  • Yandex has factored CWV into ranking since 2023 — top-tier sites gain +11% visibility
  • INP (FID's replacement) reflects real click/tap latency — a pain point for SPAs with heavy state
  • Mobile results are ~2× worse than desktop — mobile LCP median = 3.8s

Methodology

Top 500 Runet sites by SimilarWeb.ru ranking (March 2026). Measurements via the PageSpeed Insights API (Field Data from the Chrome UX Report), at least one reading per URL across 14 days. Platforms detected by HTTP headers and inline markers (Bitrix: X-Powered-By-Site; WP: wp-content/wp-includes).

Related guides

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

Related tools

Security CheckHealth ScoreBroken LinksRobots.txt

Learn more

How-to

Glossary

Research

Alternatives

Frequently Asked Questions

Where does the platform data come from?

From response HTTP headers and HTML signatures: Bitrix emits X-Powered-By-Site, WordPress exposes /wp-content/ in asset URLs, Next.js exposes /_next/ and __NEXT_DATA__. Auto-detect confidence 89%; remainder is manually verified.

Why does 1С-Bitrix lag on CWV?

A typical Bitrix site ships 20+ scripts via core.js, jQuery, heavy widgets (amCharts/Kendo), composite cache without an edge CDN. On cheap shared hosting TTFB is often ≥600ms — already fails LCP.

Next.js at 67% pass — why not 90%?

The SPA pattern wins on INP and CLS but often loses LCP on hero images (crop, lazy-load). Next.js 15 with the app router improved SSR — migration is slow though.

How do I check my own CWV?

<a href="/en/speed">Enterno PageSpeed Checker</a> — shows field data + lab data, mobile/desktop separately. Free.

Start monitoring for free

Sign up and get access to API, monitoring and notifications

Create Account API Documentation