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.
Free online tool — page speed test: instant results, no signup.
| Metric | Pass-rate / Value | Median | p75 |
|---|---|---|---|
| LCP (Largest Contentful Paint) | 48% | 2.9s | 4.2s |
| INP (Interaction to Next Paint) | 61% | 218ms | 380ms |
| CLS (Cumulative Layout Shift) | 72% | 0.05 | 0.18 |
| All three (good) | 38% | — | — |
| Platform | Share | Pass / Detail | avg LCP |
|---|---|---|---|
| 1С-Bitrix | 31% | 28% | 3.6s |
| WordPress | 18% | 34% | 3.2s |
| Next.js/React SPA | 12% | 67% | 2.1s |
| Tilda/Wix/no-code | 9% | 42% | 2.8s |
| Custom / unknown | 30% | 39% | 2.9s |
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.
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.
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.
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:
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:
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:
By addressing these metrics, webmasters can significantly enhance user experience, leading to improved search rankings and user engagement.
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:
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 lighthouseTo analyze a specific URL, execute the following command:
lighthouse https://example.com --output html --output-path ./report.htmlThis command generates a Lighthouse report in HTML format, saved as report.html in the current directory.
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.
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.
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.
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.
Google Lighthouse-based analysis: Performance, Accessibility, Best Practices, SEO.
LCP (rendering), FID (interactivity), CLS (visual stability) — key Google metrics.
Breakdown by type: HTML, CSS, JavaScript, images, fonts. Size, request count, blocking resources.
Specific recommendations with savings estimates: image compression, caching, minification, etc.
Core Web Vitals for rankings
performance optimization
speed = conversions
performance regression
async/defer block rendering. Move to end or add attribute.Cache-Control, the browser reloads CSS/JS on every visit.loading="lazy" for images below the fold.brotli on;Cache-Control: max-age=31536000, immutable. HTML: max-age=0, s-maxage=60.<link rel="preload"> for fonts and CSS. Reduces LCP by 200-500ms.Speed check history, competitor comparison and PageSpeed monitoring.
Sign up freeFrom 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.
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.
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.
<a href="/en/speed">Enterno PageSpeed Checker</a> — shows field data + lab data, mobile/desktop separately. Free.
Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.