Skip to content
https://www.dpd.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

32

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

Performance issues directly impact user engagement and conversion rates.

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.

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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:64.488 source:map[column:483766 line:19 type:source-location url:https://cdn.amcharts.com/lib/version/4.10.29/core.js?ver=1.6.1 urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:42.671 source:map[type:text value:[unattributed]]] map[reflowTime:64.488 source:map[column:913022 line:18 type:source-location url:https://cdn.amcharts.com/lib/version/4.10.29/core.js?ver=1.6.1 urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
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.gif1.4 MiB1.3 MiB
We­lco­me to DPD DPD is part of Geo­post, one of the world le­ading par­cel 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.png830.9 KiB530.9 KiB

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-1-DIV
nodeLabel: We­lco­me to DPD DPD is part of Geo­post, one of the world le­ading par­cel de…
path: 1,HTML,1,BODY,1,DIV,5,DIV,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV
selector: div#pgc-1169-0-0 > div#panel-1169-0-0-0 > div.textwidget > div.hero-image
snippet: <div class="hero-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.

URLTransfer SizeDuration
www.dpd.com/wp-content/themes/DPD_NoLogin/js/fontawesome-all.min.js?ver=6.8.3434.2 KiB2.6 s
www.dpd.com/wp-content/plugins/form-maker/js/scripts.min.js?ver=2.15.745.2 KiB166 ms
cdn.tagcommander.com/5380/tc_DPD_HUB_80.js20.5 KiB1.1 s
www.dpd.com/wp-includes/js/jquery/ui/effect-shake.min.js?ver=1.13.3581 B166 ms
/wp-content/plugins/dpd-eshopper/public/js/dpd-eshopper-p...596 B
www.dpd.com/wp-includes/js/jquery/ui/effect.min.js?ver=1.13.33.9 KiB
www.dpd.com/wp-includes/js/jquery/ui/core.min.js?ver=1.13.37.0 KiB
www.dpd.com/wp-content/themes/DPD_NoLogin/js/jquery-ui.min.js?ver=6.8.38.8 KiB166 ms
www.dpd.com/wp-content/plugins/dpd-news/js/popper.min.js?ver=1.0.07.2 KiB
www.dpd.com/wp-content/plugins/siteorigin-premium/js/animate.min.js?ver=1.8.0879 B
/wp-content/plugins/siteorigin-premium/js/on-screen.umd.m...1.6 KiB
www.dpd.com/wp-content/themes/DPD_NoLogin/js/jquery.vEllipsis.min.js?ver=6.8.31.5 KiB
www.dpd.com/wp-content/themes/DPD_NoLogin/js/objectFitPolyfill.min.js?ver=6.8.31.3 KiB
www.dpd.com/wp-content/themes/DPD_NoLogin/js/jquery-3.6.0.min.js?ver=3.6.030.3 KiB331 ms
www.dpd.com/wp-content/themes/DPD_NoLogin/js/doubletaptogo.min.js?ver=6.8.3521 B
www.dpd.com/wp-content/themes/DPD_NoLogin/js/jquery.sticky-kit.min.js?ver=6.8.31.3 KiB
www.dpd.com/wp-content/themes/DPD_NoLogin/js/slick.min.js?ver=6.8.310.3 KiB
www.dpd.com/wp-content/themes/DPD_NoLogin/js/dragdealer.min.js?ver=6.8.34.0 KiB
www.dpd.com/wp-content/themes/DPD_NoLogin/js/bootstrap.min.js?ver=6.8.315.2 KiB166 ms
www.dpd.com/wp-content/plugins/dpd-cms-modules/admin/js/popper.min.js?ver=1.0.07.2 KiB
/wp-content/themes/DPD_NoLogin/js/bootstrap-datepicker.mi...10.7 KiB166 ms
www.dpd.com/wp-content/themes/DPD_NoLogin/js/jquery.appear.min.js?ver=6.8.3621 B
/wp-content/plugins/dpd-cms-modules/assets/js/blocker-lay...1017 B
/wp-content/plugins/dpd-cms-modules/assets/js/anchor-link...3.5 KiB166 ms
www.dpd.com/wp-content/themes/DPD_NoLogin/js/Hyphenopoly/Hyphenopoly_Loader.js3.5 KiB
www.dpd.com/wp-includes/css/dist/block-library/style.min.css?ver=6.8.315.1 KiB166 ms
www.dpd.com/wp-content/plugins/form-maker/css/styles.min.css?ver=2.15.718.8 KiB331 ms
www.dpd.com/wp-content/plugins/dpd-cms-page/pub/css/frontend.min.css?ver=6.8.3440 B
/wp-content/plugins/dpd-forms-management/public/css/form-...2.0 KiB
/wp-content/plugins/dpd-forms-management/public/css/defau...978 B
/wp-content/plugins/siteorigin-panels/css/front-flex.min....675 B
/wp-content/plugins/dpd-exchange-media/public/css/dpd-exc...221 B
/wp-content/plugins/dpd-popup/public/css/dpd-popup-public...974 B
/wp-content/plugins/dpd-eshopper/public/css/dpd-eshopper-...189 B
www.dpd.com/wp-content/plugins/dpd-custom-layout/public/css/style.css?ver=1.0.01.3 KiB
www.dpd.com/wp-content/plugins/siteorigin-premium/css/animate.min.css?ver=1.8.04.0 KiB
/wp-content/plugins/dpd-cms-modules/assets/css/animate.mi...5.3 KiB
/wp-content/plugins/dpd-cms-modules/assets/css/front-end....10.3 KiB166 ms
www.dpd.com/wp-includes/css/dashicons.min.css?ver=6.8.335.0 KiB497 ms
www.dpd.com/wp-content/themes/DPD_NoLogin/css/styles.min.css?ver=6.8.372.7 KiB1.2 s

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation3.8 s
Other861 ms
Style & Layout843 ms
Script Parsing & Compilation434 ms
Parse HTML & CSS147 ms
Garbage Collection128 ms
Rendering83 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Use efficient cache lifetimes
Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Avoid long main-thread tasks 13 long tasks found
Avoid non-composited animations 2 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 30 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 40 ms
INP breakdown
User Timing marks and measures
Avoid large layout shifts
70

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Afri­ca div.row > div.column > h3 > span
Ame­ri­cas div.row > div.column > h3 > span
Asia div.row > div.column > h3 > span
Eu­ro­pe div.row > div.column > h3 > span

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Best practices

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.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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
`<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
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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
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.
96

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: the server responded with a status of 500 ()
Failed to load resource: the server responded with a status of 500 ()
Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

SEO

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

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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 have descriptive text
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback