Free Website Speed Test India
– Check website speed & Fixes
Free Website Speed Test 2026 – Check Page Speed, Core Web Vitals & Get Instant Fix Recommendations Powered by Google PageSpeed Insights
Find out if it’s your hosting or your website that’s slow – tested from India, with the fix either way.
Why is your website slow – your hosting, or your pages?
Every other speed test hands you one score. That score cannot tell you whether to hire a developer or change your host, and those are very different bills. This test measures the two separately, because they happen in two different places.
The first byte arrives where the colours change. Everything left of that point is your hosting; everything right of it is your pages.
Before the page arrives
Finding your address, opening the connection, and your server building the page. Measured from our own server in Mumbai, on an Indian network.
Slow here? A caching plugin will not help. It is your host, your server’s distance from India, or your DNS provider – and the result names which one, with the measurement behind it.
After the page arrives
Scripts, stylesheets and images loading inside the visitor’s browser. Measured by Google, on a simulated mid-range phone.
Slow here? Changing host changes nothing. The fixes are on the page itself, listed in order of what each one saves.
Your own site always feels fast to you. Your browser has it stored and you are often on the same city’s network as the server. The slow half is usually the half you cannot feel – which is the reason to measure it once, properly, from where your visitors actually are.
A Shopify store we checked answered in 36 ms – excellent hosting – then took 470 ms to send its HTML. A single score would have called that site slow, and sent its owner shopping for hosting that was already fine.
Run the test above and we will email the findings for your domain – what is slow, in order, with the fix for each. Nothing at all if your site turns out to be healthy.
High performance hosting – Live Hosting TTFB from Mumbai (2026)
Before you test – here’s what good hosting looks like from Mumbai. Server response times monitored 24/7 by Host Latency, an independent India hosting benchmark, on plans paid for out of pocket.
What is a good TTFB in India? Measured from Mumbai, under 400ms is good, 400 to 600ms is worth attention, 600ms to 1 second is slow, and anything past 1 second is poor. The 600ms line is Google’s own Lighthouse lab threshold – we hold to it because this is a clean lab measurement from a single Mumbai node. Google’s field data (CrUX) allows up to 800ms because it averages real visitors on real mobile networks.
Why measure from Mumbai and not the US or Europe: most global speed tools measure from American or European datacenters, which makes hosting located there look faster than it is for Indian visitors. A server in Virginia can show a 50ms response to a US test probe while the same server takes 300ms or more to reach a visitor in India, purely due to network distance. Measuring from Mumbai reflects what Indian visitors actually experience.
How to read your speed test report
You get two numbers. They are not competing – they measure different stretches of the same visit, from different places.
Time to First Byte – your hosting
Split into four phases, each named with who owns it: your DNS provider, the distance to your server, the secure handshake, and your server building the page.
Page score – your pages
A full simulation on a throttled mid-range phone: scripts, stylesheets, images, and layout shifting as the page draws.
Google says my site is slow, but my host says the server is fine. Who is right?
Usually both. They are measuring different halves of the same visit. A Shopify store we checked answered in 36 ms – genuinely excellent hosting – and still scored badly with Google, because the pages themselves were heavy. Your host is right about the server; Google is right about the page. This test shows both, so the argument ends with a number rather than an opinion.
My site loads instantly for me. Why do visitors say it is slow?
Your browser has already stored most of it, and you are often on the same city’s network as the server. A first-time visitor pays for finding your address and opening a secure connection; you pay for neither. On one site we measured 348 ms for a first visit and 42 ms for a return – the same page, minutes apart.
Does my domain registrar affect my website speed?
No – but your DNS provider does, and they are easy to confuse. The registrar is where you bought the domain. The DNS provider runs the nameservers that tell browsers where your site lives, and they need not be the same company. Only first-time visitors wait for that lookup, and you can change it without touching your registrar – though it means copying every record across first, including email, so it is not a casual change.
I tested twice and got very different numbers. Which one is right?
Usually both. One site read 881 ms on one check and 217 ms hours later, with the server completely unchanged – almost the whole difference was the address lookup being remembered the second time. It is why we also ask your nameservers directly, and why a single check is a moment rather than a verdict.
I moved to better hosting and my score barely changed. Why?
Because the score mostly measures the half hosting does not touch. Better hosting cuts the wait before your page arrives; the score is dominated by what happens after it arrives – scripts, images and layout in the visitor’s browser. If the server was never the problem, moving it was never going to fix the score. That is the mistake this test exists to prevent.
Site speed is an India-first problem
The benchmark above shows what good hosting delivers. Here’s why it matters more in India than anywhere else – every statistic below is what your Indian visitors actually experience.
Sources: Google/SOASTA mobile page speed research; IAMAI–Kantar Internet in India Report 2025.
Why is my server slow, and what actually fixes it?
Six things that reduce server response time, roughly in order of what they typically save. None are compulsory – plenty of sites run well without several – so take the ones that match what your result found.
Turn on page caching – the right one for your server
What to do: check which web server you run – the result above names it. On LiteSpeed, LiteSpeed Cache does the caching inside the server itself. On nginx or Apache that same plugin caches nothing at all, so use WP Rocket, W3 Total Cache or WP Super Cache, which write static files in PHP.
Move to PHP 8
What to do: in cPanel open Select PHP Version, or
ask your host which version you are on. Take a backup, switch, then load a few pages to
check nothing breaks. Older plugins occasionally need updating first.
Clean the database
What to do: clear post revisions, expired temporary data and
spam comments – WP-Optimize does this safely. Then look for tables left
behind by plugins you removed years ago, which nothing cleans automatically. Back up
before that second part.
Find the plugin that is costing you
What to do: the number of plugins matters far less than which
ones. Query Monitor shows what each is spending on a page build; otherwise
deactivate them one at a time and re-test after each. Page caching hides most of this
cost – without caching, nothing does.
Ask your host what is guaranteed
What to do: on shared hosting your site runs on the same processor as dozens of others, so a busy hour next door becomes your slow page. Ask how many sites share your server, and how many pages your plan can build at once. Readings that swing between tests are the sign.
Move to a server in India
What to do: no setting removes distance. An Indian host answers a visitor here in under 30 ms; an overseas server costs 150 ms or more before it starts any work, and the secure handshake pays that distance again. It shows in your TCP connect time. Check what the alternatives actually measure before moving.
The test above names which of these your site is hitting, with the measurement behind it. When the answer is the host rather than anything you can change, the Indian hosting benchmark shows what the alternatives measure – and the fixes that work on any site cover everything outside WordPress.
How to improve your website speed in India
Five proven fixes that move the needle most for Indian websites. Ranked by impact.
This single change has more impact on Indian TTFB than every plugin combined. A server responding from Mumbai eliminates the network distance that no amount of caching or image compression can fix from a US or European server. If your speed test shows TTFB above 600ms even on repeat tests, a hosting migration is your highest-leverage action – see the live benchmark above for the fastest options..
Without a caching plugin, WordPress regenerates every page dynamically for each visitor. A caching plugin stores a static version of each page and serves it instantly, cutting server response time by 40–70%. WP Rocket is the most effective commercial option. LiteSpeed Cache is free and excellent on LiteSpeed servers (Hostinger, MilesWeb). W3 Total Cache works on any host.
Unoptimised images are the single most common cause of poor LCP scores on Indian websites. A 2MB hero image that should be 200KB adds 1–3 seconds to your load time on Indian mobile connections. Convert images to WebP format (30–40% smaller than JPEG), set explicit width and height attributes on all images, and use lazy loading for below-the-fold images.
A CDN serves your images, CSS, and JavaScript from edge servers near your visitors. Cloudflare’s free plan is the usual starting point, with India PoPs in Mumbai, Chennai, and Delhi. One honest caveat: on the free plan, some Indian ISPs (notably certain Jio and Airtel routes) are served from Singapore instead of an Indian PoP because of peering arrangements – so run your own test to confirm you’re actually getting Indian-edge delivery. When it does route locally, the improvement for cached content is substantial. If your test shows Singapore routing, a paid CDN with a dependable Mumbai PoP (see BunnyCDN below) is the reliable fix.
JavaScript that loads synchronously blocks the browser from rendering your page. High Total Blocking Time (TBT above 300ms) is almost always caused by render-blocking JS. WP Rocket’s “Delay JS Execution” feature and LiteSpeed Cache’s JS optimisation settings handle this automatically. Check your Google Tag Manager, chat widgets, and social sharing buttons first.
Text-based assets like HTML, CSS, and JavaScript can be compressed by up to 70% before transmission. Brotli compression typically reduces file sizes 20–26% more than GZIP. LiteSpeed servers (used by Hostinger and MilesWeb) support Brotli natively. On Apache servers, enable GZIP via .htaccess or through your caching plugin. This directly improves First Contentful Paint.
What is a website speed test and why does it matter?
A website speed test is a diagnostic tool that measures how quickly a webpage loads, renders, and becomes interactive for a visitor. Our free website speed test is powered by the Google PageSpeed Insights API – the same engine that Google uses to assess websites for its Core Web Vitals ranking signal. Also powered by HG Node, Mumbai for rendering server response time for analysing your server speed.
The six metrics your site speed test measures
Our free website speed test measures all six Core Web Vitals metrics used by Google. Here is exactly what each one means and the threshold values for Indian websites:
| Metric | What it measures | Good ✓ | Needs Work | Poor ✗ | Score weight |
|---|---|---|---|---|---|
| LCP Largest Contentful Paint | How fast your main content loads | Under 2.5s | 2.5–4s | Over 4s | 25% |
| FCP First Contentful Paint | How fast any content first appears | Under 1.8s | 1.8–3s | Over 3s | 10% |
| TBT Total Blocking Time | How long the page is unresponsive | Under 200ms | 200 – 600ms | Over 600ms | 30% |
| CLS Cumulative Layout Shift | How much the layout jumps around | Under 0.1 | 0.1 –0.25 | Over 0.25 | 15% |
| TTFB Time to First Byte | How fast your server responds | Under 400ms | 400ms–600ms | Over 600ms | — |
| INP Interaction to Next Paint | How quickly the page responds to taps and clicks | Under 200ms | 200ms–500ms | Over 500ms | Field Metric |
TBT carries 30% of your total score – more than any other metric – because it measures whether users can actually interact with your page after it appears loaded. If clicking a button does nothing for a second, that’s JavaScript blocking the main thread – most commonly from third-party scripts and heavy WordPress plugins.
Note: INP is the newest Core Web Vital, replacing FID in 2024. It measures real interaction responsiveness – while TBT (above) is the lab-test proxy that predicts it. Google PageSpeed reports TBT in lab tests and INP in field data
7 reasons your website speed test report score is low
A poor score almost always traces to one of these seven causes – and the fix for a hosting problem is completely different from the fix for an image problem.
- Server far from your visitors (hurts TTFB). Every request travels to your server and back – a US or European origin adds 200–300ms of round trip before any content is sent, on every page view. Fix: hosting with a Mumbai datacenter – see the live hosting benchmark above.
- No caching plugin (hurts TTFB). Without caching, WordPress rebuilds every page from scratch – PHP, database queries, HTML assembly – for every visitor. A cached copy serves instantly, often saving 500ms or more per view. Fix: free with LiteSpeed Cache or WP Super Cache.
- Oversized images (hurts LCP). Images are usually the heaviest part of a page – a single unoptimised hero image can weigh several megabytes and take seconds on mobile data. Compression plus WebP cuts file sizes dramatically with no visible difference. Fix: ShortPixel, or Squoosh before upload.
- Render-blocking JavaScript and CSS (hurts FCP and TBT). Browsers pause rendering until each blocking file loads. Deferring non-critical JavaScript and loading CSS asynchronously gets pixels on screen sooner. Fix: WP Rocket or LiteSpeed handle this automatically.
- Too many heavy plugins (hurts TBT). Every plugin adds PHP time, database queries, and scripts – many load on every page whether needed or not. A plugin audit is free and often the single biggest interactivity win. Fix: remove unused plugins, replace the heaviest.
- No CDN for static files (hurts LCP). A CDN serves your images, CSS, and JavaScript from servers near each visitor. It helps most when your audience is spread across regions – less critical if your host and visitors are both in India. Fix: Cloudflare or BunnyCDN – see the plugins section below.
- Oversold shared hosting (hurts TTFB – inconsistently). Budget shared hosts pack many sites onto one server. Yours runs fine when neighbours are quiet, then slows sharply under load – showing up as wildly different TTFB between test runs. Fix: hosting with guaranteed resources – VPS, cloud, or managed.
Priority rule – confirm the server first, then fix it first. Run the test 2–3 times. If even your lowest TTFB reading stays above 600ms, fix hosting before buying any plugin – no plugin compensates for a server thousands of kilometres from your visitors. If only your highest reading is slow, caching is your fix, not a migration.
WordPress plugins to improve your website speed
Once your TTFB is under 400ms – meaning your server location is good – the next step is using plugins to optimise LCP, TBT, CLS and FCP. Each plugin below directly addresses specific Core Web Vitals metrics. The improvement percentages are based on our tests on 50+ Indian WordPress sites.
Fixes that work on any site
These are server and DNS settings rather than plugins, so they apply whether your site is WordPress, hand-built, or on a hosted platform. Most are changed in your hosting control panel, or by asking your host.
| Fix | What it changes | Where |
|---|---|---|
| Page caching | Stores the finished page so the server stops rebuilding it for every visitor. This is the single biggest change for most slow servers. | LiteSpeed servers have it built in (enable LSCache in the control panel). On nginx it is FastCGI cache; on Apache, Varnish or mod_cache. Ask your host which applies — the answer depends on the web server, not your site. |
| Compression | Sends pages compressed, usually cutting transferred size by about three quarters. Costs nothing and changes nothing visible. | A server setting: Brotli or gzip. Most control panels expose it directly; otherwise one line of server configuration. |
| A CDN | Keeps copies of images, stylesheets and scripts on servers near your visitors, so those files travel a short hop instead of a long one. It does not speed up your server building pages — unless the page itself is cached at the edge, every visit still waits for your origin. | Set up at your DNS provider or through the CDN’s own dashboard. Worth it when your server is far from your visitors; of little use when it is already close. |
| Removing redirect chains | Each redirect is a full trip to the server and back before the real page starts. Two hops can add half a second on a first visit. | Point the first address straight at the final one — usually one rule in the server config or control panel. |
| Nameserver speed | Only first-time visitors pay this, and only when their resolver has not seen your domain recently. | If your nameservers run on your own domain, they are usually the same machine as your site — so this is a hosting question, not a DNS one. Moving to a different DNS provider means copying every record first: website, email, verification. Anything missed takes the site or email down. |
| A server closer to your visitors | Distance is paid on every single request and no setting removes it. A server in India answers Indian visitors in under 30ms; one overseas can cost 150ms or more before any work begins. | A migration, so it is the last resort — but the only real fix when the round trip is high and most of your visitors are in one country. |
Not sure which applies? The result above names the one that is costing you most. Start there — the others rarely matter until it is fixed.
Website speed test – questions answered
The most common questions about website performance testing and improving website speed in India.
How do I run a free website speed test?
Use the free website speed test tool at the top of this page powered by Google PageSpeed Insights API and HG Node, Mumbai. Enter your website URL, select Mobile or Desktop, click Test Speed. You will get your Google Performance Score from 0 to 100, all Core Web Vitals metrics including LCP, FCP, TBT and CLS from google insights, server TTFB from HG nodes Mumbai, and specific opportunities to fix speed problems identified by Google. No login or signup required. The test typically takes 10–25 seconds to complete.
What is a good website speed test score?
A Google PageSpeed score of 90 to 100 is good. A score of 50 to 89 needs improvement. A score below 50 is poor and is likely harming your Google search rankings. For Indian websites specifically, aim for a mobile score of 70 or higher as a minimum – because Google uses mobile-first indexing to determine your rankings on Google.co.in and 75% of Indian users browse on mobile. For TTFB, under 400ms is good for Indian visitors; Past 600ms your hosting needs attention – that’s Google’s Lighthouse lab threshold, and the point where visitors start noticing the wait.
Why is my website slow in India but fast elsewhere?
Your website is slow in India but fast elsewhere because your server is hosted outside India – likely in the US or Europe. A server in the US adds 80–200ms of one-way network latency, pushing TTFB to 800 – 1500ms for Indian visitors versus under 200ms for US visitors. The fix is switching to hosting with an Indian data centre. find the Indian hosting benchmark data to decide the fastest and best host in India.
What is TTFB and why does it matter?
TTFB (Time to First Byte) is the time from a browser sending a request to receiving the first byte of data from the server. For Indian websites, TTFB is primarily determined by server location. Hostinger India delivers 140ms TTFB, Bigrock delivers 123ms TTFB, while US-hosted sites deliver 800–1,500ms TTFB to Indian visitors. High TTFB directly increases your LCP score, which carries 25% of your overall PageSpeed score. Google’s threshold for good TTFB is under 800ms — but for Indian websites, under 400ms is the practical target.
Which plugins improve website speed in India?
The best WordPress plugins for improving your website speed test score in India are: WP Rocket (best all-in-one, ₹3,800/yr, fixes LCP+TBT+FCP), LiteSpeed Cache (free, best for LiteSpeed hosts like Hostinger and MilesWeb), ShortPixel (image compression to WebP, reduces LCP by 1–3s), Cloudflare (free CDN with Mumbai PoP, reduces LCP and FCP), and BunnyCDN ($0.01/GB, paid CDN with Mumbai PoP). Important: fix your hosting TTFB first if it is above 600ms – no plugin compensates for a server that is geographically distant from your Indian audience.
How often should I run a website speed test?
Run a website speed test at minimum once per month, and additionally after any of these events: adding a new WordPress plugin, updating your theme, adding new images or content types, changing your hosting provider, adding third-party scripts (chat widgets, analytics, tracking pixels), or after any major WordPress or WooCommerce updates. Score changes of more than 10 points between tests indicate a significant change in performance that requires investigation. Set a calendar reminder to run the test at the same time each month for consistent comparison.
Does website speed affect Google rankings?
Yes. Google uses Core Web Vitals – LCP, interactivity, and visual stability (CLS) – as a ranking signal, part of its page experience assessment. A slow site can rank below a faster competitor with similar content, and the effect is strongest on mobile, where most Indian searches happen through mobile-first indexing. Speed won’t outrank genuinely better content, but between two comparable pages, the faster one usually wins. Improving your LCP and reducing your server response time (TTFB) supports both your ranking and the experience of visitors who arrive.
Why is my website so slow?
A slow website almost always traces to one of a few causes: a server that’s slow to respond (high TTFB, often from hosting located far from your visitors or a lack of caching), heavy unoptimised images, too much render-blocking JavaScript, or an overloaded shared hosting plan. The fastest way to find your specific cause is to run the test at the top of this page – it separates page-code problems (fixed with caching and optimisation) from hosting problems (fixed with a faster server), so you know exactly where to start instead of guessing.
Why is my website slow on mobile but fast on desktop?
Mobile is tested on a simulated mid-range phone over a throttled 4G connection, while desktop assumes a fast machine and wired broadband – so the same site scores lower on mobile by design. The usual culprits are heavy JavaScript (phones have far less processing power, so scripts that are instant on desktop block a phone’s main thread), large images served at full size to small screens, and render-blocking resources. Since Google uses mobile-first indexing and most Indian traffic is mobile, your mobile score is the one that matters most for rankings.
Built by people with 13+ years of hands-on experience in the Indian web hosting industry - including those who've measured TTFB from Mumbai with Google PageSpeed data. We explain what a result means, its root cause and how to fix it.
Most page speed tests give you a score. This tool Interprets the result for you on what is fault.
✕ One Lighthouse score and a list of raw warnings
✕ Measured from a US or EU datacenter
✕ You guess whether it’s your website or your hosting
✓ Google PageSpeed plus an independent server check from Mumbai
✓ Separates page-code problems from hosting problems
✓ Each problem gets its specific fix – plugins, caching, or hosting
The Hosting Garage Built in India website speed test tool measures two things: how well your page is built (Google PageSpeed score and Core Web Vitals) and how fast your hosting responds (TTFB measured from Mumbai). Results are interpreted for you – verdict, root cause, and the specific fix – Also recommendation of best hosting in India from a independent 90-day benchmark data from host Latency.
Is your site slow? – Install a caching plugin or Introspect your hosting
Not sure which one you need? Run the test – it tells you ↑