Singapore · Singapore Completed: Apr 7, 2026 20:04 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 73 / 100
Based on 8 categories, 0 sections
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
'unsafe-eval' found in script source
'unsafe-inline' found in script source
Cookie 'locale' is missing the Secure flag
Page weighs 18.0 MB (11.4 MB transferred)
1 button(s) with no accessible text
[](https://beavercheck.com/results/48a24ff3-6aa4-41d9-b02a-2d8212a6ee37)<a href="https://beavercheck.com/results/48a24ff3-6aa4-41d9-b02a-2d8212a6ee37"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.dropbox.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.dropbox.comThis badge auto-updates with your latest scan result.
Thanks for your feedback!
Industry-standard audits powered by Google Lighthouse.
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.
2.87 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.64 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
3.31 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.053
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
6.63 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.
21.03 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
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.
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.
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.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
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.
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.
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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /static/typescript/component_libraries/dwg-components/src... | 40.0 KiB | 36.1 KiB |
| /static/metaserver/static/css/font_sharp_grotesk-vflwgPRU... | 12.2 KiB | 12.2 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.
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
| Category | Time Spent |
|---|---|
| Script Evaluation | 7.3 s |
| Other | 4.5 s |
| Style & Layout | 1.8 s |
| Script Parsing & Compilation | 1.2 s |
| Rendering | 283 ms |
| Parse HTML & CSS | 276 ms |
| Garbage Collection | 271 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
| 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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /static/metaserver/static/css/dig-components/components-v... | 43.5 KiB | 3.9 KiB |
| /static/metaserver/static/css/font_sharp_grotesk-vflwgPRU... | 12.4 KiB | 3.0 KiB |
| /static/metaserver/static/css/dig-components/foundations-... | 30.5 KiB | 2.9 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.
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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.
| 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.
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.
| Failing Elements |
|---|
body > iframe#ccpa-iframe body > iframe#ccpa-iframe |
These are opportunities to improve keyboard navigation in your application.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
| Deprecation / Warning | Source |
|---|---|
| Fledge | /static/atlas/warp/warp_page_edison_bundle_amd/dist/c_fin... line 1, col 66125 |
| AttributionReporting |
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
| 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 |
Not signed in with the identity provider. |
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
| 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.
Industry-standard audits powered by Google Lighthouse. — Desktop
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.07 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.63 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
601 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.023
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.56 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.
9.80 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
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.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
| 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 |
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.
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.
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.
| URL | Est Savings |
|---|---|
| /static/metaserver/static/fonts/paper-atlasgrotesk/AtlasG... | 20 ms |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
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.
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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /static/typescript/component_libraries/dwg-components/src... | 40.0 KiB | 40.0 KiB |
| /static/metaserver/static/css/font_sharp_grotesk-vflwgPRU... | 12.2 KiB | 12.2 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.
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
| Category | Time Spent |
|---|---|
| Other | 1775592204.7 s |
| Script Evaluation | 3.5 s |
| Script Parsing & Compilation | 567 ms |
| Style & Layout | 526 ms |
| Garbage Collection | 159 ms |
| Rendering | 86 ms |
| Parse HTML & CSS | 81 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
| 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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /static/metaserver/static/css/dig-components/components-v... | 43.5 KiB | 3.9 KiB |
| /static/metaserver/static/css/font_sharp_grotesk-vflwgPRU... | 12.4 KiB | 3.0 KiB |
| /static/metaserver/static/css/dig-components/foundations-... | 30.5 KiB | 2.9 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.
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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.
| Failing Elements |
|---|
body > iframe#ccpa-iframe body > iframe#ccpa-iframe |
These are opportunities to improve keyboard navigation in your application.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
| Deprecation / Warning | Source |
|---|---|
| Fledge | /static/atlas/warp/warp_page_edison_bundle_amd/dist/c_fin... line 1, col 66125 |
| AttributionReporting |
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
| 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 |
Access to XMLHttpRequest at 'https://tags.srv.stackadapt.com/print_cookie?f=1&err=Cannot%20set%20properties%20of%20undefined%20(setting%20%27callMethod%27)' from origin 'https://marketing.dropbox.com' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute. | |
Failed to load resource: net::ERR_FAILED | |
Loading the script 'blob:https://marketing.dropbox.com/ed30a1b5-e4ec-4e4a-967a-926468ded52b' violates the following Content Security Policy directive: "default-src https: 'unsafe-inline' 'unsafe-eval'". Note that 'script-src-elem' was not explicitly set, so 'default-src' is used as a fallback. The action has been blocked. | |
Not signed in with the identity provider. |
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
| Issue type |
|---|
| Content security policy |
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
| 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.
Send Feedback