Skip to content

Why your business website is slow, and how to fix it

Core Web Vitals in plain English: what LCP, INP and CLS measure, the usual reasons business sites are slow, and a fix list in order of impact.

By AlphaZero Team5 min read
On this page
  1. Core Web Vitals in plain English
  2. LCP: Largest Contentful Paint
  3. INP: Interaction to Next Paint
  4. CLS: Cumulative Layout Shift
  5. Lab data and field data
  6. Why business sites are usually slow
  7. Oversized images
  8. Too many scripts
  9. Heavy page builders and plugins
  10. Slow hosting and no caching
  11. Web fonts
  12. Layout shifts from late content
  13. Heavy JavaScript on the main thread
  14. A fix list in order of impact
  15. Common myths
  16. When to rebuild instead of patch
  17. What to send us

A slow website costs you visitors before they read a word. On a mobile connection in a tier-2 city, or on a mid-range Android phone, a heavy page can feel broken. Google also uses page experience as one of many signals, so speed touches search visibility as well.

This guide explains Core Web Vitals without jargon and gives a fix list ordered by what usually helps most.

Core Web Vitals in plain English

Google measures three things that describe how a page feels to a real user.

LCP: Largest Contentful Paint

How quickly the main content shows up. It is the time until the biggest visible element, usually a hero image, a banner or a big heading, finishes rendering. Google’s guidance is that 2.5 seconds or less is good, and over 4 seconds is poor.

INP: Interaction to Next Paint

How quickly the page responds when you tap or click. It measures the delay between an action, such as opening a menu or pressing a button, and the screen updating. Google’s guidance is 200 milliseconds or less for good. INP replaced the older First Input Delay metric.

CLS: Cumulative Layout Shift

Whether things jump around while loading. You are about to tap a link and an image loads above it, pushing the link down, and you tap the wrong thing. CLS scores that. Google’s guidance is 0.1 or less for good.

These thresholds come from Google’s published guidance, and they can change, so check the current documentation when you test.

Lab data and field data

Two kinds of numbers confuse people.

  • Lab data comes from a tool like Lighthouse running a simulated test on your page. It is repeatable and good for debugging.
  • Field data comes from real visitors’ browsers over time, and it is what Google uses. You can see it in Search Console’s Core Web Vitals report and in PageSpeed Insights when your site has enough traffic.

Use lab tests to find problems and field data to confirm they are fixed. A great lab score with poor field data usually means your real visitors have slower phones and networks than your test.

Why business sites are usually slow

Oversized images

The most common cause. A phone photo uploaded straight from the camera can be several megabytes. The page then downloads it to show a 400-pixel box.

Fix: resize to the size actually displayed, use modern formats such as WebP or AVIF, add width and height attributes, and lazy-load images below the fold. Do not lazy-load the main hero image, because that delays LCP.

Too many scripts

Chat widgets, analytics, ad pixels, heat maps, social feeds and A/B testing tools each add JavaScript. Together they block the page and hurt INP.

Fix: list every script and ask what business value it gives. Remove those nobody looks at. Load the rest after the page is usable, or on user interaction.

Heavy page builders and plugins

A WordPress site with a bulky theme, a visual builder and twenty plugins ships a lot of code on every page. Many of these load their CSS and JavaScript sitewide even when a page does not use them.

Fix: audit plugins, remove unused ones, use a lightweight theme, and add caching. For sites where speed and search matter, a purpose-built site on a modern framework can be much lighter. That is what our web development work focuses on.

Slow hosting and no caching

If the server takes a second to respond, nothing else can be fast. Cheap shared hosting far from your visitors makes it worse.

Fix: use hosting with a CDN so pages are served from a location near the visitor, and enable caching. Static pages that are generated ahead of time are the fastest option for content that does not change per user.

Web fonts

Multiple font families and weights can add hundreds of kilobytes, and text may stay invisible until the font arrives.

Fix: use one or two families, subset them to the characters you need, host them yourself, and use font-display: swap so text appears at once. If your site shows Odia, read our note on bilingual Odia and English apps for font loading, as Odia fonts are large.

Layout shifts from late content

Images without dimensions, ads that load late, banners that push content down, and fonts that swap and change text size all cause CLS.

Fix: reserve space with explicit width and height, set a fixed container for ads and embeds, and avoid inserting content above what the user is already reading.

Heavy JavaScript on the main thread

Large bundles take time to download, parse and run, especially on mid-range phones. This is the main cause of poor INP.

Fix: ship less JavaScript. Remove unused libraries, split code by page, and avoid using a heavy framework for a page that is mostly text. Break up long tasks so the browser can respond to taps.

A fix list in order of impact

  1. Measure first. Run PageSpeed Insights on your key pages: home, a service page and the contact page. Note the LCP element it reports.
  2. Fix the LCP element. Usually compress and resize the hero image, and make sure it loads early (preload it, don’t lazy-load it).
  3. Compress all other images and add dimensions.
  4. Remove or defer third-party scripts you do not need at load time.
  5. Reduce fonts to what you actually use.
  6. Add caching and a CDN.
  7. Cut JavaScript and CSS that the page does not use.
  8. Re-test on a real mid-range Android phone on a mobile connection, not only on your laptop.

Expect the first two or three steps to give most of the improvement. Do them before anything more complicated.

Common myths

  • “A 100 Lighthouse score is the goal.” The goal is a fast experience for real users. A score is a diagnostic.
  • “Speed only matters for SEO.” It matters for conversion too. People leave slow pages, whether or not Google noticed.
  • “My site is fast on my laptop.” Your laptop on office wifi is the best case. Test on the devices your customers use.
  • “A CDN fixes everything.” It helps delivery, but a 5 MB page is still 5 MB.

When to rebuild instead of patch

If you have done the basics and the site is still slow, the cause may be the platform: a theme that cannot be slimmed down, a builder that outputs heavy markup, or an architecture that renders everything on the server per request. At that point, rebuilding key pages on a leaner stack can be cheaper than endless tuning. We can look at your site and say honestly whether it needs a patch or a rebuild.

What to send us

If you want an opinion, send your URL and tell us which pages matter most. We will run the tests, tell you what we see and suggest the order of fixes, whether you use us for the work or not. Contact us to start.

Keep reading

Have something to build? Let us talk it through.

Tell us what you have in mind. We reply within one business day with questions, a rough plan and an honest view on cost.