Website Performance Benchmark 2026: How Does Your Site Compare?

The Three Core Web Vitals in Benchmark

Google evaluates websites based on three metrics: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). Each metric has a clearly defined threshold, and only when all three are met simultaneously does the page pass. The assessment is based on the 75th percentile of field data from the Chrome User Experience Report (CrUX), meaning the actual experiences of real users (Google).

Below we examine the current benchmark data based on evaluations from HTTP Archive, CrUX, and XICTRAQ's own measurement data. Values refer to median values of German websites unless otherwise noted.

LCP: Largest Contentful Paint Compared

LCP measures how long it takes until the largest visible content element in the viewport is rendered. The threshold is 2.5 seconds. The German average stands at 3.2 seconds, clearly above the threshold. The best 10% of websites achieve LCP values of 1.4 seconds or less (HTTP Archive).

The main causes of poor LCP values in Germany are oversized hero images without modern formats like WebP or AVIF, missing server-side caches in WordPress installations, slow shared hosting infrastructures with high TTFB, and render-blocking CSS and JavaScript resources. WordPress websites in particular, which account for about 40% of the German market (W3Techs), score below average on LCP when no targeted optimization is performed.

LCP Benchmarks by Industry

SaaS and technology companies perform best because they frequently use modern frameworks like SvelteKit, Next.js, or Astro that support server-side rendering and static generation out of the box. E-commerce websites suffer under the load of product images, tracking scripts, and complex page structures. Media sites often load dozens of third-party scripts that significantly delay LCP.

INP: Interaction to Next Paint Compared

INP replaced First Input Delay (FID) as a Core Web Vital in March 2024 and measures how quickly a page responds to user interactions. The threshold is 200 milliseconds. The German average stands at 287 milliseconds, representing a clear failure. Only about 55% of websites worldwide meet the INP threshold (HTTP Archive).

INP is the most challenging of the three metrics because it evaluates not just the first interaction but all interactions throughout the entire page visit. A single slow response, such as when opening a dropdown menu or submitting a form, can worsen the overall INP value. The main culprits are large JavaScript bundles that block the main thread and poorly optimized event handlers.

• Reduce JavaScript load: Remove unused code through tree shaking and code splitting. Every kilobyte of JavaScript must be downloaded, parsed, and executed.
• Break up long tasks: Tasks blocking the main thread for more than 50 milliseconds should be split into smaller units using requestIdleCallback, setTimeout, or the Scheduler API.
• Minimize rendering updates: Avoid forced layout recalculations (forced reflows) in event handlers. Do not read layout properties immediately after DOM changes.
• Use Web Workers: Computationally intensive operations like data processing or image manipulation should be offloaded to Web Workers to keep the main thread free.

The detailed Core Web Vitals optimization guide shows further strategies for INP improvement. With XICTRAQ's performance monitoring, you can continuously track your website's INP development.

CLS: Cumulative Layout Shift Compared

CLS measures the visual stability of a page and captures unexpected layout shifts during the page visit. The threshold is 0.1. The German average stands at 0.18, indicating systematic problems with undefined image dimensions, late-loading ad banners, and web font swaps.

CLS is the easiest metric to improve because the causes are almost always traceable to missing dimension specifications. Images and videos without explicit width and height attributes, iframes without defined aspect ratios, and dynamically inserted content above the visible area are the most frequent culprits.

• Provide all images and videos with explicit width/height attributes
• Use CSS aspect-ratio for responsive media elements
• Provide ad banners and dynamic content with reserved placeholders
• Load web fonts with font-display: swap and a metrically similar fallback font
• Implement cookie consent banners as overlays rather than inserted elements
• Use skeleton loading states for asynchronously loaded content

Benchmark by Technology: CMS and Frameworks Compared

The technology used has a significant influence on the performance baseline. Modern frameworks based on server-side rendering or static site generation achieve significantly better values than traditional CMS installations with plugin overhead.

The data shows clearly: pure static HTML pages and modern frameworks like SvelteKit or Astro achieve near-perfect CWV values. WordPress can be brought into the green zone with targeted optimization, full-page caching, and CDN, but requires significantly more configuration effort. More on load time optimization in the complete load time guide.

TTFB: The Forgotten Baseline Metric

Time to First Byte (TTFB) is not an official Core Web Vital, but it forms the foundation for all other metrics. If the server takes a full second to respond, LCP cannot possibly stay under 2.5 seconds. The German TTFB average stands at 680 milliseconds, with shared hosting providers often showing values exceeding one second (HTTP Archive).

TTFB is primarily determined by server infrastructure: hosting quality, server software, database optimization, and caching strategies. A dedicated server or managed cloud hosting achieves TTFB values under 200 milliseconds, while overloaded shared hosting regularly exceeds 800 milliseconds. The comprehensive guide to TTFB optimization covers all adjustable factors in detail.

Industry Comparison: Where Does Your Industry Stand?

Performance requirements vary significantly by industry. E-commerce websites need to be particularly fast because every second of delay reduces conversion rates by an average of 7% (Aberdeen Group). Service providers benefit from fast pages through more contact inquiries. Media websites struggle with high ad loads that systematically degrade performance.

The economic leverage of performance also varies: for an online shop with EUR 500,000 in annual revenue, doubling load time potentially means EUR 35,000 less revenue per year (Aberdeen Group). For a tradesperson's website with 20 inquiries per week, a fast page can make the difference between one and two additional inquiries per week. The downtime cost calculator helps quantify the economic value of availability.

Mobile vs. Desktop: The Performance Gap

The difference between mobile and desktop performance is particularly pronounced in Germany. On desktop, 52% of websites pass all three CWV; on mobile devices, only 31% (CrUX). The main reason: mobile devices have slower processors, less memory, and often more unstable network connections. Additionally, many websites are primarily optimized for desktop screens and only adapted for mobile devices afterward.

Since Google fully switched to mobile-first indexing in 2021 (Google), mobile CWV values are decisive for rankings. A website that performs excellently on desktop but fails on smartphones will be ranked accordingly lower in search results. The comprehensive guide to mobile website speed shows how to specifically improve mobile performance.

Measuring and Contextualizing Your Own Values

To position your own website in the benchmark, you need reliable measurement data. One-time tests with Lighthouse or PageSpeed Insights give a first impression but do not reflect real user experience. Field data from the Chrome User Experience Report (CrUX) shows actual performance but requires sufficient traffic for statistically reliable values.

1. Establish baseline: Measure your current CWV with PageSpeed Insights (field data if available) and Lighthouse (lab data) for all important pages.
2. Compare with industry: Compare your values with the industry benchmarks listed above and identify the largest deviations.
3. Prioritize weaknesses: Focus first on the metric with the greatest deviation from the threshold. In most cases, this is LCP.
4. Implement measures: Use Lighthouse recommendations and the concrete optimization guides in the Lighthouse guide as your roadmap.
5. Monitor continuously: Set up automated monitoring to measure progress and detect deterioration immediately.

XICTRAQ enables this entire process from a single platform: performance monitoring, Lighthouse audits, SEO tracking, and trend analysis show you at any time where your website stands. The cookieless analytics provide real user data without GDPR issues.

Concrete Optimization Strategy for Reaching the Top 10%

The path from average performance to the top 10% does not require revolutionary changes but rather the consistent implementation of proven measures. The following strategy is prioritized by effectiveness and covers the most common problems of German websites.

1. Bring TTFB below 200 ms: Set up server-side full-page caching, activate CDN, and evaluate hosting. This single step often improves LCP by 1-2 seconds.
2. Prioritize LCP element: Identify the largest visible element, prioritize with fetchpriority=high and preload, serve in WebP/AVIF.
3. Halve JavaScript load: Remove unused code, evaluate third-party scripts and keep only those truly needed. Use code splitting for page-specific bundles.
4. Ensure layout stability: Provide all images and media with explicit dimensions, use CSS aspect-ratio, load web fonts with font-display: swap.
5. Activate compression: Brotli for static assets, Gzip as fallback. This step alone reduces transfer size by 60-80%.
6. Enable HTTP/2 or HTTP/3: The switch is a pure configuration change on modern web servers and noticeably speeds up parallel loading.

Performance as a Continuous Process

Benchmarks are not a one-time snapshot but an ongoing reference point. Every CMS update, new plugin, and design change can affect performance. Without continuous monitoring, you will not notice gradual deterioration until rankings have already declined.

XICTRAQ automates this process. Uptime and performance monitoring measures your core metrics around the clock, compares them with industry benchmarks, and alerts you to deterioration. Combined with the security scan, GDPR compliance checking, and SEO monitoring, you get a complete picture of website health.

Start now with a free demo or register directly to keep your website performance permanently in view and systematically improve it.