Skip to content
Audit Complete

Results for https://businessinsider.com

Visit site
E-commerce · estimated Tracking: purchases
Singapore Singapore · Singapore Completed: Apr 15, 2026 23:23 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)
C74

Site Health

Score: 74 / 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.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Reasonable footprint with room for optimization.

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

Ecommerce sites average 72
At average
Better than 60% of Ecommerce sites
CMS sites average 73
At average
Better than 49% of CMS sites

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

No Content-Security-Policy header found

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

Security › Content Security Policy
3

10 button(s) with no accessible text

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

Accessibility › Link & Button Quality
4

No <main> landmark found

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

Accessibility › Landmark Structure
5

360 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

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%2Fbusinessinsider.com)](https://beavercheck.com/results/bbec09a2-fa84-40d2-bd24-5f7838877e75)
<a href="https://beavercheck.com/results/bbec09a2-fa84-40d2-bd24-5f7838877e75"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbusinessinsider.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fbusinessinsider.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 3.2s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.
Your LCP is 3.2s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Return on Investment

$600 investment → $1,249/month returns + USD 157,500 risk avoided

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

Investment

$600

6h · 5 findings

Monthly returns

$1,249 /mo

~$14,988 / year

  • Conversions recovered $1,248
  • Bandwidth savings $0.81

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

Payback period

0 12mo 24mo

$100 — 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

$600

6.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$100 2 fixes in ~60 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

$13,126 / month at risk

~$157,510 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • 2 advertising/retargeting trackers detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+5 more

Bandwidth Waste

$0.81 /mo

10175.7 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.0 MB per page load
    Saves $0.81/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 4 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.

55
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.
77
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.

2.23 s

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

3.16 s

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

6.53 s

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

0.018

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

6.28 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.

32.36 s

Detailed Report

Audit breakdown by category with detailed findings.

55

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:0.58 source:map[column:81241 line:2 type:source-location url:https://www.businessinsider.com/scripts/vendors.d03c9333f2796fb8b6a6.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:68.63 source:map[type:text value:[unattributed]]] map[reflowTime:0.622 source:map[column:143040 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604130101/pubads_impl.js?cb=31097849 urlProvider:network]] map[reflowTime:0.58 source:map[column:165380 line:0 type:source-location url:https://www.businessinsider.com/scripts/main.f6eb5c9cd6b4e76438bf.js urlProvider:network]]]

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: Josh Disney
path: 1,HTML,1,BODY,3,SECTION,0,SECTION,1,SECTION,0,SECTION,0,ARTICLE,0,A,0,DIV,0,IMG
selector: article.tout > a.tout-image > div.aspect-ratio > img
snippet: <img src="https://i.insider.com/69e002303c23517615b2f8b1?width=1000&amp;format=jpeg&amp;auto…" srcset="https://i.insider.com/69e002303c23517615b2f8b1?width=400&amp;format=jpeg&amp;auto=…" sizes="(min-width: 1280px) 900px" alt="Josh Disney" decoding="sync">

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.

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
value: no origins were preconnected
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
businessinsider.edge.permutive.app/3aba5292-ba75-422b-8715-bd21146f7836-web.js900.0 s192.0 KiB
cdn.doubleverify.com/dvbm.js900.0 s102.1 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.4 KiB
c.amazon-adsystem.com/aax2/apstag.js3600.0 s90.8 KiB
/cdnm50QDU6s2lq_RrjTCOPkh-uY/gpt_and_prebid/config.js1100.0 s70.2 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s73.1 KiB
cdn.confiant-integrations.net/UoN9YEYmGSZDADuK_Pua9WU_GTY/video/config.js1100.0 s60.4 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=33781800.0 s58.9 KiB
verticalvideo.businessinsider.com/vs.js?cid=8CU2241SO300.0 s47.3 KiB
/signals/config/1988166924554892?v=2.9.298&r=stable&domai...1200.0 s44.6 KiB
cdn.sophi.io/assets/demeter/1/stable/1539492444.js900.0 s43.0 KiB
cdn.id5-sync.com/api/1.0/esp.js3600.0 s34.8 KiB
scripts.atmtd.com/js/prebid_analytics/prebid_analytics.js120.0 s25.6 KiB
sdk.mrf.io/statics/0639f9e9af1a7496d5c3.js3600.0 s24.0 KiB
b-code.liadm.com/b-01h4.min.js86400.0 s45.8 KiB
pub.doubleverify.com/dvtag/23280644/DV673672/pub.js900.0 s19.3 KiB
/scripts/bundle/65568.js?sid=e212afbd-8285-4839-a80d-4aa9...3600.0 s17.2 KiB
ep2.adtrafficquality.google/sodar/VFc2VJAc.js3000.0 s14.0 KiB
ml314.com/tag.aspx?1533600.0 s12.7 KiB
cdn.speedcurve.com/js/lux.js?id=383835243600.0 s11.3 KiB
/cdn-cgi/challenge-platform/h/g/scripts/jsd/b0a7532ac8ec/...14400.0 s12.9 KiB
edge.atmtd.com/pub/mgnt/afihbs.js0.0 ms8.6 KiB
eus.rubiconproject.com/usync.js12830.0 s11.5 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
/mapper.js?zdid=1380&eventType=map&env=mWeb&cluid=aea0f6d...21600.0 s11.6 KiB
s.yimg.com/wi/ytc.js0.0 ms7.4 KiB
connectid.analytics.yahoo.com/connectId-gpt.js3600.0 s9.0 KiB
static.criteo.net/js/ld/publishertag.ids.js86400.0 s14.8 KiB
/data-sales-tag/v1/parent/48a9bcaaa1/script?domain=www.bu...0.0 ms4.9 KiB
a.amxrtb.com/js/cframe.js#gdpr=0&gdpr_consent=&cc=SG14400.0 s5.1 KiB
cdn.brandmetrics.com/tag/2307d3ae2e9240c98867fcda61fc7d4f/insider.js3600.0 s4.3 KiB
sdk.mrf.io/statics/compass-multimedia-sdk.js?version=22583600.0 s4.3 KiB
sb.scorecardresearch.com/internal-cs/default/beacon-and.js86400.0 s7.8 KiB
invstatic101.creativecdn.com/encrypted-signals/encrypted-tag-g.js0.0 ms2.9 KiB
config.aps.amazon-adsystem.com/configs/32013600.0 s2.3 KiB
pd.sharethis.com/pd/carbon0.0 ms1.2 KiB
/pagead/js/r20260414/r20110914/client/qs_click_protection...1209600.0 s8.9 KiB
pagead2.googlesyndication.com/pagead/js/r20260414/r20110914/abg_lite_fy2021.js1209600.0 s8.4 KiB
ps.eyeota.net/pixel/bounce/?pid=r8hrb20&t=gif0.0 ms354 B
/pixel/bounce/?pid=cb2cb90&t=ajs&sid=976&uid=aea0f6da-3e9...0.0 ms354 B
/pagead/js/r20260414/r20110914/elements/html/omrhp_fy2021.js1209600.0 s3.3 KiB
/c.js?siteid=e212afbd-8285-4839-a80d-4aa911385e1e&toploc=...0.0 ms291 B
/collect?v=2&fmt=js&pid=1420146&time=1776295265398&li_ads...0.0 ms271 B
match.adsrvr.org/track/cmb/generic?ttd_pid=d0tro1j&ttd_tpi=10.0 ms254 B
/pagead/js/r20260414/r20110914/client/window_focus_fy2021.js1209600.0 s1.3 KiB
cdn.indexww.com/ht/htw-pixel.gif?086400.0 s222 B
/AdServer/ImgSync?p=159706&gdpr=1&gdpr_consent=&us_privac...0.0 ms69 B
/api/sync?callerId=5&gdpr=1&gdpr_consent=&us_privacy=&red...0.0 ms45 B
/imsync.ashx?pi=3660420469677359156&data=eyJwaCI6MTgyNjEs...0.0 ms29 B
/imsync.ashx?pi=3660420469677359156&data=eyJwaCI6MTgyNjEs...0.0 ms29 B
ml314.com/csync.ashx?fp=7724625262568804630&person_id=3660420469677359156&eid=286331.0 s56 B
/tr/?id=1988166924554892&ev=PageView&dl=https%3A%2F%2Fwww...0.0 ms19 B
cdn.doubleverify.com/dvbm.js900.0 s0 B
cdn.doubleverify.com/dvbm.js900.0 s0 B
cdn.doubleverify.com/dvbm.js900.0 s0 B
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s0 B
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s0 B
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s0 B
ep2.adtrafficquality.google/sodar/VFc2VJAc.js3000.0 s0 B
ep2.adtrafficquality.google/sodar/VFc2VJAc.js3000.0 s0 B
ep2.adtrafficquality.google/sodar/VFc2VJAc.js3000.0 s0 B
pagead2.googlesyndication.com/pagead/js/r20260414/r20110914/abg_lite_fy2021.js1209600.0 s0 B
pagead2.googlesyndication.com/pagead/js/r20260414/r20110914/abg_lite_fy2021.js1209600.0 s0 B
pagead2.googlesyndication.com/pagead/js/r20260414/r20110914/abg_lite_fy2021.js1209600.0 s0 B
/pagead/js/r20260414/r20110914/client/qs_click_protection...1209600.0 s0 B
/pagead/js/r20260414/r20110914/client/qs_click_protection...1209600.0 s0 B
/pagead/js/r20260414/r20110914/client/qs_click_protection...1209600.0 s0 B
/pagead/js/r20260414/r20110914/elements/html/omrhp_fy2021.js1209600.0 s0 B
/pagead/js/r20260414/r20110914/elements/html/omrhp_fy2021.js1209600.0 s0 B
/pagead/js/r20260414/r20110914/elements/html/omrhp_fy2021.js1209600.0 s0 B
/pagead/js/r20260414/r20110914/client/window_focus_fy2021.js1209600.0 s0 B
/pagead/js/r20260414/r20110914/client/window_focus_fy2021.js1209600.0 s0 B
/pagead/js/r20260414/r20110914/client/window_focus_fy2021.js1209600.0 s0 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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
Josh Disney article.tout > a.tout-image > div.aspect-ratio > img
i.insider.com/69e002303c23517615b2f8b1?width=1000&format=jpeg&auto=webp20.0 KiB16.6 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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 752 ms

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

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

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
www.businessinsider.com/32.8 s300 ms60 ms
/pagead/managed/js/gpt/m202604130101/pubads_impl.js?cb=31...3.8 s3.3 s95 ms
Unattributable3.6 s1.0 s0.0 ms
www.businessinsider.com/scripts/main.f6eb5c9cd6b4e76438bf.js1.5 s1.1 s43 ms
micro.rubiconproject.com/prebid/dynamic/10306.js1.2 s1.1 s77 ms
cdn.confiant-integrations.net/gptprebidnative/202603241056/wrap.js958 ms772 ms52 ms
cdn.confiant-integrations.net/video/202603241056/wrap.js746 ms670 ms46 ms
www.googletagmanager.com/gtm.js?id=GTM-MP6F46L728 ms575 ms69 ms
sdk.mrf.io/statics/marfeel-sdk.js?id=3378594 ms578 ms1.8 ms
www.googletagmanager.com/gtag/js?id=G-E21CV80ZCZ&cx=c&gtm=4e64e1534 ms461 ms67 ms
www.googletagmanager.com/gtag/js?id=AW-708493099&cx=c&gtm=4e64e1392 ms334 ms55 ms
my.businessinsider.com/cdn-cgi/challenge-platform/scripts/jsd/main.js356 ms341 ms3.9 ms
fundingchoicesmessages.google.com/i/4442842?ers=3345 ms335 ms2.8 ms
businessinsider.edge.permutive.app/3aba5292-ba75-422b-8715-bd21146f7836-web.js345 ms203 ms117 ms
/signals/config/1988166924554892?v=2.9.298&r=stable&domai...313 ms225 ms36 ms
c.amazon-adsystem.com/aax2/apstag.js273 ms214 ms47 ms
cdn.sophi.io/assets/demeter/1/stable/1539492444.js196 ms173 ms23 ms
my.businessinsider.com/cross-domain/196 ms137 ms34 ms
www.businessinsider.com/chunks/scripts/14657.17fc26f01ed4db34d9f1.js179 ms163 ms8.7 ms
connect.facebook.net/en_US/fbevents.js178 ms131 ms47 ms
pub.doubleverify.com/dvtag/23280644/DV673672/pub.js159 ms119 ms9.7 ms
/scripts/bundle/65568.js?sid=e212afbd-8285-4839-a80d-4aa9...134 ms115 ms7.9 ms
sb.scorecardresearch.com/cs/9900186/beacon.js132 ms101 ms3.3 ms
static.ads-twitter.com/uwt.js109 ms100 ms6.8 ms
securepubads.g.doubleclick.net/tag/js/gpt.js?network-code=4442842104 ms88 ms15 ms
b-code.liadm.com/b-01h4.min.js101 ms77 ms23 ms
snap.licdn.com/li.lms-analytics/insight.min.js86 ms68 ms12 ms
/cdnm50QDU6s2lq_RrjTCOPkh-uY/gpt_and_prebid/config.js77 ms34 ms43 ms
ml314.com/tag.aspx?15377 ms63 ms5.4 ms
cdn.confiant-integrations.net/UoN9YEYmGSZDADuK_Pua9WU_GTY/video/config.js76 ms37 ms37 ms
ep2.adtrafficquality.google/sodar/sodar2.js74 ms63 ms5.2 ms
scripts.atmtd.com/js/prebid_analytics/prebid_analytics.js72 ms50 ms20 ms
verticalvideo.businessinsider.com/vs.js?cid=8CU2241SO70 ms51 ms17 ms
cdn.speedcurve.com/js/lux.js?id=3838352468 ms47 ms4.3 ms
static.criteo.net/js/ld/publishertag.ids.js65 ms59 ms5.6 ms
connectid.analytics.yahoo.com/connectId-gpt.js65 ms55 ms1.4 ms
/chunks/scripts/components~marquee-client.633201902de1ad6...64 ms28 ms4.6 ms
cdn.id5-sync.com/api/1.0/esp.js52 ms29 ms19 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
Other19.0 s
Script Evaluation13.8 s
Rendering12.3 s
Style & Layout4.5 s
Script Parsing & Compilation1.2 s
Garbage Collection287 ms
Parse HTML & CSS201 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.

Estimated savings: 0.0 ms 28.3 KiB

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

Layout shift culprits
Optimize DOM size
Font display
LCP breakdown
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 128 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 1 animated element found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 270 ms
Server Backend Latencies 1,240 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 10 ms
Avoid large layout shifts 9 layout shifts found
INP breakdown
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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.grid-container > aside.side-section > div.newsletter > div.newsletter-dynamic section.grid-container > aside.side-section > div.newsletter > div.newsletter-dynamic

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Here's the severance package Disney is giving to laid-off employees section.tout-layout > article.tout > div.tout-text > h3.tout-title

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Your Briefing header.masthead > section.bottom-section > div.user-greeting > span.catch-me-up-quickly
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-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
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
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.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` 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
`<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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
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.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
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.
77

Best Practices

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.

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
Access to XMLHttpRequest at 'https://c.amazon-adsystem.com/cdn/prod/config?src=3201&u=https%3A%2F%2Fwww.businessinsider.com' from origin 'https://www.businessinsider.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
Failed to load resource: the server responded with a status of 400 (Bad Request)
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
Displays images with correct aspect ratio
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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

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
Document has a meta description
Page has successful HTTP status code
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

73
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.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
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.

559 ms

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

787 ms

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

621 ms

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

0.015

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

1.57 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.

6.81 s

Detailed Report

Audit breakdown by category with detailed findings.

73

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.

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: Josh Disney
path: 1,HTML,1,BODY,3,SECTION,0,SECTION,1,SECTION,0,SECTION,0,ARTICLE,0,A,0,DIV,0,IMG
selector: article.tout > a.tout-image > div.aspect-ratio > img
snippet: <img src="https://i.insider.com/69e002303c23517615b2f8b1?width=1000&amp;format=jpeg&amp;auto…" srcset="https://i.insider.com/69e002303c23517615b2f8b1?width=400&amp;format=jpeg&amp;auto=…" sizes="(min-width: 1280px) 900px" alt="Josh Disney" decoding="sync">

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.

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
value: no origins were preconnected
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
businessinsider.edge.permutive.app/3aba5292-ba75-422b-8715-bd21146f7836-web.js900.0 s192.0 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.4 KiB
c.amazon-adsystem.com/aax2/apstag.js3600.0 s90.8 KiB
/cdnm50QDU6s2lq_RrjTCOPkh-uY/gpt_and_prebid/config.js1100.0 s70.2 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s73.1 KiB
cdn.confiant-integrations.net/UoN9YEYmGSZDADuK_Pua9WU_GTY/video/config.js1100.0 s60.4 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=33781800.0 s58.9 KiB
verticalvideo.businessinsider.com/vs.js?cid=8CU2241SO300.0 s47.3 KiB
/signals/config/1988166924554892?v=2.9.298&r=stable&domai...1200.0 s44.6 KiB
cdn.sophi.io/assets/demeter/1/stable/1539492444.js900.0 s43.0 KiB
cdn.id5-sync.com/api/1.0/esp.js3600.0 s34.8 KiB
scripts.atmtd.com/js/prebid_analytics/prebid_analytics.js120.0 s25.7 KiB
sdk.mrf.io/statics/0639f9e9af1a7496d5c3.js3600.0 s24.0 KiB
b-code.liadm.com/b-01h4.min.js86400.0 s45.8 KiB
pub.doubleverify.com/dvtag/23280644/DV673672/pub.js900.0 s19.3 KiB
/scripts/bundle/65568.js?sid=e212afbd-8285-4839-a80d-4aa9...3600.0 s17.2 KiB
ep2.adtrafficquality.google/sodar/VFc2VJAc.js3000.0 s14.0 KiB
ml314.com/tag.aspx?1533600.0 s12.7 KiB
/cdn-cgi/challenge-platform/h/g/scripts/jsd/b0a7532ac8ec/...14400.0 s13.4 KiB
cdn.speedcurve.com/js/lux.js?id=383835243600.0 s11.3 KiB
edge.atmtd.com/pub/mgnt/afihbs.js0.0 ms8.6 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
/mapper.js?zdid=1380&eventType=map&env=mWeb&cluid=6f09989...21600.0 s11.6 KiB
s.yimg.com/wi/ytc.js0.0 ms7.4 KiB
connectid.analytics.yahoo.com/connectId-gpt.js3600.0 s9.0 KiB
eus.rubiconproject.com/usync.js26549.0 s11.5 KiB
static.criteo.net/js/ld/publishertag.ids.js86400.0 s14.8 KiB
/data-sales-tag/v1/parent/48a9bcaaa1/script?domain=www.bu...0.0 ms5.0 KiB
a.amxrtb.com/js/cframe.js#gdpr=0&gdpr_consent=&cc=SG14400.0 s5.1 KiB
cdn.brandmetrics.com/tag/2307d3ae2e9240c98867fcda61fc7d4f/insider.js3600.0 s4.3 KiB
sdk.mrf.io/statics/compass-multimedia-sdk.js?version=22583600.0 s4.3 KiB
invstatic101.creativecdn.com/encrypted-signals/encrypted-tag-g.js0.0 ms2.9 KiB
sb.scorecardresearch.com/internal-cs/default/beacon.js86400.0 s6.7 KiB
config.aps.amazon-adsystem.com/configs/32013600.0 s2.3 KiB
pd.sharethis.com/pd/carbon0.0 ms1.2 KiB
pagead2.googlesyndication.com/pagead/js/r20260414/r20110914/abg_lite.js1209600.0 s10.5 KiB
/pagead/js/r20260414/r20110914/client/qs_click_protection...1209600.0 s8.9 KiB
sync.cootlogix.com/api/cookie?partnerId=rubiconut&userId=MO0OE1X7-11-LHEB0.0 ms496 B
/pagead/js/r20260414/r20110914/elements/html/omrhp.js1209600.0 s4.7 KiB
ps.eyeota.net/pixel/bounce/?pid=r8hrb20&t=gif0.0 ms354 B
/pixel/bounce/?pid=cb2cb90&t=ajs&sid=976&uid=6f09989c-fe1...0.0 ms354 B
/c.js?siteid=e212afbd-8285-4839-a80d-4aa911385e1e&toploc=...0.0 ms299 B
/collect?v=2&fmt=js&pid=1420146&time=1776295351466&li_ads...0.0 ms271 B
match.adsrvr.org/track/cmb/generic?ttd_pid=d0tro1j&ttd_tpi=10.0 ms254 B
/track/cmb/generic?ttd_pid=sonobi&ttd_tpi=1&ttd_puid=&gdp...0.0 ms254 B
/track/cmb/generic?ttd_pid=sirnsvg&ttd_tpi=1&gdpr=0&gdpr_...0.0 ms254 B
/pagead/js/r20260414/r20110914/client/window_focus_fy2021.js1209600.0 s1.3 KiB
creativecdn.com/cm-notify?pi=sonobi&tc=10.0 ms124 B
cdn.indexww.com/ht/htw-pixel.gif?086400.0 s222 B
/AdServer/ImgSync?p=166397&gdpr=0&gdpr_consent=&us_privac...0.0 ms40 B
/AdServer/ImgSync?p=160318&gdpr=&gdpr_consent=&pu=https%3...0.0 ms40 B
ml314.com/csync.ashx?fp=1091342663744275357&person_id=3660420492762808402&eid=286379.0 s56 B
/tr/?id=1988166924554892&ev=PageView&dl=https%3A%2F%2Fwww...0.0 ms19 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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
Bryan Johnson speaking at Business Insider event article.tout > a.tout-image > div.lazy-holder > img.lazy-image
/simgad/1718768457543532452?sqp=uqWu0g0HCFoQ2AVAZA&rs=AOg...49.4 KiB38.7 KiB
Sydney Sweeney stars in the new American Eagle campaign, "Syd for Short." article.tout > a.tout-image > div.lazy-holder > img.lazy-image
i.insider.com/69dfe6a0557731f181e95100?width=500&format=jpeg&auto=webp13.3 KiB4.4 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 201 ms

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

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 minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation2.5 s
Other1.1 s
Rendering433 ms
Script Parsing & Compilation320 ms
Style & Layout287 ms
Garbage Collection52 ms
Parse HTML & CSS51 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.

Estimated savings: 0.0 ms 26.5 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.

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

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

Layout shift culprits
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 85 user timings
Avoid long main-thread tasks 12 long tasks found
Avoid non-composited animations 2 animated elements found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 270 ms
Server Backend Latencies 1,250 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 10 ms
Avoid large layout shifts 7 layout shifts found
INP breakdown
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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.grid-container > aside.side-section > div.newsletter > div.newsletter-dynamic section.grid-container > aside.side-section > div.newsletter > div.newsletter-dynamic

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Here's the severance package Disney is giving to laid-off employees section.tout-layout > article.tout > div.tout-text > h3.tout-title

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Your Briefing header.masthead > section.bottom-section > div.user-greeting > span.catch-me-up-quickly
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-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
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
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.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` 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
`<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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
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.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
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.
77

Best Practices

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
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
AttributionReporting
Topics

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
Access to XMLHttpRequest at 'https://c.amazon-adsystem.com/cdn/prod/config?src=3201&u=https%3A%2F%2Fwww.businessinsider.com' from origin 'https://www.businessinsider.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
Failed to load resource: the server responded with a status of 400 (Bad Request)
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
Displays images with correct aspect ratio
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
100

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.

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

Send Feedback