https://caniuse.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.
89
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.
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.
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.
| URL | Transfer Size | Duration |
|---|---|---|
| caniuse.com/css/theme-light.css?1776478325 | 704 B | |
| caniuse.com/css/home.css?1776478324 | 1.5 KiB | 304 ms |
| caniuse.com/css/main.css?1776478324 | 7.8 KiB | |
| fonts.googleapis.com/css?family=Inconsolata&display=swap | 988 B | 819 ms |
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.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| /pagead/managed/js/adsense/m202604160101/show_ads_impl_fy... | 1209600.0 s | 177.5 KiB |
| caniuse.com/fonts/open-sans-300.woff2 | 0.0 ms | 14.8 KiB |
| caniuse.com/fonts/open-sans-regular.woff2 | 0.0 ms | 14.2 KiB |
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 CSS files can reduce network payload sizes. Learn how to minify CSS.
Why this matters
Performance issues directly impact user engagement and conversion rates.
Estimated savings: 0.0 ms 2.2 KiB
| URL | Transfer Size | Est Savings |
|---|---|---|
| caniuse.com/css/main.css?1776478324 | 7.8 KiB | 2.2 KiB |
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: 0.0 ms 262.2 KiB
| URL | Transfer Size | Est Savings |
|---|---|---|
| /pagead/managed/js/adsense/m202604160101/show_ads_impl_fy... | 177.5 KiB | 126.3 KiB |
| www.googletagmanager.com/gtag/js?id=G-8SCDSGDGKM | 151.0 KiB | 62.1 KiB |
| caniuse.com/js/bundle.js?1776478326 | 90.7 KiB | 49.4 KiB |
| pagead2.googlesyndication.com/pagead/js/adsbygoogle.js | 54.2 KiB | 24.4 KiB |
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
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 670 KiB
●User Timing marks and measures 5 user timings
●JavaScript execution time 0.9 s
●Minimizes main-thread work 1.6 s
●Avoid long main-thread tasks 6 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 150 ms
●Server Backend Latencies 190 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 310 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
100
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.
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●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
●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
●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
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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 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.
○`[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.
○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
●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
●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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
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
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.
| Line # | Content | Error |
|---|---|---|
| 1 | <!doctype html> | Syntax not understood |
| 2 | <html dir="ltr" lang="en-US" class="no-js"> | Syntax not understood |
| 3 | <head> | Syntax not understood |
| 4 | <meta charset="utf-8" /> | Syntax not understood |
| 5 | <title>"robots.txt" | Can I use... Support tables for HTML5, CSS3, etc</title> | Syntax not understood |
| 7 | <meta name="viewport" content="width=device-width"> | Syntax not understood |
| 9 | <link rel="alternate" type="application/atom+xml" title="Can I Use updates" href="/feed"> | Syntax not understood |
| 10 | <link href="//fonts.googleapis.com/css?family=Inconsolata&display=swap" rel="stylesheet"> | Syntax not understood |
| 11 | <link rel="icon" href="/img/favicon-128.png" sizes="16x16 32x32 64x64 128x128" type="image/png"/> | Syntax not understood |
| 12 | <link rel="apple-touch-icon" href="/img/favicon-128.png"> | Syntax not understood |
| 14 | <link rel="stylesheet" href="/css/main.css?1776478324" media="all"> | Syntax not understood |
| 15 | <link rel="stylesheet" data-theme="light" href="/css/theme-light.css?1776478325" media="all"> | Syntax not understood |
| 16 | <link rel="stylesheet" data-theme="dark" href="/css/theme-dark.css?1776478325" media="(prefers-color-scheme: dark)"> | Unknown directive |
| 17 | <meta name="Description" content=""Can I use" provides up-to-date browser support tables for support of front-end web technologies on desktop and mobile web browsers."> | Syntax not understood |
| 18 | <meta name="keywords" content="web browser compatibility support html css svg html5 css3 opera chrome firefox safari internet explorer"> | Syntax not understood |
| 19 | <link rel="search" href="/opensearch.xml" type="application/opensearchdescription+xml" title="Can I use"/> | Syntax not understood |
| 20 | <link rel="preconnect" href="https://ipinfo.io"> | Unknown directive |
| 21 | <link rel="preconnect" href="https://www.google-analytics.com"> | Unknown directive |
| 22 | <base href="/" /> | Syntax not understood |
| 23 | <script> | Syntax not understood |
| 24 | document.write('<style>.static-only {display:none}</style>'); | Unknown directive |
| 25 | </script> | Syntax not understood |
| 27 | <script async src="https://www.googletagmanager.com/gtag/js?id=G-8SCDSGDGKM"></script> | Unknown directive |
| 28 | <script> | Syntax not understood |
| 29 | window.dataLayer = window.dataLayer || []; | Syntax not understood |
| 30 | function gtag(){dataLayer.push(arguments);} | Syntax not understood |
| 31 | gtag('js', new Date()); | Syntax not understood |
| 33 | gtag('config', 'G-8SCDSGDGKM'); | Syntax not understood |
| 34 | </script> | Syntax not understood |
| 36 | <script> | Syntax not understood |
| 37 | (function() { | Syntax not understood |
| 38 | if (!window.customElements) { | Syntax not understood |
| 39 | var s = document.createElement('script'); | Syntax not understood |
| 40 | s.src = '/legacy-handler.js'; | Syntax not understood |
| 41 | document.getElementsByTagName('head')[0].appendChild(s); | Syntax not understood |
| 42 | } | Syntax not understood |
| 43 | }()); | Syntax not understood |
| 44 | </script> | Syntax not understood |
| 45 | <!--[if IE]><script src="/legacy-handler.js"></script><![endif]--><script defer src="js-data/data.js?1776729872"></script><script defer src="js/bundle.js?1776478326"></script></head> | Syntax not understood |
| 46 | <body class="is-home"> | Syntax not understood |
| 47 | <div id="main" class="ciu-main-wrap"> | Syntax not understood |
| 49 | <header class="ciu-page-header"> | Syntax not understood |
| 50 | <nav role="navigation" id="tab-container"> | Syntax not understood |
| 51 | <ul class="ciu-page-header__primary-nav"> | Syntax not understood |
| 52 | <li class="site-nav-item js-site-nav"><a href="/" data-route="home">Home</a></li> | Syntax not understood |
| 53 | <li class="site-nav-item js-site-nav site-nav-item--news"><a href="/ciu/news" data-route="news">News</a></li> | Syntax not understood |
| 54 | </ul> | Syntax not understood |
| 56 | <ul class="ciu-page-header__secondary-nav"> | Syntax not understood |
| 57 | <li class="site-nav-item js-site-nav site-nav-item--comparison"><a href="/ciu/comparison" data-route="comparison">Compare<span class="site-nav__extra-text"> browsers</span></a></li> | Syntax not understood |
| 58 | <li class="site-nav-item js-site-nav site-nav-item--last "><a href="/ciu/about" data-route="about">About</a></li> | Syntax not understood |
| 59 | </ul> | Syntax not understood |
| 61 | <a class="news js-news" data-newstime="1772668800" href="https://caniuse.com/loading-lazy-media"><span class="date">March 5, 2026 -</span> New feature: Lazy loading via attribute for video & audio</a> </nav> | Unknown directive |
| 64 | <section class="ciu-search"> | Syntax not understood |
| 65 | <div class="ciu-search__inner js-search"> | Syntax not understood |
| 66 | <a href="/" class="ciu-search__label">Can I use</a> | Syntax not understood |
| 67 | <form action="/" class="ciu-search__form"> | Syntax not understood |
| 68 | <label class="ciu-search__a11y-label" for="feat_search">Search</label> | Syntax not understood |
| 69 | <input type="text" class="ciu-search__input" id="feat_search" name="search" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false" autofocus value="robots.txt"> | Syntax not understood |
| 70 | <input type="hidden" name="static" value="1"> | Syntax not understood |
| 71 | </form> | Syntax not understood |
| 72 | ? | Syntax not understood |
| 73 | <button class="options-toggle js-options-toggle"> | Syntax not understood |
| 74 | <svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" viewBox="0 0 16 16" class="icon"> | Unknown directive |
| 75 | <path d="M16,8.87V7L15.74,7l-1.95-.64-.52-1.25,1-2.12L13,1.67l-.25.12-1.82.93L9.66,2.2,8.87,0H7.05L7,.26,6.33,2.21l-1.25.52L3,1.73,1.67,3l.12.25.93,1.82L2.2,6.34,0,7.13V8.95L.26,9l2,.64.52,1.25L1.73,13,3,14.33l.25-.12,1.82-.93,1.26.52L7.13,16H8.95L9,15.74l.64-2,1.26-.52,2.11,1L14.33,13l-.12-.25-.93-1.82.52-1.26ZM8,10.55A2.55,2.55,0,1,1,10.55,8,2.55,2.55,0,0,1,8,10.55Z"/> | Syntax not understood |
| 76 | </svg> | Syntax not understood |
| 77 | <span> | Syntax not understood |
| 78 | Settings | Syntax not understood |
| 79 | </span> | Syntax not understood |
| 80 | </button> | Syntax not understood |
| 81 | </div> | Syntax not understood |
| 83 | <div class="search-result-info js-search-result-info">0 results found. <p>Why not <a href="https://github.com/Fyrd/caniuse/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+thnthnth">suggest this feature be added?</a></p></div> | Unknown directive |
| 84 | </section> | Syntax not understood |
| 86 | </header> | Syntax not understood |
| 88 | <main class="ciu-page-content js-content" data-static-id="search"> | Syntax not understood |
| 89 | </main> | Syntax not understood |
| 91 | <aside class="bottom-ad"> | Syntax not understood |
| 92 | <script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script> | Syntax not understood |
| 93 | <!-- Bottom leaderboard --> | Syntax not understood |
| 94 | <ins class="adsbygoogle" | Syntax not understood |
| 95 | style="display:inline-block;width:728px;height:90px" | Unknown directive |
| 96 | data-ad-client="ca-pub-3347535679733957" | Syntax not understood |
| 97 | data-ad-slot="1205929339"></ins> | Syntax not understood |
| 98 | <script> | Syntax not understood |
| 99 | (adsbygoogle = window.adsbygoogle || []).push({}); | Syntax not understood |
| 100 | </script> | Syntax not understood |
| 101 | </aside> | Syntax not understood |
| 103 | <footer class="ciu-footer"> | Syntax not understood |
| 104 | <div class="footer__section footer__primary"> | Syntax not understood |
| 105 | <h3 class="footer__heading">Can I use...</h3> | Syntax not understood |
| 106 | <p class="site-description">Browser support tables for modern web technologies</p> | Syntax not understood |
| 107 | <p>Created & maintained by <a class="external-link" href="https://front-end.social/@fyrd">@Fyrd</a>, design by <a class="external-link" href="https://mastodon.world/@lensco">@Lensco</a>.</p> | Unknown directive |
| 108 | <p>Support data contributions by the GitHub <a class="external-link" href="https://github.com/Fyrd/caniuse/graphs/contributors">community</a>. | Unknown directive |
| 110 | <p id="usage_note"> | Syntax not understood |
| 111 | Usage share statistics by <a class="external-link" href="http://gs.statcounter.com/">StatCounter GlobalStats</a> for March, 2026 </p> | Unknown directive |
| 113 | <p>Location detection provided by <a class="external-link" href="//ipinfo.io">ipinfo.io</a>. | Syntax not understood |
| 114 | </p> | Syntax not understood |
| 116 | <p> | Syntax not understood |
| 117 | Browser testing done via | Syntax not understood |
| 118 | <a class="external-link" href="https://www.browserstack.com?ref=caniuse-source&caniuse_source=brand-asset&utm_source=caniuse&utm_medium=partnered&utm_campaigncode=701OW000008y9C1YAI" target="_blank"> | Unknown directive |
| 119 | <img src="/img/browserstack.svg" alt="BrowserStack" width="140" height="28" loading="lazy"> | Syntax not understood |
| 120 | </a> | Syntax not understood |
| 121 | </p> | Syntax not understood |
| 123 | </div> | Syntax not understood |
| 125 | <div class="footer__section footer__patreon"> | Syntax not understood |
| 126 | <h3 class="footer__heading">Support via Patreon</h3> | Syntax not understood |
| 128 | <p>Become a caniuse Patron to support the site and disable ads for only $1/month!</p> | Syntax not understood |
| 130 | <div class="patreon-button"> | Syntax not understood |
| 131 | <a href="https://www.patreon.com/join/caniuse"> | Unknown directive |
| 132 | <img src="/img/become_a_patron_button.png" width="163" height="38" alt="Become a Patron!" loading="lazy"> | Syntax not understood |
| 133 | </a> | Syntax not understood |
| 134 | </div> | Syntax not understood |
| 135 | <p> | Syntax not understood |
| 136 | or <a class="external-link" href="http://www.patreon.com/oauth2/authorize?response_type=code&client_id=efdd32564c7459c2c0dcd644b984e6948070b23b72961a3b9fb32ab3ad797184&redirect_uri=https%3A%2F%2Fcaniuse.com">Log in</a> | Unknown directive |
| 137 | </p> | Syntax not understood |
| 138 | </div> | Syntax not understood |
| 140 | <div class="footer__section footer__links"> | Syntax not understood |
| 141 | <h3 class="footer__heading">Site links</h3> | Syntax not understood |
| 142 | <ol class="footer__list"> | Syntax not understood |
| 143 | <li class="footer__list-item"> | Syntax not understood |
| 144 | <a href="/">Home</a> | Syntax not understood |
| 145 | </li> | Syntax not understood |
| 146 | <li class="footer__list-item"> | Syntax not understood |
| 147 | <a href="/ciu/index">Feature index</a> | Syntax not understood |
| 148 | </li> | Syntax not understood |
| 149 | <li class="footer__list-item"> | Syntax not understood |
| 150 | <a href="/usage-table">Browser usage table</a> | Syntax not understood |
| 151 | </li> | Syntax not understood |
| 152 | <li class="footer__list-item"> | Syntax not understood |
| 153 | <a href="/issue-list">Feature suggestion list</a> | Syntax not understood |
| 154 | </li> | Syntax not understood |
| 155 | <li class="footer__list-item"> | Syntax not understood |
| 156 | <a href="https://github.com/fyrd/caniuse">Caniuse data on GitHub</a> | Unknown directive |
| 157 | </li> | Syntax not understood |
| 158 | </ol> | Syntax not understood |
| 159 | </div> | Syntax not understood |
| 161 | <div class="footer__section footer__legend"> | Syntax not understood |
| 162 | <section class="ciu-legend js-legend"> | Syntax not understood |
| 163 | <h2 class="ciu-legend__header">Legend</h2> | Syntax not understood |
| 164 | <ul class="ciu-legend__list"> | Syntax not understood |
| 165 | <li class="ciu-legend__item"> | Syntax not understood |
| 166 | <span class="y ciu-legend__color">Green</span> | Syntax not understood |
| 167 | <span class="ciu-legend__symbol">✅</span> | Syntax not understood |
| 168 | = Supported | Syntax not understood |
| 169 | </li> | Syntax not understood |
| 170 | <li class="ciu-legend__item"> | Syntax not understood |
| 171 | <span class="n ciu-legend__color">Red</span> | Syntax not understood |
| 172 | <span class="ciu-legend__symbol">❌</span> | Syntax not understood |
| 173 | = Not supported | Syntax not understood |
| 174 | </li> | Syntax not understood |
| 175 | <li class="ciu-legend__item"> | Syntax not understood |
| 176 | <span class="a ciu-legend__color">Greenish yellow</span> | Syntax not understood |
| 177 | <span class="ciu-legend__symbol">◐</span> | Syntax not understood |
| 178 | = Partial support | Syntax not understood |
| 179 | </li> | Syntax not understood |
| 180 | <li class="ciu-legend__item"> | Syntax not understood |
| 181 | <span class="u ciu-legend__color">Gray</span> | Syntax not understood |
| 182 | <span class="ciu-legend__symbol">﹖</span> | Syntax not understood |
| 183 | = Support unknown | Syntax not understood |
| 184 | </li> | Syntax not understood |
| 185 | </ul> | Syntax not understood |
| 186 | </section> | Syntax not understood |
| 187 | </div> | Syntax not understood |
| 188 | </footer> | Syntax not understood |
| 189 | </div><!-- /all --> | Syntax not understood |
| 190 | </body> | Syntax not understood |
| 191 | </html> | Syntax not understood |
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
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`