geus.dk website review

17 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.7 s.

28 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

About 383 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.9 s faster on a phone.

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

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

4 third-party services load with your homepage (gopublic.dk, Siteimprove and Google Fonts and others), adding 3.6 MB and 120 ms of main-thread time.

gopublic.dk costs a phone 109 ms of main-thread work and 3.5 MB 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.

About 47 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

15 KiB could be saved by minifying JavaScript.

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

Desktop scores 85 but mobile only 43. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

For real visitors the layout shifts by 0.44 (75th percentile). Good is under 0.1.

The first text or image appears after 6.1 s on a phone. Good is under 1.8 s.

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

The layout shifts by 0.358 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

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

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

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

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

Your homepage downloads 3.7 MB in 47 requests on a phone: images 2.2 MB (16), fonts 890 KiB (4) and stylesheets 396 KiB (3). Under 2 MB keeps phones on slow connections fast.

geus_dk_logo_header.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

3 tap targets are too small or too close together to hit reliably with a finger.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

Your title is only 4 characters: “GEUS”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 5 <h1> headlines (“GEUS ansætter to nye vicedirektører”, “Klimatilpasning kan flytte forureningsfaner” and “Ny forskning viser, hvordan tørke udvikler sig i …”). One clear main headline is easier for people and search engines.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 176 pages on geus.dk and 46 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.geus.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://www.geus.dk/om-geus/kontakt, https://www.geus.dk/om-geus/nyheder, https://www.geus.dk/energiressourcer/geotermi-og-jordvarme/stratigrafiske-metoder/sedimentaere-bassiner, https://www.geus.dk/natur-og-klima/jordskaelv-og-seismologi, https://www.geus.dk/natur-og-klima/jordskaelv-og-seismologi/overvaagning-af-seismisk-aktivitet and https://www.geus.dk/natur-og-klima/jordskaelv-og-seismologi/registrerede-jordskaelv-i-groenland-aeldre-version have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.geus.dk/energiressourcer/geotermi-og-jordvarme/aflejringsmodeller, https://www.geus.dk/energiressourcer/geotermi-og-jordvarme/geofysiske-metoder, https://www.geus.dk/energiressourcer/geotermi-og-jordvarme/stratigrafiske-metoder/sedimentaere-bassiner and https://www.geus.dk/energiressourcer/geotermi-og-jordvarme/stratigrafiske-metoder took over 3 s to send their HTML from our server.

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

21 of 38 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.