Website review, no card needed

janeiredale.dk logo

janeiredale.dk website review

Visit site (opens in a new tab)Reviewed 17 November 202633 issues · 81 checks

This review found 33 issues worth fixing on janeiredale.dk, 11 of them high impact, across 81 checks. The most urgent: page weight: 56.7 MB in 314 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
1.3 s1.1 sMay 30Nov 141.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.2 s
Jun 13, 20261.3 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Nov 7, 20261.2 s
Nov 14, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
149 ms129 msOct 17Nov 14147 ms
Show as table
DateReal-visitor tap response (INP)
Oct 17, 2026131 ms
Oct 31, 2026139 ms
Nov 7, 2026146 ms
Nov 14, 2026147 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 janeiredale.dk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. janeiredale.dk at 0.6 s0.6 s
  2. janeiredale.dk at 1.2 s1.2 s
  3. janeiredale.dk at 1.8 s1.8 s
  4. janeiredale.dk at 2.5 s2.5 s
  5. janeiredale.dk at 3.1 s3.1 s
  6. janeiredale.dk at 3.7 s3.7 s
  7. janeiredale.dk at 4.3 s4.3 s
  8. janeiredale.dk at 4.9 s4.9 s

Speed

10 to fix57
  • Reduce unused JavaScript

    1.5 s · 893 KiB

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

  • Render-blocking requests

    1.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, vitals.app and karlachat.com and others), adding 2.0 MB and 1.1 s of main-thread time.

  • Mobile performance score: 57

    57/100

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

  • Use efficient cache lifetimes

    300 ms · 172 KiB

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

  • Google Tag Manager adds 376 ms

    376 ms

    Google Tag Manager costs a phone 376 ms of main-thread work and 524 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.

  • Main-thread work: 4.0 s

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

  • 2,503 HTML elements

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

  • Shopify adds 146 ms

    146 ms

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

  • karlachat.com adds 152 ms

    152 ms

    karlachat.com costs a phone 152 ms of main-thread work and 348 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.

  • Improve image delivery

    150 ms · 180 KiB

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

  • Font display

    200 ms

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

  • 9 long tasks on the main thread

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

  • Reduce unused CSS

    65 KiB

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

  • Legacy JavaScript

    29 KiB

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 10.2 s

    10.2 s

    Your largest element takes 10.2 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: 20.8 s

    20.8 s

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

  • Speed Index: 7.5 s

    7.5 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Total Blocking Time: 307 ms

    307 ms

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

  • Tap response (INP) held steady for real visitors

    +9%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

6 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user INP: 147 ms

    147 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

3 to fix53
  • Page weight: 56.7 MB in 314 requests

    56.7 MB

    Your homepage downloads 56.7 MB in 314 requests on a phone: media 52.1 MB (4), scripts 2.1 MB (116) and images 990 KiB (27). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Untitled_design_48.jpg 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 far larger than shown

    62 KiB

    1 image is downloaded at several times the size a phone draws it, for example Homepage-1900x931-Model.jpg at 745 px wide, shown at 166 px. Resized copies would save about 62 KiB.

  • About 16.1 g of CO₂ per visit

    16.06 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

6 to fixGoogle 8891
  • 10 tap targets too small

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

  • 5 text elements with low contrast

    5 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)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 4 images without alt text

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

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

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

  • 5 links without text

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

1 checks passed
  • 52 automated accessibility rules passed

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

SEO

1 to fixGoogle 9293
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Jane Iredale mineralmakeup - køb ren og cruelty-free mineralmakeup”.

  • 106 internal links, 5 external

    The homepage links to 106 pages on janeiredale.dk and 5 external pages.

7 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Jane Iredale er mineralmakeup med hudplejende ingredienser – makeup med omtanke, der beskytter, plejer og fremhæver din…”.

  • One H1 headline

    Your main headline reads: “Janeiredale.dk”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://janeiredale.dk/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 12 pages without a meta description

    https://janeiredale.dk/collections/alle-produkter, https://janeiredale.dk/collections/nyheder, https://janeiredale.dk/collections/alt-ansigtsmakeup, https://janeiredale.dk/collections/alt-ojenmakeup, https://janeiredale.dk/collections/alle-laebeprodukter and https://janeiredale.dk/collections/alt-til-kinder and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://janeiredale.dk/collections/alle-produkter, https://janeiredale.dk/collections/bestsellere, https://janeiredale.dk/collections/nyheder, https://janeiredale.dk/collections/alt-ansigtsmakeup, https://janeiredale.dk/collections/alt-ojenmakeup and https://janeiredale.dk/collections/alle-laebeprodukter and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 24 small tap targets

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

  • 3 JavaScript errors while loading

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

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.

  • Thin social proof

    Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 594 words of copy

    The homepage carries about 594 words of visible text.

3 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop efter hudtilstand”, “Shop makeup” and “Shop her”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 5 trackers load before any consent

    5

    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). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 11 cookies set on arrival

    11

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

  • 41 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 janeiredale.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 13 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Wishlist By Square · Xo Insert Code · Ecomposer Builder · Multifeeds · Klaviyo Email Marketing Sms · Sticky Add To Cart Bar · Koala Upsell Gift · Selleasy · Al Bulk Discount Manager · Countdown Timer · Essential Post Purchase Upsell · Essential Free Gifts · trustpilot.com

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
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on janeiredale.dk, including 15 speed issues, 1 SEO issue 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