blandselvfroe.dk website review

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

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

36 images could be 791 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Klaviyo, Clarity and Google Tag Manager and others), adding 954 KiB and 818 ms of main-thread time.

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

Klaviyo costs a phone 258 ms of main-thread work and 323 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.

Shopify costs a phone 81 ms of main-thread work and 385 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.

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

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

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

42 KiB JavaScript is shipped twice across bundles.

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

About 10 KiB of CSS is downloaded but never applied on this page.

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.

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 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

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

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

Your homepage downloads 7.0 MB in 788 requests on a phone: images 4.2 MB (398), other files 1.4 MB (252) and scripts 849 KiB (91). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

2 images have no alt text, which hurts accessibility and image search.

96 form fields have no label, so screen readers announce an empty box and autofill guesses.

Main landmark should not be contained in another landmark: 12 elements on the page fail this check, rated moderate by axe-core.

All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 visible link has no text or label, so screen readers cannot say where it goes.

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

Your title is 66 characters, so Google will cut it off around 60: “Økologiske Frø | Økologiske frø til kun 19,95 kr. - Køb online her”.

The homepage links to 495 pages on blandselvfroe.dk and 6 external pages.

https://blandselvfroe.dk/pages/wishlist is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://blandselvfroe.dk/policies/shipping-policy, https://blandselvfroe.dk/pages/germination-guarantee, https://blandselvfroe.dk/pages/kundeservice, https://blandselvfroe.dk/pages/wishlist, https://blandselvfroe.dk/collections/black-month and https://blandselvfroe.dk/collections/sidste-chance have no meta description, so Google writes the search snippet from whatever text it finds.

https://blandselvfroe.dk/policies/shipping-policy, https://blandselvfroe.dk/pages/germination-guarantee, https://blandselvfroe.dk/pages/kundeservice, https://blandselvfroe.dk/pages/wishlist, https://blandselvfroe.dk/products/aarets-froe-julekalender-2026 and https://blandselvfroe.dk/collections/black-month and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://blandselvfroe.dk/collections/black-month, https://blandselvfroe.dk/collections/sidste-chance, https://blandselvfroe.dk/collections/mikrogroent, https://blandselvfroe.dk/collections/mikrogroent-froe and https://blandselvfroe.dk/collections/tulipaner 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 15 pages linked from your homepage (of 197 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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 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 3,376 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (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.

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