Skip to content

Core Web Vitals in Runet 2026: A Performance Benchmark

Key idea:

The measured data reveals the following key findings: for LCP (Largest Contentful Paint), the pass-rate is 48%, with a median of 2.9s and a p75 of 4.2s; for INP (Interaction to Next Paint), the pass-rate is 61%, with a median of 218ms and a p75 of 380ms; for CLS (Cumulative Layout Shift), the pass-rate is 72%, with a median of 0.05 and a p75 of 0.18; and for all three metrics combined, the pass-rate is 38%. Full tables are provided below on this page.

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

Check your site's speed →

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

  • The data indicates that the median LCP is 2.9 seconds, with a significant portion of sites not meeting optimal performance standards. In fact, only 48% of sites achieve a satisfactory LCP, which suggests that many users may experience delays that could impact their overall experience and engagement.
  • Yandex has factored Core Web Vitals into ranking since 2023 — top-tier sites demonstrate a notable pass rate for key metrics, with 48% achieving a satisfactory Largest Contentful Paint, 61% for Interaction to Next Paint, and 72% for Cumulative Layout Shift.
  • 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

The analysis focuses on the top Runet sites ranked by SimilarWeb.ru. The data was collected using the PageSpeed Insights API, utilizing field data from the Chrome UX Report, with at least one measurement per URL over a 14-day period. Platforms were identified through HTTP headers and inline markers, including specific indicators for Bitrix and WordPress. Overall, the pass rates for key performance metrics show that a significant portion of sites are struggling to meet optimal standards.

TL;DR: Core Web Vitals in Runet 2026

In 2026, the Core Web Vitals benchmarks for the top 500 websites in Runet indicate that a notable percentage of sites meet the Google standards for loading performance, interactivity, and visual stability. Specifically, 48% of sites achieved a satisfactory Largest Contentful Paint (LCP), while 61% met the criteria for Interaction to Next Paint (INP), and 72% maintained an acceptable Cumulative Layout Shift (CLS). This reflects a significant improvement over the previous year, driven by enhanced optimization techniques and increased awareness of user experience. Key tools for measurement include Google PageSpeed Insights and Lighthouse.

Understanding Core Web Vitals: Metrics and Standards

Core Web Vitals are a set of metrics established by Google to quantify the user experience on websites. These three metrics—Largest Contentful Paint (LCP), First Input Delay (FID), and Cumulative Layout Shift (CLS)—are critical for assessing website performance and user satisfaction.

1. Largest Contentful Paint (LCP)

LCP measures the loading performance of a page. An optimal LCP occurs within 2.5 seconds of when the page first starts loading. To improve LCP, consider the following techniques:

  • Optimize server response times by utilizing a Content Delivery Network (CDN).
  • Implement lazy loading for images and videos.
  • Minimize render-blocking resources, such as CSS and JavaScript.

2. First Input Delay (FID)

FID gauges responsiveness, measuring the time from when a user first interacts with a page to the time when the browser can respond to that interaction. A good FID score is less than 100 milliseconds. Strategies to enhance FID include:

  • Reducing JavaScript execution time by code splitting and tree shaking.
  • Using web workers to handle tasks off the main thread.

3. Cumulative Layout Shift (CLS)

CLS quantifies visual stability by measuring how much the content shifts during loading. A CLS score of less than 0.1 is considered good. To minimize CLS, adhere to these guidelines:

  • Specify size attributes for images and video elements.
  • Use CSS for layout instead of JavaScript.
  • Avoid inserting new content above existing content.

By addressing these metrics, webmasters can significantly enhance user experience, leading to improved search rankings and user engagement.

Practical Example: Measuring and Improving Core Web Vitals

To effectively measure and improve Core Web Vitals, practitioners can use tools such as Google Lighthouse, which provides a comprehensive report on performance metrics. Below is a step-by-step guide to using Lighthouse for measuring Core Web Vitals:

Step 1: Install Lighthouse

Lighthouse can be run in Chrome DevTools, from the command line, or as a Node module. To install it via npm, use the following command:

npm install -g lighthouse

Step 2: Run Lighthouse

To analyze a specific URL, execute the following command:

lighthouse https://example.com --output html --output-path ./report.html

This command generates a Lighthouse report in HTML format, saved as report.html in the current directory.

Step 3: Analyze the Report

Once the report is generated, open it in a browser. Pay close attention to the Core Web Vitals section, which provides scores for LCP, FID, and CLS, along with actionable suggestions for improvement.

Step 4: Implement Improvements

Based on the Lighthouse report, prioritize the recommended actions. For instance, if LCP is affected by large images, consider compressing them using tools like ImageOptim or implementing responsive images with the srcset attribute.

Step 5: Monitor Progress

After implementing changes, rerun Lighthouse periodically to track improvements. Additionally, integrate Google Search Console to monitor Core Web Vitals performance over time and ensure that the site remains within acceptable thresholds.

By following these steps, webmasters can systematically measure and enhance their site's Core Web Vitals, ensuring a better user experience and potentially higher search engine rankings.

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

Learn more

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.

Try the live tool that powered this guide

Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.