wwf.dk website review

About 735 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

4 images could be 376 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 33 (desktop: 40). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, GetSiteControl and Cookiebot and others), adding 724 KiB and 506 ms of main-thread time.

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

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

29 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.

23 KiB could be saved by minifying JavaScript.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.

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

Polyfills for old browsers add 17 KiB JavaScript that modern phones do not need.

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 layout shifts by 1 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NATUREN HAR BRUG FOR 300 NYE STØTTER​”.

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.7 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 968 ms for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 449 ms in total while the page loads. Good is under 200 ms.

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

Your homepage downloads 2.5 MB in 50 requests on a phone: scripts 1.4 MB (26), images 632 KiB (6) and fonts 363 KiB (4). Under 2 MB keeps phones on slow connections fast.

3 images (600 KiB) 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.

3 images further down the page (226 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 13 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 on the page fails this check, rated moderate by axe-core.

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

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

The homepage links to 67 pages on wwf.dk and 15 external pages.

There is no https://wwf.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://wwf.dk/kaemper-for, https://wwf.dk/kaemper-for/biodiversitet, https://wwf.dk/kaemper-for/natur-i-danmark, https://wwf.dk/kaemper-for/groenland, https://wwf.dk/kaemper-for/plastikfri-natur and https://wwf.dk/kaemper-for/livet-under-vand and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://wwf.dk/kaemp-med-os/testamente has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.

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.

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 373 words of visible text.

Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 11 cookies (measured from a US location before any click).

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