Loading speed is how quickly a page becomes usable. Google measures it with Core Web Vitals (external site, opens in a new tab), which look at loading, responsiveness and visual stability. Start by measuring, then fix the biggest causes first, usually large images. A faster site is better for visitors on mobile data, but speed alone does not guarantee better rankings.
Large page
Heavy images and scripts.
Measure
Find the biggest causes.
Fix
Compress, remove, cache.
Test again
On a phone, on mobile data.
What to measure
web.dev describes the Core Web Vitals (external site, opens in a new tab): how fast the main content appears, how quickly the page responds to a tap, and whether the layout jumps around while loading. Free tools such as PageSpeed Insights show how your page performs on phones. Test the pages customers use most, not only the home page.
The usual causes
| Cause | What happens | Typical fix |
|---|---|---|
| Large images | A photo of several megabytes downloads on mobile data | Resize, compress and use modern formats |
| Too many scripts | The page waits on code it does not need | Remove unused plug-ins and trackers |
| Weak hosting | The server is slow to answer | Move to suitable hosting |
| No caching | Every visit rebuilds the page | Turn on caching |
| Heavy page builders | Extra code on every page | Use a lighter theme or build |
Fixes you can ask for
- Compress images and size them for the space they fill.
- Load images below the first screen only when needed (lazy loading).
- Remove plug-ins, fonts and tracking you do not use.
- Check hosting speed and caching.
- Test again on a phone after each change.
For a deeper guide see web.dev's Learn Performance course (external site, opens in a new tab).
Common mistakes
- Testing only on fast office Wi-Fi. Test on mobile data.
- Uploading photos straight from a phone camera. They are far too large for a web page.
- Adding more plug-ins to fix a slow site. Each can add weight.
- Chasing a perfect score. Aim for a page that feels quick to a real visitor.
Key terms and where the definitions come from
Show key terms and sources
These explanations are ADA's own words, adapted from the independent sources named. Those organisations do not endorse or work with ADA, and the examples are illustrations, not real clients.
What are Core Web Vitals?
Core Web Vitals are measurements of how quickly a page loads, how soon it responds to a tap or click, and how stable the layout is while it loads.
Source: Adapted from web.dev, Web Vitals.
Reference: web.dev: Web Vitals (external site, opens in a new tab)
For a Namibian business: A heavy page with large photos can feel slow on a rural mobile connection, so visitors may leave before it appears.
Related ADA service: Slow website? ยท Website care plans
Common questions
Why is my website slow?
The most common reasons are large images, many scripts, slow hosting and no caching. Measure first to see which applies.
How fast should a website load?
As quickly as you can reasonably make it. web.dev publishes target values for Core Web Vitals. Aim for pages that feel quick on a phone.
Does speed affect Google ranking?
Google uses page experience signals, including Core Web Vitals, but says great content still matters most. Speed is one factor among many.
Can I fix speed myself?
Compressing images and removing unused plug-ins is within reach. Hosting and code problems usually need a developer.
Will a new design make it faster?
It can, if the new build is lean. A heavier design can make things worse, so ask about speed before you approve it.
Need help with this?
Optional. You do not need any ADA service to use what you have just read.
- Slow website
The usual causes and what we check first. - Website redesign
Rebuild a heavy site as a lean one. - Website care plans
Ongoing checks so speed does not slip.