zetland.dk website review

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

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

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

12 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

6 third-party services load with your homepage (sanity.io, mux.com and imgix and others), adding 6.1 MB and 1 ms of main-thread time.

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

Other Google APIs/SDKs costs a phone 0 ms of main-thread work and 4.3 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.

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

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

imgix costs a phone 0 ms of main-thread work and 1.4 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 20 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

Desktop scores 82 but mobile only 49. 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.

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

Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Video thumbnail”.

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

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

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

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

Your homepage downloads 7.3 MB in 94 requests on a phone: media 4.5 MB (5), images 1.6 MB (17) and scripts 1,024 KiB (47). Under 2 MB keeps phones on slow connections fast.

2025101410240658256x5504ma.jpg weighs 920 KiB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example 2025101410240658256x5504ma.jpg at 8,192 px wide, shown at 342 px. Resized copies would save about 920 KiB.

thumbnail.jpg 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).

4 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (159 KiB) is 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.

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

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

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

All page content should be contained by landmarks: 38 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.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 7 characters: “Zetland”. 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.

Your meta description is 227 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 11 pages on zetland.dk and 0 external pages.

Your robots.txt shuts out ChatGPT (ChatGPT-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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

robots.txt blocks GPTBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

/, https://www.zetland.dk/nytmedlem, https://www.zetland.dk/virksomhed, https://www.zetland.dk/undervisning and https://www.zetland.dk/voreshelte all use the title “Zetland”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.zetland.dk/nytmedlem, https://www.zetland.dk/forlag, https://www.zetland.dk/virksomhed, https://www.zetland.dk/undervisning, https://www.zetland.dk/voreshelte and https://www.zetland.dk/vilkaar use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.zetland.dk/forlag, whose canonical is https://www.zetland.dk/publishing. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.zetland.dk/nytmedlem has 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.

https://www.zetland.dk/nytmedlem took over 3 s to send its HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

There is no form on the homepage, so every lead has to click through to another page first.

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 2,301 words of visible text.

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