Skip to content
https://lacounty.gov

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.

27

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.

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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:53.693 source:map[column:12317 line:82 type:source-location url:https://cdnjs.cloudflare.com/ajax/libs/uswds/3.13.0/js/uswds.min.js urlProvider:network]] map[reflowTime:0.034 source:map[column:3645 line:68 type:source-location url:https://cdnjs.cloudflare.com/ajax/libs/uswds/3.13.0/js/uswds.min.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
Five females standing side by side, and the woman in the middle holding a gavel div.grve-row > div.wpb_column > div.grve-element > img.grve-full-image
lacounty.gov/wp-content/uploads/2025/12/BOS-2026_new-scaled.jpg547.1 KiB503.7 KiB
Vehicles navigating a flooded street in Los Angeles, with the "Ready LA County"… div.grve-isotope-item-inner > figure.grve-hover-style-2 > div.grve-media > img.attachment-blade-grve-small-rect-horizontal
lacounty.gov/wp-content/uploads/2024/02/ready-la-county-home-page-800x600.png531.3 KiB490.1 KiB
guidecover-english-5 div.grve-isotope-item-inner > figure.grve-hover-style-2 > div.grve-media > img.attachment-blade-grve-small-rect-horizontal
lacounty.gov/wp-content/uploads/2022/05/GuideCover.English.5.png82.7 KiB72.1 KiB
LA County Closeup div.grve-isotope-item-inner > figure.grve-hover-style-2 > div.grve-media > img.attachment-blade-grve-small-rect-horizontal
lacounty.gov/wp-content/uploads/2019/01/closeup.featured-800x600.jpg81.6 KiB40.4 KiB
el condado contigo logo div.grve-isotope-item-inner > figure.grve-hover-style-2 > div.grve-media > img.attachment-blade-grve-small-rect-horizontal
lacounty.gov/wp-content/uploads/2022/03/El-Condado-Contigo-800x600.jpg33.0 KiB15.6 KiB
COUNTY OF LOS ANGELES div.grve-logo > div.grve-wrapper > a > img.grve-logo-responsive
lacounty.gov/wp-content/uploads/2022/01/LAC_Header_Logo.dk_.png13.9 KiB9.8 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:367.0520009765625 label:Time to first byte subpart:timeToFirstByte] map[duration:2198.8829990234376 label:Resource load delay subpart:resourceLoadDelay] map[duration:118.774 label:Resource load duration subpart:resourceLoadDuration] map[duration:32.578 label:Element render delay subpart:elementRenderDelay]]
lhId: page-6-SR7-IMG
nodeLabel: sr7-module#SR7_4_1 > sr7-content > sr7-slide#SR7_4_1-241 > sr7-img#SR7_4_1-241-48
path: 3,HTML,2,BODY,1,DIV,7,DIV,0,DIV,1,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,SR7-MODULE,1,SR7-CONTENT,0,SR7-SLIDE,3,SR7-IMG
selector: sr7-module#SR7_4_1 > sr7-content > sr7-slide#SR7_4_1-241 > sr7-img#SR7_4_1-241-48
snippet: <sr7-img id="SR7_4_1-241-48" class="sr7-layer" aria-hidden="true" data-need-color-bg="false" style="overflow: visible; padding: 0px; width: 464px; height: 260px; z-index: 14;">

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-6-SR7-IMG
nodeLabel: sr7-module#SR7_4_1 > sr7-content > sr7-slide#SR7_4_1-241 > sr7-img#SR7_4_1-241-48
path: 3,HTML,2,BODY,1,DIV,7,DIV,0,DIV,1,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,SR7-MODULE,1,SR7-CONTENT,0,SR7-SLIDE,3,SR7-IMG
selector: sr7-module#SR7_4_1 > sr7-content > sr7-slide#SR7_4_1-241 > sr7-img#SR7_4_1-241-48
snippet: <sr7-img id="SR7_4_1-241-48" class="sr7-layer" aria-hidden="true" data-need-color-bg="false" style="overflow: visible; padding: 0px; width: 464px; height: 260px; z-index: 14;">

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

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
lacounty.gov/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.14.9 KiB
lacounty.gov/wp-content/themes/blade/js/modernizr.custom.js?ver=2.8.36.2 KiB
lacounty.gov/wp-includes/js/jquery/jquery.min.js?ver=3.7.130.1 KiB
/wp-content/plugins/js_composer/assets/css/js_composer.mi...46.0 KiB259 ms
lacounty.gov/wp-content/plugins/eventON/assets/css/eventon_styles.css?ver=5.0.940.7 KiB259 ms
lacounty.gov/wp-content/plugins/eventon-full-cal/assets/fc_styles.css?ver=1.1.122.8 KiB
lacounty.gov/wp-content/plugins/vc-elegant-tabs/css/tabs.css?ver=3.6.72.5 KiB259 ms
lacounty.gov/wp-content/plugins/vc-elegant-tabs/css/animate.min.css?ver=3.6.72.7 KiB
lacounty.gov/wp-content/plugins/vc-elegant-tabs/css/tabstyles.css?ver=3.6.74.2 KiB
lacounty.gov/wp-content/plugins/eventON/assets/fonts/all.css?ver=5.0.931.8 KiB517 ms
lacounty.gov/wp-content/plugins/easy-tables-vc/assets/css/themes.css?ver=6.8.5964 B
lacounty.gov/wp-content/plugins/easy-tables-vc/assets/css/style.css?ver=1.0.0395 B
/wp-content/plugins/eventON/assets/css/eventon_dynamic_st...5.8 KiB
lacounty.gov/wp-content/themes/blade/css/theme-style.css?ver=3.6.619.7 KiB259 ms
lacounty.gov/wp-content/themes/blade/css/elements.css?ver=3.6.613.4 KiB259 ms
lacounty.gov/wp-content/themes/blade/css/responsive.css?ver=3.6.62.0 KiB
lacounty.gov/wp-content/themes/blade-child/style.css?ver=3.6.6288 B
lacounty.gov/wp-content/themes/blade/css/grid.css?ver=3.6.62.1 KiB
lacounty.gov/wp-content/themes/blade/css/basic.css?ver=3.6.62.7 KiB
lacounty.gov/wp-content/themes/blade/css/font-awesome-v4-shims.min.css?ver=6.4.24.4 KiB259 ms
lacounty.gov/wp-content/themes/blade/css/font-awesome.min.css?ver=6.4.222.2 KiB517 ms
/wp-content/plugins/inel_elementsbox_plugin/css/animate.c...4.6 KiB259 ms
lacounty.gov/wp-content/themes/blade/style.css?ver=6.8.5513 B
lacounty.gov/wp-content/plugins/revslider/public/css/sr7.css?ver=6.7.541.7 KiB
/wp-content/plugins/inel_elementsbox_plugin/css/themify-i...3.0 KiB
/wp-content/plugins/inel_elementsbox_plugin/css/elegant-f...4.8 KiB259 ms
/wp-content/plugins/inel_elementsbox_plugin/css/font-awes...6.2 KiB
/wp-content/plugins/inel_elementsbox_plugin/css/elementsb...6.8 KiB517 ms
/wp-content/plugins/google-language-translator/css/style....10.1 KiB
/wp-content/plugins/ditty-news-ticker/includes/libs/fonta...23.6 KiB776 ms
lacounty.gov/wp-content/plugins/blade-uswds-modules/assets/css/responsive.css494 B
lacounty.gov/wp-content/plugins/blade-uswds-modules/assets/css/style.css1.0 KiB
lacounty.gov/wp-includes/css/dist/block-library/style.min.css?ver=6.8.515.5 KiB
/wp-content/plugins/vc-extensions-expandgrid/css/admin_ic...315 B
/wp-content/plugins/ditty-news-ticker/assets/build/dittyD...1.5 KiB
cdnjs.cloudflare.com/ajax/libs/uswds/3.13.0/css/uswds.min.css39.6 KiB1.6 s
/css?family=Noto+Sans%3A400%2C400italic%2C700%7CPoppins%3...1.1 KiB820 ms
/css?family=Rubik%3A400%2C700%7CNunito+Sans%3A400%2C700&d...1.2 KiB172 ms
fonts.googleapis.com/css?family=Amatic+SC1009 B

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.

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

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 reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
lacounty.gov/m-faine-you-make-farweyan-houghter-Mast-the-Besi3.1 s2.8 s69 ms
lacounty.gov/wp-content/plugins/revslider/public/js/libs/tptools.js?ver=6.7.541.7 s483 ms18 ms
lacounty.gov/1.0 s110 ms63 ms
Unattributable763 ms175 ms0.0 ms
www.googletagmanager.com/gtag/js?id=G-HYDNR8V2E5492 ms398 ms49 ms
cdnjs.cloudflare.com/ajax/libs/uswds/3.13.0/js/uswds.min.js260 ms35 ms9.0 ms
lacounty.gov/wp-includes/js/jquery/jquery.min.js?ver=3.7.1237 ms185 ms11 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwOA.js215 ms164 ms49 ms
/_/translate_http/_/js/k=translate_http.tr.es.eNjH1Jo6ldQ...181 ms131 ms41 ms
www.googletagmanager.com/gtm.js?id=GTM-WM426K7160 ms119 ms39 ms
lacounty.gov/wp-content/plugins/revslider/public/js/sr7.js?ver=6.7.54160 ms54 ms30 ms
/signals/config/1438485966979255?v=2.9.303&r=stable&domai...144 ms103 ms30 ms
connect.facebook.net/en_US/fbevents.js143 ms105 ms38 ms
maps.googleapis.com/maps/api/js?ver=1.0126 ms90 ms32 ms
lacounty.gov/wp-content/themes/blade/js/plugins.js?ver=3.6.6110 ms68 ms22 ms
lacounty.gov/wp-content/themes/blade/js/modernizr.custom.js?ver=2.8.3106 ms37 ms1.5 ms
lacounty.gov/wp-content/plugins/revslider/public/js/migration.js90 ms83 ms6.5 ms
lacounty.gov/wp-content/themes/blade/js/main.js?ver=3.6.688 ms22 ms9.8 ms
meet.jit.si/external_api.js?ver=5.0.956 ms44 ms12 ms
lacounty.gov/wp-content/plugins/eventON/assets/fonts/all.css?ver=5.0.956 ms0.0 ms0.0 ms
/_Incapsula_Resource?SWJIYLWA=719d34d31c8e3a6e6fffd425f7e...51 ms43 ms8.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 Evaluation5.5 s
Other1.8 s
Style & Layout1.2 s
Script Parsing & Compilation639 ms
Parse HTML & CSS329 ms
Garbage Collection189 ms
Rendering172 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
Modern HTTP
Optimize viewport for mobile
User Timing marks and measures 9 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 2 animated elements found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 110 ms
Server Backend Latencies 170 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 140 ms
INP breakdown
Avoid large layout shifts
83

Accessibility

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

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
$48.8 billion spending plan protects jobs and avoids broad cuts as County brace… sr7-module#SR7_4_1 > sr7-content > sr7-slide#SR7_4_1-241 > sr7-txt#SR7_4_1-241-3

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

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
Access County payment systems div.wpb_column > div.inel_iconbox > div.inel_iconbox_text > p
Get information or apply online div.wpb_column > div.inel_iconbox > div.inel_iconbox_text > p
Register for services div.wpb_column > div.inel_iconbox > div.inel_iconbox_text > p
Report issues or complaints div.wpb_column > div.inel_iconbox > div.inel_iconbox_text > p
Request important documents div.wpb_column > div.inel_iconbox > div.inel_iconbox_text > p
Click “SUBSCRIBE” to receive news and updates from Los Angeles County div.wpb_column > div.grve-element > h5 > span
or “TEXT TO SUBSCRIBE” to receive news and updates via SMS div.grve-row > div.wpb_column > div.grve-element > h5
SUBSCRIBE div.wpb_column > div.grve-element > a.grve-btn > span
TEXT TO SUBSCRIBE div.wpb_column > div.grve-element > a.grve-btn > span
LEARN MORE div.wpb_column > div.inel_button_container > a.inel_button > span.inel_button_text
Find the LA County services and facilities that serve your area div.grve-row > div.wpb_column > div.grve-element > p
div.wpb_raw_code > div.wpb_wrapper > form#mapGoSearch > input div.wpb_raw_code > div.wpb_wrapper > form#mapGoSearch > input

These are opportunities to improve the legibility of your content.

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Click “SUBSCRIBE” to receive news and updates from Los Angeles County div.grve-row > div.wpb_column > div.grve-element > h5
Category div.wpb_raw_code > div.wpb_wrapper > form#mapGoSearch > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
County Offices Parks and Gardens Libraries Health Centers Metro Stations Sherif… div.wpb_raw_code > div.wpb_wrapper > form#mapGoSearch > select#find

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

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>`
`[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 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 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.
All heading elements contain content.
Elements with visible text labels have matching accessible names.
`[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 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
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.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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>`.
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.
77

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
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
lacounty.gov/ line 440, col 0
SyntaxError: Unexpected token '<'

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 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 clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
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

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Send Feedback