www.indiatoday.in speed test — 20 Oct 2026

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

https://www.indiatoday.in/

20 October 2026 at 13:43 UTC · Free test · report pt_027eb7143f7c

Re-test this page Test your own site

Grade

89/100

Performance89/100

Structure88/100

12 audit(s) passed, 4 need work

First byte (TTFB)460 msmeasured from this server

Fully loaded2.56 sfirst byte + slowest asset

Requests26document + assets

Page weight518.9 KBcompressed transfer

HTML document210.1 KBbr

ProtocolHTTP/3itgdweb

Third-party58.4 KBother hosts

Where the first byte went

DNS lookup 74 ms 16%
TCP connect 23 ms 5%
Server wait 363 ms 79%

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 here460 ms against a median of 448 ms

Page weightlighter than 57% of 4,999 pages tested here518.9 KB against a median of 650.5 KB

Fully loadedslower than 75% of 4,999 pages tested here2.56 s against a median of 1.84 s

Requestssends more requests than 100% of 4,999 pages tested here26 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 460 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 518.9 KB over 26 request(s). Images files are 60% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 532 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.006), so nothing jumps under the reader's cursor.
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.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Desktop screenshot of www.indiatoday.in — **Desktop** 1366 × 768 · 299.8 KB · page is 6000 px tall

Mobile screenshot of www.indiatoday.in — **Mobile** 390 × 844 · 146.8 KB · page is 6000 px tall

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 paint532 msgood is under 2.5 s

Cumulative layout shift0.006under 0.1 is stable

Total blocking time58 mslong tasks during load

First contentful paint532 msfirst content on screen

Browser page weight417.5 KB19 request(s), scripts included

Largest contentful paint532 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.006

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 25 requests

308.8 KB 60%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 460 ms. Of that, 363 ms was the server thinking and 97 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.

Cache static assets

medium impact

1 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

HTML document size

medium impact

The document transfers 210.1 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.

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.