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.

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.721163] map[node:map[boundingRect:map[bottom:1419 height:682 left:0 right:412 top:737 width:412] lhId:page-3-DIV nodeLabel:Say goodbye to file silos and content chaos Move your data and store all of yo… path:1,HTML,1,BODY,0,DIV,1,MAIN,4,SECTION,0,DIV,0,DIV selector:main#main > section#migration > div.TemplateTwoColumn_template > div.Grid_grid snippet:<div class="Grid_grid TemplateTwoColumn_grid" style="Grid_grid"> type:node] score:0.721163 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2794 height:313 left:16 right:396 top:2481 width:380] lhId:page-1-IMG nodeLabel:Indicating 30 gigabytes of storage used in Google Workspace path:1,HTML,1,BODY,0,DIV,1,MAIN,10,SECTION,0,GWS-ACCORDION-5050-CONTAINER,0,DIV,0,DIV,0,DIV,0,DIV,0,GWS-ACCORDION-ITEM,2,DIV,0,PICTURE,2,IMG selector:gws-accordion-item > div.AccordionItem_imageContainer > picture > img snippet:<img src="https://lh3.googleusercontent.com/r5D_bbSaYm9hhy1tcQ9--ySN64I-iKSGlnvv6UWG…" srcset="https://lh3.googleusercontent.com/r5D_bbSaYm9hhy1tcQ9--ySN64I-iKSGlnvv6UWG…" alt="Indicating 30 gigabytes of storage used in Google Workspace" width="608" height="500" loading="lazy"> type:node]]] type:subitems]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:284.457 source:map[type:text value:[unattributed]]] map[reflowTime:58.086 source:map[column:3481 line:0 type:source-location url:https://workspace.google.com/assets/Dz-Ho5pc.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.

	URL	Resource Size	Est Savings
A user starts typing a file name into the Google Drive search tool, and a list … `div.Grid_grid > div.Grid_column > picture > img`	/yii01ecysRl3f2TblmxOdGyrw6bVn6RrrSsQ4LuQbvW0YyvfAAgrq3GH...	444.2 KiB	391.6 KiB
Indicating 30 gigabytes of storage used in Google Workspace `gws-accordion-item > div.AccordionItem_imageContainer > picture > img`	/r5D_bbSaYm9hhy1tcQ9--ySN64I-iKSGlnvv6UWGv6tmvNaRUEgfFT7m...	78.9 KiB	29.4 KiB
video.video `video.video`	/5lMAXDhPZzGyIPU0HYUjSXgYkRr5FdO03K1i1yrMLTZYBH_G_baeCEfA...	52.4 KiB	18.5 KiB

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.

URL	Transfer Size	Duration
workspace.google.com/assets/Bctcio4i.css	34.5 KiB	603 ms
workspace.google.com/assets/BJgsXLRu.css	244 B
www.gstatic.com/glue/cookienotificationbar/cookienotificationbar.min.js	27.3 KiB	455 ms
workspace.google.com/assets/QPiEWdQu.css	17.2 KiB	302 ms
fonts.googleapis.com/css?family=Material+Icons+Outlined&display=swap	455 B	153 ms
/css?family=Material+Icons\|Google+Sans:500,700\|Google+San...	4.0 KiB	805 ms
workspace.google.com/assets/8nwFsvE3.css	639 B
workspace.google.com/assets/7WYUZQKH.css	1.5 KiB
workspace.google.com/assets/DB6tYjNO.css	919 B
workspace.google.com/assets/zPypI3Wr.css	1.3 KiB
workspace.google.com/assets/CoLj0pNL.css	168 B
workspace.google.com/assets/SdHIXrh5.css	728 B
workspace.google.com/assets/DQ3xPM8B.css	9.0 KiB	151 ms
www.gstatic.com/glue/cookienotificationbar/cookienotificationbar.min.css	2.2 KiB	773 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
ssl.google-analytics.com/ga.js	7200.0 s	17.4 KiB
/a?v=3&t=l&pid=1606961587&rv=64h1&tag_exp=0~115616986~115...	0.0 ms	11 B

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

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.4 s

URL	Time Spent
drive.google.com/	783 ms
/ServiceLogin?service=wise&passive=1209600&osid=1&continu...	801 ms
www.google.com/intl/en-US/drive/	772 ms
workspace.google.com/intl/en-US/products/drive/	0.0 ms

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.

Element	Layout shift score
Say goodbye to file silos and content chaos Move your data and store all of yo… `main#main > section#migration > div.TemplateTwoColumn_template > div.Grid_grid`	0.721

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

Diagnostics

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
workspace.google.com/intl/en-US/products/drive/	3.0 s	30 ms	12 ms
Unattributable	1.1 s	65 ms	0.0 ms
workspace.google.com/chunks/C6X1K7VT.min.js	995 ms	956 ms	0.2 ms
www.googletagmanager.com/gtm.js?id=GTM-Q4J6	667 ms	565 ms	70 ms
workspace.google.com/chunks/BOtnvvVV.min.js	415 ms	341 ms	0.2 ms
www.googletagmanager.com/gtag/js?id=G-FWCBRW1RY8&cx=c&gtm=4e64h1	326 ms	269 ms	53 ms
www.googletagmanager.com/gtag/destination?id=AW-10836211492&cx=c&gtm=4e64h1	318 ms	267 ms	48 ms
www.googletagmanager.com/gtag/destination?id=DC-2507573&cx=c&gtm=4e64h1	286 ms	236 ms	44 ms
workspace.google.com/assets/Dz-Ho5pc.min.js	250 ms	16 ms	0.2 ms
workspace.google.com/chunks/DX-UClOw.min.js	243 ms	236 ms	0.1 ms
ssl.google-analytics.com/ga.js	107 ms	86 ms	19 ms
workspace.google.com/assets/CZtCh9OT.min.js	102 ms	0.0 ms	2.0 ms
workspace.google.com/assets/DmMVEAbJ.min.js	99 ms	0.0 ms	0.1 ms
workspace.google.com/assets/0DoU6G7H.min.js	92 ms	12 ms	0.2 ms
workspace.google.com/chunks/v5v0npB_.min.js	71 ms	69 ms	0.5 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	3.3 s
Style & Layout	2.9 s
Other	1.4 s
Parse HTML & CSS	303 ms
Script Parsing & Compilation	280 ms
Rendering	264 ms
Garbage Collection	151 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.

Estimated savings: 0.0 ms 2.8 KiB

URL	Transfer Size	Est Savings
/css?family=Google+Sans:400\|Google+Sans+Text:700\|Roboto:7...	26.2 KiB	2.8 KiB

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: 0.0 ms 41.8 KiB

URL	Transfer Size	Est Savings
/css?family=Google+Sans:400\|Google+Sans+Text:700\|Roboto:7...	26.1 KiB	26.1 KiB
workspace.google.com/assets/Bctcio4i.css	34.4 KiB	15.8 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 241.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/destination?id=AW-10836211492&cx=c&gtm=4e64h1	146.1 KiB	62.8 KiB
www.googletagmanager.com/gtag/js?id=G-FWCBRW1RY8&cx=c&gtm=4e64h1	151.3 KiB	61.7 KiB
www.googletagmanager.com/gtag/destination?id=DC-2507573&cx=c&gtm=4e64h1	131.7 KiB	61.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-Q4J6	170.3 KiB	55.3 KiB

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
/yii01ecysRl3f2TblmxOdGyrw6bVn6RrrSsQ4LuQbvW0YyvfAAgrq3GH...	444.8 KiB
/o4wxafHy28RsP2VVOv2ZnCJPmZe22lRRv57Eay90LpKawkKZ-S6vsRoh...	298.1 KiB
/5vqi-23-fEE4_tEqYq2SMsJYK9zmyZFEMdETyKv6-EKhkzOSxAeTIH_h...	217.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-Q4J6	170.7 KiB
/s/materialiconsoutlined/v110/gok-H7zzDkdnRel8-DQ6KAXJ69w...	151.7 KiB
www.googletagmanager.com/gtag/js?id=G-FWCBRW1RY8&cx=c&gtm=4e64h1	151.4 KiB
www.googletagmanager.com/gtag/destination?id=AW-10836211492&cx=c&gtm=4e64h1	146.1 KiB
www.googletagmanager.com/gtag/destination?id=DC-2507573&cx=c&gtm=4e64h1	131.7 KiB
fonts.gstatic.com/s/materialicons/v145/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2	125.6 KiB
/r5D_bbSaYm9hhy1tcQ9--ySN64I-iKSGlnvv6UWGv6tmvNaRUEgfFT7m...	78.9 KiB

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

●Optimize DOM size

●Font display

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●User Timing marks and measures 173 user timings

●Avoid long main-thread tasks 17 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 70 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 10 ms

○INP breakdown

○Avoid non-composited animations

Accessibility

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

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.carousel__pagination > button.controls__dots__dot `div.container > div.carousel__pagination > button.controls__dots__dot`
div.container > div.carousel__pagination > button.controls__dots__dot `div.container > div.carousel__pagination > button.controls__dots__dot`
div.container > div.carousel__pagination > button.controls__dots__dot `div.container > div.carousel__pagination > button.controls__dots__dot`

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.

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
Try Drive for work `gws-header > gws-action-bar > span.gws-button > a.button`
Try Drive for work `div.Text_container > div.ButtonGroup_buttonGroup > span.gws-button > a.button`
Open Tooltip: This feature is available on some Google Workspace Business and E… `aside.container > button.trigger`
Open Tooltip: This feature is available on some Google Workspace Business and E… `aside.container > button.trigger`
Try Drive for work `div.Text_container > div.ButtonGroup_buttonGroup > span.gws-button > a.button`
Change Language `div.footer__nav__help > div.footer__nav__language__selector > div.language-selector > button.language-selector__toggle`

○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]`s are contained by their required parent element

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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

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

○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

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

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.

Link destination	Link Text
workspace.google.com/resources/	See more
workspace.google.com/resources/	See more
workspace.google.com/resources/	See more
workspace.google.com/resources/	See more
workspace.google.com/resources/	See more
workspace.google.com/resources/	See more
workspace.google.com/solutions/migration/drive-migration/	Learn more
workspace.google.com/customers/blueoxfilms/	Learn more
/blog/customer-stories/roche-protects-files-ai-classifica...	Learn more
workspace.google.com/customers/mmp/	Learn more

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`