Spain · Madrid Completed: Apr 7, 2026 20:05 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.
Content-Security-Policy header is missing
No Content-Security-Policy header found
2 control(s) without accessible label
2 image(s) missing alt attribute
2 link(s) with no accessible text
[](https://beavercheck.com/results/8fe29f7e-bc16-a6a2-fc33-0668f4093b36)<a href="https://beavercheck.com/results/8fe29f7e-bc16-a6a2-fc33-0668f4093b36"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.dpd.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.dpd.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.
8.28 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
15.40 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.32 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.
8.28 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.
15.40 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.
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 | |
|---|---|---|---|
Geopost value proposition div.wrap > div.row > div.col-lg-6 > img.image-inline | www.dpd.com/wp-content/uploads/2023/04/Geopost_Web_ValueProp_800x534.gif | 1.4 MiB | 1.3 MiB |
Welcome to DPD
DPD is part of Geopost, one of the world leading parcel de… div#pgc-1169-0-0 > div#panel-1169-0-0-0 > div.textwidget > div.hero-image | www.dpd.com/wp-content/uploads/2023/04/Powerpoint_PNG-GeopostNetwork_Van_DPD.png | 830.9 KiB | 530.9 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
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.
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 |
|---|---|---|
| www.dpd.com/wp-content/themes/DPD_NoLogin/css/styles.min.css?ver=6.8.3 | 72.5 KiB | 69.8 KiB |
| www.dpd.com/wp-includes/css/dashicons.min.css?ver=6.8.3 | 34.9 KiB | 34.9 KiB |
| www.dpd.com/wp-content/plugins/form-maker/css/styles.min.css?ver=2.15.7 | 18.7 KiB | 18.7 KiB |
| www.dpd.com/wp-includes/css/dist/block-library/style.min.css?ver=6.8.3 | 15.0 KiB | 15.0 KiB |
| /wp-content/plugins/dpd-cms-modules/assets/css/front-end.... | 10.3 KiB | 10.2 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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| cdn.amcharts.com/lib/version/4.10.29/core.js?ver=1.6.1 | 253.6 KiB | 157.8 KiB |
| www.dpd.com/wp-content/plugins/form-maker/js/scripts.min.js?ver=2.15.7 | 45.0 KiB | 37.7 KiB |
| cdn.amcharts.com/lib/version/4.10.29/maps.js?ver=1.6.1 | 40.3 KiB | 23.1 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.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| cdn.amcharts.com/lib/version/4.10.29/core.js?ver=1.6.1 | 3.9 s | 2.9 s | 130 ms |
| www.dpd.com/ | 561 ms | 39 ms | 18 ms |
| Unattributable | 428 ms | 15 ms | 0.0 ms |
| www.dpd.com/wp-content/themes/DPD_NoLogin/js/fontawesome-all.min.js?ver=6.8.3 | 373 ms | 241 ms | 98 ms |
| cdn.tagcommander.com/5380/tc_DPD_HUB_80.js | 279 ms | 173 ms | 7.5 ms |
| www.dpd.com/wp-content/themes/DPD_NoLogin/js/jquery-3.6.0.min.js?ver=3.6.0 | 159 ms | 119 ms | 11 ms |
| cdn.trustcommander.net/iab-tcfapi/tcfapi.js?v=96.0 | 123 ms | 111 ms | 11 ms |
| www.dpd.com/wp-content/themes/DPD_NoLogin/js/Hyphenopoly/Hyphenopoly_Loader.js | 113 ms | 6.4 ms | 18 ms |
| cdn.amcharts.com/lib/4/geodata/worldLow.js?ver=1.6.1 | 67 ms | 40 ms | 27 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 | 3.8 s |
| Other | 861 ms |
| Style & Layout | 843 ms |
| Script Parsing & Compilation | 434 ms |
| Parse HTML & CSS | 147 ms |
| Garbage Collection | 128 ms |
| Rendering | 83 ms |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| blob:https://www.dpd.com/38b31a08-c798-42cc-9dd3-95a5fa723fe3 | 34.9 KiB | 20.5 KiB |
| www.dpd.com/wp-content/themes/DPD_NoLogin/js/Hyphenopoly/Hyphenopoly_Loader.js | 3.3 KiB | 2.1 KiB |
| www.dpd.com/wp-content/themes/DPD_NoLogin/js/Hyphenopoly/Hyphenopoly_Loader.js | 3.3 KiB | 2.1 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
| URL | |
|---|---|
Geopost value proposition div.wrap > div.row > div.col-lg-6 > img.image-inline | www.dpd.com/wp-content/uploads/2023/04/Geopost_Web_ValueProp_800x534.gif |
DPD logo header.row-fix-margin-auto > nav.navbar > a.navbar-brand > img.size-icon-logo | /wp-content/themes/DPD_NoLogin/images/DPD_logo_redgrad_rg... |
form#search-mobile > div.mobile-search > i.input-icon > img form#search-mobile > div.mobile-search > i.input-icon > img | www.dpd.com/wp-content/themes/DPD_NoLogin/images/magnifier.svg |
header.row-fix-margin-auto > nav.navbar > span.offmenu-toggle > img header.row-fix-margin-auto > nav.navbar > span.offmenu-toggle > img | www.dpd.com/wp-content/themes/DPD_NoLogin/images/burger-menu.svg |
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 an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
| Failing Elements |
|---|
g.imapsContainer > g.imapsSprite-group > g.imapsContainer > g.imapsSprite-group g.imapsContainer > g.imapsSprite-group > g.imapsContainer > g.imapsSprite-group |
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
| Failing Elements |
|---|
Cookie Settings
We and our partners use cookies or other tracers to facilitate… body.home > div#tc-privacy-wrapper > div#popin_tc_privacy |
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
| Failing Elements |
|---|
Use plus and minus keys on your keyboard to zoom in and out g.imapsSprite-group > g.imapsContainer > g.imapsSprite-group > g.imapsSprite-group |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
Africa div.row > div.column > h3 > span |
Americas div.row > div.column > h3 > span |
Asia div.row > div.column > h3 > span |
Europe div.row > div.column > h3 > span |
These are opportunities to improve the legibility of your content.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
| Failing Elements |
|---|
English nav.nav > ul.footer-link > li.language-items > select#footer-language-select |
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
| Failing Elements |
|---|
nav.nav > ul.footer-link > li.language-items > a.select-arrow nav.nav > ul.footer-link > li.language-items > a.select-arrow |
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.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
| Failing Elements |
|---|
head > meta head > meta |
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 |
|---|
English nav.nav > ul.footer-link > li.language-items > select#footer-language-select |
nav.nav > ul.footer-link > li.language-items > a.select-arrow nav.nav > ul.footer-link > li.language-items > a.select-arrow |
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 |
|---|---|
Failed to load resource: the server responded with a status of 500 () | |
Failed to load resource: the server responded with a status of 500 () |
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.
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
| Uncrawlable Link |
|---|
nav.nav > ul.footer-link > li.language-items > a.select-arrow nav.nav > ul.footer-link > li.language-items > a.select-arrow |
nav.nav > ul.footer-link > li.language-items > a.select-arrow nav.nav > ul.footer-link > li.language-items > a.select-arrow |
To appear in search results, crawlers need access to your app.
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.30 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.38 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
232 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.003
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.79 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.43 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.
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 | |
|---|---|---|---|
Geopost value proposition div.wrap > div.row > div.col-lg-6 > img.image-inline | www.dpd.com/wp-content/uploads/2023/04/Geopost_Web_ValueProp_800x534.gif | 1.4 MiB | 1.2 MiB |
Welcome to DPD
DPD is part of Geopost, one of the world leading parcel de… div#pgc-1169-0-0 > div#panel-1169-0-0-0 > div.textwidget > div.hero-image | www.dpd.com/wp-content/uploads/2023/04/Powerpoint_PNG-GeopostNetwork_Van_DPD.png | 830.9 KiB | 530.9 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
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.
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 |
|---|---|---|
| www.dpd.com/wp-content/themes/DPD_NoLogin/css/styles.min.css?ver=6.8.3 | 72.5 KiB | 69.0 KiB |
| www.dpd.com/wp-includes/css/dashicons.min.css?ver=6.8.3 | 34.9 KiB | 34.9 KiB |
| www.dpd.com/wp-content/plugins/form-maker/css/styles.min.css?ver=2.15.7 | 18.7 KiB | 18.7 KiB |
| www.dpd.com/wp-includes/css/dist/block-library/style.min.css?ver=6.8.3 | 15.0 KiB | 15.0 KiB |
| /wp-content/plugins/dpd-cms-modules/assets/css/front-end.... | 10.3 KiB | 10.2 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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| cdn.amcharts.com/lib/version/4.10.29/core.js?ver=1.6.1 | 253.8 KiB | 157.9 KiB |
| www.dpd.com/wp-content/plugins/form-maker/js/scripts.min.js?ver=2.15.7 | 45.0 KiB | 37.7 KiB |
| cdn.amcharts.com/lib/version/4.10.29/maps.js?ver=1.6.1 | 40.3 KiB | 23.1 KiB |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| blob:https://www.dpd.com/c261f3e3-e1c7-416d-8cec-a13b77db039e | 34.9 KiB | 20.5 KiB |
| www.dpd.com/wp-content/themes/DPD_NoLogin/js/Hyphenopoly/Hyphenopoly_Loader.js | 3.3 KiB | 2.1 KiB |
| www.dpd.com/wp-content/themes/DPD_NoLogin/js/Hyphenopoly/Hyphenopoly_Loader.js | 3.3 KiB | 2.1 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
| URL | |
|---|---|
Geopost value proposition div.wrap > div.row > div.col-lg-6 > img.image-inline | www.dpd.com/wp-content/uploads/2023/04/Geopost_Web_ValueProp_800x534.gif |
DPD logo header.row-fix-margin-auto > nav.navbar > a.navbar-brand > img.size-icon-logo | /wp-content/themes/DPD_NoLogin/images/DPD_logo_redgrad_rg... |
form#search-desktop > div.input-box > i.input-icon > img form#search-desktop > div.input-box > i.input-icon > img | www.dpd.com/wp-content/themes/DPD_NoLogin/images/magnifier.svg |
header.row-fix-margin-auto > nav.navbar > span.offmenu-toggle > img header.row-fix-margin-auto > nav.navbar > span.offmenu-toggle > img | www.dpd.com/wp-content/themes/DPD_NoLogin/images/burger-menu.svg |
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 an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
| Failing Elements |
|---|
g.imapsContainer > g.imapsSprite-group > g.imapsContainer > g.imapsSprite-group g.imapsContainer > g.imapsSprite-group > g.imapsContainer > g.imapsSprite-group |
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
| Failing Elements |
|---|
Cookie Settings
We and our partners use cookies or other tracers to facilitate… body.home > div#tc-privacy-wrapper > div#popin_tc_privacy |
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
| Failing Elements |
|---|
Use plus and minus keys on your keyboard to zoom in and out g.imapsSprite-group > g.imapsContainer > g.imapsSprite-group > g.imapsSprite-group |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
Africa div.row > div.column > h3 > span |
Americas div.row > div.column > h3 > span |
Asia div.row > div.column > h3 > span |
Europe div.row > div.column > h3 > span |
These are opportunities to improve the legibility of your content.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
| Failing Elements |
|---|
English nav.nav > ul.footer-link > li.language-items > select#footer-language-select |
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
| Failing Elements |
|---|
nav.nav > ul.footer-link > li.language-items > a.select-arrow nav.nav > ul.footer-link > li.language-items > a.select-arrow |
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.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
| Failing Elements |
|---|
head > meta head > meta |
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 |
|---|
Privacy nav.nav > ul.footer-link > li > a.grey-color |
English nav.nav > ul.footer-link > li.language-items > select#footer-language-select |
nav.nav > ul.footer-link > li.language-items > a.select-arrow nav.nav > ul.footer-link > li.language-items > a.select-arrow |
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 |
|---|---|
Failed to load resource: the server responded with a status of 500 () | |
Failed to load resource: the server responded with a status of 500 () |
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.
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
| Uncrawlable Link |
|---|
nav.nav > ul.footer-link > li.language-items > a.select-arrow nav.nav > ul.footer-link > li.language-items > a.select-arrow |
nav.nav > ul.footer-link > li.language-items > a.select-arrow nav.nav > ul.footer-link > li.language-items > a.select-arrow |
To appear in search results, crawlers need access to your app.
Send Feedback