%201.png){kind=icon}
.webp)
%201.png)
Most slow websites are not slow because of the platform they run on. They are slow because of what was added to them over time: a chat widget, three tracking tags, a hero video, a slider nobody asked for. Speed optimization in 2026 is less about exotic techniques and more about knowing which of those additions is costing you, and removing it.
This is the short, practical version: what Google actually measures, what actually slows a site, why the phone is where it is decided, and what to fix first.
The three numbers Google measures
Google judges speed with Core Web Vitals, collected from real visitors using Chrome, at the 75th percentile of visits. Mobile and desktop are measured separately.
- Largest Contentful Paint (LCP): 2.5 seconds or less. How long until the main content, usually the hero image or headline, appears.
- Interaction to Next Paint (INP): 200 milliseconds or less. How quickly the page responds when someone taps or clicks. It replaced First Input Delay in March 2024.
- Cumulative Layout Shift (CLS): 0.1 or less. How much the page jumps around while it loads. The button that moves just as you tap it.
Lab tools like Lighthouse give you a score. The field data in Search Console tells you what your actual visitors experience. When they disagree, the field data wins.
What actually slows a site, in order of impact
- Third-party scripts and plugins. Chat widgets, tag managers loaded with old tags, heatmaps, review badges, and on WordPress, plugins that load their code on every page whether it is used or not. Each one is small. Together they are usually the biggest cause of a poor INP.
- Images and video. One oversized hero image can outweigh every script on the page. Serve modern formats like WebP or AVIF, size images for the screen they appear on, and lazy load everything below the first screen, but never the hero itself.
- Hosting and caching. On shared hosting, your response time depends on what the other sites on the server are doing. A decent host with caching and a CDN fixes more than most optimization plugins.
- Fonts. Four weights of two families is eight files before any text appears. Use fewer weights, host them well, and let text show immediately while fonts load.
- Layout shifts. Images without set dimensions, banners that push content down, embeds that load late. Reserve the space before the content arrives.
When we audit a slow site, we start with hosting and scripts, not the page builder. On WordPress, Elementor is rarely the root cause. On Webflow, hosting and the CDN are handled, so slowness usually comes from heavy interactions, oversized images and embedded scripts. On Shopify, every app that adds something to the storefront also adds code to it.
The phone is where it is decided
Google indexes the mobile version of your site, and most of your visitors see it first on a phone, often on a slower connection than your office Wi-Fi. A site that feels fast on a desktop can fail every Core Web Vital on a mid-range phone.
Speed on mobile is only half of it. The other half is whether the site is usable there:
- Tap targets at least 48 pixels, with space between them, so nobody taps the wrong link.
- The main action within thumb reach, not hidden in a menu.
- Forms that help: the right keyboard for phone numbers and emails, autofill enabled, as few fields as possible.
- A checkout tested on a real phone. A store can look acceptable on mobile and still break at the last step. Franco's Pasta came to us with a site that did not adapt to phones and a broken checkout flow.
How to check your own site in fifteen minutes
- Run your homepage through PageSpeed Insights. Look at the field data at the top, the part based on real visitors, before the lab score.
- Open the Core Web Vitals report in Search Console. It groups your URLs into good, needs improvement and poor, for mobile and desktop.
- Load the site on your own phone, on mobile data. Try to tap the main button while the page is still loading. If it moves, you have a layout shift.
- List every third-party tool on the site. Chat, analytics, ads, reviews, heatmaps. For each one, ask who still uses it.
- Find the heaviest image on your homepage. If it is over a few hundred kilobytes, start there.
What to fix first
The order that usually pays off, cheapest and fastest first:
- Remove scripts, plugins and apps nobody uses.
- Compress and resize the hero image and the heaviest images on key pages.
- Delay non-essential scripts until after the page loads.
- Reserve space for images, embeds and banners so nothing jumps.
- Only then, look at hosting, caching and a CDN.
Speed is not a one-time project. It decays every time someone adds a tool, which is why it belongs in ongoing maintenance, not in a one-time check at launch. If you want someone to look at yours, tell us about your site.
.png)
.png)
Join the 1% of Data-Driven Founders
Stop letting technical debt limit your revenue. Get a 30-minute strategic diagnostic of your digital infrastructure. No fluff, just strategy.
.webp)