washworld.dk website review

2 images could be 7.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

Your mobile performance score is 85 (desktop: 89). Pages that score under 90 lose visitors before the first paint.

About 416 KiB of JavaScript is downloaded but never used on this page.

Google Tag Manager costs a phone 253 ms of main-thread work and 529 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.

A phone's processor spends 2.1 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 2,118 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

7 third-party services load with your homepage (Google Tag Manager, cookieinformation.com and GitHub and others), adding 639 KiB and 305 ms of main-thread time.

4 files are served with short cache lifetimes, so returning visitors download them again (61 KiB).

Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

6 long tasks block the main thread while loading, the longest for 121 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

The page becomes fully interactive after 13.6 s. Good is under 3.8 s.

Real visitors wait 205 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 159 ms to 205 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Visually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

1 image have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 17.4 MB in 72 requests on a phone: images 10.3 MB (5), media 5.8 MB (3) and scripts 1.1 MB (34). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 4.93 g of CO₂e: 592.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 buttons have no accessible name, so screen readers announce just “button”.

5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

3 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

There are 3 <h1> headlines (“Hader du køen til bilvasken?”, “Vask UbegrænsetBliv Premium medlem - få første må…” and “Over 4 millioner biler vasket i 2025”). One clear main headline is easier for people and search engines.

The homepage links to 39 pages on washworld.dk and 4 external pages.

There is no https://washworld.dk/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.

https://washworld.dk/enkeltvask, https://washworld.dk/vores-vaskemaskiner, https://washworld.dk/nyhedsbrev, https://washworld.dk/om-os, https://washworld.dk/miljoeprofil and https://washworld.dk/presse and 2 others all use the title “Wash World”. Search engines can't tell which page to show for a search, so each competes with the others.

https://washworld.dk/vores-vaskemaskiner, https://washworld.dk/erhverv, https://washworld.dk/nyhedsbrev, https://washworld.dk/om-os, https://washworld.dk/miljoeprofil and https://washworld.dk/presse and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://washworld.dk/find-wash-world-vaskehal, https://washworld.dk/vask-selv, https://washworld.dk/blivmedlem, https://washworld.dk/nyhedsbrev, https://washworld.dk/om-os and https://washworld.dk/miljoeprofil and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://washworld.dk/blivmedlem, https://washworld.dk/nyhedsbrev and https://washworld.dk/presse have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 14 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 529 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.