Mobile 375 × 812

Desktop 1440 × 900

Score: 69 / 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.
Content-Security-Policy header is missing
Cookie 'Rbt' is missing the Secure flag
HSTS header is missing
No Content-Security-Policy header found
No <main> landmark found
[](https://beavercheck.com/results/0f13ea85-f444-a032-097d-2b484165a86e)<a href="https://beavercheck.com/results/0f13ea85-f444-a032-097d-2b484165a86e"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.fedex.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.fedex.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.
5.32 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
19.39 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
3.73 s
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.
10.13 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.55 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.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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.
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 | |
|---|---|---|---|
FedEx nav.fxg-nav > div.fxg-wrapper > a.fxg-header__logo_wrapper > img.fxg-header__logo | www.fedex.com/content/dam/fedex-com/logos/logo.png | 17.5 KiB | 16.4 KiB |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
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.
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.
| URL | Time Spent |
|---|---|
| www.fedex.com/ | 807 ms |
| www.fedex.com/global/choose-location.html | 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.
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.
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /etc.clientlibs/fedex-core/clientlibs/clientlib-base.min.... | 291.0 KiB | 127.5 KiB |
| web.cmp.usercentrics.eu/ui/v/3.111.0/WebSdk.lib.f9924d53.js | 73.2 KiB | 22.8 KiB |
| web.cmp.usercentrics.eu/ui/TvGdprCmpView.b6de9c89.js | 35.3 KiB | 11.6 KiB |
| web.cmp.usercentrics.eu/ui/loader.js | 19.7 KiB | 6.8 KiB |
| web.cmp.usercentrics.eu/ui/v/3.111.0/GdprCmpController.51b3e85e.js | 12.7 KiB | 4.5 KiB |
| web.cmp.usercentrics.eu/ui/v/3.111.0/UcGdprCmpView.c071ab9b.js | 21.4 KiB | 2.6 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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /etc.clientlibs/fedex-core/clientlibs/clientlib-base.min.... | 72.8 KiB | 70.9 KiB |
| /etc.clientlibs/fedex-core/clientlibs/clientlib-dependenc... | 26.5 KiB | 26.0 KiB |
| .overlay { --color-cmp-overlay: #333333; --feature-overlay-opacity: 0.7; } … | 15.1 KiB | 13.7 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
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.1 s |
| Script Parsing & Compilation | 1.7 s |
| Other | 1.1 s |
| Style & Layout | 530 ms |
| Parse HTML & CSS | 189 ms |
| Garbage Collection | 150 ms |
| Rendering | 80 ms |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
Privacy Notice div#uc-cmp-description > div#uc-privacy-description > span.privacy-text-detailed > a |
COOKIE PREFERENCES div#main-view > header.has-custom-logo > div.links > a#uc-more-link |
ACCEPT ALL COOKIES footer#uc-cmp-footer > div.buttons > div.buttons-row > button#accept |
REJECT OPTIONAL COOKIES footer#uc-cmp-footer > div.buttons > div.buttons-row > button#deny |
These are opportunities to improve the legibility of your content.
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the `lang` attribute.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
| Failing Elements |
|---|
CARIBBEAN div.fxg-col > div.link > div.link > a.fxg-link |
CENTRAL & SOUTH AMERICA div.fxg-col > div.link > div.link > a.fxg-link |
MIDDLE EAST div.fxg-col > div.link > div.link > a.fxg-link |
NORTH AMERICA div.fxg-col > div.link > div.link > a.fxg-link |
These items highlight common accessibility best practices.
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 |
|---|---|
assets.adobedtm.com/launch-EN3932511771fb4e5e9dd852ae89372b59.min.js line 11, col 10177 | [ADOBE OPT-IN] Invalid `preOptInApprovals`! |
www.fedex.com/gdl/next/gdl-next-fedex.js line 1, col 368642 | ❌ AEP Web SDK sendEvent failed: Error: AEP Web SDK is not initialized. Ensure the platform is activated before sending events. |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
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.
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.17 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.40 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
378 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.
3.00 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.
3.44 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.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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.
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.
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
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.
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 | |
|---|---|---|---|
FedEx nav.fxg-nav > div.fxg-wrapper > a.fxg-header__logo_wrapper > img.fxg-header__logo | www.fedex.com/content/dam/fedex-com/logos/logo.png | 17.5 KiB | 17.2 KiB |
Search div.fxg-user-options > div.fxg-user-options__option > a > img.fxg-user-options__icon | www.fedex.com/content/dam/fedex-com/common/sprite-placeholder.png | 7.7 KiB | 7.7 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.
| URL | Time Spent |
|---|---|
| www.fedex.com/ | 242 ms |
| www.fedex.com/global/choose-location.html | 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.
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.
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /etc.clientlibs/fedex-core/clientlibs/clientlib-base.min.... | 291.0 KiB | 127.5 KiB |
| web.cmp.usercentrics.eu/ui/v/3.111.0/WebSdk.lib.f9924d53.js | 73.2 KiB | 22.8 KiB |
| web.cmp.usercentrics.eu/ui/TvGdprCmpView.b6de9c89.js | 35.3 KiB | 11.6 KiB |
| web.cmp.usercentrics.eu/ui/loader.js | 19.7 KiB | 6.8 KiB |
| web.cmp.usercentrics.eu/ui/v/3.111.0/GdprCmpController.51b3e85e.js | 12.7 KiB | 4.5 KiB |
| web.cmp.usercentrics.eu/ui/v/3.111.0/UcGdprCmpView.c071ab9b.js | 21.4 KiB | 2.6 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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /etc.clientlibs/fedex-core/clientlibs/clientlib-base.min.... | 72.8 KiB | 71.5 KiB |
| /etc.clientlibs/fedex-core/clientlibs/clientlib-dependenc... | 26.5 KiB | 26.0 KiB |
| .overlay { --color-cmp-overlay: #333333; --feature-overlay-opacity: 0.7; } … | 15.1 KiB | 13.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.
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.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| www.fedex.com/global/choose-location.html | 783 ms | 524 ms | 2.5 ms |
| www.fedex.com/assets/79a26a5472ae5cd0a0e5f981ba0cc5db9001192124f | 294 ms | 251 ms | 11 ms |
| Unattributable | 282 ms | 26 ms | 0.0 ms |
| www.fedex.com/E80caW4ngR02/FHpJqZ/kxMI4c/1QDuGc7rhO1mkhz5J9/WHQ5MQ/DzNT/PH5iWhsB | 236 ms | 208 ms | 25 ms |
| www.fedex.com/gdl/next/gdl-next-fedex.js | 138 ms | 108 ms | 30 ms |
| /686b8f0c4520/a46df9c77975/launch-f96010731c97-developmen... | 133 ms | 24 ms | 108 ms |
| assets.adobedtm.com/launch-EN3932511771fb4e5e9dd852ae89372b59.min.js | 109 ms | 86 ms | 19 ms |
| /etc.clientlibs/fedex-core/clientlibs/clientlib-base.min.... | 101 ms | 19 ms | 78 ms |
| /etc.clientlibs/fedex-core/clientlibs/clientlib-dependenc... | 80 ms | 50 ms | 24 ms |
| /maps/api/js?key=testkey&libraries=places&callback=FDX.IN... | 75 ms | 48 ms | 26 ms |
| web.cmp.usercentrics.eu/ui/v/3.111.0/WebSdk.lib.f9924d53.js | 57 ms | 35 ms | 22 ms |
| www.fedex.com/akam/13/4c79ddaf | 56 ms | 49 ms | 1.8 ms |
| /dxjsmodule/12.45e656039b3fa23613e1.chunk.js?Q_CLIENTVERS... | 52 ms | 41 ms | 7.5 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.7 s |
| Script Parsing & Compilation | 412 ms |
| Other | 298 ms |
| Style & Layout | 155 ms |
| Parse HTML & CSS | 52 ms |
| Garbage Collection | 52 ms |
| Rendering | 44 ms |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
Privacy Notice div#uc-cmp-description > div#uc-privacy-description > span.privacy-text-detailed > a |
COOKIE PREFERENCES footer#uc-cmp-footer > div.left-container > div.links > a#uc-more-link |
REJECT OPTIONAL COOKIES footer#uc-cmp-footer > div.buttons > div.buttons-row > button#deny |
ACCEPT ALL COOKIES footer#uc-cmp-footer > div.buttons > div.buttons-row > button#accept |
These are opportunities to improve the legibility of your content.
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the `lang` attribute.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
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 |
|---|---|
assets.adobedtm.com/launch-EN3932511771fb4e5e9dd852ae89372b59.min.js line 11, col 10177 | [ADOBE OPT-IN] Invalid `preOptInApprovals`! |
www.fedex.com/gdl/next/gdl-next-fedex.js line 1, col 368642 | ❌ AEP Web SDK sendEvent failed: Error: AEP Web SDK is not initialized. Ensure the platform is activated before sending events. |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
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.
Send Feedback