Skip to content
Audit Complete

Results for https://cointelegraph.com

Visit site
Netherlands Netherlands · Amsterdam Completed: Apr 21, 2026 20:36 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)
C77

Site Health

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

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

WordPress · 712 peers
You 77
·
Avg 74
At average
0 50 100
Better than 74% of WordPress sites See full WordPress benchmark →
core-js · 1488 peers
You 77
·
Avg 72
At average
0 50 100
Better than 89% of core-js sites See full core-js benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

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

Security › Security Headers
2

No Content-Security-Policy header found

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

Security › Content Security Policy
3

3 button(s) with no accessible text

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

Accessibility › Link & Button Quality
4

3 image(s) missing alt attribute

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

Accessibility › Alt Text Quality
5

4 link(s) with no accessible text

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

Accessibility › Link & Button Quality
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%2Fcointelegraph.com)](https://beavercheck.com/results/77baaf49-b592-42ec-b906-b9a5aee3edc1)
<a href="https://beavercheck.com/results/77baaf49-b592-42ec-b906-b9a5aee3edc1"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fcointelegraph.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fcointelegraph.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. 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.
3 accessibility issues exclude users who rely on assistive technology.
B
Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 3 warning

5 barrier(s) likely increasing bounce by ~26%.

Speed (2)

Page takes 19.2s to load

+12% bounce

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

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

Page feels frozen for 3.3s

+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 (1)

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

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

2 broken link(s) on the page

+3% 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

$550 investment → $0.76/month returns + USD 157,500 risk avoided

Payback period: > 2 years First-year ROI: -98%

Investment

$550

6h · 5 findings

Monthly returns

$0.76 /mo

~$9.16 / year

  • Bandwidth savings $0.76

Regulatory risk avoided

USD 157,500

if kept compliant

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

$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

$550

5.5 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,509 / 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

+3 more

Bandwidth Waste

$0.76 /mo

9538.6 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~954 KB per page load
    Saves $0.76/mo

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

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

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

Fix 5 critical issues to capture this value

How this is calculated

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

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

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

Was this report useful?

Thanks for your feedback!

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

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

39
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
85
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
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.

1.59 s

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

19.19 s

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

3.29 s

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

0.001

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

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

22.66 s

Detailed Report

Audit breakdown by category with detailed findings.

39

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

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

Learn more

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

Source: Google web.dev / Lighthouse

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: DoorDash to offer stablecoin payments to users via Tempo blockchain
path: 1,HTML,1,BODY,0,DIV,1,DIV,0,DIV,4,DIV,3,DIV,0,MAIN,0,DIV,0,DIV,3,DIV,1,DIV,0,UL,5,LI,1,DIV,0,ARTICLE,0,A,0,FIGURE,0,DIV,2,IMG
selector: a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
snippet: <img src="https://images.cointelegraph.com/cdn-cgi/image/format=auto,onerror=redirec…" srcset="https://images.cointelegraph.com/cdn-cgi/image/format=auto,onerror=redirec…" alt="DoorDash to offer stablecoin payments to users via Tempo blockchain" loading="lazy" fetchpriority="low" decoding="async" class="lazy-image__img post-card__image">

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
New York targets Coinbase, Gemini in fresh crackdown on prediction markets a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...181.0 KiB166.0 KiB
Nium taps Coinbase to add USDC into global payments network a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...161.6 KiB146.6 KiB
Core Scientific plans $3.3B debt raise to fund AI data center push a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...134.9 KiB119.9 KiB
Blockchain.com adds perpetual futures trading to self-custody wallets a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...122.8 KiB107.8 KiB
European investors may switch banks for better crypto access, survey finds a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...106.4 KiB91.4 KiB
DoorDash to offer stablecoin payments to users via Tempo blockchain a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...105.1 KiB90.1 KiB
div.header-zone__flower > div.container > div.relative > img.image_GVcVq div.header-zone__flower > div.container > div.relative > img.image_GVcVq
/images/373_aHR0cHM6Ly9zMy5jb2ludGVsZWdyYXBoLmNvbS9zdG9yY...88.6 KiB88.0 KiB
Here’s what happened in crypto today a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...102.1 KiB87.1 KiB
Fed chair nominee pressed on potential conflicts of interest, independence a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...81.7 KiB66.7 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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.

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
Style & Layout24.7 s
Script Evaluation19.5 s
Other13.0 s
Rendering6.1 s
Script Parsing & Compilation971 ms
Garbage Collection617 ms
Parse HTML & CSS155 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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 27.1 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Cointelegraph iOS App div > div.flex > a > img.cursor-pointer
Cointelegraph Android App div > div.flex > a > img.cursor-pointer

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

Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 11 user timings
Avoid long main-thread tasks 20 long tasks found
Network Requests
Network Round Trip Times 90 ms
Server Backend Latencies 320 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 130 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
Avoid non-composited animations
85

Accessibility

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

Contrast

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
MOBILE APPS div.md:max-w-243 > div.py-4 > div.flex-none > div.text-center
COINTELEGRAPH NEWSLETTER div.md:max-w-243 > div.py-4 > div.flex > div.text-center
Cointelegraph covers fintech, blockchain and Bitcoin bringing you the latest cr… div.md:max-w-243 > div.py-4 > div.flex > div.text-center
© Cointelegraph 2013 - 2026 div.py-4 > div.flex > div > div
Cointelegraph is committed to providing independent, high-quality journalism ac… div.md:max-w-243 > div.py-4 > div.text-start > p
All news, reviews, and analysis are produced with full journalistic independenc… div.md:max-w-243 > div.py-4 > div.text-start > p

These are opportunities to improve the legibility of your content.

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
div.flex > div.flex > div.w-[4.5rem] > img.image_GVcVq div.flex > div.flex > div.w-[4.5rem] > img.image_GVcVq
div.header-zone__flower > div.container > div.relative > img.image_GVcVq div.header-zone__flower > div.container > div.relative > img.image_GVcVq
ul.grid > li.group-[.inline]:mb-8 > div.rounded-lg > img.image_GVcVq ul.grid > li.group-[.inline]:mb-8 > div.rounded-lg > img.image_GVcVq

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.

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>`
Buttons have an accessible name
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.
Document has a `<title>` element
`<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
Touch targets have sufficient size and spacing.
Document has a main landmark.
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[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 use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
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
`[role]` values are valid
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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
Heading elements appear in a sequentially-descending order
`<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.
No element has a `[tabindex]` value greater than 0
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
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.
81

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
AttributionReporting

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 browser errors logged to the console
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
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.

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
div.flex > div.flex > div.w-[4.5rem] > img.image_GVcVq div.flex > div.flex > div.w-[4.5rem] > img.image_GVcVq
div.header-zone__flower > div.container > div.relative > img.image_GVcVq div.header-zone__flower > div.container > div.relative > img.image_GVcVq
ul.grid > li.group-[.inline]:mb-8 > div.rounded-lg > img.image_GVcVq ul.grid > li.group-[.inline]:mb-8 > div.rounded-lg > img.image_GVcVq

hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about `hreflang`.

Why this matters

Performance issues directly impact user engagement and conversion rates.

head > link#33

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
Links are crawlable
robots.txt is valid
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

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

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

403 ms

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

4.72 s

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

566 ms

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

0.097

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

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

4.79 s

Detailed Report

Audit breakdown by category with detailed findings.

45

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:2.623 source:map[column:177482 line:2 type:source-location url:https://cointelegraph.com/_nuxt/0e94ba4.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:45.41 source:map[type:text value:[unattributed]]] map[reflowTime:4.789 source:map[column:198858 line:1 type:source-location url:https://cointelegraph.com/_nuxt/41060f2.js urlProvider:network]] map[reflowTime:27.885 source:map[column:185254 line:1 type:source-location url:https://cointelegraph.com/_nuxt/0e94ba4.js urlProvider:network]] map[reflowTime:23.201 source:map[column:177512 line:1 type:source-location url:https://cointelegraph.com/_nuxt/0e94ba4.js urlProvider:network]] map[reflowTime:2.135 source:map[column:57 line:24 type:source-location url:https://static.chartbeat.com/js/chartbeat.js urlProvider:network]] map[reflowTime:0.926 source:map[column:376 line:763 type:source-location url:https://www.googletagmanager.com/gtm.js?id=GTM-N5X5C39 urlProvider:network]] map[reflowTime:1.128 source:map[column:123 line:23 type:source-location url:https://static.chartbeat.com/js/chartbeat.js urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Strategy buys 34,164 Bitcoin for $2.5B, holdings top 800,000 BTC a.cursor-pointer > figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...158.6 KiB101.2 KiB
53 DeFi projects infiltrated, 50M NEO tokens could be ‘given back’: Asia Express a.cursor-pointer > figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...100.7 KiB59.6 KiB
Group of 39 firms urge EU to fast-track DLT rules, warn of lagging the US a.cursor-pointer > figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...110.4 KiB53.0 KiB
European investors may switch banks for better crypto access, survey finds a.cursor-pointer > figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...106.4 KiB49.0 KiB
Canton, ZKsync clash over how blockchains enforce rules a.cursor-pointer > figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...104.9 KiB47.5 KiB
Crypto hackers stole $17B over past 10 years: DefiLlama a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...57.8 KiB43.2 KiB
New York targets Coinbase, Gemini in fresh crackdown on prediction markets a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...52.9 KiB38.4 KiB
Nium taps Coinbase to add USDC into global payments network a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...49.8 KiB35.2 KiB
Bitcoin risks losing $70K as Strategy's STRC slips below $100 a.cursor-pointer > figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...90.8 KiB33.4 KiB
Core Scientific plans $3.3B debt raise to fund AI data center push a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...47.8 KiB33.3 KiB
Scammers demand crypto from stranded ships in Strait of Hormuz: Report a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...46.5 KiB31.9 KiB
Blockchain.com adds perpetual futures trading to self-custody wallets a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...46.4 KiB31.8 KiB
South Korea tax agency opens bidding for crypto tracing tool a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...44.3 KiB29.7 KiB
BitMEX taps Zodia Custody for off-exchange collateral trading a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...41.8 KiB27.2 KiB
European investors may switch banks for better crypto access, survey finds a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...37.8 KiB23.2 KiB
Bank of Korea governor backs CBDCs, deposit tokens in first address a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...37.1 KiB22.5 KiB
Kelp DAO attacker moves $175M in Ether after exploit: Arkham a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...37.1 KiB22.5 KiB
DoorDash to offer stablecoin payments to users via Tempo blockchain a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...36.8 KiB22.2 KiB
Here’s what happened in crypto today a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...31.7 KiB17.1 KiB
Fed chair nominee pressed on potential conflicts of interest, independence a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...31.4 KiB16.8 KiB
UK plans payments rule changes for stablecoins, tokenized deposits a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...30.8 KiB16.2 KiB
Play: Video div#frame > picture > img#fallbackPlaceholder
i.ytimg.com/vi_webp/4mAIAoxtawI/hqdefault.webp35.9 KiB14.2 KiB
Philippines SEC flags dYdX, six crypto platforms as unauthorized a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...28.5 KiB13.9 KiB
Fake delivery driver targets French crypto worker in armed home invasion a.post-card__figure-link > figure.post-card__figure > div.lazy-image > img.lazy-image__img
/cdn-cgi/image/format=auto,onerror=redirect,quality=90,wi...21.5 KiB6.9 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:282.2690002441406 label:Time to first byte subpart:timeToFirstByte] map[duration:8942.936999755859 label:Resource load delay subpart:resourceLoadDelay] map[duration:28.735 label:Resource load duration subpart:resourceLoadDuration] map[duration:436.638 label:Element render delay subpart:elementRenderDelay]]
lhId: page-8-IMG
nodeLabel: Bitcoin risks losing $70K as Strategy's STRC slips below $100
path: 0,ARTICLE,0,A,0,FIGURE,0,DIV,2,IMG
selector: a.cursor-pointer > figure > div.lazy-image > img.lazy-image__img
snippet: <img src="https://images.cointelegraph.com/cdn-cgi/image/format=auto,onerror=redirec…" srcset="https://images.cointelegraph.com/cdn-cgi/image/format=auto,onerror=redirec…" alt="Bitcoin risks losing $70K as Strategy's STRC slips below $100" loading="eager" fetchpriority="high" decoding="async" class="lazy-image__img">

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-8-IMG
nodeLabel: Bitcoin risks losing $70K as Strategy's STRC slips below $100
path: 0,ARTICLE,0,A,0,FIGURE,0,DIV,2,IMG
selector: a.cursor-pointer > figure > div.lazy-image > img.lazy-image__img
snippet: <img src="https://images.cointelegraph.com/cdn-cgi/image/format=auto,onerror=redirec…" srcset="https://images.cointelegraph.com/cdn-cgi/image/format=auto,onerror=redirec…" alt="Bitcoin risks losing $70K as Strategy's STRC slips below $100" loading="eager" fetchpriority="high" decoding="async" class="lazy-image__img">

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

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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.

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
Style & Layout5.2 s
Other5.0 s
Script Evaluation4.9 s
Rendering1.9 s
Script Parsing & Compilation236 ms
Garbage Collection113 ms
Parse HTML & CSS41 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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 25.5 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Cointelegraph Android App div > div.flex > a > img.cursor-pointer
cointelegraph.com/assets/img/mobile-stores/play-store-badge-en.svg
Cointelegraph iOS App div > div.flex > a > img.cursor-pointer
cointelegraph.com/assets/img/mobile-stores/app-store-badge-en.svg

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

Layout shift culprits
Document request latency
Optimize DOM size
Font display
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 11 user timings
Avoid long main-thread tasks 7 long tasks found
Network Requests
Network Round Trip Times 90 ms
Server Backend Latencies 320 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 260 ms
Avoid large layout shifts 8 layout shifts found
INP breakdown
Avoid non-composited animations
85

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.bg-bg-primary > div.flex > div.group > button.p-3 div.bg-bg-primary > div.flex > div.group > button.p-3

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flex > div.z-[2] > div.flex > a.p-0.5 div.flex > div.z-[2] > div.flex > a.p-0.5
div.flex > div.z-[2] > div.flex > a.p-0.5 div.flex > div.z-[2] > div.flex > a.p-0.5
div.flex > div.z-[2] > div.flex > a.p-0.5 div.flex > div.z-[2] > div.flex > a.p-0.5
div.flex > div.z-[2] > div.flex > a.p-0.5 div.flex > div.z-[2] > div.flex > a.p-0.5

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.

Contrast

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Subscribe div.stretch-youtube__action > a.stretch-youtube__action-link > span.stretch-youtube__link-wrp > span.stretch-youtube__link-cap
NEWS div.py-8 > nav.items-stretch > div.max-w-38.5 > div.uppercase
INDEX div.py-8 > nav.items-stretch > div.max-w-38.5 > div.uppercase
IN DEPTH div.py-8 > nav.items-stretch > div.max-w-38.5 > div.uppercase
LEARN div.py-8 > nav.items-stretch > div.max-w-38.5 > div.uppercase
INDUSTRY div.py-8 > nav.items-stretch > div.max-w-38.5 > div.uppercase
ABOUT US div.py-8 > nav.items-stretch > div.max-w-38.5 > div.uppercase
MOBILE APPS div.md:max-w-243 > div.py-4 > div.flex-none > div.text-center
COINTELEGRAPH NEWSLETTER div.md:max-w-243 > div.py-4 > div.flex > div.text-center
Cointelegraph covers fintech, blockchain and Bitcoin bringing you the latest cr… div.md:max-w-243 > div.py-4 > div.flex > div.text-center
FOLLOW US div.py-4 > div.flex > div.hidden > div.text-bodySStrong
© Cointelegraph 2013 - 2026 div.py-4 > div.flex > div > div
Cointelegraph is committed to providing independent, high-quality journalism ac… div.md:max-w-243 > div.py-4 > div.text-start > p
All news, reviews, and analysis are produced with full journalistic independenc… div.md:max-w-243 > div.py-4 > div.text-start > p

These are opportunities to improve the legibility of your content.

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>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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.
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Document has a main landmark.
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[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
`[role]`s have all required `[aria-*]` attributes
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
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
Heading elements appear in a sequentially-descending order
`<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.
No element has a `[tabindex]` value greater than 0
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
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.
81

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
AttributionReporting

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 browser errors logged to the console
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
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

hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about `hreflang`.

Why this matters

Performance issues directly impact user engagement and conversion rates.

head > link#33

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
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `rel=canonical`

Send Feedback