Skip to content
Audit Complete

Results for https://phonearena.com

Visit site
Spain Spain · Madrid Completed: Apr 22, 2026 22:02 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)
C70

Site Health

Score: 70 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Missing signals may be hurting your search visibility.

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.

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

Amazon ALB · 46 peers
You 70
·
Avg 71
At average
0 50 100
Better than 10% of Amazon ALB sites See full Amazon ALB benchmark →
AngularJS · 396 peers
You 70
·
Avg 73
At average
0 50 100
Better than 14% of AngularJS sites See full AngularJS 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

Cookie 'AWSALB' is missing the Secure flag

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

Security › Cookie Security
3

No Content-Security-Policy header found

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

Security › Content Security Policy
4

Soft 404: server returns HTTP 200 for non-existent pages

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

Accessibility › 404 Error Page
5

131 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fphonearena.com)](https://beavercheck.com/results/a8b1b2bf-5d98-4551-b17c-3d734681c407)
<a href="https://beavercheck.com/results/a8b1b2bf-5d98-4551-b17c-3d734681c407"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fphonearena.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fphonearena.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 5.9s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes 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 user trust.

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

Conversion Barriers

2 critical 6 warning

8 barrier(s) likely increasing bounce by ~30%.

Speed (2)

Page takes 5.9s to load

+12% bounce

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

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

Page feels frozen for 991ms

+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

Content (4)

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

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (1)

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

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

Return on Investment

$500 investment → $4,440/month returns + USD 150,000 risk avoided

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

Investment

$500

5h · 5 findings

Monthly returns

$4,440 /mo

~$53,278 / year

  • Conversions recovered $4,439
  • Bandwidth savings $0.74

Regulatory risk avoided

USD 150,000

if kept compliant

  • ADA Title III USD 150,000

Payback period

0 12mo 24mo

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

$500

5.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$12,501 / month at risk

~$150,009 / year if left unfixed

Compliance Risk

$150,000

ADA Title III
  • No <nav> landmark found
    ADA Title III: USD 25,000 – USD 150,000
  • Skip navigation link is missing (WCAG 2.4.1)
    ADA Title III: USD 25,000 – USD 150,000

Bandwidth Waste

$0.74 /mo

9213.8 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~921 KB per page load
    Saves $0.74/mo

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

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

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

Fix 4 critical issues to capture this value

How this is calculated

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

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

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

Was this report useful?

Thanks for your feedback!

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

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

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

4.01 s

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

5.89 s

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

991 ms

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.

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

20.36 s

Detailed Report

Audit breakdown by category with detailed findings.

43

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.

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: The holy trinity of Ultra camera phones for 2026 is now complete. Choose wisely!
path: 1,HTML,1,BODY,8,ARTICLE,1,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,0,IMG
selector: div.primary-big-tile > div.tile-picture > picture > img.cover
snippet: <img src="https://m-cdn.phonearena.com/images/article/179842-wide-two_800/The-holy-t…" alt="The holy trinity of Ultra camera phones for 2026 is now complete. Choose w…" class="cover" loading="" fetchpriority="high">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
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.

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
T-Mobile shares crash after talk of Deutsche Telekom merger div#article-179845 > div.tile-picture > picture > img.cover
/images/article/179845-wide-two_800/T-Mobile-shares-crash...103.5 KiB96.6 KiB
Tello’s flexible plans have been simplified, pay less for even more data! div#article-179400 > div.tile-picture > picture > img.cover
/images/article/179400-wide-two_800/Tellos-flexible-plans...47.3 KiB40.4 KiB
AT&T is the first of the "Big 3" carriers in the U.S. to tell us how it is doin… div#article-179851 > div.tile-picture > picture > img.cover
/images/article/179851-wide-two_800/AT-T-is-the-first-of-...29.1 KiB23.1 KiB
Samsung hands Galaxy Z Fold 7 and Z Flip 7 shoppers a $300 reason to stop waiti… div#article-179857 > div.tile-picture > picture > img.cover
/images/article/179857-wide-two_800/Samsung-hands-Galaxy-...27.7 KiB22.0 KiB
Verizon says it wants to treat you like a human, but its plan to do that feels … div#article-179854 > div.tile-picture > picture > img.cover
/images/article/179854-wide-two_800/Verizon-says-it-wants...25.5 KiB20.2 KiB
You wouldn't want to put a case on this one – it's just too pretty div#article-179848 > div.tile-picture > picture > img.cover
/images/article/179848-wide-two_800/You-wouldnt-want-to-p...23.6 KiB18.7 KiB
T-Mobile shares crash after talk of Deutsche Telekom merger div.fourth-tile > div.tile-picture > picture > img.cover
/images/article/179845-wide-two_350/T-Mobile-shares-crash...18.4 KiB8.9 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.2 s
URLTime Spent
phonearena.com/2.2 s
www.phonearena.com/0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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: 150 ms 37.1 KiB
URLTransfer SizeEst Savings
/?b=build/wp/css&1776850282965&f=pogo-fixes-mobile.css,ad...29.7 KiB23.0 KiB
16.6 KiB14.1 KiB

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
Script Evaluation4.3 s
Other1.6 s
Script Parsing & Compilation474 ms
Style & Layout377 ms
Garbage Collection257 ms
Rendering145 ms
Parse HTML & CSS92 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 with WebSocket cannot enter back/forward cache.Pending browser support
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
Back/forward cache is disabled because WebSocket has been used.Not actionable

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

Why this matters

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

Learn more

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

Source: Google web.dev / Lighthouse

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
PhoneArena | Phone News, Reviews, Deals and Specs div.m-c > div.gc-3 > a.logo > img
s-cdn.phonearena.com/build/wp/images/logo.svg
PhoneArena | Phone News, Reviews, Deals and Specs body.home > nav.f-w > a.logo > img
s-cdn.phonearena.com/build/wp/images/logo-blue.svg

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

Layout shift culprits
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 16 user timings
Avoid long main-thread tasks 20 long tasks found
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 1,350 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 270 ms
INP breakdown
Avoid non-composited animations
Avoid large layout shifts
75

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#search-popover > form > div.input-group > button.button div#search-popover > form > div.input-group > button.button

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.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb
div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb
div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb
div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb
div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb
div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb
div.videos-section-container > div.videos-container > div.video-item > img.video-item-thumb div.videos-section-container > div.videos-container > div.video-item > img.video-item-thumb
div.videos-section-container > div.videos-container > div.video-item > img.video-item-thumb div.videos-section-container > div.videos-container > div.video-item > img.video-item-thumb
div.videos-section-container > div.videos-container > div.video-item > img.video-item-thumb div.videos-section-container > div.videos-container > div.video-item > img.video-item-thumb

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
body.home > nav.f-w > a.hamburger-menu body.home > nav.f-w > a.hamburger-menu
div.mobile-menu > div.menu-socials > div.menu-socials-icons > a div.mobile-menu > div.menu-socials > div.menu-socials-icons > a
div.mobile-menu > div.menu-socials > div.menu-socials-icons > a div.mobile-menu > div.menu-socials > div.menu-socials-icons > a
div.mobile-menu > div.menu-socials > div.menu-socials-icons > a div.mobile-menu > div.menu-socials > div.menu-socials-icons > a
div.mobile-menu > div.menu-socials > div.menu-socials-icons > a div.mobile-menu > div.menu-socials > div.menu-socials-icons > a
body.home > nav.f-w > a.search body.home > nav.f-w > a.search
div.m-c > div.gc-3 > div.social > a div.m-c > div.gc-3 > div.social > a
div.m-c > div.gc-3 > div.social > a div.m-c > div.gc-3 > div.social > a
div.m-c > div.gc-3 > div.social > a div.m-c > div.gc-3 > div.social > a
div.m-c > div.gc-3 > div.social > a div.m-c > div.gc-3 > div.social > a

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
Sebastian Pier div.primary-big-tile > div.tile-content > div.info > span.info-meta
Alan Friedman div.primary-small-tile > div.tile-content > div.info > span.info-meta
Adrian Diaconescu div.primary-small-tile > div.tile-content > div.info > span.info-meta
Johanna Romero • 1h ago div#article-179857 > div.tile-content > div.info > span.info-meta
1h ago div.tile-content > div.info > span.info-meta > time
Preslav Kateliev • 2w ago div#article-179400 > div.tile-content > div.info > span.info-meta
2w ago div.tile-content > div.info > span.info-meta > time
Alan Friedman • 2h ago div#article-179851 > div.tile-content > div.info > span.info-meta
2h ago div.tile-content > div.info > span.info-meta > time
Ilia Temelkov • 2h ago div#article-179856 > div.tile-content > div.info > span.info-meta
2h ago div.tile-content > div.info > span.info-meta > time
Anam Hamid • 2h ago div#article-179847 > div.tile-content > div.info > span.info-meta
2h ago div.tile-content > div.info > span.info-meta > time
Johanna Romero • 2h ago div#article-179854 > div.tile-content > div.info > span.info-meta
2h ago div.tile-content > div.info > span.info-meta > time
Johanna Romero • 3h ago div#article-179855 > div.tile-content > div.info > span.info-meta
3h ago div.tile-content > div.info > span.info-meta > time
Adrian Diaconescu • 4h ago div#article-179850 > div.tile-content > div.info > span.info-meta
4h ago div.tile-content > div.info > span.info-meta > time
Anam Hamid • 5h ago div#article-179852 > div.tile-content > div.info > span.info-meta
5h ago div.tile-content > div.info > span.info-meta > time
Johanna Romero • 6h ago div#article-179853 > div.tile-content > div.info > span.info-meta
6h ago div.tile-content > div.info > span.info-meta > time
Alan Friedman • 8h ago div#article-179845 > div.tile-content > div.info > span.info-meta
8h ago div.tile-content > div.info > span.info-meta > time
Sebastian Pier • 9h ago div#article-179848 > div.tile-content > div.info > span.info-meta
9h ago div.tile-content > div.info > span.info-meta > time
15 div#article-179848 > div.tile-content > div.info > a.info-comments
More News div#latest-stories > div.m-c > div.gc-6 > a.button
Mariyan Slavov div.fourth-tile > div.tile-content > div.info > span.info-meta
Aman Kumar div.fourth-tile > div.tile-content > div.info > span.info-meta
Abdullah Asim div.fourth-tile > div.tile-content > div.info > span.info-meta
Anam Hamid div.fourth-tile > div.tile-content > div.info > span.info-meta
Alan Friedman div.fourth-tile > div.tile-content > div.info > span.info-meta
Alan Friedman div.fourth-tile > div.tile-content > div.info > span.info-meta
Preslav Mladenov • 1h ago div.secondary-tile > div.tile-content > div.info > span.info-meta
1h ago div.tile-content > div.info > span.info-meta > time
Adrian Diaconescu • 14h ago div.secondary-tile > div.tile-content > div.info > span.info-meta
14h ago div.tile-content > div.info > span.info-meta > time
Preslav Mladenov • 1d ago div.secondary-tile > div.tile-content > div.info > span.info-meta
1d ago div.tile-content > div.info > span.info-meta > time
Adrian Diaconescu • 1d ago div.secondary-tile > div.tile-content > div.info > span.info-meta
1d ago div.tile-content > div.info > span.info-meta > time
Polina Kovalakova • 1d ago div.secondary-tile > div.tile-content > div.info > span.info-meta
1d ago div.tile-content > div.info > span.info-meta > time
Preslav Mladenov • 1d ago div.secondary-tile > div.tile-content > div.info > span.info-meta
1d ago div.tile-content > div.info > span.info-meta > time
Preslav Mladenov • 1d ago div.secondary-tile > div.tile-content > div.info > span.info-meta
1d ago div.tile-content > div.info > span.info-meta > time
Preslav Mladenov • 1d ago div.secondary-tile > div.tile-content > div.info > span.info-meta
1d ago div.tile-content > div.info > span.info-meta > time
See All Deals div#latest-deals > div.m-c > div.gc-6 > a.button
Anam Hamid div.fourth-tile > div.tile-content > div.info > span.info-meta
Johanna Romero div.fourth-tile > div.tile-content > div.info > span.info-meta
Sebastian Pier div.fourth-tile > div.tile-content > div.info > span.info-meta
Mariyan Slavov div.fourth-tile > div.tile-content > div.info > span.info-meta
Anam Hamid div.fourth-tile > div.tile-content > div.info > span.info-meta
Adrian Diaconescu div.fourth-tile > div.tile-content > div.info > span.info-meta
More Editorials div#opinion-and-analysis > div.m-c > div.gc-6 > a.button
Aman Kumar • 10h ago div#article-179841 > div.tile-content > div.info > span.info-meta
10h ago div.tile-content > div.info > span.info-meta > time
Anam Hamid • 11h ago div#article-179836 > div.tile-content > div.info > span.info-meta
11h ago div.tile-content > div.info > span.info-meta > time
11 div#article-179836 > div.tile-content > div.info > a.info-comments
Mariyan Slavov • 12h ago div#article-179772 > div.tile-content > div.info > span.info-meta
12h ago div.tile-content > div.info > span.info-meta > time
Adrian Diaconescu • 13h ago div#article-179835 > div.tile-content > div.info > span.info-meta
13h ago div.tile-content > div.info > span.info-meta > time
Aman Kumar • 13h ago div#article-179831 > div.tile-content > div.info > span.info-meta
13h ago div.tile-content > div.info > span.info-meta > time
Sebastian Pier • 14h ago div#article-179833 > div.tile-content > div.info > span.info-meta
14h ago div.tile-content > div.info > span.info-meta > time
Ilia Temelkov • 21h ago div#article-179830 > div.tile-content > div.info > span.info-meta
21h ago div.tile-content > div.info > span.info-meta > time
Ilia Temelkov • 22h ago div#article-179828 > div.tile-content > div.info > span.info-meta
22h ago div.tile-content > div.info > span.info-meta > time
Johanna Romero • 22h ago div#article-179829 > div.tile-content > div.info > span.info-meta
22h ago div.tile-content > div.info > span.info-meta > time
Johanna Romero • 23h ago div#article-179826 > div.tile-content > div.info > span.info-meta
23h ago div.tile-content > div.info > span.info-meta > time
Ilia Temelkov • 23h ago div#article-179825 > div.tile-content > div.info > span.info-meta
23h ago div.tile-content > div.info > span.info-meta > time
Johanna Romero • 1d ago div#article-179824 > div.tile-content > div.info > span.info-meta
1d ago div.tile-content > div.info > span.info-meta > time
More News div#recent-headlines > div.m-c > div.gc-6 > a.button
Mariyan Slavov div.review-big-tile > div.tile-content > div.info > span.info-meta
Preslav Kateliev div.review-small-tile > div.tile-content > div.info > span.info-meta
Mariyan Slavov div.review-small-tile > div.tile-content > div.info > span.info-meta
VERSUS div.latest-reviews-section-tiles > div.review-big-tile > div.tile-picture > div.label
Peter Kostadinov div.review-big-tile > div.tile-content > div.info > span.info-meta
VERSUS div.latest-reviews-section-tiles > div.review-small-tile > div.tile-picture > div.label
Mariyan Slavov div.review-small-tile > div.tile-content > div.info > span.info-meta
VERSUS div.latest-reviews-section-tiles > div.review-small-tile > div.tile-picture > div.label
Mariyan Slavov div.review-small-tile > div.tile-content > div.info > span.info-meta
All Reviews div#latest-reviews > div.m-c > div.gc-6 > a.button
Alan Friedman • 1d ago div#article-179822 > div.tile-content > div.info > span.info-meta
1d ago div.tile-content > div.info > span.info-meta > time
Anam Hamid • 1d ago div#article-179820 > div.tile-content > div.info > span.info-meta
1d ago div.tile-content > div.info > span.info-meta > time
Ilia Temelkov • 1d ago div#article-179821 > div.tile-content > div.info > span.info-meta
1d ago div.tile-content > div.info > span.info-meta > time
Adrian Diaconescu • 1d ago div#article-179823 > div.tile-content > div.info > span.info-meta
1d ago div.tile-content > div.info > span.info-meta > time
Johanna Romero • 1d ago div#article-179819 > div.tile-content > div.info > span.info-meta
1d ago div.tile-content > div.info > span.info-meta > time
Alan Friedman • 1d ago div#article-179816 > div.tile-content > div.info > span.info-meta
1d ago div.tile-content > div.info > span.info-meta > time
Sebastian Pier • 1d ago div#article-179809 > div.tile-content > div.info > span.info-meta
1d ago div.tile-content > div.info > span.info-meta > time
Polina Kovalakova • 1d ago div#article-179817 > div.tile-content > div.info > span.info-meta
1d ago div.tile-content > div.info > span.info-meta > time
More News div#in-case-you-missed-it > div.m-c > div.gc-6 > a.button
Anam Hamid div.secondary-small-tile > div.tile-content > div.info > span.info-meta
Sebastian Pier div.secondary-small-tile > div.tile-content > div.info > span.info-meta
Anam Hamid div.secondary-small-tile > div.tile-content > div.info > span.info-meta
More Videos div#videos-section > div.m-c > div.gc-6 > a.button

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

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
Contact Us div.gc-6 > ul.list > li > a.link
How we rate div.gc-6 > ul.list > li > a.link
Home div.gc-6 > ul.list > li > a.link
Sitemap div.gc-6 > ul.list > li > a.link

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
Form elements have associated labels
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
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
No element has a `[tabindex]` value greater than 0
`[lang]` attributes have a valid value
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.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements 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 with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
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.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
73

Best Practices

Trust and Safety

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.

Why this matters

Performance issues directly impact user engagement and conversion rates.

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
AttributionReporting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Access to XMLHttpRequest at 'https://c.amazon-adsystem.com/cdn/prod/config?src=600&u=https%3A%2F%2Fwww.phonearena.com&pubid=8ddab72d-69f0-4d85-bc1a-3c0e55c11145' from origin 'https://www.phonearena.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED

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
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
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
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
nav.f-w > div#nc-popover > div.nc-header > a.button nav.f-w > div#nc-popover > div.nc-header > a.button

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
div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb
div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb
div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb
div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb
div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb
div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb div.videos-section-container > div.shorts-container > div.shorts-item > img.shorts-item-thumb
div.videos-section-container > div.videos-container > div.video-item > img.video-item-thumb div.videos-section-container > div.videos-container > div.video-item > img.video-item-thumb
div.videos-section-container > div.videos-container > div.video-item > img.video-item-thumb div.videos-section-container > div.videos-container > div.video-item > img.video-item-thumb
div.videos-section-container > div.videos-container > div.video-item > img.video-item-thumb div.videos-section-container > div.videos-container > div.video-item > img.video-item-thumb

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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

100
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
90
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.
36
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.

284 ms

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

547 ms

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

8 ms

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.

368 ms

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

547 ms

Detailed Report

Audit breakdown by category with detailed findings.

100

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Diagnostics

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 that use WebXR are not currently eligible for back/forward cache.Actionable
Only pages with a status code of 2XX can be cached.Not actionable

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

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: 220 ms
URLTime Spent
phonearena.com/220 ms
phonearena.com/0.0 ms
Layout shift culprits
Optimize DOM size
Font display
Forced reflow
Improve image delivery
LCP breakdown
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Time to Interactive 0.5 s
Max Potential First Input Delay 60 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
Reduce unused JavaScript
Avoids enormous network payloads Total size was 513 KiB
JavaScript execution time 0.2 s
Minimizes main-thread work 0.3 s
Avoid long main-thread tasks 1 long task found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 20 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 20 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid non-composited animations
90

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.

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
`[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
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
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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Image elements have `[alt]` attributes
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
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
`<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
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
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
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 ()
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
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
36

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 are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
head > meta

Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Structured data is valid
Document has a `<title>` element
Links have descriptive text
Links are crawlable
Document has a valid `hreflang`
Image elements have `[alt]` attributes
Document has a valid `rel=canonical`

Send Feedback