Skip to content
https://research.google

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.

52

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.

RequestCache TTLTransfer Size
/gweb-research2023-media/original_images/Research_Homepag...3600.0 s3.7 MiB
/gweb-research2023-media/images/WIldfires_homepage-projec...3600.0 s385.7 KiB
storage.googleapis.com/gweb-research2023-media/images/HP_EarthAI.width-800.png3600.0 s221.0 KiB
/gweb-research2023-media/original_images/USS0291-Google_R...3600.0 s143.2 KiB
/gr/static/js/googleresearch.js?id=b23210a21057c86d701509...600.0 s116.8 KiB
/gr/static/css/googleresearch.css?id=5cbfeb4af4cff622307d...600.0 s72.2 KiB
/gweb-research2023-media/images/yossi-portrait-high-res_1...3600.0 s80.2 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
www.gstatic.com/feedback/js/1qbsrllwsv954/api.js3000.0 s14.5 KiB
storage.googleapis.com/gweb-research2023-media/media/research-areas.mp43600.0 s14.0 KiB
research.google/gr/static/assets/icons/google-cloud.svg600.0 s11.4 KiB
research.google/gr/static/assets/icons/google-deepmind.svg600.0 s8.2 KiB
www.gstatic.com/glue/v27_1/material-components-web.min.js1209600.0 s69.0 KiB
i.ytimg.com/vi/VqSrYdDM0Zw/default.jpg7200.0 s4.0 KiB
www.gstatic.com/glue/v27_1/glue-material.min.css1209600.0 s18.6 KiB
research.google/gr/static/assets/icons/google-labs.svg600.0 s989 B
research.google/gr/static/assets/icons/super-g.svg600.0 s499 B
static.doubleclick.net/instream/ad_status.js900.0 s495 B
research.google/gr/static/assets/icons/caret.svg600.0 s221 B
storage.googleapis.com/gweb-research2023-media/media/research-areas.mp43600.0 s0 B
storage.googleapis.com/gweb-research2023-media/media/research-areas.mp43600.0 s0 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.210756] map[node:map[boundingRect:map[bottom:11031 height:10963 left:0 right:412 top:68 width:412] lhId:page-5-MAIN nodeLabel:Research to reality Our mission is to drive breakthroughs that benefit society… path:1,HTML,1,BODY,5,MAIN selector:body.template-homepage > main#page-content snippet:<main id="page-content"> type:node] score:0.210756 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:472 height:208 left:28 right:384 top:264 width:356] lhId:page-0-IMG nodeLabel:People standing among trees path:1,HTML,1,BODY,5,MAIN,0,DIV,0,SECTION,0,DIV,0,DIV,1,DIV,0,DIV,0,IMG selector:div.glue-grid > div.glue-grid__col > div.dynamic-image-wrapper > img snippet:<img src="https://storage.googleapis.com/gweb-research2023-media/original_images/Res…" alt="People standing among trees"> type:node]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/googlesans/v67/4UasrENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RPjIUvbQoi-E.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/googlesansdisplay/v23/ea8FacM9Wef3EJPWRrHjgE4B6CnlZxHVDv79oT3ZQZQ.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/googlesanstext/v25/5aUp9-KzpRiLCAt4Unrc-xIKmCU5oPFTnmhjtjm4DZw.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/googlesanstext/v25/5aUp9-KzpRiLCAt4Unrc-xIKmCU5oLlVnmhjtjm4DZw.woff2]]] type:subitems]]]

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.

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
People standing among trees div.glue-grid > div.glue-grid__col > div.dynamic-image-wrapper > img
/gweb-research2023-media/original_images/Research_Homepag...3.7 MiB3.7 MiB
WIldfires_homepage-project-collage div.glue-grid__col > div.dynamic-image-wrapper > picture > img
/gweb-research2023-media/images/WIldfires_homepage-projec...385.3 KiB345.5 KiB
HP_EarthAI div.glue-grid__col > div.dynamic-image-wrapper > picture > img
storage.googleapis.com/gweb-research2023-media/images/HP_EarthAI.width-800.png220.7 KiB183.8 KiB
Video preview image div.glue-video__preview-container > div.dynamic-image-wrapper > picture.glue-video__preview > img.glue-video__preview-image
/gweb-research2023-media/original_images/USS0291-Google_R...142.9 KiB128.3 KiB
yossi-portrait-high-res (1) div.avatar-card > div.dynamic-image-wrapper > picture.avatar-card__image > img
/gweb-research2023-media/images/yossi-portrait-high-res_1...79.9 KiB77.3 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-IMG
nodeLabel: People standing among trees
path: 1,HTML,1,BODY,5,MAIN,0,DIV,0,SECTION,0,DIV,0,DIV,1,DIV,0,DIV,0,IMG
selector: div.glue-grid > div.glue-grid__col > div.dynamic-image-wrapper > img
snippet: <img src="https://storage.googleapis.com/gweb-research2023-media/original_images/Res…" alt="People standing among trees">

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.

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Research to reality Our mission is to drive breakthroughs that benefit society… body.template-homepage > main#page-content
0.211

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: 860 ms 80.7 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.

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 Evaluation789 ms
Other763 ms
Style & Layout331 ms
Script Parsing & Compilation153 ms
Rendering68 ms
Parse HTML & CSS54 ms
Garbage Collection38 ms

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
People standing among trees div.glue-grid > div.glue-grid__col > div.dynamic-image-wrapper > img
/gweb-research2023-media/original_images/Research_Homepag...
WIldfires_homepage-project-collage div.glue-grid__col > div.dynamic-image-wrapper > picture > img
/gweb-research2023-media/images/WIldfires_homepage-projec...
HP_EarthAI div.glue-grid__col > div.dynamic-image-wrapper > picture > img
storage.googleapis.com/gweb-research2023-media/images/HP_EarthAI.width-800.png

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

●Document request latency
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 5 user timings
●JavaScript execution time 0.9 s
●Avoid long main-thread tasks 7 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 50 ms
●Server Backend Latencies 480 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 180 ms
○INP breakdown
○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.

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
APRIL 13 TO APRIL 17 · CONFERENCES & EVENTS Google at CHI 2026 div.glue-carousel > div.glue-carousel__viewport > div.glue-carousel__list > a.glue-card
MARCH 31 · BLOG Building better AI benchmarks: How many raters are enough? div.glue-carousel > div.glue-carousel__viewport > div.glue-carousel__list > a.glue-card
○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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[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
●`[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
●`[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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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
○Form elements have associated labels
○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.
○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
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Ensure CSP is effective against XSS attacks
○Use a strong HSTS policy
○Ensure proper origin isolation with COOP
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
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.

Content Best Practices

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
●Document has a meta description
●Page has successful HTTP status code
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback