Skip to content
https://cnet.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

26

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

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:15.585 source:map[column:23360 line:1 type:source-location url:https://www.cnet.com/a/neutron/708c8bde17c4.modern.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:3.165 source:map[type:text value:[unattributed]]] map[reflowTime:8.531 source:map[column:104 line:160 type:source-location url:https://cdn.ziffstatic.com/pg/cnet.js urlProvider:network]] map[reflowTime:0.495 source:map[column:248670 line:1 type:source-location url:https://www.cnet.com/a/neutron/eb626a70ccf6.modern.js urlProvider:network]] map[reflowTime:5.329 source:map[column:70729 line:0 type:source-location url:https://www.cnet.com/a/neutron/3d1897abd40d.modern.js urlProvider:network]] map[reflowTime:0.784 source:map[column:253687 line:0 type:source-location url:https://www.cnet.com/a/neutron/3d1897abd40d.modern.js urlProvider:network]] map[reflowTime:4.771 source:map[column:63225 line:0 type:source-location url:https://www.cnet.com/a/neutron/d52d1ea3a562.modern.js urlProvider:network]] map[reflowTime:2.903 source:map[column:6978 line:0 type:source-location url:https://www.cnet.com/a/neutron/a5012ebf0873.modern.js urlProvider:network]] map[reflowTime:15.554 source:map[column:58912 line:0 type:source-location url:https://www.cnet.com/a/neutron/d52d1ea3a562.modern.js urlProvider:network]] map[reflowTime:0.031 source:map[column:61837 line:0 type:source-location url:https://www.cnet.com/a/neutron/d52d1ea3a562.modern.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
div.c-storiesNeonHighlightsLead_media > div.c-cmsImage > div.c-cmsImage_video > video div.c-storiesNeonHighlightsLead_media > div.c-cmsImage > div.c-cmsImage_video > video
/a/img/resize/45dc3ed12ffab202ee43fee530a3c7516d9b6e72/hu...544.3 KiB495.8 KiB
/a/img/resize/67645cd53bcf5acd9b0ef7347e22f12b69936d69/hu...6.8 KiB4.0 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-VIDEO
nodeLabel: div.c-storiesNeonHighlightsLead_media > div.c-cmsImage > div.c-cmsImage_video > video
path: 1,HTML,1,BODY,1,DIV,1,DIV,0,DIV,10,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,1,DIV,0,DIV,0,A,0,DIV,0,DIV,0,DIV,0,DIV,0,VIDEO
selector: div.c-storiesNeonHighlightsLead_media > div.c-cmsImage > div.c-cmsImage_video > video
snippet: <video src="https://www.cnet.com/a/img/resize/102c5db689c0443be53c7d05547f1392c3165004…" poster="https://www.cnet.com/a/img/resize/45dc3ed12ffab202ee43fee530a3c7516d9b6e72…" width="1280" height="720" autoplay="autoplay" loop="loop" muted="muted" playsinline="" disableremoteplayback="">

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
cdn.ziffstatic.com/pg/cnet.prebid.js2867.0 s232.1 KiB
openads-cdn.adsrvr.org/openadsjs/build/v1.0/ziffdavis/openads.js0.0 ms98.3 KiB
client.aps.amazon-adsystem.com/publisher.js3600.0 s90.9 KiB
cdn.ziffstatic.com/pg/cnet.js2780.0 s86.3 KiB
cdn.static.zdbb.net/eu/js/z0WVjCBSEeGLoxIxOQVEwQ.min.js86400.0 s175.1 KiB
/J3UXFee1xclY-bfFlWh1mIZ_phU/gpt_and_prebid/config.js1100.0 s57.9 KiB
cdn.id5-sync.com/api/1.0/id5-api.js3600.0 s34.4 KiB
pub.doubleverify.com/dvtag/33936767/DV1379166/pub.js900.0 s30.8 KiB
cdn.ziffstatic.com/jst/zdconsent_eu.js273.0 s27.8 KiB
cdn.ziffstatic.com/jst/otBannerSdk.202512.1.0.js599977.0 s126.2 KiB
static.chartbeat.com/js/chartbeat.js86400.0 s15.9 KiB
static.trueanthem.com/scripts/ta.c34341.js86400.0 s10.7 KiB
config.aps.amazon-adsystem.com/configs/31583600.0 s2.8 KiB
/vendor/474a4045-633c-42d5-8a01-35be527d3b9a/lightbox_inl...0.0 ms1.8 KiB
cdn.ziffstatic.com/jst/otTCF.202512.1.0.js599977.0 s17.7 KiB
cdn.ziffstatic.com/pg/cnet.css2694.0 s1001 B
/a4flkt7l2b/z9gd/45898/www.cnet.com/jsonp/z?cb=1776295376...0.0 ms793 B
static.trueanthem.com/scripts/ta.js86400.0 s1.3 KiB
/w37htfhcq2/z9g/digibox.gif?c=1776295376141&h=www.cnet.co...0.0 ms301 B
cdn.ziffstatic.com/ajs?zoneid=a3600.0 s298 B

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.

URLTransfer SizeDuration
cdn.ziffstatic.com/pg/cnet.css1001 B755 ms

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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.

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: 751 ms
URLTime Spent
cnet.com/751 ms
www.cnet.com/0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 525 ms
URLTime Spent
www.cnet.com/625 ms

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

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.8 s 1.3 MiB
URLTransfer SizeEst Savings
cdn.ziffstatic.com/pg/cnet.prebid.js231.9 KiB188.2 KiB
www.cnet.com/a/neutron/47d696a75771.modern.js376.7 KiB179.5 KiB
/pagead/managed/js/gpt/m202604100101/pubads_impl.js186.4 KiB127.0 KiB
cdn.confiant-integrations.net/gptprebidnative/202603241056/wrap.js141.5 KiB85.5 KiB
www.cnet.com/a/neutron/a922d2a89ddd.modern.js223.5 KiB71.7 KiB
cdn.ziffstatic.com/jst/otBannerSdk.202512.1.0.js126.2 KiB71.6 KiB
/w37htfhcq2/vendor/474a4045-633c-42d5-8a01-35be527d3b9a/m...116.3 KiB69.1 KiB
cdn.ziffstatic.com/pg/cnet.js86.1 KiB68.4 KiB
openads-cdn.adsrvr.org/openadsjs/build/v1.0/ziffdavis/openads.js98.0 KiB67.4 KiB
www.cnet.com/a/neutron/3d1897abd40d.modern.js83.4 KiB62.8 KiB
www.googletagmanager.com/gtag/destination?id=G-R820W8QX02&cx=c&gtm=4e64e1161.0 KiB62.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-NHBTHTVT115.5 KiB61.8 KiB
client.aps.amazon-adsystem.com/publisher.js90.5 KiB50.0 KiB
www.cnet.com/a/neutron/eb626a70ccf6.modern.js105.5 KiB47.1 KiB
cdn.static.zdbb.net/js/z0WVjCBSEeGLoxIxOQVEwQ.min.js174.7 KiB41.5 KiB
fundingchoicesmessages.google.com/i/pub-8038936283815017?ers=168.5 KiB34.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.

URLTotal CPU TimeScript EvaluationScript Parse
www.cnet.com/a/neutron/eb626a70ccf6.modern.js3.3 s3.0 s28 ms
www.cnet.com/1.4 s96 ms248 ms
Unattributable1.2 s135 ms0.0 ms
cdn.ziffstatic.com/jst/otTCF.202512.1.0.js598 ms522 ms4.8 ms
www.cnet.com/a/neutron/6518b13b9504.modern.js512 ms439 ms4.2 ms
client.aps.amazon-adsystem.com/publisher.js410 ms372 ms32 ms
/pagead/managed/js/gpt/m202604100101/pubads_impl.js401 ms342 ms45 ms
www.cnet.com/a/neutron/47d696a75771.modern.js396 ms262 ms5.0 ms
cdn.ziffstatic.com/jst/otBannerSdk.202512.1.0.js391 ms287 ms41 ms
www.googletagmanager.com/gtag/destination?id=G-R820W8QX02&cx=c&gtm=4e64e1357 ms308 ms47 ms
www.cnet.com/a/neutron/da62f8586255.modern.js334 ms306 ms3.0 ms
cdn.confiant-integrations.net/gptprebidnative/202603241056/wrap.js319 ms286 ms30 ms
cdn.ziffstatic.com/pg/cnet.js217 ms122 ms26 ms
www.cnet.com/a/neutron/2737a08764f1.modern.js191 ms190 ms0.4 ms
fundingchoicesmessages.google.com/i/pub-8038936283815017?ers=1191 ms172 ms16 ms
cdn.ziffstatic.com/pg/cnet.prebid.js186 ms128 ms56 ms
/w37htfhcq2/vendor/474a4045-633c-42d5-8a01-35be527d3b9a/m...185 ms96 ms33 ms
www.googletagmanager.com/gtm.js?id=GTM-NHBTHTVT179 ms152 ms24 ms
openads-cdn.adsrvr.org/openadsjs/build/v1.0/ziffdavis/openads.js159 ms122 ms36 ms
www.cnet.com/a/neutron/d77860478607.modern.js143 ms141 ms1.6 ms
/a4flkt7l2b/z9gd/45898/www.cnet.com/jsonp/z?cb=1776295376...140 ms134 ms0.3 ms
/J3UXFee1xclY-bfFlWh1mIZ_phU/gpt_and_prebid/config.js101 ms24 ms25 ms
frugalfiestas.com/public/de27c0d40747/04bc79fd5f2951beba7a20d2.js101 ms62 ms9.6 ms
securepubads.g.doubleclick.net/tag/js/gpt.js100 ms89 ms11 ms
pub.doubleverify.com/dvtag/33936767/DV1379166/pub.js86 ms73 ms12 ms
www.cnet.com/a/neutron/708c8bde17c4.modern.js84 ms4.6 ms0.1 ms
cdn.ziffstatic.com/jst/zdconsent.js72 ms59 ms6.3 ms
static.chartbeat.com/js/chartbeat.js53 ms48 ms4.0 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation8.3 s
Other1.4 s
Style & Layout856 ms
Script Parsing & Compilation800 ms
Garbage Collection396 ms
Parse HTML & CSS316 ms
Rendering130 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
/a/img/resize/102c5db689c0443be53c7d05547f1392c3165004/hu...1.9 MiB
/a/img/resize/45dc3ed12ffab202ee43fee530a3c7516d9b6e72/hu...544.9 KiB
www.cnet.com/428.9 KiB
www.cnet.com/a/neutron/47d696a75771.modern.js381.0 KiB
www.cnet.com/a/neutron/fonts/Stardust/Variable.woff2377.4 KiB
/a/img/resize/16bfc489dc0310fe6f83850831773fcb861e8dad/hu...373.0 KiB
cdn.ziffstatic.com/pg/cnet.prebid.js232.1 KiB
www.cnet.com/a/neutron/a922d2a89ddd.modern.js223.6 KiB
/pagead/managed/js/gpt/m202604100101/pubads_impl.js186.4 KiB
cdn.static.zdbb.net/eu/js/z0WVjCBSEeGLoxIxOQVEwQ.min.js175.1 KiB

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

●Layout shift culprits
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●User Timing marks and measures 25 user timings
●Avoid long main-thread tasks 20 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 120 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
92

Accessibility

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

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.c-siteHeaderMasthead_container > div.c-siteHeaderMasthead_logoLogin > div.c-siteHeaderMasthead_searchLogin > button.c-siteHeaderMasthead_mobileNav div.c-siteHeaderMasthead_container > div.c-siteHeaderMasthead_logoLogin > div.c-siteHeaderMasthead_searchLogin > button.c-siteHeaderMasthead_mobileNav

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

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
2 div.c-paginationControl_buttons-wrapper > div.c-paginationControl_buttons > div.c-paginationControl_button > a
3 div.c-paginationControl_buttons-wrapper > div.c-paginationControl_buttons > div.c-paginationControl_button > a
4 div.c-paginationControl_buttons-wrapper > div.c-paginationControl_buttons > div.c-paginationControl_button > a
5 div.c-paginationControl_buttons-wrapper > div.c-paginationControl_buttons > div.c-paginationControl_button > a
6 div.c-paginationControl_buttons-wrapper > div.c-paginationControl_buttons > div.c-paginationControl_button > a
7 div.c-paginationControl_buttons-wrapper > div.c-paginationControl_buttons > div.c-paginationControl_button > a
8 div.c-paginationControl_buttons-wrapper > div.c-paginationControl_buttons > div.c-paginationControl_button > a
9 div.c-paginationControl_buttons-wrapper > div.c-paginationControl_buttons > div.c-paginationControl_button > a

These items highlight common accessibility best practices.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Manage Preferences div.md:flex > div.md:max-w-80 > div.mb-6 > a.primary-link
Our Privacy Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<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
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○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.
○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.
100

Best Practices

General

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.

URL
www.cnet.com/a/neutron/a922d2a89ddd.modern.js
www.cnet.com/a/neutron/47d696a75771.modern.js
www.cnet.com/
●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 browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
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.

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
Learn more div.c-storiesExpertise > div.c-storiesExpertise_headContainer > div.c-storiesExpertise_ctaContainer > a.c-storiesExpertise_cta

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

○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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback