Website Speed & Core Web Vitals in India 2026: Why Your Site Is Slow and How to Fix It

Speed is the most underrated thing about a website. It is invisible when it is good and brutal when it is bad: a visitor lands, the page hangs for a few seconds, and they are gone before they ever saw what you offer. They will not email you to say the site was slow. They just leave, and you never know it happened.

In India this matters more than almost anywhere. Most of your visitors arrive on a mid-range Android phone, over a mobile network that is sometimes 4G and sometimes a bar and a half in a lift. A site that feels fine on your office WiFi and your laptop can be painfully slow for the customer you actually want. This is the practical guide to website speed and Core Web Vitals in 2026: what the metrics mean, why sites are slow, and what actually fixes them.

Why speed is money, and rankings

Two reasons to care. First, conversions: study after study shows that as a page gets slower, more people abandon it, and the drop is steepest in the first few seconds. A faster site does not just feel nicer, it produces more enquiries and sales from the same traffic. Second, SEO: Google uses page experience, including Core Web Vitals, as a ranking signal. It is not the biggest factor (relevance and links matter more), but when two pages are otherwise close, the faster one wins, and a slow site can be held back across the board.

The three Core Web Vitals, in plain English

Google boils site speed down to three numbers, measured on real visitors:

• LCP (Largest Contentful Paint): how long until the biggest thing on screen (usually the hero image or headline) has loaded. Good is under 2.5 seconds. This is your 'does it feel fast to load' number.
• INP (Interaction to Next Paint): how quickly the page responds when someone taps or clicks. Good is under 200 milliseconds. This replaced the old FID metric in 2024 and measures 'does it feel responsive'.
• CLS (Cumulative Layout Shift): how much the page jumps around as it loads (the classic 'you go to tap a button and an ad pushes it down'). Good is under 0.1. This is your 'does it feel stable' number.

You want all three in the green, measured on mobile, because mobile is where your visitors and Google both look first.

Why your site is slow: the usual culprits

• Huge, unoptimised images. The single most common cause. A 4MB photo straight off a phone or a stock site, shown at thumbnail size, has to download in full first. Images should be compressed, correctly sized, and served as WebP or AVIF.
• Too much JavaScript. Heavy themes, page builders, and a pile of plugins ship megabytes of script the browser has to download and run before the page is usable. This is the biggest INP killer.
• No caching or CDN. If every visitor fetches everything fresh from a single server far away, the site is slow for anyone not next to that server. A CDN serves files from close to the user.
• Cheap, overloaded hosting. A ₹150-a-month shared plan with a thousand other sites on the same box will be slow under any real traffic.
• Render-blocking resources. Fonts and stylesheets that the browser must load before it can show anything delay the whole page.
• Layout shift from ads, fonts, and images without dimensions. When elements load late without reserved space, everything jumps, which wrecks CLS.
• Too many third-party scripts. Chat widgets, analytics, pixels, and embeds each add weight and can each slow things down.

How to actually fix it

• Fix images first. It is the highest-return change. Compress, resize to the dimensions actually shown, serve WebP or AVIF, and lazy-load anything below the fold. Always set width and height so nothing shifts.
• Cut and defer JavaScript. Remove plugins you do not need, defer non-critical scripts, and avoid heavy page builders. Less script means faster loads and a better INP.
• Put a CDN in front of the site. Cloudflare, or the CDN built into modern hosts like Vercel, serves your content from close to the user. This alone can transform load times across India.
• Host on something fast. A decent VPS, managed cloud, or a platform like Vercel beats the cheapest shared hosting by a wide margin. See our web hosting guide.
• Reserve space to stop layout shift. Give images and ads fixed dimensions, and load fonts with font-display: swap plus a sensible fallback so text does not jump.
• Trim third-party scripts. Keep the ones that earn their weight, load them late, and drop the rest.
• Render smart. Static or server-rendered pages (what frameworks like Next.js do well) send ready-to-show HTML instead of making the browser build the page from scratch, which is a big LCP win.

The India angle: test like your customer, not like you

The trap is judging your site on a fast laptop and good WiFi. Your customer is on a phone on mobile data. Test that way: open the site on a real mid-range phone on 4G, or use the throttling option in your browser's dev tools to simulate a slower network and a slower CPU. A site that loads in one second for you might take six for them, and six seconds is where most people give up. Hosting and CDN choices that keep content inside India also shave real milliseconds for Indian visitors.

How to measure it

Two kinds of data, both useful:

• Lab tests (PageSpeed Insights, Lighthouse in Chrome): run a page on demand and get a score plus specific fixes. Great for diagnosing, but it is a simulated single run.
• Field data (the Core Web Vitals report in Google Search Console, and the CrUX data inside PageSpeed Insights): this is from real visitors over time, and it is what Google actually uses for ranking. Trust the field data for the verdict, the lab data for the to-do list.

Start at PageSpeed Insights, run your homepage and a key landing page on mobile, and work down the list of opportunities it gives you.

How we build fast sites

Speed is not a thing we bolt on at the end, it is how we build from the start. We default to static or server-rendered Next.js, optimise and lazy-load images, ship as little JavaScript as possible, reserve space so nothing shifts, and serve everything through a CDN. The result is sites that sit in the green on Core Web Vitals on a real phone, which helps both SEO and the conversion rate at the same time. When we rebuild a slow site, the speed jump is usually the first thing the client notices.

Common questions about website speed

What is a good website loading time?

Aim for the largest content to appear within about 2.5 seconds on a mobile connection (the LCP target), the page to respond to taps within 200 milliseconds (INP), and almost no layout shifting (CLS under 0.1). If your hero loads in under 2.5 seconds on a mid-range phone on 4G, you are in good shape.

Does website speed really affect Google ranking?

Yes, through Core Web Vitals, but it is one signal among many. Relevance and backlinks matter more. Speed rarely vaults a weak page to the top on its own, but a slow site is a quiet drag on everything, and between two similar pages the faster one tends to win. It also strongly affects conversions, which matters regardless of ranking.

What is the single biggest cause of a slow website?

Unoptimised images, by a distance. Large photos that are not compressed or correctly sized are the most common reason pages are slow, and fixing them is usually the fastest, highest-return improvement you can make.

My PageSpeed score is low but the site feels fine to me. Does it matter?

Probably yes, because it does not feel fine to your visitors. You are testing on a fast device and network; they are not. Check the field data in Search Console (real users) rather than your own impression, and test on a throttled mobile connection to see what they actually experience.

Will switching hosting fix my speed?

It helps, but it is rarely the whole answer. Fast hosting plus a CDN removes the server bottleneck, but if the page itself ships huge images and heavy JavaScript, it will still be slow. Fix the page and the hosting together for the real win.

Honest summary

Website speed is quiet money. A slow site loses visitors before they convert and gives Google a reason to rank you lower, and in India the gap between your fast laptop and your customer's phone makes it worse than you think. The fixes are well understood: optimise images, cut and defer JavaScript, use a CDN and decent hosting, reserve space to stop layout shift, and render static or server-side. Measure with PageSpeed Insights and the Search Console Core Web Vitals report, and fix the biggest items first.

If your site is slow and you want it fast, the cost calculator gives a rough estimate for a rebuild or a speed pass, or send us a WhatsApp message with your URL and we will tell you honestly what is dragging it down.