Google Ads

Page Speed

Also called site speed, load time

How quickly a page becomes visible and usable on a real visitor's device, not on your office connection.

Quick facts: Page Speed

Category
Google Ads
Also called
site speed, load time
Level
Intermediate
Affects
Rankings, Ad Rank, conversion rate, bounce
Where to see it
PageSpeed Insights, Search Console Core Web Vitals report, Chrome DevTools
In this article4
  1. What page speed measures
  2. Why page speed matters
  3. Where page speed goes wrong
  4. What to do about it

What page speed measures

Speed is not one number. A browser has to fetch the HTML, then the stylesheets, scripts, fonts and images it references, then run the scripts, then paint something a person can read. Each stage can be the bottleneck, so a page that starts appearing quickly can still be unusable for a while because a heavy script is blocking the main thread.

That is why measurement has settled on a small set of user-centred signals rather than a single load time. Google’s Core Web Vitals are three of them: how fast the main content appears, how quickly the page responds to a tap, and how much the layout shifts while loading. Lab tools simulate a device to give you a repeatable score; field data reports what real visitors experienced. The two disagree often, and the field data is the one that reflects your customers.

Why page speed matters

Slow pages cost twice. On the organic side, speed is a ranking signal, though a modest one — a fast page will not outrank a genuinely better answer, but a slow one loses ties. On the paid side the effect is more direct: landing page experience feeds into Ad Rank, so a slow page can raise the price of every click while also converting fewer of them.

The conversion side is where the money usually is. A visitor who arrives from an ad has no loyalty and no reason to wait. In Nepal, where much of the traffic is mobile and connections vary widely between a fibre office and a phone on a hillside, a page tuned on a fast desktop can be an unusable page for a large part of your audience.

Where page speed goes wrong

Most slow sites are not slow because of hosting. They are slow because of what has been added to them: uncompressed photographs at full camera resolution, a page builder loading its whole library on every page, several tracking scripts, a chat widget, a review widget, three font families and a slider nobody scrolls to. Each was added for a reason, and together they make the site heavy.

The second common fault is optimising the wrong page. Homepage scores get watched because they are easy to check, while the landing pages taking paid traffic and the product pages taking search traffic go unmeasured. The third is chasing a perfect tool score, which pushes people into risky changes for gains no visitor will feel.

What to do about it

Measure the pages that earn money, on a mobile connection, before touching anything. Then work in the usual order of return: compress and correctly size images, remove scripts and plugins that no longer earn their place, enable caching, and only then look at hosting or a content delivery network. Re-measure after each change so you know which one helped.

Treat it as maintenance rather than a project. Sites get slower on their own as content, tags and plugins accumulate, so a periodic check keeps the gains. Where the causes are structural, page speed optimisation is its own piece of work rather than a setting to switch on.

Do and do not

Do

  • Measure the pages that earn money, on mobile
  • Compress and size images before blaming hosting
  • Re-check speed after every plugin or tag you add

Do not

  • Judge the whole site by its homepage score
  • Chase a perfect tool score at any cost
  • Keep widgets and fonts nobody actually uses

Questions people ask about this

Does page speed really affect Google rankings?

It is a genuine ranking signal, but a small one compared with relevance and content quality. A fast page will not lift weak content above a better answer. Where speed does decide things is between pages of similar quality, and in how many visitors stay long enough to read yours at all, which shapes results indirectly.

Why does my speed score differ between tools?

Lab tools simulate a specific device and connection, so they give a repeatable but artificial result. Field data reports what real visitors on real devices experienced, which varies by location, handset and network. Neither is wrong. Use lab tools to find causes and compare changes, and treat the field data as the truth about your customers.

What usually makes a website slow?

Nearly always the things added over time rather than the server itself. Large uncompressed images, a page builder loading its full library everywhere, several third-party scripts such as chat and review widgets, and multiple font files are the common causes. Removing what nobody uses is usually faster and safer than upgrading hosting.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.