www.airtel.in speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:18 UTC. Grade B (87/100), with the screenshots, the timings and the fixes that matter.

https://www.airtel.in/

20 October 2026 at 14:18 UTC · Free test · report pt_098466002375
Grade
B
87/100
Performance93/100
Structure79/100

12 audit(s) passed, 4 need work

First byte (TTFB)457 msmeasured from this server
Fully loaded1.56 sfirst byte + slowest asset
Requests7document + assets
Page weight780.7 KBcompressed transfer
HTML document1.2 KBgzip
ProtocolHTTP/3Apache
Third-party779.5 KBother hosts

Where the first byte went

  • DNS lookup 50 ms 11%
  • TCP connect 28 ms 6%
  • Server wait 379 ms 83%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First byteslower than 51% of 4,999 pages tested here457 ms against a median of 448 ms
Page weightheavier than 55% of 4,999 pages tested here780.7 KB against a median of 650.3 KB
Fully loadedfaster than 66% of 4,999 pages tested here1.56 s against a median of 1.84 s
Requestssends fewer requests than 91% of 4,999 pages tested here7 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

  • The first byte arrived in 457 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 780.7 KB over 7 request(s), which is lean. Images files are 77% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 100% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element painted at 2.10 s, inside the 2.5 s Google calls good.
  • The main thread was blocked for 58 ms in total, which is not enough to feel.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint2.10 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time58 mslong tasks during load
First contentful paint424 msfirst content on screen
Browser page weight5.36 MB32 request(s), scripts included
Failed requests8blocked or unreachable
Largest contentful paint2.10 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time58 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 4 requests
600.4 KB 77%
Javascript 1 request
175.3 KB 22%
Css 1 request
3.7 KB 0%

Transfer size, compressed as sent. 7 request(s) in total, 780.7 KB across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 457 ms. Of that, 379 ms was the server thinking and 78 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Image delivery and format

high impact

1 image(s) over 200 KB and 1 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Third-party weight

medium impact

1 third-party host(s) serve 779.5 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Waterfall

Slowest requests

IMAGESassets.airtel.in/static-assets/home-recast/images/home-…
1.11 s
IMAGESassets.airtel.in/static-assets/new-home/img/favicon.ico
589 ms
IMAGESassets.airtel.in/static-assets/new-home/img/favicon-32x…
391 ms
JAVASCRIPTassets.airtel.in/static-assets/home-recast/static/js/ma…
368 ms
CSSassets.airtel.in/static-assets/home-recast/static/css/m…
345 ms
IMAGESassets.airtel.in/static-assets/new-home/img/favicon-16x…
341 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://assets.airtel.in/static-assets/home-recast/images/home-banner-1.png 3rd partyimages2001.11 s599.2 KB
https://assets.airtel.in/static-assets/new-home/img/favicon.ico 3rd partyimages200589 ms306 B
https://assets.airtel.in/static-assets/new-home/img/favicon-32x32.png 3rd partyimages200391 ms487 B
https://assets.airtel.in/static-assets/home-recast/static/js/main.c51643c4.js 3rd partyjavascript200368 ms175.3 KB
https://assets.airtel.in/static-assets/home-recast/static/css/main.e8a21776.css 3rd partycss200345 ms3.7 KB
https://assets.airtel.in/static-assets/new-home/img/favicon-16x16.png 3rd partyimages200341 ms487 B
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.