ingredien.se website review

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

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

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

8 third-party services load with your homepage (ingredien.dk, Klaviyo and Cookie-Script.com and others), adding 16.2 MB and 1.2 s of main-thread time.

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

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

ingredien.dk costs a phone 775 ms of main-thread work and 495 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.

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

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

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

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

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

Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

11 KiB JavaScript is shipped twice across bundles.

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.

Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Vi använder cookies för att anpassa innehåll, annonser och …”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 22.9 MB in 358 requests on a phone: media 19.3 MB (5), scripts 1.6 MB (102) and other files 954 KiB (150). Under 2 MB keeps phones on slow connections fast.

ingredien-logo-wh-2025-800px.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).

1 image further down the page (27 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

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

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

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 30 elements on the page fail 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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (10 elements).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 13 characters: “Ingredien A/S”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 4 <h1> headlines (“”, “NEW NEW NEW” and “Återställ ditt lösenord”). One clear main headline is easier for people and search engines.

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

The homepage links to 226 pages on ingredien.se and 19 external pages.

The HTML your server sends has 1,182 of the 2,369 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

Your homepage links to https://ingredien.se/products/efalock-stylingo-hair-dryer, which answers with an error. Visitors hit a dead end and search engines drop it.

https://ingredien.se/pages/customer-care, https://ingredien.se/collections/all, https://ingredien.se/collections/hair-styling, https://ingredien.se/collections/body-care, https://ingredien.se/collections/svanemaerket and https://ingredien.se/collections/okologisk and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://ingredien.se/pages/customer-care, https://ingredien.se/collections/all, https://ingredien.se/collections/hair-care, https://ingredien.se/collections/hair-styling, https://ingredien.se/collections/body-care and https://ingredien.se/collections/svanemaerket and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://ingredien.se/pages/customer-care, https://ingredien.se/collections/body-care, https://ingredien.se/collections/saltvandsspray and https://ingredien.se/products/ingredien-dry-shampoo 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 72 found) and read each the way a search engine does.

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

4 errors were 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.

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

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