Website speed test from India

Measure load time, TTFB and page size as seen from within India.

Have feedback or an idea for this tool?

Why test website speed from India?

Page speed depends heavily on distance, so a site hosted far away feels slower to Indian visitors no matter how well it is built. This test loads a URL from within India and reports the time to first byte, the total load time and the size of the page transferred, which together show how the site actually performs for a local audience rather than for a server in the United States or Europe. Enter a URL, with or without the https prefix, to measure it. A high time to first byte usually points to server distance or slow backend processing, while a large transfer size points to heavy images or scripts. Use it to compare hosting locations, to justify moving to Indian infrastructure, or to find the pages that need optimisation for local users.

Key facts

Time to first byte (TTFB) is the gap between a request going out and the first byte of the response arriving, covering DNS, the TCP and TLS handshake, the network round trip and server processing.
A TTFB under 200 ms is fast, 200 to 500 ms is acceptable, and consistently above 500 to 600 ms is worth investigating.
Google treats a TTFB of around 800 ms at the 75th percentile as the point where it starts to harm Largest Contentful Paint.
Network latency is bounded by physical distance, so a round trip from India to a US or European server is inherently longer than to a server in Mumbai, Delhi or Chennai.
Interaction to Next Paint (INP) replaced First Input Delay as a Core Web Vital in March 2024, with a good INP being under 200 ms.

What this test measures

This tool requests your URL from a server located inside India and reports three raw numbers: time to first byte (TTFB), total load time, and page size in bytes. It measures how your server responds to an Indian visitor, not how it responds from a US or European probe.

TTFB is the gap between the request going out and the first byte of the response coming back. It bundles DNS resolution, the TCP and TLS handshake, the network round trip, and how long your server or application takes to build the response. Total load time is how long the full document took to arrive. Page size is the number of bytes transferred, which matters most on India's mobile networks where bandwidth is uneven.

Because the request originates in India, the network round-trip component reflects the real distance between an Indian user and wherever your site is hosted. A site on a US East Coast server can add 200 ms or more of round-trip latency for a Chennai or Delhi visitor before your application does any work at all.

What counts as a good TTFB

As a working guide, a TTFB under 200 ms is fast, 200 to 500 ms is acceptable, and consistently above 500 to 600 ms is worth investigating. Google's own guidance treats around 800 ms at the 75th percentile as the point where TTFB starts to hurt Largest Contentful Paint.

A high TTFB has two common causes and it helps to separate them. The first is server processing: slow database queries, no caching, an overloaded VM, or a cold serverless function. The second is distance: even a perfectly fast server adds latency for every kilometre between it and the user. If your server-side processing is quick but TTFB is still high from India, distance is usually the culprit.

Run the test a few times. A single reading can be skewed by a cold cache or a one-off network blip; three or four runs give you a truer picture of the typical response.

Why server location matters for Indian visitors

Network latency is bounded by the speed of light and the path packets take through undersea cables and peering points. A round trip from India to a server in Virginia or Frankfurt is physically longer than a round trip to a server in Mumbai, and no amount of application tuning removes that floor.

For Indian audiences, hosting in an India region (Mumbai, Delhi or Chennai points of presence) or putting a CDN edge inside India cuts the round trip dramatically. A CDN caches static assets like images, CSS and JavaScript at an edge near the user, so those bytes travel a short distance even if your origin server sits abroad. Dynamic responses still hit the origin, so for API-heavy or logged-in pages, the origin's location keeps mattering.

ServerCake runs infrastructure inside India with rupee billing, so for an India-first audience the origin round trip is short by default. That is one honest lever among several - CDN, caching and page weight are the others.

Uptime / SLA calculator

Quick server test vs a full Lighthouse audit

This is a fast server-response test, not a full front-end audit. It tells you how quickly bytes leave your server and reach India, which is the foundation everything else sits on. It does not render the page, run JavaScript, or measure how the layout paints in a browser.

For the rendering side you need Core Web Vitals, which Google measures on real visits: Largest Contentful Paint (LCP, how fast the main content appears, good is under 2.5 s), Interaction to Next Paint (INP, how responsive the page feels to input, good is under 200 ms), and Cumulative Layout Shift (CLS, how much the layout jumps, good is under 0.1). Note that INP replaced First Input Delay as a Core Web Vital in March 2024.

A Lighthouse or PageSpeed Insights audit covers that rendering layer - render-blocking resources, image formats, unused JavaScript, and lab-simulated LCP. Use this tool first to confirm the server responds quickly from India, then run Lighthouse to fix what happens after the bytes arrive. A slow TTFB will drag down LCP no matter how well the front end is built, so it is the right thing to check first.

Glossary

TTFB: Time to first byte (TTFB) is the gap between a request going out and the first byte of the response arriving. It bundles DNS, the TCP and TLS handshake, the network round trip and server processing time.
Network latency: Network latency is the time a packet takes to travel between two points, bounded by physical distance and the path through undersea cables and peering points. A round trip from India to a US or European server is inherently longer than to a server in Mumbai.
Page weight: Page weight is the total number of bytes a page transfers, including HTML, images, fonts, CSS and JavaScript. Heavy pages load slowly on India's uneven mobile networks, so trimming assets is often the biggest speed win.
Largest Contentful Paint: Largest Contentful Paint (LCP) is a Core Web Vital that measures how quickly a page's main content appears, with under 2.5 seconds considered good. A slow TTFB drags LCP down regardless of front-end tuning.
Interaction to Next Paint: Interaction to Next Paint (INP) is a Core Web Vital measuring how responsive a page feels to user input, with under 200 ms considered good. It replaced First Input Delay as a Core Web Vital in March 2024.
CDN edge: A CDN edge is a cache near the user that serves static assets like images, CSS and JavaScript over a short distance. Placing an edge inside India cuts the round trip for Indian visitors, though dynamic responses still reach the origin.

Questions, answered.

Why test speed from India specifically?+

If your audience is in India but your site is hosted far away, distance adds network latency that global test tools running from the US or Europe never show you. This test measures load time from a server inside India, so you see what your Indian visitors actually get.

What is TTFB and why does it matter?+

Time to first byte is how long the server takes to start responding after a request, covering DNS, the TLS handshake, the network round trip and your server's processing time. A high TTFB delays everything that follows, so it drags down the whole page including your Largest Contentful Paint score.

What is a good TTFB?+

As a rule of thumb, under 200 ms is fast, 200 to 500 ms is acceptable, and consistently above 500 to 600 ms is worth investigating. Google treats around 800 ms at the 75th percentile as the point where TTFB starts to harm your Core Web Vitals.

What do the total time and page size tell me?+

Total time is how long the page took to finish loading, and page size is how many bytes it transferred. Large pages are slow on India's mobile networks, so trimming images, fonts and scripts often gives the biggest speed win.

How does server location affect speed for Indian users?+

Network latency is bounded by physical distance, so a round trip from India to a US or European server is inherently longer than to a server in Mumbai, Delhi or Chennai. Hosting in an India region or using a CDN with an Indian edge cuts that round trip and lowers TTFB for Indian visitors.

How is this different from Lighthouse or PageSpeed Insights?+

This is a quick server-response test: it measures how fast bytes leave your server and reach India. Lighthouse and PageSpeed Insights render the page and measure the front-end Core Web Vitals - LCP, INP and CLS. Use this tool first to confirm the server is fast from India, then run Lighthouse to fix what happens after the bytes arrive.

Does this measure Core Web Vitals like LCP, INP and CLS?+

No. This test reports server-response metrics (TTFB, total load time and page size), not the rendering metrics. LCP, INP and CLS are measured in a real browser on actual visits, so use a field-data tool like PageSpeed Insights or Chrome's CrUX report for those. A slow TTFB here, though, will still hurt your LCP.

My site is slow from India. What should I do?+

First separate the two causes: run the test a few times to see if TTFB is high because of slow server processing (add caching, tune queries) or because of distance. If distance is the issue, host closer to your users or add an Indian CDN edge. ServerCake runs in India with rupee billing, so for an India-first audience the origin round trip is short by default.

Built by the ServerCake team

Cloud that speaks India.

These tools run on ServerCake infrastructure in India. When our cloud opens, you get VMs and managed databases priced in ₹, billed with GST, on India-resident infrastructure. Reserve your spot for early access.

Reserve your spot

More tools

Browse all tools