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.
