Website review, no card needed
economictimes.com website review
Visit site (opens in a new tab)Reviewed 12 October 202645 issues · 94 checks
This review found 45 issues worth fixing on economictimes.com, 13 of them high impact, across 94 checks. The most urgent: main-thread work: 14.3 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 1.9 s |
| Apr 25, 2026 | 1.9 s |
| May 2, 2026 | 1.9 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 305 ms |
| Apr 25, 2026 | 301 ms |
| May 2, 2026 | 304 ms |
| May 9, 2026 | 312 ms |
| May 16, 2026 | 315 ms |
| May 23, 2026 | 315 ms |
| May 30, 2026 | 314 ms |
| Jun 6, 2026 | 316 ms |
| Jun 13, 2026 | 319 ms |
| Jun 20, 2026 | 324 ms |
| Jun 27, 2026 | 326 ms |
| Jul 4, 2026 | 324 ms |
| Jul 11, 2026 | 327 ms |
| Jul 18, 2026 | 334 ms |
| Jul 25, 2026 | 339 ms |
| Aug 1, 2026 | 350 ms |
| Aug 8, 2026 | 356 ms |
| Aug 15, 2026 | 356 ms |
| Aug 22, 2026 | 353 ms |
| Aug 29, 2026 | 348 ms |
| Sep 5, 2026 | 344 ms |
| Sep 12, 2026 | 345 ms |
| Sep 19, 2026 | 346 ms |
| Sep 26, 2026 | 350 ms |
| Oct 3, 2026 | 353 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.7 s
1.4 s
2.1 s
2.8 s
3.6 s
4.3 s
5.0 s
5.7 s
Speed
Main-thread work: 14.3 s
A phone's processor spends 14.3 s on main-thread work while loading, 7.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 31
31/100Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,175 HTML elements
The page has 6,175 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (economictimes.com, Google/Doubleclick Ads and Pubmatic and others), adding 2.8 MB and 3.4 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
1.0 MB158 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
economictimes.com adds 863 ms
863 mseconomictimes.com costs a phone 863 ms of main-thread work and 668 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
800 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Avoid multiple page redirects
756 msThe page goes through 1 redirect before it starts loading, costing about 756 ms. Link and advertise the final URL directly.
Google/Doubleclick Ads adds 559 ms
559 msGoogle/Doubleclick Ads costs a phone 559 ms of main-thread work and 599 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Pubmatic adds 549 ms
549 msPubmatic costs a phone 549 ms of main-thread work and 208 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Rubicon Project adds 493 ms
493 msRubicon Project costs a phone 493 ms of main-thread work and 169 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Google Tag Manager adds 331 ms
331 msGoogle Tag Manager costs a phone 331 ms of main-thread work and 488 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 266 ms. During a long task the page ignores taps.
Document request latency
100 msThe HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Legacy JavaScript
63 KiBPolyfills for old browsers add 63 KiB JavaScript that modern phones do not need.
Minify JavaScript
21 KiB21 KiB could be saved by minifying JavaScript.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 108 ms
108 msYour server sent the HTML in 108 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Time to Interactive: 54.8 s
54.8 sThe page becomes fully interactive after 54.8 s. Good is under 3.8 s.
Speed Index: 9.9 s
9.9 sVisually, the page fills in at 9.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.8 s
1.8 sScripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 5.2 s
5.2 sYour largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Image for Trump may bend Russian oil”.
Real-user INP: 355 ms
355 msReal visitors wait 355 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.201
0.201The layout shifts by 0.201 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 305 ms to 353 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 618 ms
618 msReal visitors wait 618 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 5.0 MB in 1,198 requests
5.0 MBYour homepage downloads 5.0 MB in 1,198 requests on a phone: scripts 3.2 MB (120), other files 748 KiB (597) and HTML 409 KiB (122). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
india-awaits-how-trump-will-route-diesel-buy-from-russia.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.4 g of CO₂ per visit
1.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.42 g of CO₂e: 170.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
10 tap targets too small
10 tap targets are too small or too close together to hit reliably with a finger.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (6 elements)
Scrollable region must have keyboard access: 6 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (196 elements)
All page content should be contained by landmarks: 196 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
ARIA role should be appropriate for the element (10 elements)
ARIA role should be appropriate for the element: 10 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (10 elements).
2 checks passed
Every image has alt text
All 304 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (109 characters)
Your title is 109 characters, so Google will cut it off around 60: “Business News Live, Share Market News - Read Latest Finance News, IPO, Mutual Funds News …”.
Meta description is long (214 characters)
Your meta description is 214 characters; Google truncates after about 160, so the end of your pitch is cut.
10 links crawlers can't follow
10 links have no real href, so search engines can't follow them.
712 internal links, 71 external
The homepage links to 712 pages on economictimes.com and 71 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Trump may bend Russian oil rules for himself & India is watching”.
Canonical URL set
The canonical URL is https://economictimes.indiatimes.com/.
Structured data in place
Structured data found: BreadcrumbList, ItemList, MobileApplication, NewsMediaOrganization and ViewAction.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://economictimes.indiatimes.com/companylisting.cms.
AI search readiness
No llms.txt
There is no https://economictimes.indiatimes.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (7,385 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 198 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
58 small tap targets
58 of 96 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
53 third-party cookies
53 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“The Topics API is deprecated and will be removed in a future release.”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Error: Invalid Discounting engine request - without SSOID or GRX”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 4,830 words of copy
The homepage carries about 4,830 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us” and “OPEN IN APP Get Free Trial”.
4 calls to action
The homepage has 4 calls to action, for example “How can Indians get a TRC?”, “Subscribe to ET Prime” and “Contact Us”.
2 short forms
2 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 2 customer or partner logos, a star rating and 11 trust badges.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 4 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
18 cookies set on arrival
18Opening the homepage sets 18 cookies, 3 of them by other companies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
72 other companies contacted
Loading the homepage contacts 72 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at economictimes.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on economictimes.com, including 24 speed issues, 3 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.