Skip to content
Audit Complete

Results for https://drive.google.com

Visit site
United Stated United Stated · New York Completed: Apr 21, 2026 18:46 UTC
Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C74

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Google Search Console · 2306 peers
You 74
·
Avg 73
At average
0 50 100
Better than 55% of Google Search Console sites See full Google Search Console benchmark →
Google Workspace · 1091 peers
You 74
·
Avg 73
At average
0 50 100
Better than 48% of Google Workspace sites See full Google Workspace benchmark →

Top Priorities (5)

1

'unsafe-inline' found in script source

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
2

Cookie 'NID' is missing the Secure flag

Security gaps expose your site and users to attacks, eroding trust.

Security › Cookie Security
3

1 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility
4

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure
5

147 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fdrive.google.com)](https://beavercheck.com/results/40144172-b88d-47d3-b7c3-b9b9cd8fcfa6)
<a href="https://beavercheck.com/results/40144172-b88d-47d3-b7c3-b9b9cd8fcfa6"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fdrive.google.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fdrive.google.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 11.9s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.
Your LCP is 11.9s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

3 critical 8 warning

11 barrier(s) likely increasing bounce by ~35%.

Speed (2)

Page takes 11.9s to load

+12% bounce

Users abandon at ~3s — you're 9.4s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 2.5s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (2)

Severe layout shift during page load

+6% bounce

Users mis-click when content jumps — converting intent into frustration

Fix: Reserve space for images, ads, and embeds with explicit width/height

1 form field(s) without a label

+2% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

1 broken link(s) on the page

+2% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$600 investment → $3,328/month returns + USD 157,500 risk avoided

Payback period: < 1 month First-year ROI: +6556%

Investment

$600

6h · 5 findings

Monthly returns

$3,328 /mo

~$39,938 / year

  • Conversions recovered $3,327
  • Bandwidth savings $0.70

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

Payback period

0 12mo 24mo

$100 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$600

6.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$100 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,126 / month at risk

~$157,508 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • 1 tracking cookie(s) set before consent interaction
    CCPA/CPRA: USD 2,500 – USD 7,500
  • No <main> landmark found
    ADA Title III: USD 25,000 – USD 150,000
  • No <nav> landmark found
    ADA Title III: USD 25,000 – USD 150,000

+2 more

Bandwidth Waste

$0.70 /mo

8744.5 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~874 KB per page load
    Saves $0.70/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 4 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

9
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
95
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

5.44 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

11.94 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

2.45 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.721

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

5.44 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

19.78 s

Detailed Report

Audit breakdown by category with detailed findings.

9

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

URLResource SizeEst 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 KiB391.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 KiB29.4 KiB
video.video video.video
/5lMAXDhPZzGyIPU0HYUjSXgYkRr5FdO03K1i1yrMLTZYBH_G_baeCEfA...52.4 KiB18.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

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.

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.

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

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 Evaluation3.3 s
Style & Layout2.9 s
Other1.4 s
Parse HTML & CSS303 ms
Script Parsing & Compilation280 ms
Rendering264 ms
Garbage Collection151 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
URLTransfer SizeEst Savings
/css?family=Google+Sans:400|Google+Sans+Text:700|Roboto:7...26.2 KiB2.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

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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
95

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

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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

37
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
88
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.49 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.55 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

416 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

1.261

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.65 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

4.23 s

Detailed Report

Audit breakdown by category with detailed findings.

37

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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:1.2605920000000002] map[node:map[boundingRect:map[bottom:8679 height:8615 left:0 right:1350 top:64 width:1350] lhId:page-3-MAIN nodeLabel:Store and share files online AI-powered, secure cloud storage for seamless fil… path:1,HTML,1,BODY,0,DIV,1,MAIN selector:body.page--scroll-tracked > div#root > main#main snippet:<main id="main"> type:node] score:0.931915 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1099 height:467 left:577 right:1216 top:632 width:639] lhId:page-0-IMG nodeLabel:A user starts typing a file name into the Google Drive search tool, and a list … path:1,HTML,1,BODY,0,DIV,1,MAIN,4,SECTION,0,DIV,0,DIV,1,DIV,0,PICTURE,2,IMG selector:div.Grid_grid > div.Grid_column > picture > img snippet:<img src="https://lh3.googleusercontent.com/RXWK2_qSKjSclzxy44kcOLqjzMe84F4h7fPxkuUM…" srcset="https://lh3.googleusercontent.com/yii01ecysRl3f2TblmxOdGyrw6bVn6RrrSsQ4LuQ…" alt="A user starts typing a file name into the Google Drive search tool, and a …" width="1132" height="828" loading="eager" fetchpriority="high"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:1099 height:467 left:0 right:1350 top:632 width:1350] lhId:page-4-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.324955 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2340 height:467 left:577 right:1216 top:1873 width:639] lhId:page-2-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,1,DIV,0,DIV,0,DIV,0,PICTURE,0,IMG selector:div.Template5050Accordion_column > div > picture > img.Template5050Accordion_laptopImage snippet:<img class="Template5050Accordion_laptopImage" src="https://lh3.googleusercontent.com/Y8GJzDqsy5HVJ39EnNZWyn3NLqG9Q2fXXUZenaap…" srcset="https://lh3.googleusercontent.com/Y8GJzDqsy5HVJ39EnNZWyn3NLqG9Q2fXXUZenaap…" alt="Indicating 30 gigabytes of storage used in Google Workspace" width="1368" height="1000" loading="lazy" attrs="[object Object]"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:1527 height:256 left:687 right:1216 top:1271 width:529] lhId:page-8-DIV nodeLabel:Make smarter decisions with Gemini in Drive Gain valuable insights by summariz… path:1,HTML,1,BODY,0,DIV,1,MAIN,6,SECTION,0,DIV,0,DIV,1,DIV,0,DIV selector:div.TemplateTwoColumn_template > div.Grid_grid > div.Grid_column > div snippet:<div> type:node] score:0.001126 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2340 height:467 left:577 right:1216 top:1873 width:639] lhId:page-2-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,1,DIV,0,DIV,0,DIV,0,PICTURE,0,IMG selector:div.Template5050Accordion_column > div > picture > img.Template5050Accordion_laptopImage snippet:<img class="Template5050Accordion_laptopImage" src="https://lh3.googleusercontent.com/Y8GJzDqsy5HVJ39EnNZWyn3NLqG9Q2fXXUZenaap…" srcset="https://lh3.googleusercontent.com/Y8GJzDqsy5HVJ39EnNZWyn3NLqG9Q2fXXUZenaap…" alt="Indicating 30 gigabytes of storage used in Google Workspace" width="1368" height="1000" loading="lazy" attrs="[object Object]"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:916 height:94 left:1061 right:1255 top:822 width:194] lhId:page-10-DIV nodeLabel:Hi there 👋 What brings you to Google Workspace today? path:1,HTML,1,BODY,5,DIV,0,DIV selector:body.page--scroll-tracked > div#container > div.message-container snippet:<div class="message-container "> type:node] score:0.000503 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2340 height:467 left:577 right:1216 top:1873 width:639] lhId:page-2-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,1,DIV,0,DIV,0,DIV,0,PICTURE,0,IMG selector:div.Template5050Accordion_column > div > picture > img.Template5050Accordion_laptopImage snippet:<img class="Template5050Accordion_laptopImage" src="https://lh3.googleusercontent.com/Y8GJzDqsy5HVJ39EnNZWyn3NLqG9Q2fXXUZenaap…" srcset="https://lh3.googleusercontent.com/Y8GJzDqsy5HVJ39EnNZWyn3NLqG9Q2fXXUZenaap…" alt="Indicating 30 gigabytes of storage used in Google Workspace" width="1368" height="1000" loading="lazy" attrs="[object Object]"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:916 height:94 left:1061 right:1255 top:822 width:194] lhId:page-10-DIV nodeLabel:Hi there 👋 What brings you to Google Workspace today? path:1,HTML,1,BODY,5,DIV,0,DIV selector:body.page--scroll-tracked > div#container > div.message-container snippet:<div class="message-container "> type:node] score:0.000497 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2340 height:467 left:577 right:1216 top:1873 width:639] lhId:page-2-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,1,DIV,0,DIV,0,DIV,0,PICTURE,0,IMG selector:div.Template5050Accordion_column > div > picture > img.Template5050Accordion_laptopImage snippet:<img class="Template5050Accordion_laptopImage" src="https://lh3.googleusercontent.com/Y8GJzDqsy5HVJ39EnNZWyn3NLqG9Q2fXXUZenaap…" srcset="https://lh3.googleusercontent.com/Y8GJzDqsy5HVJ39EnNZWyn3NLqG9Q2fXXUZenaap…" alt="Indicating 30 gigabytes of storage used in Google Workspace" width="1368" height="1000" loading="lazy" attrs="[object Object]"> 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:133.658 source:map[type:text value:[unattributed]]] map[reflowTime:51.26 source:map[column:4055 line:0 type:source-location url:https://workspace.google.com/assets/0DoU6G7H.min.js urlProvider:network]] map[reflowTime:7.458 source:map[column:4243 line:0 type:source-location url:https://workspace.google.com/assets/0DoU6G7H.min.js urlProvider:network]] map[reflowTime:16.084 source:map[column:3335 line:0 type:source-location url:https://workspace.google.com/assets/DmMVEAbJ.min.js urlProvider:network]] map[reflowTime:4.87 source:map[column:3401 line:0 type:source-location url:https://workspace.google.com/assets/DmMVEAbJ.min.js urlProvider:network]] map[reflowTime:13.613 source:map[column:7876 line:0 type:source-location url:https://workspace.google.com/assets/kaZ5Vq1i.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
A user starts typing a file name into the Google Drive search tool, and a list … div.Grid_grid > div.Grid_column > picture > img
/RXWK2_qSKjSclzxy44kcOLqjzMe84F4h7fPxkuUMg8-g-n7ELc7u5TNk...444.2 KiB395.6 KiB
video.video video.video
/o4wxafHy28RsP2VVOv2ZnCJPmZe22lRRv57Eay90LpKawkKZ-S6vsRoh...297.8 KiB259.2 KiB
Indicating 30 gigabytes of storage used in Google Workspace div.Template5050Accordion_column > div > picture > img.Template5050Accordion_laptopImage
/Y8GJzDqsy5HVJ39EnNZWyn3NLqG9Q2fXXUZenaapj7MNjKdBm1YbbElz...92.6 KiB36.9 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

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
ssl.google-analytics.com/ga.js7200.0 s17.4 KiB

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

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.

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
Store and share files online AI-powered, secure cloud storage for seamless fil… body.page--scroll-tracked > div#root > main#main
0.932
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.325
Make smarter decisions with Gemini in Drive Gain valuable insights by summariz… div.TemplateTwoColumn_template > div.Grid_grid > div.Grid_column > div
0.001
Hi there 👋 What brings you to Google Workspace today? body.page--scroll-tracked > div#container > div.message-container
0.001
Hi there 👋 What brings you to Google Workspace today? body.page--scroll-tracked > div#container > div.message-container
0.000
Hi there 👋 What brings you to Google Workspace today? body.page--scroll-tracked > div#container > div.message-container
0.000
Hi there 👋 What brings you to Google Workspace today? body.page--scroll-tracked > div#container > div.message-container
0.000
Hi there 👋 What brings you to Google Workspace today? body.page--scroll-tracked > div#container > div.message-container
0.000
Hi there 👋 What brings you to Google Workspace today? body.page--scroll-tracked > div#container > div.message-container
0.000
Hi there 👋 What brings you to Google Workspace today? body.page--scroll-tracked > div#container > div.message-container
0.000
Hi there 👋 What brings you to Google Workspace today? body.page--scroll-tracked > div#container > div.message-container
0.000
Hi there 👋 What brings you to Google Workspace today? body.page--scroll-tracked > div#container > div.message-container
0.000

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.

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 minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation826 ms
Style & Layout759 ms
Other378 ms
Parse HTML & CSS79 ms
Rendering71 ms
Script Parsing & Compilation70 ms
Garbage Collection33 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
URLTransfer SizeEst Savings
/css?family=Google+Sans:400|Google+Sans+Text:700|Roboto:7...26.1 KiB2.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 26.1 KiB
URLTransfer SizeEst Savings
/css?family=Google+Sans:400|Google+Sans+Text:700|Roboto:7...26.1 KiB26.1 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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 10 user timings
JavaScript execution time 0.8 s
Avoid long main-thread tasks 7 long tasks found
Avoid non-composited animations 1 animated element 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 60 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 20 ms
INP breakdown
88

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

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Gemini in Drive gws-jumplinks.TemplateJumplinks_jumplinks > div.TemplateJumplinks_links > div.Text_container > a.TemplateJumplinks_link
Store gws-jumplinks.TemplateJumplinks_jumplinks > div.TemplateJumplinks_links > div.Text_container > a.TemplateJumplinks_link
Manage gws-jumplinks.TemplateJumplinks_jumplinks > div.TemplateJumplinks_links > div.Text_container > a.TemplateJumplinks_link
Collaborate gws-jumplinks.TemplateJumplinks_jumplinks > div.TemplateJumplinks_links > div.Text_container > a.TemplateJumplinks_link
Security gws-jumplinks.TemplateJumplinks_jumplinks > div.TemplateJumplinks_links > div.Text_container > a.TemplateJumplinks_link
Download gws-jumplinks.TemplateJumplinks_jumplinks > div.TemplateJumplinks_links > div.Text_container > a.TemplateJumplinks_link
Customers gws-jumplinks.TemplateJumplinks_jumplinks > div.TemplateJumplinks_links > div.Text_container > a.TemplateJumplinks_link
FAQs gws-jumplinks.TemplateJumplinks_jumplinks > div.TemplateJumplinks_links > div.Text_container > a.TemplateJumplinks_link

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.

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
body.page--scroll-tracked > div#container > div#cloud-chatbot-container > button#cloud-chatbot-chat-activate-bar-desktop body.page--scroll-tracked > div#container > div#cloud-chatbot-container > button#cloud-chatbot-chat-activate-bar-desktop

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Included applications Gmail Meet Chat Calendar Drive Docs Sheets Slides Forms S… div.TemplateFooter_footer > div.TemplateFooter_footer__content > div.TemplateFooter_footer__sitemap > ul.TemplateFooter_footer__sitemap__column
Included applications Gmail Meet Chat Calendar Drive Docs Sheets Slides Forms S… div.TemplateFooter_footer__content > div.TemplateFooter_footer__sitemap > ul.TemplateFooter_footer__sitemap__column > ul.TemplateFooter_footer__sitemap__column
Security and management Admin Endpoint Vault Work Insights Solutions New Busine… div.TemplateFooter_footer > div.TemplateFooter_footer__content > div.TemplateFooter_footer__sitemap > ul.TemplateFooter_footer__sitemap__column
Security and management Admin Endpoint Vault Work Insights div.TemplateFooter_footer__content > div.TemplateFooter_footer__sitemap > ul.TemplateFooter_footer__sitemap__column > ul.TemplateFooter_footer__sitemap__column
Solutions New Business Small Business Enterprise Retail Manufacturing Professio… div.TemplateFooter_footer__content > div.TemplateFooter_footer__sitemap > ul.TemplateFooter_footer__sitemap__column > ul.TemplateFooter_footer__sitemap__column
Pricing Compare pricing plans Add-ons Meet hardware Google Voice AppSheet div.TemplateFooter_footer > div.TemplateFooter_footer__content > div.TemplateFooter_footer__sitemap > ul.TemplateFooter_footer__sitemap__column
Pricing Compare pricing plans div.TemplateFooter_footer__content > div.TemplateFooter_footer__sitemap > ul.TemplateFooter_footer__sitemap__column > ul.TemplateFooter_footer__sitemap__column
Add-ons Meet hardware Google Voice AppSheet div.TemplateFooter_footer__content > div.TemplateFooter_footer__sitemap > ul.TemplateFooter_footer__sitemap__column > ul.TemplateFooter_footer__sitemap__column
Resources Working remotely Security Customer Stories FAQs Partners Marketplace … div.TemplateFooter_footer > div.TemplateFooter_footer__content > div.TemplateFooter_footer__sitemap > ul.TemplateFooter_footer__sitemap__column
Resources Working remotely Security Customer Stories FAQs Partners Marketplace … div.TemplateFooter_footer__content > div.TemplateFooter_footer__sitemap > ul.TemplateFooter_footer__sitemap__column > ul.TemplateFooter_footer__sitemap__column
Learning and support Admin Help Setup and Deployment Center Learning Center for… div.TemplateFooter_footer > div.TemplateFooter_footer__content > div.TemplateFooter_footer__sitemap > ul.TemplateFooter_footer__sitemap__column
Learning and support Admin Help Setup and Deployment Center Learning Center for… div.TemplateFooter_footer__content > div.TemplateFooter_footer__sitemap > ul.TemplateFooter_footer__sitemap__column > ul.TemplateFooter_footer__sitemap__column
More from Google Google Cloud Google Domains Chrome Enterprise Google Business … div.TemplateFooter_footer__content > div.TemplateFooter_footer__sitemap > ul.TemplateFooter_footer__sitemap__column > ul.TemplateFooter_footer__sitemap__column

These are opportunities to improve the experience of reading tabular or list data using 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 div.TemplateHeader_headerContent > div.TemplateHeader_headerAside > 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]` 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.
`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
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
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.
92

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.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
Indicating 30 gigabytes of storage used in Google Workspace gws-accordion-item > div.AccordionItem_imageContainer > picture > img
/Y8GJzDqsy5HVJ39EnNZWyn3NLqG9Q2fXXUZenaapj7MNjKdBm1YbbElz...608 x 500 (1.22)684 x 500 (1.37)
Attaching a pdf invoice from Drive directly to an email in Gmail gws-accordion-item > div.AccordionItem_imageContainer > picture > img
/yaeFI4_QssNg_y1mJBNSYykolRzqvAsy-bUy5nSJ57YJZNJMssOMEML0...608 x 500 (1.22)684 x 500 (1.37)
Scanning a pdf grocery bill with a phone into Drive gws-accordion-item > div.AccordionItem_imageContainer > picture > img
/Dy2FGFkccm77gzVvrnl2wl8mDJ2T1MadpzdgRLhiXcX0nYgsriVe4mbd...608 x 500 (1.22)684 x 500 (1.37)

General

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
AbortError: The play() request was interrupted by a call to pause(). https://goo.gl/LdLk22
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
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
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
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
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback