OutDept

Slow Website? Why 3 Seconds Is Costing You Customers (and How to Fix It)

October 21, 2026·4 min read

Most visitors won't wait for a slow page, and Google notices too. What Core Web Vitals measure, the usual reasons a website is slow, and the fixes that actually work.

You've probably never timed your own website on a phone, but your customers do it every day without meaning to. If the page doesn't appear quickly, they hit back and tap the next result. Google's own research on mobile sites found that more than half of visits are abandoned when a page takes longer than three seconds to load. Here's what slows a website down and how to fix it.

Why website speed matters for sales and SEO

Speed affects revenue in two ways. First, directly: slow pages lose visitors before they see your offer, and every slow step in a checkout or booking form loses more. A Deloitte study commissioned by Google found that improving mobile load time by just a tenth of a second measurably increased conversions for retail and travel sites.

Second, through search: Google uses page experience, including Core Web Vitals, as one of its ranking signals. Speed alone won't push a weak page to the top, but between two similar pages, the faster one has the edge.

Core Web Vitals in plain language

Google measures real visitors' experience with three metrics:

  • Largest Contentful Paint (LCP): how quickly the main content appears. Good is 2.5 seconds or less.
  • Interaction to Next Paint (INP): how quickly the page responds when someone taps or clicks. Good is 200 milliseconds or less.
  • Cumulative Layout Shift (CLS): how much the layout jumps around while it loads. Good is 0.1 or less.

You can check your scores for free in Google PageSpeed Insights and in the Core Web Vitals report in Google Search Console.

7 common reasons a website is slow

  • Huge images: photos uploaded straight from a camera or phone, several megabytes each.
  • Too many plugins and scripts: every slider, chat widget, tracker and font adds weight.
  • Cheap shared hosting: a server shared with hundreds of other sites, often far from your customers.
  • No caching or CDN: the server builds every page from scratch for every visitor.
  • Heavy page builders that generate bloated code.
  • Autoplay video and large background animations on the first screen.
  • Third-party embeds such as maps, social feeds and review widgets loading on every page.

Quick wins you can do this week

  • Compress and resize images, and serve modern formats like WebP or AVIF.
  • Remove plugins, trackers and widgets nobody uses.
  • Lazy-load images and embeds that sit below the first screen.
  • Turn on caching and put the site behind a CDN.
  • Replace an embedded map with a static image that links to Google Maps.

When quick fixes aren't enough

If the site is still slow after the basics, the problem is usually structural: an old theme, a page builder, or a platform that loads everything on every page. At that point patching costs more than rebuilding. A modern site built with a framework like Next.js and served from a CDN typically loads in a fraction of the time, because each page ships only what it needs.

Test your site the way customers see it

Don't judge speed on the office Wi-Fi with a new laptop. Open your site on a mid-range phone over mobile data, or run it through PageSpeed Insights with the mobile setting. That's the experience most of your visitors actually get, especially tourists browsing on roaming data.

OutDept can check your website's speed, explain in plain language what's slowing it down, and fix it, whether that means cleaning up the current site or rebuilding it to be fast from the start.

Have a project behind this question?

Tell us the problem, not the service name — we'll scope it properly before quoting anything.

Talk to us

Web Development

← All articles