The Short Answer
Almost every slow website is slow for one of five reasons: oversized images, too many plugins or third-party scripts, cheap shared hosting, render-blocking code, or a page builder generating far more markup than the design requires. You can identify which one applies to you in about twenty minutes, and most of them are fixable without rebuilding anything.
What follows is the diagnostic order we use on client sites, from cheapest fix to most structural. Work through it top to bottom and stop when the numbers improve.
First, Measure Properly
Your website does not feel slow to you, because your browser has cached it and you are probably on good broadband. That is not the experience you are optimising for. Run your homepage and your two most important pages through Google PageSpeed Insights and read the mobile scores only. Pay attention to three numbers:
- Largest Contentful Paint (LCP) — how long until the main content appears. Target under 2.5 seconds. This is the number that correlates most directly with people leaving.
- Cumulative Layout Shift (CLS) — how much the page jumps around while loading. Target under 0.1. High CLS is why visitors tap the wrong button.
- Interaction to Next Paint (INP) — how quickly the page responds when tapped. Target under 200ms. Covered in depth in our guide to optimising Interaction to Next Paint.
Also check the "field data" section if it appears. That is real data from real visitors over the previous 28 days, and it matters more than the simulated lab score directly beneath it.
Cause 1: Your Images Are Enormous
This is the single most common cause, and it is responsible for more slow Indian business websites than every other cause combined. Someone uploaded photographs straight from a camera or a phone — 4000 pixels wide, three to eight megabytes each — and the browser is being asked to download and resize them on every single visit.
A hero image displayed at 1600 pixels wide should be roughly 150–250KB in a modern format. If yours is 4MB, you are sending twenty times more data than necessary, and on a 4G connection that alone can add five seconds.
The fix
- Resize images to the largest size they are actually displayed at, then export them as WebP or AVIF rather than JPEG or PNG.
- Serve different sizes to different screens using responsive image attributes, so phones do not download desktop-sized files.
- Lazy-load anything below the fold so it downloads only when the visitor scrolls to it — but never lazy-load your hero image, which delays the exact thing LCP measures.
- On WordPress, an image optimisation plugin handles most of this automatically. On a custom build, the framework should be doing it already.
Realistic effort: a few hours. Typical improvement: often two to four seconds. This is the highest-return work available on most sites.
Cause 2: Plugin and Script Bloat
Every plugin you install adds code to every page, whether that page uses the plugin or not. A site running thirty-five plugins is loading thirty-five sets of stylesheets and scripts on a contact page that needs approximately none of them.
Third-party scripts are the same problem wearing a different hat. Analytics, a chat widget, a heatmap tool, three advertising pixels, a review widget, a popup builder — each one opens a connection to somebody else's server and waits. Your site is now only as fast as the slowest company you have embedded.
The fix
- List every active plugin and honestly mark the ones that are actively earning their place. Deactivate the rest, then test.
- Replace multi-purpose plugins with narrower ones. A page builder installed to make one section look nice is an expensive way to buy one section.
- Audit your tracking scripts. Most businesses are running pixels for advertising platforms they stopped using a year ago.
- Load non-critical third-party scripts after the page has rendered rather than before it.
Realistic effort: half a day, plus testing. Typical improvement: one to three seconds, and a meaningful reduction in security exposure as a side benefit.
Cause 3: Your Hosting Is Too Cheap For Your Traffic
A ₹199-per-month shared hosting plan puts your website on a server shared with hundreds of other websites, competing for the same processor and memory. When one of them gets a traffic spike, yours slows down. You have no visibility into this and no control over it.
The number to watch is Time To First Byte — how long the server takes to begin responding at all. If TTFB is above 600ms and your images are already optimised, the server is the problem, not the page.
| Hosting tier | Typical monthly cost (India) | Suitable for |
|---|---|---|
| Shared hosting | ₹200 – ₹500 | Personal sites, very low traffic, testing |
| Managed WordPress hosting | ₹1,500 – ₹5,000 | Most business sites and small stores |
| Cloud / VPS | ₹4,000 – ₹15,000 | Busy stores, membership sites, portals |
| Edge platforms (Vercel, Netlify) | ₹0 – ₹2,000 | Static and framework-built sites like Next.js |
A content delivery network sits in front of whichever tier you choose and serves cached copies from a location closer to the visitor. For an audience spread across India, this alone can remove several hundred milliseconds. Our hosting guide for business owners covers how to choose without over-buying.
Cause 4: Render-Blocking Code and Fonts
Browsers must download and process CSS and, often, JavaScript before they can display anything. If your site loads eleven stylesheets and nine scripts in the page head, the visitor stares at white space until all twenty finish.
Custom fonts deserve specific mention because they are a frequent and invisible offender. Loading four weights of two font families means eight font files, and if the font is not configured to display a fallback while loading, your text is invisible until they arrive.
The fix
- Combine and minify stylesheets, and inline the small amount of CSS needed for the visible portion of the page.
- Defer JavaScript that is not needed for the first render.
- Self-host fonts rather than pulling them from a third-party service, and limit yourself to the two or three weights you genuinely use.
- Set fonts to swap so text is readable in a fallback face while the custom font downloads.
Cause 5: The Site Is Structurally Heavy
Sometimes none of the above is the real answer. Sometimes the page is 6MB and makes 180 requests because it was assembled in a drag-and-drop builder that wraps every element in five nested containers and ships the styling for every feature it supports, used or not.
You can optimise a site like this and reach acceptable numbers. You will not reach excellent ones, and each round of optimisation gets undone the next time someone edits a page in the builder. This is the point where patching becomes more expensive than rebuilding, which is the argument we make in detail in custom website versus template.
The honest test: if you have already fixed images, plugins, hosting, and render-blocking resources and mobile LCP is still above four seconds, the platform is the constraint.
What Speed Work Costs in India
| Scope | Typical cost | What it covers |
|---|---|---|
| Speed audit only | ₹5,000 – ₹15,000 | Diagnosis, prioritised report, no implementation |
| Image and caching pass | ₹10,000 – ₹25,000 | Compression, formats, caching, CDN setup |
| Full optimisation engagement | ₹25,000 – ₹60,000 | Above plus plugin rationalisation, code splitting, font and script work |
| Rebuild on a modern stack | From ₹60,000 | New build where speed is structural rather than a fix |
Be sceptical of anyone quoting a fixed price before looking at your site, and be equally sceptical of anyone promising a PageSpeed score of 100. Chasing the last few points frequently means removing functionality your business actually uses.
A Twenty-Minute Diagnostic You Can Run Today
- Run your homepage through PageSpeed Insights and note the mobile LCP.
- Open your homepage in an incognito window with browser dev tools on the Network tab. Sort by size. If any single image is above 500KB, you have found cause one.
- Look at the total page weight at the bottom of that panel. Above 3MB is heavy; above 5MB is a structural problem.
- Check TTFB in the same panel. Above 600ms points at hosting.
- Count the requests going to domains that are not yours. That is your third-party script load.
Those five numbers will tell you which section of this article applies to you, and roughly what the fix will cost.
The Part Most People Get Backwards
Speed is a floor, not a ceiling. A fast site does not persuade anybody to buy — it merely stops you losing people who were already willing to. If your site is fast and still not producing enquiries, the problem has moved elsewhere, and our piece on traffic without enquiries covers where to look next.
If you would like your site diagnosed properly rather than guessed at, send us the URL and we will tell you what is actually wrong with it.