Skip to content
Audit Complete

Results for https://indianexpress.com

Visit site
Netherlands Netherlands · Amsterdam Completed: Apr 15, 2026 23:21 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
D68

Site Health

Score: 68 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

Several regulatory requirements are not yet met.

Missing metadata means poor previews on social media and search.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Facebook sites average 72
At average
Better than 6% of Facebook sites See full Facebook benchmark →
Google Search Console sites average 73
At average
Better than 5% of Google Search Console sites See full Google Search Console benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure
5

No favicon or icon links detected

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Favicon & Branding
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Findianexpress.com)](https://beavercheck.com/results/56e016e5-d823-4162-a9fc-c83a7d23c9db)
<a href="https://beavercheck.com/results/56e016e5-d823-4162-a9fc-c83a7d23c9db"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Findianexpress.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Findianexpress.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.
C
Could reach Estimate based on resolving critical issues

Return on Investment

₹6,750 investment → ₹7,332/month returns + INR 2,500,000,000 risk avoided

Payback period: < 1 month First-year ROI: +1203%

Investment

₹6,750

4h · 5 findings

Monthly returns

₹7,332 /mo

~₹87,982 / year

  • Conversions recovered ₹7,269
  • Bandwidth savings ₹63

Regulatory risk avoided

INR 2,500,000,000

if kept compliant

  • DPDP Act INR 2,500,000,000

Payback period

0 12mo 24mo

₹2,250 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

₹6,750

4.5 developer hours at ₹1500/hr

Based on India rates (₹1500/hr)

Quick wins
₹2,250 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

₹208,333,396 / month at risk

~₹2,500,000,757 / year if left unfixed

Compliance Risk

₹2,500,000,000

DPDP Act
  • No privacy policy link detected
    DPDP Act: INR 10,000 – INR 2,500,000,000
  • Trackers detected but no cookie policy found
    DPDP Act: INR 10,000 – INR 2,500,000,000
  • Trackers detected but no privacy policy found
    DPDP Act: INR 10,000 – INR 2,500,000,000

+1 more

Bandwidth Waste

₹63 /mo

9461.7 MB/mo × 6.667 INR/GB

  • Optimize transfer: save ~946 KB per page load
    Saves ₹63/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

46
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
92
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.98 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.85 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

6.39 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.243

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

6.34 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

27.29 s

Detailed Report

Audit breakdown by category with detailed findings.

46

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.243249] map[node:map[boundingRect:map[bottom:1914 height:1238 left:0 right:412 top:677 width:412] lhId:page-1-DIV nodeLabel:ADVERTISEMENT INDIA Govt plan: Keep south share unchanged in LS, list each stat… path:1,HTML,1,BODY,4,MAIN,2,DIV selector:body.home > main#home-main-content > div.wp-block-template-part snippet:<div class="wp-block-template-part"> type:node] score:0.243249]]
headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.011054] map[node:map[boundingRect:map[bottom:1914 height:1238 left:0 right:412 top:677 width:412] lhId:page-1-DIV nodeLabel:ADVERTISEMENT INDIA Govt plan: Keep south share unchanged in LS, list each stat… path:1,HTML,1,BODY,4,MAIN,2,DIV selector:body.home > main#home-main-content > div.wp-block-template-part snippet:<div class="wp-block-template-part"> type:node] score:0.011054 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/ptserif/v19/EJRVQgYoZZY2vCFuvAFWzr-_dSb_.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/roboto/v51/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/ptserif/v19/EJRSQgYoZZY2vCFuvAnt66qSVyvVp8NA.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/roboto/v51/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2]]] type:subitems]]]

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:47.601 source:map[type:text value:[unattributed]]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: donald trump, china, iran, hormuz
path: 1,HTML,1,BODY,4,MAIN,1,DIV,0,SECTION,0,DIV,0,DIV,0,DIV,2,FIGURE,0,A,0,IMG
selector: div.breking-big-text > figure.breking-big-img > a > img
snippet: <img src="https://images.indianexpress.com/2026/04/donald-trump-AP-File-photo-expres…" alt="donald trump, china, iran, hormuz" width="440" height="248" pinger-seen="true">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
new Bills, Delimitation Bill 2026, Union Territories Laws (Amendment) Bill 2026… article.topblockNews__featured > figure.topblockNews__featuredImage > a > img
/2026/04/lok-sabha_20260414171335_20260415212558.jpg?w=62096.2 KiB61.1 KiB
No junk food in govt schools, only 2 cooked meals from school farms article.o-express-premium__item > a.article_url > figure.card-image > img.lazyloading
/2026/04/Students-with-a-food-educator-at-the-farm-of-a-g...10.3 KiB6.2 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
ADVERTISEMENT INDIA Govt plan: Keep south share unchanged in LS, list each stat… body.home > main#home-main-content > div.wp-block-template-part
0.243
ADVERTISEMENT INDIA Govt plan: Keep south share unchanged in LS, list each stat… body.home > main#home-main-content > div.wp-block-template-part
0.011

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
indianexpress.com/3.9 s244 ms76 ms
Unattributable2.0 s553 ms0.0 ms
cdn.taboola.com/libtrc/indianexpress-indianexpress/loader.js1.7 s1.4 s232 ms
/pagead/managed/js/gpt/m202604100101/pubads_impl.js910 ms786 ms94 ms
/f/AGSKWxX7AweMoKQ-keK7dmaNShbpRBrBPfQCJgmXjTXNSREOb5WTkm...769 ms365 ms67 ms
www.googletagmanager.com/gtag/js?id=G-HEQWL2KPC5657 ms553 ms92 ms
ads.pubmatic.com/AdServer/js/pwt/156021/7083/pwt.js574 ms470 ms83 ms
fundingchoicesmessages.google.com/i/1050432?ers=3566 ms520 ms34 ms
cdn.moengage.com/webpush/moe_webSdk.min.latest.js503 ms370 ms60 ms
pm-widget.taboola.com/indianexpress-indianexpress/pmk-20220605.8.js475 ms456 ms13 ms
www.googletagmanager.com/gtag/js?id=AW-11033859954392 ms296 ms64 ms
/signals/config/444470064056909?v=2.9.298&r=stable&domain...376 ms309 ms63 ms
www.googletagmanager.com/gtm.js?id=GTM-PGQG2HFB348 ms263 ms71 ms
/wp-content/themes/indianexpress/js/evolok/min/ev-em.min....330 ms235 ms23 ms
/wp-content/plugins/ie-newsblock-builder/assets/js/ie-hom...298 ms208 ms3.3 ms
/wp-content/themes/indianexpress/js/evolok/min/ev-dab.min...270 ms248 ms18 ms
connect.facebook.net/en_US/fbevents.js220 ms163 ms55 ms
c2.taboola.com/nr/indianexpress-indianexpress/newsroom.js137 ms119 ms14 ms
/wp-content/themes/indianexpress/js/min/city-section.js?v...133 ms123 ms1.2 ms
securepubads.g.doubleclick.net/tag/js/gpt.js122 ms102 ms19 ms
static.chartbeat.com/js/chartbeat.js116 ms100 ms6.4 ms
www.googletagmanager.com/gtag/js?id=AW-11033859954&cx=c&gtm=4e64e1103 ms37 ms65 ms
/wp-content/themes/indianexpress/js/min/ie-events-all.js?...82 ms71 ms6.4 ms
accounts.google.com/gsi/client78 ms33 ms39 ms
accounts.google.com/gsi/client?ver=2026041572 ms30 ms41 ms
accounts.indianexpress.com/swagger-js/v5.0.0/sdk.min.js?v=08082022.162 ms30 ms11 ms
/wp-content/themes/indianexpress/js/evolok/min/ev-custom-...57 ms42 ms12 ms
/wp-content/themes/indianexpress/js/ie-moengage-custom-sc...56 ms52 ms2.7 ms
apis.google.com/js/platform.js?onload=renderButton51 ms39 ms11 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation8.7 s
Style & Layout2.4 s
Other2.2 s
Script Parsing & Compilation1.3 s
Rendering688 ms
Parse HTML & CSS412 ms
Garbage Collection230 ms

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
System will change when MLAs trust govt schools with their children: Bains div.epaper-panel > a > figure.round-img > img.center-image
/wp-content/plugins/ie-newsblock-builder/src/blocks/ie-ar...

More information about the performance of your application. These numbers don't directly affect the Performance score.

Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 365 user timings
Avoid long main-thread tasks 20 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 90 ms
Server Backend Latencies 400 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 10 ms
INP breakdown
Avoid non-composited animations
92

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn more div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label
List of partners. div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog

These are opportunities to improve the legibility of your content.

Best practices

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Select elements have associated label elements.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Links are distinguishable without relying on color.
`<object>` elements have alternate text
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
73

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
Delimitation div.o-commonTopnews__rhs > figure.o-newsImage > a.article_url > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...440 x 248 (1.77)97 x 54 (1.80)
Royal Challengers Bengaluru div.o-matchesbx__card-team > a > div.o-matchesbx__card-flag > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Lucknow Super Giants div.o-matchesbx__card-team > a > div.o-matchesbx__card-flag > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Chennai Super Kings div.o-matchesbx__card-team > a > div.o-matchesbx__card-flag > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Kolkata Knight Riders div.o-matchesbx__card-team > a > div.o-matchesbx__card-flag > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
mumbai, mumbai metro, mumbai news, div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
Will drop all false cases against Gorkha leaders: Amit Shah in Darjeeling div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
Pune div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
chandigarh, cbse div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
morbi, ceramic, div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
CM Yogi div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
VIjay div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
Anudeep Katikala div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
bengaluru man-murder mother div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting
Topics
Specifying overflow: visible on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/shared-element-transitions/blob/main/debugging_overflow_on_images.md.

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
[GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token.
A bad HTTP response code (403) was received when fetching the script.
A bad HTTP response code (403) was received when fetching the script.
A bad HTTP response code (403) was received when fetching the script.
Not signed in with the identity provider.
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`
robots.txt is valid

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

65
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
92
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

582 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

815 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

803 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.009

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

3.24 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

5.67 s

Detailed Report

Audit breakdown by category with detailed findings.

65

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:128.199 source:map[type:text value:[unattributed]]] map[reflowTime:106.435 source:map[column:449 line:19 type:source-location url:/_/mss/boq-content-ads-contributor/_/js/k=boq-content-ads-contributor.ContributorServingResponseClientJs.en_US.WQSjKtkEYiM.es5.O/d=1/exm=kernel_loader,loader_js_executable/ed=1/rs=AJlcJMwIx8fty2eKv_YgAn45g2tx1JaJ2w/m=web_iab_tcf_v2_wall_executable urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
new Bills, Delimitation Bill 2026, Union Territories Laws (Amendment) Bill 2026… article.topblockNews__featured > figure.topblockNews__featuredImage > a > img
/2026/04/lok-sabha_20260414171335_20260415212558.jpg?w=680101.6 KiB68.1 KiB
donald trump, china, iran, hormuz div.breaking-flex > figure.breking-big-img > a > img
images.indianexpress.com/2026/04/donald-trump-AP-File-photo-express-5.jpg?w=82031.3 KiB5.1 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-1-IMG
nodeLabel: donald trump, china, iran, hormuz
path: 1,HTML,1,BODY,5,MAIN,1,DIV,1,SECTION,0,DIV,0,DIV,1,FIGURE,0,A,0,IMG
selector: div.breaking-flex > figure.breking-big-img > a > img
snippet: <img src="https://images.indianexpress.com/2026/04/donald-trump-AP-File-photo-expres…" alt="donald trump, china, iran, hormuz" width="750" height="422" pinger-seen="true">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/signals/config/444470064056909?v=2.9.298&r=stable&domain...1200.0 s126.3 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.4 KiB
c.amazon-adsystem.com/aax2/apstag.js3600.0 s90.9 KiB
ads.pubmatic.com/AdServer/js/pwt/156021/7083/pwt.js168826.0 s171.9 KiB
c2.taboola.com/nr/indianexpress-indianexpress/newsroom.js14400.0 s18.7 KiB
a.quora.com/qevents.js14400.0 s14.8 KiB
cdn.moengage.com/webpush/moe_webSdk.min.latest.js1209600.0 s101.0 KiB
eus.rubiconproject.com/usync.js11799.0 s11.5 KiB
ua.indianexpress.com/personlization-sdk.min.js?ver=05012026.11800.0 s9.1 KiB
static.chartbeat.com/js/chartbeat.js86400.0 s15.9 KiB
static.chartbeat.com/js/subscriptions.js86400.0 s10.8 KiB
static.chartbeat.com/js/chartbeat_mab.js?ver=6.8.586400.0 s10.1 KiB
assets.bounceexchange.com/cache/7834/website-f84194f4fb312c52b02ae980bddf6150.js120.0 s3.5 KiB
tag.wknd.ai/7834/i.js60.0 s3.0 KiB
sb.scorecardresearch.com/internal-cs/default/beacon.js86400.0 s6.7 KiB
/jDbww4UsKQL1l58iE5iD2WOhxmH4oZkLLVEF5H2LeHT_YtXJGSYJJ9-U...86400.0 s5.2 KiB
pm-widget.taboola.com/indianexpress-indianexpress/load.js3600.0 s1.7 KiB
config.aps.amazon-adsystem.com/configs/ea69f535-72ee-47bc-ad42-cec60377d1ec3600.0 s1.1 KiB
applets.ebxcdn.com/ebx.js7200.0 s1.0 KiB
/newsroom/1.0/indianexpress-indianexpress/get-action?page...0.0 ms302 B
/_/ad/639d3df60891483ca8e8f7a0b3c1a025/pixel?tag=ViewCont...0.0 ms272 B
/track/usersync?us_privacy=&gdpr=0&gdpr_consent=undefined...0.0 ms148 B
/tr/?id=444470064056909&ev=PageView&dl=https%3A%2F%2Findi...0.0 ms19 B

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation2.5 s
Style & Layout704 ms
Other569 ms
Script Parsing & Compilation391 ms
Rendering159 ms
Parse HTML & CSS97 ms
Garbage Collection72 ms

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
The Indian EXPRESS E-paper div.o-epaper > a > div.o-epaper__thumbnail > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/src/blocks/ie-ar...

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 22 user timings
Avoid long main-thread tasks 18 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 110 ms
Server Backend Latencies 600 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 400 ms
Avoid large layout shifts 5 layout shifts found
INP breakdown
Avoid non-composited animations
92

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn more div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label
List of partners. div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog

These are opportunities to improve the legibility of your content.

Best practices

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Select elements have associated label elements.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Links are distinguishable without relying on color.
`<object>` elements have alternate text
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
73

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
Mumbai Indians div.wc-team-desc > a > div.o-matchesbx__card-flag > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Punjab Kings div.wc-team-desc > a > div.o-matchesbx__card-flag > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Gujarat Titans div.wc-team-desc > a > div.o-matchesbx__card-flag > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Kolkata Knight Riders div.wc-team-desc > a > div.o-matchesbx__card-flag > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Royal Challengers Bengaluru div.o-matchesbx__card-team > a > div.o-matchesbx__card-flag > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Lucknow Super Giants div.o-matchesbx__card-team > a > div.o-matchesbx__card-flag > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Chennai Super Kings div.o-matchesbx__card-team > a > div.o-matchesbx__card-flag > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Kolkata Knight Riders div.o-matchesbx__card-team > a > div.o-matchesbx__card-flag > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Royal Challengers Bengaluru div.tbl-row__team > a.team-flagname > span.tbl-row__team--logo > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Rajasthan Royals div.tbl-row__team > a.team-flagname > span.tbl-row__team--logo > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Punjab Kings div.tbl-row__team > a.team-flagname > span.tbl-row__team--logo > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Sunrisers Hyderabad div.tbl-row__team > a.team-flagname > span.tbl-row__team--logo > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Delhi Capitals div.tbl-row__team > a.team-flagname > span.tbl-row__team--logo > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Gujarat Titans div.tbl-row__team > a.team-flagname > span.tbl-row__team--logo > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Lucknow Super Giants div.tbl-row__team > a.team-flagname > span.tbl-row__team--logo > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Chennai Super Kings div.tbl-row__team > a.team-flagname > span.tbl-row__team--logo > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Mumbai Indians div.tbl-row__team > a.team-flagname > span.tbl-row__team--logo > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
Kolkata Knight Riders div.tbl-row__team > a.team-flagname > span.tbl-row__team--logo > img.lazyloading
indianexpress.com/wp-content/themes/indianexpress/images/default-ie.jpg49 x 24 (2.04)97 x 54 (1.80)
mumbai, mumbai metro, mumbai news, div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
Will drop all false cases against Gorkha leaders: Amit Shah in Darjeeling div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
Pune div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
chandigarh, cbse div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
morbi, ceramic, div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
CM Yogi div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
VIjay div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
Anudeep Katikala div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)
bengaluru man-murder mother div.o-commonTopnews__rhs > figure.o-newsImage > a > img.lazyloading
/wp-content/plugins/ie-newsblock-builder/assets/images/de...350 x 197 (1.78)97 x 54 (1.80)

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Topics
Specifying overflow: visible on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/shared-element-transitions/blob/main/debugging_overflow_on_images.md.
AttributionReporting

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
A bad HTTP response code (403) was received when fetching the script.
A bad HTTP response code (403) was received when fetching the script.
Not signed in with the identity provider.
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`
robots.txt is valid

Send Feedback