Website Performance Basics: Why Speed Matters and What Affects It

Time-lapsed of street lights

Website performance is how quickly a page becomes visible and usable for a visitor. It affects whether people stay, whether they complete a purchase or enquiry, and to a degree how the page is treated in search. This guide explains what speed really means, what slows a site down and which improvements give the most for the least effort.

Why speed matters

  • Visitors leave slow pages. The longer a page takes to show something useful, the more people give up, particularly on phones.
  • Conversions depend on it. A slow checkout or form loses orders and enquiries.
  • Search engines consider page experience. Speed is one of many signals. It will not outrank relevance, but it can separate similar pages.
  • Not everyone has a fast connection or a new phone. Performance is also a matter of accessibility.

What happens when a page loads

  1. The browser looks up the domain in DNS.
  2. It connects to the server and requests the page.
  3. The server builds the page, often by running code and querying a database, and sends the HTML.
  4. The browser reads the HTML and requests the files it references: stylesheets, scripts, fonts, images.
  5. It renders the page, then runs scripts that make it interactive.

A delay at any step slows the whole experience. Problems fall into two groups: a slow server response, and a heavy page.

How speed is measured

The most widely used measures are Google’s Core Web Vitals.

  • Largest Contentful Paint (LCP): how long until the main content is visible. Aim for 2.5 seconds or less.
  • Interaction to Next Paint (INP): how quickly the page responds when a visitor clicks or types. Aim for 200 milliseconds or less.
  • Cumulative Layout Shift (CLS): how much the layout jumps while loading. Aim for 0.1 or less.

A related measure is Time to First Byte (TTFB), the time before the server starts to answer. It reflects hosting and server-side work.

Lab data and field data

  • Lab data comes from a test run on one simulated device. It is useful for diagnosing problems.
  • Field data comes from real visitors over recent weeks. It shows what people actually experience.

PageSpeed Insights shows both where enough data exists, and the Core Web Vitals report in Search Console shows field data across the site. A single score is a summary. The individual measures tell you what to fix.

What affects performance

Hosting and server response

An overloaded or underpowered server is slow before a single image loads. Server location matters too: the farther the visitor, the longer the journey. See Web Hosting Explained.

Caching

Without caching, the server rebuilds every page for every visitor. Page caching stores the finished page and serves it instantly. Browser caching lets returning visitors reuse files they already have. For most content sites, caching is the single biggest improvement.

Images

Images are usually the heaviest part of a page. Common problems are photographs uploaded at camera size, outdated formats and images loaded long before they scroll into view. How to Prepare Website Images Without Losing Useful Detail covers the remedy.

Scripts and styles

Every script must be downloaded and executed. Chat widgets, sliders, trackers, advertising and social embeds add up quickly. Scripts that block rendering delay everything behind them.

Third-party content

Anything loaded from another company’s server is outside your control. Each one adds connections and can slow or even stall your page.

Fonts

Several font families and weights mean several downloads. Text may be invisible or jump while they load.

Themes, plugins and page builders

Some load large amounts of code on every page whether or not it is used. The number of plugins matters less than what each one does.

The database

A cluttered database slows uncached requests such as the admin area, search and checkout. See How to Optimize a WordPress Database Without Risky Cleanup.

The improvements that matter most

In rough order of effect for a typical small site:

  1. Switch on page caching, through your host or a caching plugin.
  2. Resize and compress images, use modern formats such as WebP, and let images below the first screen load lazily.
  3. Remove what you do not need: unused plugins, widgets, trackers, sliders.
  4. Use good hosting with a current PHP version.
  5. Limit fonts to one or two families and host them locally where possible.
  6. Set width and height on images and reserve space for embeds to prevent layout shifts.
  7. Defer non-essential scripts so content appears first.
  8. Use a content delivery network if your visitors are spread across regions.

How to check your own site

  1. Run your homepage and one typical inner page through PageSpeed Insights. Look at the mobile results first.
  2. Note LCP, INP, CLS and the list of opportunities.
  3. Find the largest element. It is usually a hero image.
  4. Open the page on your own phone using mobile data, not office Wi-Fi.
  5. Make one change, test again and keep a record.

What not to worry about

  • A perfect score. A fast, stable page for real visitors is the goal. Chasing 100 often costs more than it returns.
  • Small differences between test runs. Results vary. Look at trends.
  • Advice to add another plugin for every problem. Removing something is often the better fix.

Common mistakes

  • Uploading images straight from a camera or phone.
  • Running two caching plugins together.
  • Testing only on a fast desktop connection.
  • Adding tracking and chat tools without measuring their cost.
  • Optimising the homepage and ignoring the pages visitors actually land on.

Next step

Performance is one part of technical health. Technical SEO Basics: Crawling, Indexing and Ranking Explained shows how it fits with the rest.