Visitors judge a page in seconds. If nothing useful shows up quickly, many leave before reading a word, and the ad click or search result that brought them is wasted. The usual guideline is to show the main content within about 2.5 seconds, the "good" threshold for Largest Contentful Paint. Past three seconds, the drop-off grows on mobile connections.
Measure like a customer
- Test on a mid-range phone over mobile data, not on a developer laptop over office fibre.
- Use field data in PageSpeed Insights to see the experience of real visitors.
- Check the home page, a product or service page and the checkout or contact page separately.
Where the three seconds go
| Stage | Typical cause of delay | Fix |
|---|---|---|
| Waiting for the server | Slow database, no page cache, distant server | Cache pages, tune queries, host near visitors |
| Downloading the page | Large images, many files | Compress images, serve modern formats, combine assets |
| Running scripts | Chat widgets, trackers, heavy sliders | Remove or defer what is not essential |
| Layout shifting | Images without dimensions, late ads | Reserve space for every element |
Fixes in the order of payback
- Compress and resize images. This is usually the fastest win.
- Enable caching. A page cache plus browser cache headers removes repeated work.
- Remove unused scripts. Each tag adds requests and main-thread work.
- Check the server. A server response over about 600 ms points to code, database or plan limits. See why your site is slow for the checklist.
- Put the origin near the audience. A server in Sofia suits visitors in Bulgaria, the Balkans and Turkey.
When the plan is the limit
If a trimmed site still responds slowly under load, resources are the cause. What happens when you pick the wrong hosting package describes the symptoms. A cloud server gives CPU and RAM of your own, while web hosting suits lighter sites. The broader strategy is in website performance and your future.
Frequently asked questions
Is three seconds a hard limit?
No. It is a practical guideline. Faster is better, and the cost of delay rises steadily rather than at a single cut-off.
What should I fix first on a slow shop?
Images and caching, then third-party scripts, then the server plan.
Does mobile need different treatment?
Yes. Mobile has slower processors and variable networks, so test there first.




