Slow Website: Why It Happens and What It Costs You

Websites are usually slow because of heavy images, too many plugins and scripts and weak or overloaded hosting. In most cases all three can be fixed without building a new site.

Few people notice a slow site from the inside. You open it on fast office internet, from the browser cache, and it all seems fine. A customer opens it for the first time, on a phone, on a bus, and stares at a blank screen.

The cost does not show up on an invoice, but it is real. People who do not wait for the page to load go to a competitor, paid ad clicks go to waste, and Google measures speed and takes it into account as part of page experience.

Below we explain Core Web Vitals, Google's three speed metrics, in plain words, then the most common causes of a slow website, how to spot them and what to fix first.

IT Expert is a team from Belgrade that builds websites and does SEO. We measure speed on real visitors, not only in a test, because those two numbers often differ.

Core Web Vitals in plain words

01LCP

Good up to 2.5 seconds, how long until the largest piece of content appears, usually the main image or headline

02INP

Good up to 200 milliseconds, how quickly the page visibly reacts when you click or type

03CLS

Good up to 0.1, how much the content shifts while the page loads

What LCP, INP and CLS mean

What LCP, INP and CLS mean

Core Web Vitals are three Google metrics that measure how a visitor experiences speed: how long they wait for content, how long they wait for a reaction and whether the page moves under their finger.

LCP (Largest Contentful Paint) measures when the largest element on screen appears, usually a big image or headline. Up to 2.5 seconds is good, over 4 seconds is poor. When LCP is poor, the cause is usually a heavy hero image or a slow server.

INP (Interaction to Next Paint) measures the time from a click to a visible change on screen. Up to 200 milliseconds is good, over 500 is poor. Poor INP usually means too much JavaScript: chat widgets, ad pixels, sliders and plugins all running at once.

CLS (Cumulative Layout Shift) measures how much the content moves while loading. Up to 0.1 is good, over 0.25 is poor. It is the moment you go to tap a button and it jumps away because an image or banner loaded above it.

Google says its ranking systems use Core Web Vitals, but also that a good score does not guarantee the top spot. Speed is one signal, and content still matters most.

The most common causes of a slow website

01Heavy images

How to spot it: the hero image is several megabytes and the page loads from top to bottom. What helps: smaller dimensions, WebP or AVIF, lazy loading for images below the screen.

02Too many plugins

How to spot it: a WordPress site with dozens of plugins, slow even in the admin panel. What helps: remove unused plugins, replace heavy ones with lighter ones.

03Third-party scripts

How to spot it: chat, pixels, maps and video load right away, INP is poor. What helps: load them only when needed or after the first interaction.

04Weak hosting

How to spot it: even an empty page responds slowly, the site is slow at night too. What helps: a better plan or a server closer to visitors.

05No caching

How to spot it: every visit builds the page from the database again. What helps: page caching and caching of static files.

06A heavy theme

How to spot it: the theme loads sliders and fonts on every page. What helps: a lighter theme or a custom-built site.

Images are the most common culprit

Images are the most common culprit

Images are the most common reason for a slow site because they are uploaded straight from a phone or camera at full size. A photo of several megabytes is shown in a frame a few hundred pixels wide, and the visitor downloads all of it.

The fix is simple and does not change the design: the image is resized to the dimensions it is shown at, saved in a modern format such as WebP or AVIF and given a separate, smaller version for phones.

Images that are not on the first screen load only when the visitor scrolls to them. The hero image, on the other hand, should load right away, because LCP usually depends on it.

If you manage the site yourself, build a habit: check the file size before uploading. A blog image rarely needs to be larger than a few hundred kilobytes.

Why a website is slower on phones

Why a website is slower on phones

A website is slower on phones because a phone has a weaker processor than a computer and often a worse connection. The same JavaScript a computer runs in an instant takes a mid-range phone noticeably longer.

That is why Google measures Core Web Vitals separately for phones and computers. A site can pass on desktop and still have poor LCP and INP on mobile.

You can check how many of your visitors come from phones in Google Analytics 4, in the report by device type. If phones lead, measure and fix speed for phones first.

Less JavaScript helps the most: fewer plugins, third-party scripts that load later and sliders replaced by one good image.

What a slow website costs you

01Customers who do not wait

A visitor looking at a blank screen has no idea your offer is good. They go back to search and click the next result, and you never learn they were there.

02Paid clicks that go to waste

When an ad leads to a slow site, you pay for a click from someone who never saw the page. For Google Ads, landing page experience also affects Quality Score.

03A measured difference in sales

In a test published on web.dev in 2021, Vodafone improved LCP by 31 percent and got 8 percent more sales, with the same design and content on the page.

Loading chart before speeding up, with many long red and grey bars

Before and after: what changes when you speed up a site

The easiest way to see the difference is the loading chart (waterfall), which shows every file the page pulls in. Before speeding up, the list is long: dozens of files, heavy images and scripts waiting on each other.

After speeding up, the list is short. Images are smaller, scripts that are not needed on the first screen wait, and the server answers from cache. The site looks the same, only the visitor's wait changes.

Whoever speeds up your site, ask for both charts and the before and after measurements, so the difference can be checked rather than promised.

How to measure website speed

How to measure website speed

The easiest way to measure website speed is PageSpeed Insights: enter the address and you get real visitor data, if Google has enough of it, plus a lab test with suggestions on what to fix.

For the whole site, not just one page, open the Core Web Vitals report in Google Search Console. It shows which groups of pages are good, which need improvement and which are poor, separately for phones and computers.

Test several pages, not only the home page: a service page, a product category, the contact page. Often the slowest page is exactly the one an ad points to.

Measure again after every change. Real visitor data in Search Console changes slowly because it covers the last 28 days, so you get the true picture only after a few weeks.

Speed it up or build a new site?

Most slow websites can be sped up without a new site: images, plugins, caching and hosting. When the problem is in the foundation, such as a heavy theme and dozens of plugins that depend on each other, a lighter new site is sometimes cheaper than patching the old one. After measuring, we look at your case together, and you choose who does the work.

Frequently asked questions about website speed

By Google's thresholds, the main content should appear within 2.5 seconds (LCP), the page should react to a click within 200 milliseconds (INP) and layout shift should be at most 0.1 (CLS), for 75 percent of visits.
The lab test depends on the current server load and network, so the score changes from test to test. Real visitor data at the top of the report and the Core Web Vitals report in Search Console give a steadier picture.
Google says its ranking systems use Core Web Vitals, but also that good results do not guarantee the top spot. Speed is one signal. It has a bigger effect on whether a visitor stays on your site.
Only if hosting really is the cause, for example when even an empty page responds slowly. If the problem is heavy images or too many scripts, a faster server helps little. Measure first, then change hosting.
Partly. You can resize images and delete plugins you do not use yourself. Caching, deferring scripts and theme changes take experience, because they easily break the design or the forms on the site.