Skip to content
HomeServicesAboutPricingArticlesContactPerformance test

Web Development

What makes a website fast, and why does it matter?

What makes websites slow, and how does load time affect visitors and Google? Learn what Core Web Vitals measure and test your website's speed for free.

Kevin A. Sommerstein5 min read

First impressions

The first thing a visitor meets on your website isn't the design or the copy. It's the wait. If the page loads slowly, many give up before anything appears, and then it doesn't matter how good the rest is.

This article covers why load time matters for a small business, what Google measures, what usually makes websites slow and how to check your own.

Key factsOctober 2026
LCP, good
2.5 seconds or less
INP, good
200 milliseconds or less
CLS, good
0.1 or less
Measured on
real visits in Chrome, last 28 days
Test your website
Free performance test, about 30 seconds
A fast website on a phone

Visitors don't wait

Most people looking for a small business do it on their phone, often on the go and with a weaker connection than at the office. They compare a few options and pick the one that responds first. If your page takes a long time to show anything, they go back to the search results and click the next one.

Google has studied this. In its 2016 study of mobile sites, more than half of visits were abandoned if a page took longer than three seconds to load. How many leave varies by industry and audience, but the direction is clear: every second of waiting costs visitors.

For a small business, this rarely shows up in a report. It shows up as the phone ringing a little less often and fewer people filling in the contact form.

What Google measures: Core Web Vitals

Google measures how fast and stable a page is with three metrics called Core Web Vitals. The numbers come from real visitors using Chrome, and Google looks at the last 28 days.

  • LCP (Largest Contentful Paint): how long it takes for the largest content, usually an image or a heading, to appear. Good is 2.5 seconds or less.
  • INP (Interaction to Next Paint): how quickly the page responds when someone clicks or taps. Good is 200 milliseconds or less.
  • CLS (Cumulative Layout Shift): how much the content jumps around while the page loads. Good is 0.1 or less.

The thresholds come from Google's own guidance on web.dev. For a page to pass, at least three out of four visits need to meet them.

The metrics are part of what Google calls page experience and are factored into search rankings. At the same time, Google states plainly in Search Central that relevant content matters more. A fast page with thin content won't rank just because it's fast. But when two pages are equally good otherwise, speed can tip the balance, and visitors notice the difference either way.

What makes websites slow

It's rarely a single fault. Usually a few common things add up to a heavy page:

  • Heavy themes and page builders. Ready-made WordPress themes and page builders like Elementor often load code for features the website doesn't use, on every page.
  • Lots of plugins. Each plugin can add its own scripts and stylesheets. Ten or so plugins is common, and it shows.
  • Large images. A photo straight from a camera or phone can weigh several megabytes. If it isn't compressed and resized for the screen, the phone downloads far more than it needs.
  • Slow hosting. Cheap shared hosting can take a long time to respond, especially when the page is rebuilt on every visit.
  • Scripts from other services. Chat widgets, tracking codes, cookie banners and fonts often load before the page has had time to appear.

How to check your own website

The simplest way is to measure. Run our free performance test: enter the address and we test the website on mobile and desktop with Google PageSpeed and show the result against Google's thresholds. It takes about half a minute.

Look at the mobile result first, since Google goes by the mobile version. In our walkthrough of the performance test we explain what the numbers mean and where to start.

Test a competitor's website too. Then you can see whether your site is slower than the ones next to you in the search results.

How we build fast websites

We build websites with Next.js. The pages are built in advance, so when someone visits, the server sends a finished page straight away. It doesn't have to be assembled from a database, a theme and a pile of plugins on every visit.

Images are automatically resized for the screen and saved in modern formats, so a phone doesn't download an image made for a large desktop monitor. Visitors only download the code the page needs.

There are no plugins piling up over the years either. If a feature is needed, we build it in the code, and you edit text and images yourself in Strapi, a CMS that's kept separate from the pages your visitors see.

To see how it works in practice, run the test on developly.se or on jcflytt.se, a website we built for a removals company in Helsingborg.

What you can do today

If you have a WordPress site, a few simple steps get you some of the way: compress the largest images, remove plugins you don't use and check whether your host offers caching. It costs little, and sometimes it's enough.

If you still can't reach Google's thresholds, the problem is usually in how the site is built. Then it may be time to look at an alternative to WordPress. If you'd like help reading the results, get in touch and we'll go through them together.

Frequently asked questions

According to Google, the largest content should appear within 2.5 seconds for a page to count as fast. The page should also respond to clicks within 200 milliseconds and not jump around while it loads.

Yes, but it isn't the strongest factor. Google includes Core Web Vitals in its search rankings, but relevant content matters more. Between two equally good pages, the faster one has an advantage.

Run our free performance test or Google's PageSpeed Insights. Look at the mobile result first, since the mobile version is what Google goes by.

Usually it's a heavy theme, lots of plugins, large images or slow hosting. The performance test shows which files and images take the longest to load.

Kevin A. Sommerstein

About the author

Kevin A. Sommerstein · Software Engineer

I have built websites and web apps for about ten years, mainly with Next.js, React and Node.js. At Developly I'm responsible for development and the technical decisions. You deal with me directly from the first call to launch.