C — https://dropbox.com | BeaverCheck Audit

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Room to improve — your 11.7s load time is above Google's 2.5s 'Good' threshold.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Heavier than average — reducing page weight saves energy and bandwidth.

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

Amazon Route 53 sites average 72

At average

Better than 29% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Apple sites average 73

At average

Better than 26% of Apple sites See full Apple benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

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

Security › Security Headers

No Content-Security-Policy header found

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

Security › Content Security Policy

Page weighs 14.6 MB (10.4 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

1 button(s) with no accessible text

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

Accessibility › Link & Button Quality

170 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

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fdropbox.com)](https://beavercheck.com/results/585cee70-f72e-4190-aea9-be2fc37bd262)

HTML

<a href="https://beavercheck.com/results/585cee70-f72e-4190-aea9-be2fc37bd262"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fdropbox.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fdropbox.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.7s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. 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.

Your LCP is 11.7s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.

1 accessibility issue excludes users who rely on assistive technology.

Conversion Barriers

3 critical 4 warning

7 barrier(s) likely increasing bounce by ~30%.

Speed (2)

Page takes 11.7s to load

+12% bounce

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

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

Page feels frozen for 974ms

+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 (1)

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

Content (2)

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

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (2)

9 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

18 broken link(s) on the page

+5% 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

$650 investment → $3,648/month returns + USD 7,500 risk avoided

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

Investment

$650

6h · 5 findings

Monthly returns

$3,648 /mo

~$43,779 / year

Conversions recovered $3,646
Bandwidth savings $2.61

Regulatory risk avoided

USD 7,500

if kept compliant

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

$650

6.5 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

Custom rate

$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$628 / month at risk

~$7,531 / year if left unfixed

Compliance Risk

$7,500

CCPA/CPRA

No privacy policy link detected
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no cookie policy found
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no privacy policy found
CCPA/CPRA: USD 2,500 – USD 7,500

+1 more

Bandwidth Waste

$2.61 /mo

32649.5 MB/mo × 0.080 USD/GB

Optimize transfer: save ~3.3 MB per page load
Saves $2.61/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

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

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

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

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

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

11.65 s

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

974 ms

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

0.000

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

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

16.17 s

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

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.

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:39.55 source:map[column:756039 line:1 type:source-location url:https://cfl.dropboxstatic.com/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_warp_warp_page_edison-vfltPCDXA.js urlProvider:network]] map[reflowTime:4.934 source:map[column:765868 line:1 type:source-location url:https://cfl.dropboxstatic.com/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_warp_warp_page_edison-vfltPCDXA.js urlProvider:network]] map[reflowTime:5.268 source:map[column:773638 line:1 type:source-location url:https://cfl.dropboxstatic.com/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_warp_warp_page_edison-vfltPCDXA.js urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:416.953 label:Time to first byte subpart:timeToFirstByte] map[duration:2772.696 label:Resource load delay subpart:resourceLoadDelay] map[duration:158.367 label:Resource load duration subpart:resourceLoadDuration] map[duration:35.645 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: Dropbox desktop and mobile screen for file sync and share

path: 1,HTML,1,BODY,16,DIV,0,DIV,1,DIV,2,MAIN,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,1,IMG

selector: div.dwg-box > div.dwg-media > picture.dwg-box > img.dwg-media-image

snippet: <img class="dwg-media-image dwg-media-image--object-fit-contain dwg-box dwg-position--…" alt="Dropbox desktop and mobile screen for file sync and share" crossorigin="anonymous" loading="eager" fetchpriority="high" sizes="(min-width: 1920px) 33vw, (min-width: 1440px) 50vw, (min-width: 1280px) 50…" src="https://fjord.dropboxstatic.com/warp/conversion/dropbox/warp/en-us/index/d…" srcset="https://fjord.dropboxstatic.com/warp/conversion/dropbox/warp/en-us/index/d…">

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: Dropbox desktop and mobile screen for file sync and share

path: 1,HTML,1,BODY,16,DIV,0,DIV,1,DIV,2,MAIN,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,1,IMG

selector: div.dwg-box > div.dwg-media > picture.dwg-box > img.dwg-media-image

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
/static/metaserver/static/css/font_sharp_grotesk-vflwgPRU...	12.5 KiB	1.2 s
/static/metaserver/static/js/alameda_bundle/alameda_bundl...	21.7 KiB	1.4 s
/static/typescript/component_libraries/dwg-components/src...	40.2 KiB	1.7 s
/static/metaserver/static/css/dig-components/tokens-vflyw...	11.9 KiB	1.2 s
/static/metaserver/static/css/warp/skip_to_main_content-v...	737 B	822 ms
/static/metaserver/static/css/dig-fonts/sharp_grotesk_23....	1.0 KiB	822 ms
cfl.dropboxstatic.com/static/metaserver/static/css/notify-vfl1v0oiv.css	739 B	822 ms
/static/metaserver/static/css/dig-fonts/index.metaserver-...	1.4 KiB	822 ms
cfl.dropboxstatic.com/static/metaserver/static/css/accessibility-vfliGZNRm.css	562 B	822 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
/cms/content/dam/dropbox/warp/en-us/index/october-2025-la...	3600.0 s	5.3 MiB
/cms/content/dam/dropbox/warp/en-us/index/october-2025-la...	3600.0 s	1.7 MiB
/cms/content/dam/dropbox/warp/en-us/index/october-2025-la...	3600.0 s	1.3 MiB
/warp/conversion/dropbox/warp/en-us/index/desktop-mobile-...	86400.0 s	49.2 KiB
/warp/conversion/dropbox/warp/icons/home-pg-logos/Crunch....	86400.0 s	12.9 KiB
/warp/conversion/dropbox/warp/icons/home-pg-logos/Cirque....	86400.0 s	9.2 KiB
/warp/conversion/dropbox/warp/icons/home-pg-logos/Hydro.s...	86400.0 s	7.8 KiB
/warp/conversion/dropbox/warp/en-us/index/october-2025-la...	86400.0 s	4.1 KiB
/warp/conversion/dropbox/warp/icons/home-pg-logos/McLaren...	86400.0 s	4.0 KiB
/warp/conversion/dropbox/warp/icons/home-pg-logos/Zoom.sv...	86400.0 s	2.4 KiB
/warp/conversion/dropbox/warp/icons/home-pg-logos/Lincoln...	86400.0 s	2.3 KiB
/warp/conversion/dropbox/warp/icons/home-pg-logos/Katz.sv...	86400.0 s	2.3 KiB
/warp/conversion/dropbox/warp/icons/reclaim-dbx-waffle-32...	86400.0 s	1.3 KiB
/warp/conversion/dropbox/warp/icons/dash-logo-nav.svg?id=...	86400.0 s	1.1 KiB
/warp/conversion/dropbox/warp/icons/DocSend-logo-nav.svg?...	86400.0 s	1.1 KiB
/warp/conversion/dropbox/warp/icons/replay-logo-nav.svg?i...	86400.0 s	1.0 KiB
/warp/conversion/dropbox/warp/icons/dropbox-sign-logo.svg...	86400.0 s	978 B
/warp/conversion/dropbox/warp/icons/Dropbox-logo-nav.svg?...	86400.0 s	870 B
/warp/conversion/dropbox/warp/icons/arrow_right.svg?id=e5...	86400.0 s	717 B

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.

Estimated savings: 800 ms

URL	Time Spent
dropbox.com/	800 ms
www.dropbox.com/	0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 420 ms 133.2 KiB

URL	Transfer Size	Est Savings
/static/metaserver/static/css/dig-components/components-v...	43.1 KiB	43.1 KiB
/static/typescript/component_libraries/dwg-components/src...	39.9 KiB	36.1 KiB
/static/metaserver/static/css/dig-components/foundations-...	30.2 KiB	30.2 KiB
/static/metaserver/static/css/font_sharp_grotesk-vflwgPRU...	12.2 KiB	12.2 KiB
/static/metaserver/static/css/dig-components/tokens-vflyw...	11.6 KiB	11.6 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

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

Estimated savings: 1.6 s 682.2 KiB

URL	Transfer Size	Est Savings
/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_war...	520.9 KiB	275.5 KiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_dig...	134.3 KiB	128.9 KiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_tri...	109.9 KiB	99.0 KiB
accounts.google.com/gsi/client	95.4 KiB	69.2 KiB
/static/metaserver/static/pithos/zoom_chat_client.bundle-...	74.0 KiB	56.5 KiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_fin...	82.2 KiB	28.3 KiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_cor...	33.8 KiB	24.7 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	7105436169.0 s	53 ms	0.0 ms
/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_war...	1.1 s	252 ms	160 ms
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_red...	797 ms	745 ms	1.3 ms
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_fin...	765 ms	628 ms	13 ms
www.dropbox.com/	358 ms	53 ms	21 ms
/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_cor...	324 ms	270 ms	11 ms
/static/metaserver/static/js/alameda_bundle/alameda_bundl...	204 ms	198 ms	4.9 ms
/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_rea...	146 ms	111 ms	12 ms
accounts.google.com/gsi/client	97 ms	78 ms	19 ms
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_src...	91 ms	59 ms	4.1 ms
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_api...	74 ms	70 ms	3.5 ms
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_ux_...	57 ms	46 ms	1.9 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
Other	7105436169.5 s
Script Evaluation	2.9 s
Style & Layout	554 ms
Script Parsing & Compilation	415 ms
Rendering	111 ms
Garbage Collection	105 ms
Parse HTML & CSS	65 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

URL	Transfer Size	Est Savings
/static/metaserver/static/css/dig-components/components-v...	43.4 KiB	3.9 KiB
/static/metaserver/static/css/font_sharp_grotesk-vflwgPRU...	12.5 KiB	3.1 KiB
/static/metaserver/static/css/dig-components/foundations-...	30.5 KiB	2.9 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
/cms/content/dam/dropbox/warp/en-us/index/october-2025-la...	5.3 MiB
/cms/content/dam/dropbox/warp/en-us/index/october-2025-la...	1.7 MiB
/cms/content/dam/dropbox/warp/en-us/index/october-2025-la...	1.3 MiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_war...	521.2 KiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_dig...	134.6 KiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_tri...	110.2 KiB
accounts.google.com/gsi/client	96.2 KiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_fin...	82.5 KiB
/static/metaserver/static/pithos/zoom_chat_client.bundle-...	74.3 KiB
/static/metaserver/static/fonts/sharpgrotesk/SharpGrotesk...	60.5 KiB

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Improve image delivery

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●User Timing marks and measures 14 user timings

●Avoid long main-thread tasks 13 long tasks found

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

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 280 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

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#warp-metadata > nav.dwg-nav > div.dwg-box > button.dwg-nav__hamburger-button `div#warp-metadata > nav.dwg-nav > div.dwg-box > button.dwg-nav__hamburger-button`

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

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●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

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

●Uses ARIA roles only on compatible elements

●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

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

○Links are distinguishable without relying on color.

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

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Fledge	/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_fin... line 1, col 66125

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
www.dropbox.com/	`Not signed in with the identity provider.`

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●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

●Use a strong HSTS policy

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

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
www.dropbox.com/features/cloud-storage	Learn more
www.dropbox.com/features/share/send-large-files	Learn more
www.dropbox.com/features/security	Learn more
www.dropbox.com/business/solutions/construction	Learn more
www.dropbox.com/business/solutions/media	Learn more
www.dropbox.com/business/solutions/technology	Learn more
www.dropbox.com/business/solutions/professional-services	Learn more
www.dropbox.com/business/solutions/manufacturing	Learn more
www.dropbox.com/education	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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

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.

2.02 s

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

2.76 s

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

56 ms

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

0.060

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

3.53 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.22 s

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.

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 ▾

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.

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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
/static/metaserver/static/fonts/paper-atlasgrotesk/AtlasG...	30 ms

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:36.356 source:map[column:756247 line:1 type:source-location url:https://cfl.dropboxstatic.com/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_warp_warp_page_edison-vfltPCDXA.js urlProvider:network]] map[reflowTime:3.719 source:map[column:765868 line:1 type:source-location url:https://cfl.dropboxstatic.com/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_warp_warp_page_edison-vfltPCDXA.js urlProvider:network]] map[reflowTime:6.095 source:map[column:773638 line:1 type:source-location url:https://cfl.dropboxstatic.com/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_warp_warp_page_edison-vfltPCDXA.js urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:396.262 label:Time to first byte subpart:timeToFirstByte] map[duration:2824.849 label:Resource load delay subpart:resourceLoadDelay] map[duration:102.248 label:Resource load duration subpart:resourceLoadDuration] map[duration:96.39 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: Dropbox desktop and mobile screen for file sync and share

path: 1,HTML,1,BODY,16,DIV,0,DIV,1,DIV,2,MAIN,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,1,IMG

selector: div.dwg-box > div.dwg-media > picture.dwg-box > img.dwg-media-image

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: Dropbox desktop and mobile screen for file sync and share

path: 1,HTML,1,BODY,16,DIV,0,DIV,1,DIV,2,MAIN,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,1,IMG

selector: div.dwg-box > div.dwg-media > picture.dwg-box > img.dwg-media-image

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.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
/static/metaserver/static/css/font_sharp_grotesk-vflwgPRU...	12.5 KiB	303 ms
/static/metaserver/static/js/alameda_bundle/alameda_bundl...	21.7 KiB	354 ms
/static/metaserver/static/css/dig-components/tokens-vflyw...	11.9 KiB	303 ms
/static/typescript/component_libraries/dwg-components/src...	40.2 KiB	405 ms
/static/metaserver/static/css/warp/skip_to_main_content-v...	737 B	251 ms
/static/metaserver/static/css/dig-fonts/sharp_grotesk_23....	1.0 KiB	251 ms
/static/metaserver/static/css/dig-fonts/index.metaserver-...	1.4 KiB	251 ms
cfl.dropboxstatic.com/static/metaserver/static/css/accessibility-vfliGZNRm.css	562 B	251 ms
cfl.dropboxstatic.com/static/metaserver/static/css/notify-vfl1v0oiv.css	775 B	251 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
/cms/content/dam/dropbox/warp/en-us/index/october-2025-la...	3600.0 s	5.3 MiB
/cms/content/dam/dropbox/warp/en-us/index/october-2025-la...	3600.0 s	1.7 MiB
/cms/content/dam/dropbox/warp/en-us/index/october-2025-la...	3600.0 s	1.3 MiB
assets.adobedtm.com/7c31e7b46b8e/5feae65e0b10/launch-9b21c433d0d6.min.js	3600.0 s	47.7 KiB
/warp/conversion/dropbox/warp/en-us/index/october-2025-la...	86400.0 s	52.8 KiB
/warp/conversion/dropbox/warp/en-us/index/desktop-mobile-...	86400.0 s	49.2 KiB
/warp/conversion/dropbox/warp/icons/home-pg-logos/Crunch....	86400.0 s	12.9 KiB
/warp/conversion/dropbox/warp/icons/home-pg-logos/Cirque....	86400.0 s	9.3 KiB
/warp/conversion/dropbox/warp/icons/home-pg-logos/Hydro.s...	86400.0 s	7.6 KiB
/warp/conversion/dropbox/warp/en-us/index/october-2025-la...	86400.0 s	4.1 KiB
/warp/conversion/dropbox/warp/icons/home-pg-logos/McLaren...	86400.0 s	4.0 KiB
/warp/conversion/dropbox/warp/icons/home-pg-logos/Zoom.sv...	86400.0 s	2.4 KiB
/warp/conversion/dropbox/warp/icons/home-pg-logos/Katz.sv...	86400.0 s	2.3 KiB
/warp/conversion/dropbox/warp/icons/home-pg-logos/Lincoln...	86400.0 s	2.2 KiB
/7c31e7b46b8e/5feae65e0b10/b301283facbc/RCe690552bddfc46d...	3600.0 s	809 B
/warp/conversion/dropbox/warp/icons/reclaim-dbx-waffle-32...	86400.0 s	1.3 KiB
/7c31e7b46b8e/5feae65e0b10/b301283facbc/RC07e99ffb24cd457...	3600.0 s	666 B
/warp/conversion/dropbox/warp/icons/replay-logo-nav.svg?i...	86400.0 s	1.1 KiB
/warp/conversion/dropbox/warp/icons/dash-logo-nav.svg?id=...	86400.0 s	1.1 KiB
/7c31e7b46b8e/5feae65e0b10/b301283facbc/RC388cd7fa3bf94c2...	3600.0 s	584 B
/warp/conversion/dropbox/warp/icons/DocSend-logo-nav.svg?...	86400.0 s	1.1 KiB
/7c31e7b46b8e/5feae65e0b10/b301283facbc/RC5525b8317527424...	3600.0 s	533 B
/warp/conversion/dropbox/warp/icons/dropbox-sign-logo.svg...	86400.0 s	977 B
/warp/conversion/dropbox/warp/icons/Dropbox-logo-nav.svg?...	86400.0 s	870 B
/warp/conversion/dropbox/warp/icons/arrow_right.svg?id=e5...	86400.0 s	717 B

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
Two women in fashionable outfits `div._media_mrwa9_95 > div.dwg-media > picture.dwg-box > img.dwg-media-image`	/warp/conversion/dropbox/warp/en-us/index/october-2025-la...	52.1 KiB	33.1 KiB
Dropbox desktop and mobile screen for file sync and share `div.dwg-box > div.dwg-media > picture.dwg-box > img.dwg-media-image`	/warp/conversion/dropbox/warp/en-us/index/desktop-mobile-...	48.6 KiB	16.3 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.

Estimated savings: 249 ms

URL	Time Spent
dropbox.com/	249 ms
www.dropbox.com/	0.0 ms

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

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 ▾

Source: Google web.dev / Lighthouse

Estimated savings: 210 ms 783.1 KiB

URL	Transfer Size	Est Savings
/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_war...	520.9 KiB	271.1 KiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_dig...	134.3 KiB	128.9 KiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_tri...	109.9 KiB	99.0 KiB
/static/atlas/privacy_consent/ccpa_iframe_bundle_amd/dist...	186.1 KiB	79.3 KiB
accounts.google.com/gsi/client	95.4 KiB	71.1 KiB
/static/metaserver/static/pithos/zoom_chat_client.bundle-...	74.0 KiB	55.5 KiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_fin...	82.2 KiB	28.3 KiB
/static/atlas/privacy_consent/ccpa_iframe_bundle_amd/dist...	33.9 KiB	25.2 KiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_cor...	33.8 KiB	24.7 KiB

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	1.1 s
Other	555 ms
Style & Layout	243 ms
Script Parsing & Compilation	159 ms
Rendering	46 ms
Garbage Collection	36 ms
Parse HTML & CSS	27 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

URL	Transfer Size	Est Savings
/static/metaserver/static/css/dig-components/components-v...	43.4 KiB	3.9 KiB
/static/metaserver/static/css/font_sharp_grotesk-vflwgPRU...	12.5 KiB	3.1 KiB
/static/metaserver/static/css/dig-components/foundations-...	30.5 KiB	2.9 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 45.7 KiB

URL	Transfer Size	Est Savings
/static/typescript/component_libraries/dwg-components/src...	39.9 KiB	33.5 KiB
/static/metaserver/static/css/font_sharp_grotesk-vflwgPRU...	12.2 KiB	12.2 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
/cms/content/dam/dropbox/warp/en-us/index/october-2025-la...	5.3 MiB
/cms/content/dam/dropbox/warp/en-us/index/october-2025-la...	1.7 MiB
/cms/content/dam/dropbox/warp/en-us/index/october-2025-la...	1.3 MiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_war...	521.3 KiB
/static/atlas/privacy_consent/ccpa_iframe_bundle_amd/dist...	186.5 KiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_dig...	134.6 KiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_tri...	110.2 KiB
accounts.google.com/gsi/client	96.2 KiB
/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_fin...	82.5 KiB
/static/metaserver/static/pithos/zoom_chat_client.bundle-...	74.3 KiB

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

●Max Potential First Input Delay 90 ms

●Layout shift culprits

●Optimize DOM size

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●User Timing marks and measures 37 user timings

●JavaScript execution time 0.6 s

●Avoid long main-thread tasks 4 long tasks found

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

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 610 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

Accessibility

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > iframe#ccpa-iframe `body > iframe#ccpa-iframe`

These are opportunities to improve keyboard navigation in your application.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

●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"]`

●Uses ARIA roles only on compatible elements

●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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Fledge	/static/atlas/warp/warp_page_edison_bundle_amd/dist/c_fin... line 1, col 66125

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
/static/atlas/warp/warp_page_edison_bundle_amd/dist/e_cor... line 1, col 60197	`[GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token. Error`
www.dropbox.com/	`Not signed in with the identity provider.`

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●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

●Use a strong HSTS policy

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

SEO

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
www.dropbox.com/features/cloud-storage	Learn more
www.dropbox.com/features/share/send-large-files	Learn more
www.dropbox.com/features/security	Learn more
www.dropbox.com/business/solutions/construction	Learn more
www.dropbox.com/business/solutions/media	Learn more
www.dropbox.com/business/solutions/technology	Learn more
www.dropbox.com/business/solutions/professional-services	Learn more
www.dropbox.com/business/solutions/manufacturing	Learn more
www.dropbox.com/education	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`

Results for https://dropbox.com

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (1)

Content (2)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Navigation

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts