Google has made it clear: Performance is a ranking factor. Online shops with poor Core Web Vitals are pushed down in search results. At the same time, industry studies show: Longer loading times can noticeably affect conversion rates. In this article, you'll learn which metrics really matter and why a PageSpeed score of 100 is achievable.
What Are Core Web Vitals?
Core Web Vitals are Google's official metrics for user experience on websites. They measure three critical aspects of page experience:
LCP (Largest Contentful Paint)
How quickly is the largest visible content loaded? Target: 2.5 seconds or less
INP (Interaction to Next Paint)
How quickly does the page respond to user interactions? Target: 200 ms or less
CLS (Cumulative Layout Shift)
How stable is the layout during loading? Target: 0.1 or less
These metrics are measured directly by Google – not in the lab, but from real users (field data). A poor score in Google Search Console has direct impact on your SEO rankings.
Why Performance Is Critical for E-Commerce
The effects of poor performance are noticeable for online shops. Various industry studies show a clear trend:
| Load Time | Impact on Conversion | Bounce Rate |
|---|---|---|
| 1–2 seconds | Optimal | Low |
| 3 seconds | May drop | May rise |
| 5 seconds | May drop further | May rise further |
| 10+ seconds | May drop even further | May rise even further |
The specific impact of loading times on conversion and bounce rates varies by industry, target audience, and study. The trends shown here are based on various e-commerce studies (including Google, Akamai) and serve as guidance.
Improving load time can have a noticeable revenue impact depending on the shop and starting situation – without additional marketing budget.
Typical Performance Killers
When analyzing online shops, we keep finding the same problems. These performance killers are often easy to fix – if you know where to look:
- Unoptimized images: A central problem. Full-resolution images without WebP/AVIF
- Render-blocking resources: CSS and JavaScript blocking the first paint
- No lazy loading: All images loaded immediately, even below the fold
- Missing browser cache: Assets reloaded on every visit
- Slow server: Time to First Byte (TTFB) over 600 ms
Many shop operators install performance plugins and think the problem is solved. Without proper configuration and systematic optimization, these tools do little.
Optimizing LCP: A Key Lever
Largest Contentful Paint (LCP) has a major impact on perceived load time. Typically, LCP is the hero image or a large product image. To optimize LCP, several factors must work together:
- Hero image as WebP/AVIF with optimal compression
- Preload for the LCP element
- Critical CSS inline in head
- No render-blocking scripts before LCP
- Fast server response (TTFB under 200 ms)
Technical implementation requires deep adjustments to the shop system. From server configuration to build system to template – all components must be coordinated.
INP: The New Metric for Interactivity
Interaction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital in 2024. INP measures how quickly the page responds to all user interactions – not just the first one.
For online shops, INP is particularly critical: Filters, product configurators, add-to-cart buttons – all these interactions must respond immediately. An INP over 200 ms feels sluggish to users and leads to abandonment.
Typical INP problems arise from too much JavaScript on the main thread. Code-splitting, lazy loading of non-critical JS, and web workers can help.
CLS: Ensuring Layout Stability
Cumulative Layout Shift (CLS) measures how much the layout shifts during loading. Nothing is more frustrating for users than when the button they were about to click suddenly jumps down.
Typical CLS causes in online shops:
- Images without defined sizes
- Late-loading web fonts (FOUT)
- Dynamically inserted ad banners
- Lazy-loaded content without placeholders
- Cookie banners without reserved space
Image Optimization: A Key Quick Win
Images are the largest single item in data volume on typical homepages: the median is 1,054 KB of images compared to 613 KB of JavaScript (HTTP Archive Web Almanac 2024). Optimizing here reduces the transferred volume at the largest single position.
| Format | File Size Compared to JPEG | Use |
|---|---|---|
| JPEG | Reference format | Fallback for older browsers |
| WebP | 25–34% smaller (Google) | Widely supported default |
| AVIF | Over 50% smaller (Google) | Highest savings, secure with the picture element |
Converting to modern image formats requires adjustments to the CMS and often the build process. Responsive images with srcset and the picture element for fallbacks are standard for professional shops.
Server Performance and Hosting
The best frontend optimization does little if the server responds slowly. Time to First Byte (TTFB) should be under 200 ms. With complex shop systems and many products, this is hardly achievable without professional hosting and caching.
- HTTP/2 or HTTP/3 for parallel loading
- CDN for static assets
- Redis/Varnish for dynamic caching
- PHP OPcache optimally configured
- Database optimization for fast queries
Why PageSpeed Score 100 Is Achievable
Many shop operators consider PageSpeed score 100 difficult to achieve. Our experience shows: For most projects, a very high score is achievable – even for complex online shops with thousands of products. However, it requires a systematic approach. An additional gain comes from the Speculation Rules API, which prepares the next page view before the user clicks.
The PageSpeed score can fluctuate slightly between measurements – this is normal and due to varying server response times and network conditions. With certain technical foundations (e.g., specific external integrations like tracking pixels or complex shop systems), score 100 is not always achievable. In these cases, we aim for the best possible value.
We systematically analyze every aspect of performance: Server, caching, assets, JavaScript, CSS, images. With optimal configuration of all components, a very high score can be achieved.
The path to optimal performance is individual for each shop. Some shops mainly need image optimization, others have JavaScript issues, still others suffer from slow servers. A professional analysis identifies the biggest levers.
Core Web Vitals are an official ranking factor at Google. Shops with poor values are ranked lower than fast competitors with equal relevance.
Google Search Console shows field data from real users. For lab data, use Lighthouse in Chrome DevTools or PageSpeed Insights.
The duration depends on the complexity of the website and the starting situation. Simple websites with a standard CMS are usually optimized faster than complex e-commerce shops with many plugins. Noticeable improvements often come early, while the final fine-tuning takes longer. We create a realistic schedule after the initial analysis.
No, in most cases existing shops like Shopware or WooCommerce (WooCommerce agency) can be made fast through targeted optimization.
The score is a lab value from Lighthouse. A high value shows that little slows the page down in the test and is a good basis for good Core Web Vitals among real users, which Google evaluates from field data. How much this affects rankings, conversions and bounces depends on industry, competition and starting point.
Mobile devices usually have weaker processors and slower network connections, so LCP and INP tend to be higher there. Google weights the mobile version particularly heavily, so optimization should typically start with the mobile experience.