Mobile 375 × 812

Desktop 1440 × 900

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.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
No favicon or icon links detected
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](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.comThis badge auto-updates with your latest scan result.
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.
₹6,750 investment → ₹7,332/month returns + INR 2,500,000,000 risk avoided
₹6,750
4h · 5 findings
₹7,332 /mo
~₹87,982 / year
INR 2,500,000,000
if kept compliant
₹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.
4.5 developer hours at ₹1500/hr
Based on India rates (₹1500/hr)
Start here for the best return on investment
₹208,333,396 / month at risk
~₹2,500,000,757 / year if left unfixed
₹2,500,000,000
+1 more
₹63 /mo
9461.7 MB/mo × 6.667 INR/GB
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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
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
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
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
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
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
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est 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=620 | 96.2 KiB | 61.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 KiB | 6.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.
Performance issues directly impact user engagement and conversion rates.
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
Performance issues directly impact user engagement and conversion rates.
| Element | Layout 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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 8.7 s |
| Style & Layout | 2.4 s |
| Other | 2.2 s |
| Script Parsing & Compilation | 1.3 s |
| Rendering | 688 ms |
| Parse HTML & CSS | 412 ms |
| Garbage Collection | 230 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| @charset 'UTF-8'; #section .container .row.follow-dev h1{font-size:20px;color:#a32020;margin:0; … } … | 87.2 KiB | 38.0 KiB |
| .fc-consent-root .fc-dialog-container.fc-fullscreen { height: 100% !important; … } … | 16.1 KiB | 13.9 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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
| URL | Transfer Size | Est Savings |
|---|---|---|
| cdn.taboola.com/libtrc/indianexpress-indianexpress/loader.js | 330.3 KiB | 168.9 KiB |
| /pagead/managed/js/gpt/m202604100101/pubads_impl.js | 186.4 KiB | 129.3 KiB |
| www.googletagmanager.com/gtag/js?id=AW-11033859954&cx=c>m=4e64e1 | 144.7 KiB | 105.7 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-PGQG2HFB | 155.8 KiB | 80.7 KiB |
| accounts.google.com/gsi/client?ver=20260415 | 95.3 KiB | 80.0 KiB |
| accounts.google.com/gsi/client | 95.4 KiB | 68.9 KiB |
| ads.pubmatic.com/AdServer/js/pwt/156021/7083/pwt.js | 171.5 KiB | 65.9 KiB |
| cdn.moengage.com/webpush/moe_webSdk.min.latest.js | 100.6 KiB | 63.0 KiB |
| www.googletagmanager.com/gtag/js?id=AW-11033859954 | 144.7 KiB | 56.2 KiB |
| www.googletagmanager.com/gtag/js?id=G-HEQWL2KPC5 | 178.3 KiB | 52.5 KiB |
| /signals/config/444470064056909?v=2.9.298&r=stable&domain... | 126.2 KiB | 39.3 KiB |
| fundingchoicesmessages.google.com/i/1050432?ers=3 | 68.7 KiB | 35.0 KiB |
| connect.facebook.net/en_US/fbevents.js | 96.3 KiB | 35.0 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
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.
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Performance issues directly impact user engagement and conversion rates.
| URL | Aspect 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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) |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| AttributionReporting | connect.facebook.net/en_US/fbevents.js line 279, col 769 |
| 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. | /_/mss/boq-content-ads-contributor/_/js/k=boq-content-ads... line 19, col 449 |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
accounts.google.com/gsi/client?ver=20260415 line 85, col 88 | [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. |
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
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
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
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
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est 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=680 | 101.6 KiB | 68.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=820 | 31.3 KiB | 5.1 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| /s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu... | 15 ms |
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 2.5 s |
| Style & Layout | 704 ms |
| Other | 569 ms |
| Script Parsing & Compilation | 391 ms |
| Rendering | 159 ms |
| Parse HTML & CSS | 97 ms |
| Garbage Collection | 72 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| @charset 'UTF-8'; #section .container .row.follow-dev h1{font-size:20px;color:#a32020;margin:0; … } … | 77.3 KiB | 27.8 KiB |
| .fc-consent-root .fc-dialog-container.fc-fullscreen { height: 100% !important; … } … | 16.1 KiB | 14.0 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
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.
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Performance issues directly impact user engagement and conversion rates.
| URL | Aspect 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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.jpg | 49 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) |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| 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. | /_/mss/boq-content-ads-contributor/_/js/k=boq-content-ads... line 19, col 449 |
| AttributionReporting | connect.facebook.net/en_US/fbevents.js line 279, col 769 |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
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. |
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
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.
Send Feedback