Page speed is one of the few technical topics a small business can verify for itself, which makes it a good area to ask precise questions of any provider. It is also one of the easiest places for vague claims to appear, so it helps to know what is actually being measured.
What Core Web Vitals measure
Core Web Vitals are three user-focused signals. The first captures how quickly the largest visible element appears, usually your heading, hero image or main banner. The second captures how quickly the page responds when someone taps a button, opens a menu or types into a form. The third captures unexpected visual movement, such as text jumping because an image loaded late.
They describe what a visitor experiences rather than how the site is built, which is why lab tests and real visits can disagree. Exact pass thresholds are defined by the platform owners and are revised periodically, so confirm current values in the official documentation or in your browser testing tools instead of quoting numbers from memory.
Why page weight matters more than anything else
Most slow business websites are slow because they load too much: oversized photographs, unused scripts, several chat and tracking widgets, and long page loads of embedded content. Each item is individually reasonable and collectively expensive.
Images are usually the quickest win. Export at the size the page actually displays, use modern formats, and add responsive sources so phones do not download desktop-sized files. Do not remove images altogether if they carry your work, but do compress them properly.
Scripts are the second. Count every tracker, chat widget, map embed and marketing tag on a page. Each one runs code that competes for the main thread. Load what is not needed immediately after the first interaction, or not at all.
How to test speed honestly
Use a page speed tool on a few of your most important pages, not just the home page, and record the date and device type. Field data from real visitors is more useful than a lab test because it reflects your actual audience and connection.
Then confirm with something simpler and harder to argue with: open the page on a mid-range Android phone over mobile data and note how long it takes to become usable. Repeat this after changes. That direct observation often tells you more than a headline score.
Do not treat a tool score as a promise. Scores vary by page, device, network and moment, so chasing a single figure across the whole site is a distraction from the underlying causes.
Fix order that makes sense
Work on shared elements first: the header, footer, global fonts and any script loaded on every page. A change there improves the entire site. Then move to individual page templates, starting with the ones that matter most, usually the home page and the main service pages.
What to do before you measure
Measure a representative selection: the home page, two or three important service pages and one heavy page if you have one. Record the date, the device type and whether you used a lab test or field data. Lab tests are useful for comparing versions because they are consistent. Field data tells you what visitors actually experience, which is what matters commercially, but it takes time to accumulate.
Use a page speed tool and a mobile connection test rather than testing on office broadband. If your own site is slow to reach on mobile data, note that, since the tool adds its own overhead and the two will not match exactly.
Where the time usually goes
Templates often arrive with unnecessary elements: sliders, layered animations, several web fonts and a set of add-ons that are not used. Removing unused items is straightforward and gives immediate benefit. Shared files such as a large hero image or a video used on every page are worth the most attention, because one change affects every visitor.
Finally, caching settings matter. When a returning visitor loads a page, the site should not download everything again. Ask what caching and compression are configured.
Questions to ask a provider
Ask what they measured, on which device and connection, before and after. Ask which specific assets were optimised. Ask whether a speed figure was quoted as a guarantee. No one can guarantee a page speed for every visitor on every network, and a provider who says otherwise is overselling.
If you would like performance reviewed alongside the rest of your site, our website development guides cover the connected topics. You can also ask for a page speed assessment and we will report what we find, including the parts that need work.
Common questions
What are Core Web Vitals and do I need to pass them?
Core Web Vitals are a set of user-experience signals covering how quickly a page shows its main content, how responsive it feels, and how much the layout shifts. They are used by search and by diagnostic tools. The exact pass thresholds are set by the platform owners and change over time, so check the current official guidance rather than relying on remembered numbers.
Does page speed affect search rankings?
Speed is one of several signals, and a fast site alone will not produce rankings. It does affect whether people stay, and for many small businesses the practical benefit is fewer bounced visitors and better form completion, which matters more than the score itself. Ranking effects depend on many competing factors.
How fast does a website need to be?
Faster is better across every connection, and mobile performance on Indian networks is usually the constraint that matters most. Measure your actual visitors with real user monitoring rather than relying only on a lab test, then prioritise the slowest templates first. Fixing shared layout and scripts improves every page at once.