Website review, no card needed

ingredien.dk logo

ingredien.dk website review

Visit site (opens in a new tab)Reviewed 9 November 202642 issues · 87 checks

This review found 42 issues worth fixing on ingredien.dk, 17 of them high impact, across 87 checks. The most urgent: page weight: 23.4 MB in 461 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.0 s1.7 sMay 23Nov 71.7 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.9 s
May 30, 20261.8 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.9 s
Jul 25, 20261.8 s
Aug 1, 20261.9 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Nov 7, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
242 ms154 msMay 23Nov 7231 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026164 ms
May 30, 2026174 ms
Jun 6, 2026185 ms
Jun 13, 2026187 ms
Jun 20, 2026188 ms
Jun 27, 2026189 ms
Jul 4, 2026205 ms
Jul 11, 2026219 ms
Jul 18, 2026219 ms
Jul 25, 2026217 ms
Aug 1, 2026215 ms
Aug 8, 2026204 ms
Aug 15, 2026202 ms
Aug 22, 2026197 ms
Aug 29, 2026194 ms
Sep 5, 2026200 ms
Sep 12, 2026205 ms
Sep 19, 2026216 ms
Sep 26, 2026218 ms
Oct 3, 2026212 ms
Oct 10, 2026211 ms
Oct 17, 2026212 ms
Oct 24, 2026217 ms
Oct 31, 2026232 ms
Nov 7, 2026231 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of ingredien.dk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ingredien.dk at 1.0 s1.0 s
  2. ingredien.dk at 2.0 s2.0 s
  3. ingredien.dk at 3.0 s3.0 s
  4. ingredien.dk at 4.0 s4.0 s
  5. ingredien.dk at 5.0 s5.0 s
  6. ingredien.dk at 6.0 s6.0 s
  7. ingredien.dk at 7.0 s7.0 s
  8. ingredien.dk at 8.0 s8.0 s

Speed

11 to fix68
  • Reduce unused JavaScript

    1.2 s · 504 KiB

    About 504 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Use efficient cache lifetimes

    1.1 s · 138 KiB

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

  • Main-thread work: 4.3 s

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

  • 3,075 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Klarna and Shopify and others), adding 16.0 MB and 290 ms of main-thread time.

  • Shopify adds 42 ms

    42 ms

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

  • Improve image delivery

    750 ms · 332 KiB

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

  • Mobile performance score: 68

    68/100

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

  • Render-blocking requests

    900 ms

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

  • Duplicated JavaScript

    450 ms · 11 KiB

    11 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 450 ms faster on a phone.

  • Klaviyo adds 106 ms

    106 ms

    Klaviyo costs a phone 106 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.

  • 6 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 12 KiB

    About 12 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.

  • Legacy JavaScript

    19 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

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

1 checks passed
  • Server response: 72 ms

    72 ms

    Your server sent the HTML in 72 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 12.7 s

    12.7 s

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

  • Time to Interactive: 18.3 s

    18.3 s

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

  • Real-user INP: 335 ms

    335 ms

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

  • Tap response (INP) got 37% slower for real visitors

    +37%

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

  • Speed Index: 5.3 s

    5.3 s

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

6 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user CLS: 0.06

    0.06

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

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Total Blocking Time: 149 ms

    149 ms

    Scripts block the page for only 149 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.07

    0.07

    The layout barely moves while loading (CLS 0.07, good is under 0.1).

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

Images and page weight

2 to fix69
  • Page weight: 23.4 MB in 461 requests

    23.4 MB

    Your homepage downloads 23.4 MB in 461 requests on a phone: media 19.3 MB (5), scripts 1.5 MB (103) and other files 1.5 MB (253). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    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 below the first screen load straight away

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

  • About 6.6 g of CO₂ per visit

    6.64 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

9 to fixGoogle 8388
  • Certain ARIA roles must contain particular children (1 element)

    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)

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

  • 3 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Summary elements must have discernible text (1 element)

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

  • 7 images without alt text

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

  • All page content should be contained by landmarks (30 elements)

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

  • 17 links without text

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

  • 1 form field without a label

    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.

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

1 checks passed
  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8575
  • No meta description

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

  • Title is short (13 characters)

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

  • 4 H1 headlines

    There are 4 <h1> headlines (“”, “NEW NEW NEW” and “Nulstil din adgangskode”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 226 internal links, 19 external

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

4 checks passed
  • Canonical URL set

    The canonical URL is https://ingredien.dk/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://ingredien.dk/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,125 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://ingredien.dk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix65
  • 2 linked pages are broken

    Your homepage links to https://ingredien.dk/collections/hair-styling and https://ingredien.dk/products/efalock-stylingo-hair-dryer, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 11 pages without a meta description

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

  • 13 pages without an H1

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

  • 4 pages with very little text

    https://ingredien.dk/pages/customer-care, https://ingredien.dk/collections/body-care, https://ingredien.dk/collections/saltvandsspray and https://ingredien.dk/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.

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 16 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No call to action on the first screen

    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 detected

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 929 words of copy

    The homepage carries about 929 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop” and “B2B Shop ↗”.

  • 4 short forms

    4 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 14 testimonial or review blocks and 18 trust badges.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    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.

  • 23 cookies set on arrival

    23

    Opening the homepage sets 23 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 44 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at ingredien.dk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Powerful Form Builder · Tolstoy · Avada Seo Suite · Sc Easy Redirects · Instafeed · Stape Remix · profitmetrics.io

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on ingredien.dk, including 18 speed issues, 4 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25