raworganics.dk website review

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

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

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

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

8 third-party services load with your homepage (cloudfront.net, Google Tag Manager and Facebook and others), adding 1.3 MB and 446 ms of main-thread time.

About 68 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

cloudfront.net costs a phone 139 ms of main-thread work and 606 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.

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

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

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

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

Polyfills for old browsers add 39 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.

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

3 KiB could be saved by minifying CSS.

2 KiB JavaScript is shipped twice across bundles.

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

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

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

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

Your homepage downloads 7.8 MB in 321 requests on a phone: media 3.9 MB (1), other files 1.3 MB (210) and scripts 1.3 MB (61). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Rejuvenate-Final_1000x1000_d6073483-15f5-491f-884c-b8af65ac2 at 520 px wide, shown at 163 px. Resized copies would save about 13 KiB.

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

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

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

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

Contentinfo 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 contentinfo 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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

Your title is 79 characters, so Google will cut it off around 60: “Kvalitetskontrolleret CBD olie til gode priser → Raw Organics – Raw Organics DK”.

The homepage links to 77 pages on raworganics.dk and 8 external pages.

https://raworganics.dk/collections/frontpage is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://raworganics.dk/collections/cbd-cremer and https://raworganics.dk/collections/tilbud have no meta description, so Google writes the search snippet from whatever text it finds.

https://raworganics.dk/pages/om-os, https://raworganics.dk/pages/kontakt-os, https://raworganics.dk/blogs/kosttilskud and https://raworganics.dk/collections/frontpage use the same meta description. A description written for each page earns more clicks.

Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://raworganics.dk/collections/cbd-cremer/products/mirakel-salve-50ml, whose canonical is https://raworganics.dk/products/mirakel-salve-50ml. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://raworganics.dk/collections/tilbud, https://raworganics.dk/pages/om-os and https://raworganics.dk/pages/kontakt-os have no <h1> headline, so visitors and search engines get no clear main topic.

https://raworganics.dk/pages/kontakt-os 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://raworganics.dk/collections/tilbud and https://raworganics.dk/collections/kosttilskud/products/flower-power took over 3 s to send their HTML from our server.

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

6 errors were logged to the browser console while the page loaded, for example “Identifier 'roEfterLoad' has already been declared”.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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 18 cookies, 1 of them by other companies (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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.