Website review, no card needed
dpd.nl website review
Visit site (opens in a new tab)Reviewed 27 October 202639 issues · 89 checks
This review found 39 issues worth fixing on dpd.nl, 17 of them high impact, across 89 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.3 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 195 ms |
| May 16, 2026 | 193 ms |
| May 23, 2026 | 186 ms |
| May 30, 2026 | 175 ms |
| Jun 6, 2026 | 161 ms |
| Jun 13, 2026 | 148 ms |
| Jun 20, 2026 | 144 ms |
| Jun 27, 2026 | 144 ms |
| Jul 4, 2026 | 144 ms |
| Jul 11, 2026 | 145 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 146 ms |
| Aug 1, 2026 | 147 ms |
| Aug 8, 2026 | 148 ms |
| Aug 15, 2026 | 149 ms |
| Aug 22, 2026 | 150 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 157 ms |
| Sep 12, 2026 | 159 ms |
| Sep 19, 2026 | 162 ms |
| Sep 26, 2026 | 162 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 162 ms |
| Oct 17, 2026 | 162 ms |
| Oct 24, 2026 | 161 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Improve image delivery
7.7 s · 1.8 MB10 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.7 s faster on a phone.
Render-blocking requests
7.5 s40 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.5 s.
Reduce unused JavaScript
1.8 s · 387 KiBAbout 387 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 48
48/100Your mobile performance score is 48 (desktop: 70). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
900 ms · 159 KiBAbout 159 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Use efficient cache lifetimes
800 ms · 157 KiB9 files are served with short cache lifetimes, so returning visitors download them again (157 KiB).
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, consentmanager.net and Hubspot and others), adding 831 KiB and 833 ms of main-thread time.
Google Tag Manager adds 400 ms
400 msGoogle Tag Manager costs a phone 400 ms of main-thread work and 502 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
consentmanager.net adds 292 ms
292 msconsentmanager.net costs a phone 292 ms of main-thread work and 132 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify JavaScript
150 ms · 24 KiB24 KiB could be saved by minifying JavaScript.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 132 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 23.8 s
23.8 sYour largest element takes 23.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “100%”.
First Contentful Paint: 6.9 s
6.9 sThe first text or image appears after 6.9 s on a phone. Good is under 1.8 s.
Time to Interactive: 24.0 s
24.0 sThe page becomes fully interactive after 24.0 s. Good is under 3.8 s.
Speed Index: 10.9 s
10.9 sVisually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.
Real-user INP: 246 ms
246 msReal visitors wait 246 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 333 ms
333 msScripts block taps and scrolling for 333 ms in total while the page loads. Good is under 200 ms.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 449 ms
449 msReal visitors wait 449 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 195 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
1 image over 500 KB
DPDNL-042_DemandGen_B_1200x1200_V1.png weighs 1.8 MB. On a phone connection a single image that size takes seconds.
Page weight: 3.8 MB in 111 requests
3.8 MBYour homepage downloads 3.8 MB in 111 requests on a phone: images 2.1 MB (25), scripts 1.5 MB (57) and stylesheets 180 KiB (15). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (1.9 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 1.1 g of CO₂ per visit
1.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.09 g of CO₂e: 130.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
12 tap targets too small
12 tap targets are too small or too close together to hit reliably with a finger.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (24 elements)
All page content should be contained by landmarks: 24 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
7 form fields without a label
7 form fields have no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Zoek je iets anders?” and “Vier redenen om met DPD te versturen”). One clear main headline is easier for people and search engines.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
111 internal links, 28 external
The homepage links to 111 pages on dpd.nl and 28 external pages.
7 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Pakket Versturen of Ontvangen? Ontdek het Gemak van DPD ✓Verzendkosten v.a. €4,95 ✓Verzending in Europa ✓Bezorging tot …”.
Title: 64 characters
Your title is a healthy 64 characters: “Pakket Versturen of Ontvangen | Altijd onderweg. Voor jou. | DPD”.
Canonical URL set
The canonical URL is https://www.dpd.com/nl/nl/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.dpd.com/de/de/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.dpd.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (485 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
15 small tap targets
15 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 319 words of copy
The homepage carries about 319 words of visible text.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.
13 cookies set on arrival
13Opening the homepage sets 13 cookies (measured from a US location before any click).
16 other companies contacted
Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: consentmanager
A consent management tool (consentmanager) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at dpd.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Ingenit
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on dpd.nl, including 18 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.