Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

URL	Est Savings
/static/mathjax/fonts/HTML-CSS/TeX/woff/MathJax_Math-Ital...	175 ms
/static/mathjax/fonts/HTML-CSS/TeX/woff/MathJax_Size1-Reg...	170 ms
/static/mathjax/fonts/HTML-CSS/TeX/woff/MathJax_Main-Regu...	60 ms
/s/googlesymbols/v419/HhzZU5Ak9u-oMExPeInvcuEmPosC9zS3FYk...	45 ms
/s/googlesanstext/v25/5aUp9-KzpRiLCAt4Unrc-xIKmCU5oPFTnmh...	15 ms
/s/googlesanstext/v25/5aUu9-KzpRiLCAt4Unrc-xIKmCU5qCR2i0V...	15 ms
/s/googlesans/v67/4UasrENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iq...	15 ms
/s/googlesanstext/v25/5aUu9-KzpRiLCAt4Unrc-xIKmCU5qEp2i0V...	10 ms
/s/googlesans/v67/4UasrENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iq...	10 ms
fonts.gstatic.com/s/roboto/v51/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	10 ms
/s/googlesanstext/v25/5aUp9-KzpRiLCAt4Unrc-xIKmCU5oLlVnmh...	5.0 ms

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:24.222 source:map[column:40 line:7813 type:source-location url:https://ssl.gstatic.com/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1b28/external_binary.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:0.849 source:map[column:72 line:8210 type:source-location url:https://ssl.gstatic.com/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1b28/external_binary.js urlProvider:network]] map[reflowTime:33.173 source:map[type:text value:[unattributed]]] map[reflowTime:18.326 source:map[column:3649 line:56 type:source-location url:https://colab.research.google.com/static/mathjax/config/TeX-AMS_HTML-full.js?V=2.7.5 urlProvider:network]] map[reflowTime:8.558 source:map[column:3719 line:56 type:source-location url:https://colab.research.google.com/static/mathjax/config/TeX-AMS_HTML-full.js?V=2.7.5 urlProvider:network]] map[reflowTime:6.221 source:map[column:3866 line:56 type:source-location url:https://colab.research.google.com/static/mathjax/config/TeX-AMS_HTML-full.js?V=2.7.5 urlProvider:network]] map[reflowTime:9.824 source:map[column:2168 line:56 type:source-location url:https://colab.research.google.com/static/mathjax/config/TeX-AMS_HTML-full.js?V=2.7.5 urlProvider:network]] map[reflowTime:5.082 source:map[column:2257 line:56 type:source-location url:https://colab.research.google.com/static/mathjax/config/TeX-AMS_HTML-full.js?V=2.7.5 urlProvider:network]] map[reflowTime:0.4 source:map[column:3607 line:58 type:source-location url:https://colab.research.google.com/static/mathjax/config/TeX-AMS_HTML-full.js?V=2.7.5 urlProvider:network]] map[reflowTime:0.639 source:map[column:12157 line:56 type:source-location url:https://colab.research.google.com/static/mathjax/config/TeX-AMS_HTML-full.js?V=2.7.5 urlProvider:network]] map[reflowTime:10.438 source:map[column:165 line:7812 type:source-location url:https://ssl.gstatic.com/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1b28/external_binary.js urlProvider:network]] map[reflowTime:0.097 source:map[column:198 line:7812 type:source-location url:https://ssl.gstatic.com/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1b28/external_binary.js urlProvider:network]] map[reflowTime:0.088 source:map[column:231 line:7812 type:source-location url:https://ssl.gstatic.com/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1b28/external_binary.js urlProvider:network]] map[reflowTime:0.068 source:map[column:269 line:7812 type:source-location url:https://ssl.gstatic.com/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1b28/external_binary.js urlProvider:network]] map[reflowTime:0.08 source:map[column:308 line:7812 type:source-location url:https://ssl.gstatic.com/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1b28/external_binary.js urlProvider:network]] map[reflowTime:0.07 source:map[column:346 line:7812 type:source-location url:https://ssl.gstatic.com/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1b28/external_binary.js urlProvider:network]] map[reflowTime:0.074 source:map[column:383 line:7812 type:source-location url:https://ssl.gstatic.com/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1b28/external_binary.js urlProvider:network]] map[reflowTime:14.047 source:map[column:352 line:7813 type:source-location url:https://ssl.gstatic.com/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1b28/external_binary.js urlProvider:network]] map[reflowTime:13.592 source:map[column:114 line:5073 type:source-location url:https://ssl.gstatic.com/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1b28/external_binary.js urlProvider:network]] map[reflowTime:9.659 source:map[column:244 line:4978 type:source-location url:https://ssl.gstatic.com/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1b28/external_binary.js urlProvider:network]] map[reflowTime:9.427 source:map[column:43 line:2241 type:source-location url:https://ssl.gstatic.com/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1b28/external_binary.js urlProvider:network]] map[reflowTime:10.476 source:map[column:386 line:7859 type:source-location url:https://ssl.gstatic.com/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1b28/external_binary.js urlProvider:network]]]

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

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
/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1...	1.5 MiB	11.4 s
/static/mathjax/MathJax.js?config=TeX-AMS_HTML-full,Safe&...	19.0 KiB	600 ms
/css?family=Roboto:300,400,500,600,700\|Google+Sans:300,40...	4.1 KiB	151 ms
fonts.googleapis.com/css2?family=Google+Symbols:FILL@0..1&display=block	919 B	780 ms
/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1...	21.5 KiB	455 ms
/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1...	35.8 KiB	1.4 s
/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1...	7.1 KiB
/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1...	9.1 KiB

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
www.gstatic.com/feedback/js/help/prod/service/lazy.min.js	3000.0 s	39.5 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.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

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

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/zFuF-tbndD6YrdyXHX3EVT0n/styles__ltr.css	41.6 KiB	40.1 KiB
/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1...	35.2 KiB	31.2 KiB
.codicon-add:before { content: '\ea60'; } …	10.7 KiB	10.6 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: 9.8 s 2.4 MiB

URL	Transfer Size	Est Savings
/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1...	1.5 MiB	913.6 KiB
/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1...	836.5 KiB	603.5 KiB
www.gstatic.com/recaptcha/releases/zFuF-tbndD6YrdyXHX3EVT0n/recaptcha__en.js	361.8 KiB	245.2 KiB
www.gstatic.com/recaptcha/releases/zFuF-tbndD6YrdyXHX3EVT0n/recaptcha__en.js	361.8 KiB	180.5 KiB
www.gstatic.com/recaptcha/releases/zFuF-tbndD6YrdyXHX3EVT0n/recaptcha__en.js	361.8 KiB	175.9 KiB
www.googletagmanager.com/gtag/js?id=G-S3V05QCXK5&cx=c&_slc=1	148.1 KiB	64.1 KiB
colab.research.google.com/static/mathjax/config/TeX-AMS_HTML-full.js?V=2.7.5	88.9 KiB	57.7 KiB
/og/_/js/k=og.qtm.en_US.Z6E9e-jZ3gE.2019.O/rt=j/m=qabr,q_...	84.1 KiB	57.7 KiB
/_/scs/abc-static/_/js/k=gapi.gapi.en.5G9F9JPGjf8.O/m=cli...	70.0 KiB	55.7 KiB
www.gstatic.com/feedback/js/help/prod/service/lazy.min.js	39.1 KiB	30.2 KiB
/_/scs/abc-static/_/js/k=gapi.gapi.en.5G9F9JPGjf8.O/m=gap...	39.2 KiB	24.6 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.

URL	Total CPU Time	Script Evaluation	Script Parse
/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1...	3.1 s	2.6 s	11 ms
www.gstatic.com/recaptcha/releases/zFuF-tbndD6YrdyXHX3EVT0n/recaptcha__en.js	2.2 s	1.5 s	514 ms
/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1...	2.0 s	1.2 s	760 ms
colab.research.google.com/	1.1 s	40 ms	22 ms
Unattributable	824 ms	151 ms	0.0 ms
/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1...	697 ms	238 ms	427 ms
colab.research.google.com/_/bscframe	314 ms	90 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-S3V05QCXK5&cx=c&_slc=1	260 ms	202 ms	54 ms
/static/mathjax/jax/output/HTML-CSS/fonts/TeX/fontdata.js...	253 ms	49 ms	5.2 ms
www.google.com/js/bg/EXhBhUaAPGW-fRpAMA-c23Y5TFEBiEfCQpe1mRG-KHM.js	194 ms	181 ms	8.2 ms
/recaptcha/api2/anchor?ar=1&k=6LfQPtEUAAAAAHBpAdFng54jyuB...	175 ms	123 ms	5.2 ms
/og/_/js/k=og.qtm.en_US.Z6E9e-jZ3gE.2019.O/rt=j/m=qabr,q_...	175 ms	112 ms	32 ms
/_/scs/abc-static/_/js/k=gapi.gapi.en.5G9F9JPGjf8.O/m=gap...	109 ms	95 ms	14 ms
/static/mathjax/MathJax.js?config=TeX-AMS_HTML-full,Safe&...	97 ms	51 ms	7.9 ms
colab.research.google.com/static/mathjax/config/TeX-AMS_HTML-full.js?V=2.7.5	71 ms	33 ms	37 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.

Category	Time Spent
Script Evaluation	7.3 s
Script Parsing & Compilation	2.0 s
Style & Layout	1.3 s
Other	1.1 s
Parse HTML & CSS	246 ms
Garbage Collection	219 ms
Rendering	130 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 reason	Failure type
The page has an unload handler in the main frame.	Actionable

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.

URL	Transfer Size
/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1...	1.5 MiB
/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1...	836.5 KiB
/s/googlesymbols/v419/HhzZU5Ak9u-oMExPeInvcuEmPosC9zS3FYk...	534.3 KiB
/v2/external/notebooks/intro.ipynb?vrz=colab-external_202...	432.3 KiB
www.gstatic.com/recaptcha/releases/zFuF-tbndD6YrdyXHX3EVT0n/recaptcha__en.js	361.8 KiB
www.googletagmanager.com/gtag/js?id=G-S3V05QCXK5&cx=c&_slc=1	148.4 KiB
/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1...	124.0 KiB
colab.research.google.com/static/mathjax/config/TeX-AMS_HTML-full.js?V=2.7.5	89.0 KiB
/og/_/js/k=og.qtm.en_US.Z6E9e-jZ3gE.2019.O/rt=j/m=qabr,q_...	84.1 KiB
/_/scs/abc-static/_/js/k=gapi.gapi.en.5G9F9JPGjf8.O/m=cli...	70.6 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
logo.webp `div.markdown > span > p > img`

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

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 26 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 1 animated element found

●Network Requests

●Network Round Trip Times 0 ms

●Server Backend Latencies 40 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 40 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

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
button#button `button#button`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.output-iframe-sizer > div > div.outputview > iframe `div.output-iframe-sizer > div > div.outputview > iframe`

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

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` 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

●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

●`[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

●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

○`button`, `link`, and `menuitem` elements have accessible names

○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

○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

○`<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.

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
Thumbnail for a video showing 3 AI-powered Google Colab features `span > center > a > img`		302 x 188 (1.61)	900 x 512 (1.76)

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
logo.webp `div.markdown > span > p > img`		230 x 58	230 x 58	345 x 87

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 / Warning	Source
Unload event listeners are deprecated and will be removed.	/colaboratory-static/common/624e67562667e7b52c4396bf2d5d1... line 4775, col 830

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.

Source	Description
/$rpc/google.internal.colab.v1.UserInfoService/GetUserInfo	`Failed to load resource: the server responded with a status of 401 ()`

●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

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Ensure CSP is effective against XSS attacks

○Mitigate clickjacking with XFO or CSP

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.

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 have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`