lbst.dk website review

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

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

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

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

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

3 third-party services load with your homepage (cookiebot.eu, teamviewer.com and Siteimprove), adding 262 KiB and 65 ms of main-thread time.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

3 images could be 16 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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.

Your largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LANDBRUGSSTYRELSEN FORDELT PÅ TO NYE STYRELSER”. Most of its time is element render delay (4.5 s).

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

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

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

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

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

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

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

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 94 ms to 94 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 1.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.8 MB in 38 requests on a phone: stylesheets 975 KiB (2), fonts 695 KiB (6) and images 667 KiB (13). Under 2 MB keeps phones on slow connections fast.

4 images (396 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.

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

Banner landmark should not be contained in another landmark: 1 element on the page fails 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.

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 140 pages on lbst.dk and 16 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://lbst.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://lbst.dk/tast-selv-performance has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

Opening the homepage sets 1 cookie (measured from a US location before any click).

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