Skip to content
Audit Complete

Results for https://businessweek.com

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

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)
C71

Site Health

Score: 71 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

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

Amazon ELB · 120 peers
You 71
·
Avg 70
At average
0 50 100
Better than 50% of Amazon ELB sites See full Amazon ELB benchmark →
HSTS · 1596 peers
You 71
·
Avg 74
At average
0 50 100
Better than 14% of HSTS sites See full HSTS benchmark →

Top Priorities (5)

1

Page weighs 17.9 MB (5.8 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
2

No <main> landmark found

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

Accessibility › Landmark Structure
3

No favicon or icon links detected

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

Accessibility › Favicon & Branding
4

165 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
5

166 HTTP requests — consider bundling or reducing

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

0

High impact, low effort — start here.

Nothing in this quadrant — good news.

Strategic

5

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%2Fbusinessweek.com)](https://beavercheck.com/results/582f4f0e-3f96-45b1-be45-f0c58dc86833)
<a href="https://beavercheck.com/results/582f4f0e-3f96-45b1-be45-f0c58dc86833"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbusinessweek.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fbusinessweek.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 11.8s exceeds Google's 2.5s 'Good' threshold and the 3 performance issues below directly contribute to it. 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 conversion rate.

Your LCP is 11.8s — fixing the 3 performance criticals could bring it under Google's 2.5s 'Good' threshold.
2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

3 critical 6 warning

9 barrier(s) likely increasing bounce by ~33%.

Speed (2)

Page takes 11.8s to load

+12% bounce

Users abandon at ~3s — you're 9.3s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 5.5s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

3 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$900 investment → $3,003/month returns + USD 157,500 risk avoided

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

Investment

$900

9h · 5 findings

Monthly returns

$3,003 /mo

~$36,041 / year

  • Conversions recovered $3,002
  • Bandwidth savings $1.45

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

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

$900

9.0 developer hours at $100/hr

Based on United States rates ($100/hr)

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,517 / 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
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+4 more

Bandwidth Waste

$1.45 /mo

18111.4 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.8 MB per page load
    Saves $1.45/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 3 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.

28
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
91
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
85
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.

7.15 s

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

11.83 s

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

5.46 s

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

0.000

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

7.78 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.78 s

Detailed Report

Audit breakdown by category with detailed findings.

28

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.

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.

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:35.273 source:map[type:text value:[unattributed]]]]

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
May 1, 2026 section.Media_image__n9qKY > figure > picture.styles_lazy___9s4S > img
assets.bwbx.io/images/users/iqjWHBFdfxIU/i1uR2v.BejqQ/v0/1430x1907.webp421.0 KiB331.9 KiB
How Chobani Turned Greek Yogurt Into an American Refrigerator Staple section.Media_image__n9qKY > figure > picture.styles_lazy___9s4S > img
assets.bwbx.io/images/users/iqjWHBFdfxIU/iOqeYKWWeLeU/v1/1430x954.webp296.4 KiB249.4 KiB
OpenTable Won Over the Wrong Customers, Then Changed Course section.Media_image__n9qKY > figure > picture.styles_lazy___9s4S > img
assets.bwbx.io/images/users/iqjWHBFdfxIU/ivZDee5MF1z4/v0/1430x953.webp98.2 KiB77.4 KiB
The AI School Bus Camera Company Blanketing America in Tickets section.Media_image__n9qKY > figure > picture.styles_lazy___9s4S > img
assets.bwbx.io/images/users/iqjWHBFdfxIU/it4npgCELPI8/v2/1200x800.webp91.7 KiB64.1 KiB
PURSUITS_Chagall section.Media_image__n9qKY > figure > picture.styles_lazy___9s4S > img
assets.bwbx.io/images/users/iqjWHBFdfxIU/i_bhevF1kBGc/v0/660x440.webp72.7 KiB62.0 KiB
The World’s Anti-Recession Guardrails Are Weaker Than Ever section.Media_image__n9qKY > figure > picture.styles_lazy___9s4S > img
assets.bwbx.io/images/users/iqjWHBFdfxIU/iACInkik2f2I/v0/1430x953.webp77.2 KiB60.8 KiB
The Magical Corner of Spain Tourists Haven’t Found Yet section.Media_image__n9qKY > figure > picture.styles_lazy___9s4S > img
assets.bwbx.io/images/users/iqjWHBFdfxIU/i9yqwNbnW4zs/v2/660x440.webp67.6 KiB57.0 KiB
The $10 Billion Startup Training AI to Replace the White-Collar Workforce section.Media_image__n9qKY > figure > picture.styles_lazy___9s4S > img
assets.bwbx.io/images/users/iqjWHBFdfxIU/iOZi51OoLVVk/v0/1200x800.webp71.5 KiB50.0 KiB
PURSUITS_WEB_Greek Mountains web crop section.Media_image__n9qKY > figure > picture.styles_lazy___9s4S > img
assets.bwbx.io/images/users/iqjWHBFdfxIU/iGazZ0CGmSf4/v1/660x440.webp34.3 KiB26.5 KiB
0526_PURSUITS_CANADA section.Media_image__n9qKY > figure > picture.styles_lazy___9s4S > img
assets.bwbx.io/images/users/iqjWHBFdfxIU/i9.tLzDN3ALk/v1/660x440.webp30.1 KiB23.3 KiB
PURSUITS_WEB_CEO diet HP section.Media_image__n9qKY > figure > picture.styles_lazy___9s4S > img
assets.bwbx.io/images/users/iqjWHBFdfxIU/iL5J.vnrFMMw/v0/660x440.webp25.7 KiB19.9 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.

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

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.

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: 857 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 637 ms
URLTime Spent
www.bloomberg.com/businessweek737 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
Unattributable2.7 s507 ms0.0 ms
www.bloomberg.com/businessweek2.5 s687 ms86 ms
assets.bwbx.io/s3/lineup/_next/static/chunks/framework-945b357d4a851f4b.js1.5 s1.4 s22 ms
www.googletagmanager.com/gtm.js?id=GTM-MNTH5N1.5 s1.2 s175 ms
sourcepointcmp.bloomberg.com/Notice.8f529.js866 ms686 ms54 ms
assets.bwbx.io/s3/lineup/_next/static/chunks/pages/_app-28862177fc79ed9c.js807 ms557 ms248 ms
/s3/lineup/_next/static/chunks/pages/curation/phoenix/[pa...594 ms590 ms1.9 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js413 ms295 ms111 ms
sourcepointcmp.bloomberg.com/unified/wrapperMessagingWithoutDetection.js410 ms299 ms48 ms
www.googletagmanager.com/gtag/js?id=G-GQ1PBLXZCT&cx=c&gtm=4e64h1386 ms308 ms75 ms
js-agent.newrelic.com/nr-spa-1.313.1.min.js296 ms239 ms17 ms
/unified/4.40.1/usnat-uspapi.090eccada574d39af6f8.bundle.js264 ms198 ms65 ms
cdn.lgrckt-in.com/logger-1.min.js242 ms113 ms128 ms
assets.bwbx.io/s3/lineup/_next/static/chunks/main-a5b6b28eaa6544ab.js230 ms210 ms19 ms
assets.bwbx.io/s3/abba/abba-client/latest/abba-client.js201 ms154 ms45 ms
securepubads.g.doubleclick.net/tag/js/gpt.js152 ms101 ms16 ms
pub.doubleverify.com/dvtag/24434720/DV1462763/pub.js146 ms116 ms17 ms
assets.bwbx.io/s3/spritz/v1/spritz.mjs144 ms120 ms0.3 ms
/unified/4.40.1/gdpr-tcf.27718c8cb9d29947d2c1.bundle.js91 ms65 ms26 ms
assets.bwbx.io/s3/fence/notify-unsupported-browser/v1/app.bundle.js86 ms64 ms21 ms
assets.bwbx.io/s3/lineup/_next/static/chunks/d6e1aeb5-6c1a556b50118c84.js86 ms1.5 ms84 ms
assets.bwbx.io/s3/fence/plug-client/v0/app.bundle.js77 ms52 ms24 ms
assets.bwbx.io/s3/lineup/_next/static/chunks/2619eb1e-8e00cd468b1d1bed.js72 ms61 ms9.7 ms
assets.bwbx.io/s3/lineup/_next/static/chunks/6580-c9228d3283ef7fbb.js51 ms1.7 ms48 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.2 s
Other2.5 s
Script Parsing & Compilation1.6 s
Style & Layout853 ms
Parse HTML & CSS792 ms
Garbage Collection228 ms
Rendering101 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.1 KiB

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 14.2 KiB
URLTransfer SizeEst Savings
assets.bwbx.io/s3/lineup/_next/static/css/d6fe4208f7bfc24f.css15.1 KiB14.2 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
Optimize viewport for mobile
Minify JavaScript
User Timing marks and measures 104 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 90 ms
Server Backend Latencies 100 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
INP breakdown
Avoid non-composited animations
Avoid large layout shifts
91

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.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section#header_text > figure.SectionFrontHeaderImageTitle_imageStyles__j6IPz > picture.styles_lazy___9s4S > img section#header_text > figure.SectionFrontHeaderImageTitle_imageStyles__j6IPz > picture.styles_lazy___9s4S > img

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
navigation dot section#shadow_magazine_cover_carousel > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb
navigation dot section#shadow_magazine_cover_carousel > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb
navigation dot section#shadow_magazine_cover_carousel > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb
navigation dot section#shadow_magazine_cover_carousel > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb
navigation dot div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb
navigation dot div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb
navigation dot div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb
navigation dot div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb
navigation dot div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb
navigation dot div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb
navigation dot div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb
navigation dot div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb
navigation dot div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb

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
`[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
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
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 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
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`[aria-hidden="true"]` elements do not contain focusable descendents
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
Form elements have associated labels
Links are distinguishable without relying on color.
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.
Elements with visible text labels have matching accessible names.
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.
96

Best Practices

General

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
bloomberg.that.spotlight { "message": "There was an error when retrieving the spotlight ", "extra": 403 }
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Uncaught (in promise) Error: Error when fetching from api/paginate: <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Bloomberg - Are you a robot?</title> <style rel="stylesheet"> @font-face { font-family: BWHaasGroteskWeb; font-display: swap; font-weight: 400; font-style: normal; src: url('https://assets.bwbx.io/s3/fontservice/fonts/BWHaasGrotesk-55Roman-Web-7998fbcba8.eot'); src: local('?'), url('https://assets.bwbx.io/s3/fontservice/fonts/BWHaasGrotesk-55Roman-Web-5cf5733cd9.woff2') format('woff2'), url('https://assets.bwbx.io/s3/fontservice/fonts/BWHaasGrotesk-55Roman-Web-a1ea4fd367.woff') format('woff') } @font-face { font-family: BWHaasGroteskWeb; font-display: swap; font-weight: 700; font-style: normal; src: url('https://assets.bwbx.io/s3/fontservice/fonts/BWHaasGrotesk-75Bold-Web-de8c77cce2.woff2') format('woff2'), url('https://assets.bwbx.io/s3/fontservice/fonts/BWHaasGrotesk-75Bold-Web-506363704e.woff') format('woff') } </style> <style rel="stylesheet"> html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, b, u, i, center, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, details, embed, figure, figcaption, footer, header, hgroup, menu, nav, output, ruby, section, summary, time, mark, audio, video { margin: 0; padding: 0; border: 0; font-size: 100%; font: inherit; vertical-align: baseline; } /* HTML5 display-role reset for older browsers */ article, aside, details, figcaption, figure, footer, header, hgroup, menu, nav, section { display: block; } body { line-height: 1; } ol, ul { list-style: none; } blockquote, q { quotes: none; } blockquote:before, blockquote:after, q:before, q:after { content: ''; content: none; } table { border-collapse: collapse; border-spacing: 0; } * { box-sizing: border-box; } body { background-color: #f2f2f2; font-family: "BWHaasGroteskWeb", Helvetica, Arial, sans-serif; line-height: 1.2; } .header { margin: 0; height: 60px; width: 100%; background-color: black; color: white; overflow-x: hidden; } .logo { float: left; margin: 0 20px; height: 60px; width: 140px; background-image: url('data:image/svg+xml;base64,PHN2ZyBpZD0iTGF5ZXJfMSIgZGF0YS1uYW1lPSJMYXllciAxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyNTcuNzUgNDcuNjMiPjxkZWZzPjxzdHlsZT4uY2xzLTF7ZmlsbDojZmZmO308L3N0eWxlPjwvZGVmcz48dGl0bGU+Qmxvb21iZXJnX05IR193aHQ8L3RpdGxlPjxwYXRoIGNsYXNzPSJjbHMtMSIgZD0iTTgxLjczLDExMzhIMTAwLjZjMy41NywwLDYuMzIuODcsOC4yNiwyLjQ1YTkuNDUsOS40NSwwLDAsMSwzLjM3LDcuNmMwLDMuNjctMS40OCw2LTQuNTQsNy4zOXYwLjE1YzQsMS4zMyw2LjI3LDQuOSw2LjI3LDkuMjMsMCw0LjEzLTEuNTgsNy4zNC00LjE4LDkuMjgtMi4xOSwxLjU4LTUsMi4zNS04LjgyLDIuMzVIODEuNzNWMTEzOFptMTcsMTVjMiwwLDMuNTItMS4xMiwzLjUyLTMuMzdzLTEuNTMtMy4yNi0zLjU3LTMuMjZIOTIuMTlWMTE1M2g2LjUzWm0xLDE0Ljg5YTMuOTMsMy45MywwLDEsMC0uMDUtNy44NUg5Mi4xOXY3Ljg1aDcuNVoiIHRyYW5zZm9ybT0idHJhbnNsYXRlKC04MS43MyAtMTEzNy45OCkiLz48cGF0aCBjbGFzcz0iY2xzLTEiIGQ9Ik0xMTUuOCwxMTM4aDkuODl2MzguNDVIMTE1LjhWMTEzOFoiIHRyYW5zZm9ybT0idHJhbnNsYXRlKC04MS43MyAtMTEzNy45OCkiLz48cGF0aCBjbGFzcz0iY2xzLTEiIGQ9Ik0xMjcuNjksMTE2Mi43N2MwLTguNjcsNS42MS0xNC41NCwxNC4yOC0xNC41NHMxNC4xOCw1Ljg3LDE0LjE4LDE0LjU0LTUuNTEsMTQuNTMtMTQuMTgsMTQuNTNTMTI3LjY5LDExNzEuNDgsMTI3LjY5LDExNjIuNzdabTE4LjY2LDBjMC00Ljc5LTEuNTMtNy44LTQuNDktNy44cy00LjM5LDMtNC4zOSw3LjgsMS40Myw3Ljg1LDQuMzksNy44NVMxNDYuMzUsMTE2Ny42MSwxNDYuMzUsMTE2Mi43N1oiIHRyYW5zZm9ybT0idHJhbnNsYXRlKC04MS43MyAtMTEzNy45OCkiLz48cGF0aCBjbGFzcz0iY2xzLTEiIGQ9Ik0xNTcuMzIsMTE2Mi43N2MwLTguNjcsNS42MS0xNC41NCwxNC4yOC0xNC41NHMxNC4xOCw1Ljg3LDE0LjE4LDE0LjU0LTUuNTEsMTQuNTMtMTQuMTgsMTQuNTNTMTU3LjMyLDExNzEuNDgsMTU3LjMyLDExNjIuNzdabTE4LjY2LDBjMC00Ljc5LTEuNTMtNy44LTQuNDktNy44cy00LjM5LDMtNC4zOSw3LjgsMS40Myw3Ljg1LDQuMzksNy44NVMxNzYsMTE2Ny42MSwxNzYsMTE2Mi43N1oiIHRyYW5zZm9ybT0idHJhbnNsYXRlKC04MS43MyAtMTEzNy45OCkiLz48cGF0aCBjbGFzcz0iY2xzLTEiIGQ9Ik0xODcuNzYsMTE0OWg5LjE4djQuMTNoMC4xNWMxLjg0LTMuMjEsNC4zMy00Ljk1LDguMjYtNC45NWE3LjY2LDcuNjYsMCwwLDEsNy4zOSw0Ljc0aDAuMTVhOS4yMSw5LjIxLDAsMCwxLDguNTItNC43NGM2LjM3LDAsOS4xMyw0LjY5LDkuMTMsMTF2MTcuMjRoLTkuNjR2LTE1LjVjMC0yLjgtLjg3LTQuNjQtMy4zMS00LjY0cy0zLjYyLDIuMjQtMy42Miw1LjJ2MTQuOTRoLTkuNjR2LTE1LjVjMC0yLjgtLjg3LTQuNjQtMy4zMS00LjY0cy0zLjYyLDIuMjQtMy42Miw1LjJ2MTQuOTRoLTkuNjRWMTE0OVoiIHRyYW5zZm9ybT0idHJhbnNsYXRlKC04MS43MyAtMTEzNy45OCkiLz48cGF0aCBjbGFzcz0iY2xzLTEiIGQ9Ik0yNDIuNjksMTE3Mi44NmgtMC4xdjMuNTdoLTkuMThWMTEzOEgyNDN2MTMuODdoMC4xNWE5LjEyLDkuMTIsMCwwLDEsNy44LTMuNjdjNi44OCwwLDEwLjg2LDYuMjIsMTAuODYsMTQuNDgsMCw5LjMzLTQuMzMsMTQuNjktMTEuNDcsMTQuNjlBOC42Nyw4LjY3LDAsMCwxLDI0Mi42OSwxMTcyLjg2Wm05LjM4LTEwLjNjMC00LjQ0LTEuNjMtNy4yOS00LjU0LTcuMjlzLTQuODQsMi44Ni00Ljg0LDcuMjksMS44OSw3LjI5LDQuODQsNy4yOVMyNTIuMDcsMTE2NywyNTIuMDcsMTE2Mi41NloiIHRyYW5zZm9ybT0idHJhbnNsYXRlKC04MS43MyAtMTEzNy45OCkiLz48cGF0aCBjbGFzcz0iY2xzLTEiIGQ9Ik0yNjMsMTE2Mi42NmMwLTguNTcsNS42Ni0xNC41MywxMy44Ny0xNC41M2ExMy4zNCwxMy4zNCwwLDAsMSw5LjY0LDMuNTdjMy4xNiwzLjA2LDQuNTksNy44NSw0LjQ5LDEzLjUxSDI3Mi42M2MwLjQxLDMuNDIsMiw1LjE1LDQuOTUsNS4xNWEzLjcsMy43LDAsMCwwLDMuNzctMi42aDkuMjhjLTEuNjMsNi4yNy02LjQ4LDkuNDQtMTMuMzYsOS40NEMyNjguNzUsMTE3Ny4yLDI2MywxMTcxLjQzLDI2MywxMTYyLjY2Wm05LjU5LTIuODZoOC43N2MtMC4xNS0zLjMxLTItNS00LjI4LTVDMjc0LjQ2LDExNTQuNzYsMjczLDExNTYuNjQsMjcyLjYzLDExNTkuODFaIiB0cmFuc2Zvcm09InRyYW5zbGF0ZSgtODEuNzMgLTExMzcuOTgpIi8+PHBhdGggY2xhc3M9ImNscy0xIiBkPSJNMzAyLDExNTMuNjloMC4xNWMyLTMuODIsNC41OS01LjI1LDcuOS01LjI1YTMuNzIsMy43MiwwLDAsMSwxLjU4LjI1djguNDFoLTAuMmMtNS42Ni0xLTksMS42OC05LDcuODV2MTEuNDdoLTkuNjRWMTE0OUgzMDJ2NC42OVoiIHRyYW5zZm9ybT0idHJhbnNsYXRlKC04MS43MyAtMTEzNy45OCkiLz48cGF0aCBjbGFzcz0iY2xzLTEiIGQ9Ik0zMTIuNjYsMTE3Ni40OGg5LjI4YzAuMzYsMS4xNywxLjU4LDIuMzUsMy44OCwyLjM1LDMuMTEsMCw0LjE4LTEuOTQsNC4xOC00Ljc5di0yaC0wLjJhOC4yNiw4LjI2LDAsMCwxLTYuNTgsMy4xMWMtNS45MiwwLTExLjA3LTQuMzgtMTEuMDctMTMsMC03Ljg1LDQuMjMtMTQsMTAuNjEtMTQsMy42NywwLDUuOTEsMS40OCw3LjM5LDMuODJoMC4xNXYtM2g5LjE4djIzLjc2YzAsNC4zOC0xLjUzLDcuOC0zLjgyLDkuODRzLTUuODEsMy05LjY5LDNDMzE4LjY4LDExODUuNjEsMzEzLjU4LDExODIuNiwzMTIuNjYsMTE3Ni40OFptMTcuNzUtMTQuNzljMC0zLjQyLTEuNjMtNi4xNy00LjQ0LTYuMTdzLTQuNDQsMi40NS00LjQ0LDYuMTcsMS43Myw2LjMyLDQuNDQsNi4zMlMzMzAuNDEsMTE2NS4zMSwzMzAuNDEsMTE2MS42OVoiIHRyYW5zZm9ybT0idHJhbnNsYXRlKC04MS43MyAtMTEzNy45OCkiLz48L3N2Zz4='); background-repeat: no-repeat; background-position: center; font-size: 0; } .contact-us { float: right; margin: 0 20px; line-height: 60px; font-family: "BWHaasGroteskWeb", Helvetica, Arial, sans-serif; font-size: 14px; color: white; text-decoration: underline; } .box { margin: 30px auto; padding: 30px; width: 680px; background-color: white; } @media (max-width: 760px) { .box { width: calc(100% - 20px); } } .main__heading, .info__heading { font-family: "BWHaasGroteskWeb", Helvetica, Arial, sans-serif; font-weight: bold; } .main__heading { font-size: 19px; padding-bottom: 9px; } .continue { font-size: 18px; } #px-captcha { width: 320px; margin: 20px auto 0; min-height: 80px; } .info { border-top: dotted 1px black; padding-top: 9px; } .info + .info { margin-top: 30px; } .info__link { color: black; text-decoration: underline; } .info__heading { font-size: 16px; line-height: 20px; padding-bottom: 9px; } .info__text { padding-bottom: 9px; } .subscribe__btn { padding: 18px 24px; color: #fff; background-color: #000; border-radius: 8px; font-size: x-large; font-weight: bold; f…
Uses HTTPS
Avoids deprecated APIs
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
85

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Terms of Service div.media-ui-Footer_footerContainer-48Eos3T24SA- > div.media-ui-Footer_bottomContent-FGNwwTOXYJc- > div.media-ui-Footer_bottomLeftContent-BOyobil9rv4- > a.media-ui-Footer_link-eSdhpCwbm6w-
Trademarks div.media-ui-Footer_footerContainer-48Eos3T24SA- > div.media-ui-Footer_bottomContent-FGNwwTOXYJc- > div.media-ui-Footer_bottomLeftContent-BOyobil9rv4- > a.media-ui-Footer_link-eSdhpCwbm6w-
Privacy Policy div.media-ui-Footer_footerContainer-48Eos3T24SA- > div.media-ui-Footer_bottomContent-FGNwwTOXYJc- > div.media-ui-Footer_bottomLeftContent-BOyobil9rv4- > a.media-ui-Footer_link-eSdhpCwbm6w-
Careers div.media-ui-Footer_footerContainer-48Eos3T24SA- > div.media-ui-Footer_bottomContent-FGNwwTOXYJc- > div.media-ui-Footer_bottomRightContent--131BbNfIQg- > a.media-ui-Footer_link-eSdhpCwbm6w-
Advertise div.media-ui-Footer_footerContainer-48Eos3T24SA- > div.media-ui-Footer_bottomContent-FGNwwTOXYJc- > div.media-ui-Footer_bottomRightContent--131BbNfIQg- > a.media-ui-Footer_link-eSdhpCwbm6w-
Ad Choices div.media-ui-Footer_bottomContent-FGNwwTOXYJc- > div.media-ui-Footer_bottomRightContent--131BbNfIQg- > div.media-ui-Footer_link-eSdhpCwbm6w- > a
Help div.media-ui-Footer_footerContainer-48Eos3T24SA- > div.media-ui-Footer_bottomContent-FGNwwTOXYJc- > div.media-ui-Footer_bottomRightContent--131BbNfIQg- > a.media-ui-Footer_link-eSdhpCwbm6w-

To appear in search results, crawlers need access to your app.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section#header_text > figure.SectionFrontHeaderImageTitle_imageStyles__j6IPz > picture.styles_lazy___9s4S > img section#header_text > figure.SectionFrontHeaderImageTitle_imageStyles__j6IPz > picture.styles_lazy___9s4S > img

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 have descriptive text
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Desktop audit not available for this result.

Send Feedback