Website review, no card needed

kandii.dk logo

kandii.dk website review

Visit site (opens in a new tab)Reviewed 5 November 202626 issues · 81 checks

This review found 26 issues worth fixing on kandii.dk, 10 of them high impact, across 81 checks. The most urgent: form elements must have labels (1 element). 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
872 ms786 msMay 16Oct 31807 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026847 ms
May 23, 2026834 ms
May 30, 2026823 ms
Jun 6, 2026839 ms
Jun 13, 2026841 ms
Jun 20, 2026836 ms
Jun 27, 2026845 ms
Jul 4, 2026831 ms
Jul 11, 2026824 ms
Jul 18, 2026819 ms
Jul 25, 2026821 ms
Aug 1, 2026830 ms
Aug 8, 2026846 ms
Aug 15, 2026862 ms
Aug 22, 2026861 ms
Aug 29, 2026859 ms
Sep 5, 2026850 ms
Sep 12, 2026829 ms
Sep 19, 2026821 ms
Sep 26, 2026802 ms
Oct 3, 2026801 ms
Oct 10, 2026796 ms
Oct 17, 2026818 ms
Oct 24, 2026831 ms
Oct 31, 2026807 ms
Real-visitor tap response (INP)75th percentile, phones
122 ms102 msMay 16Oct 31113 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026104 ms
May 23, 2026104 ms
May 30, 2026104 ms
Jun 6, 2026111 ms
Jun 13, 2026111 ms
Jun 20, 2026111 ms
Jun 27, 2026113 ms
Jul 4, 2026112 ms
Jul 11, 2026113 ms
Jul 18, 2026114 ms
Jul 25, 2026114 ms
Aug 1, 2026120 ms
Aug 8, 2026120 ms
Aug 15, 2026120 ms
Aug 22, 2026116 ms
Aug 29, 2026112 ms
Sep 5, 2026112 ms
Sep 12, 2026110 ms
Sep 19, 2026110 ms
Sep 26, 2026104 ms
Oct 3, 2026104 ms
Oct 10, 2026104 ms
Oct 17, 2026112 ms
Oct 24, 2026114 ms
Oct 31, 2026113 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 kandii.dk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kandii.dk at 0.4 s0.4 s
  2. kandii.dk at 0.8 s0.8 s
  3. kandii.dk at 1.1 s1.1 s
  4. kandii.dk at 1.5 s1.5 s
  5. kandii.dk at 1.9 s1.9 s
  6. kandii.dk at 2.3 s2.3 s
  7. kandii.dk at 2.6 s2.6 s
  8. kandii.dk at 3.0 s3.0 s

Speed

4 to fix86
  • Mobile performance score: 86

    86/100

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

  • Render-blocking requests

    750 ms

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

  • Shopify adds 225 ms

    225 ms

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

  • 2,197 HTML elements

    The page has 2,197 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 (Shopify, Klaviyo and conversionbear.com and others), adding 878 KiB and 343 ms of main-thread time.

  • Reduce unused JavaScript

    160 KiB

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

  • 2 long tasks on the main thread

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

  • Improve image delivery

    63 KiB

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

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    37 KiB

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

  • Minify JavaScript

    34 KiB

    34 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    27 KiB

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

  • Duplicated JavaScript

    12 KiB

    12 KiB JavaScript is shipped twice across bundles.

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

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 660 ms of it running JavaScript. That is comfortably low.

  • Server response: 9 ms

    9 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 9.5 s

    9.5 s

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

  • Largest Contentful Paint: 4.1 s

    4.1 s

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

  • Speed Index: 3.4 s

    3.4 s

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

  • Tap response (INP) held steady for real visitors

    +9%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

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

    1.3 s

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

  • Real-user INP: 176 ms

    176 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 431 ms

    431 ms

    Real visitors wait 431 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

  • Cumulative Layout Shift: 0.015

    0.015

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

  • Total Blocking Time: 30 ms

    30 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.5 MB in 301 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 301 requests on a phone: other files 906 KiB (136), scripts 849 KiB (91) and images 410 KiB (25). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

    2 images further down the page (70 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.7 g of CO₂ per visit

    0.72 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.72 g of CO₂e: 86.2 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

6 to fixGoogle 8992
  • Form elements must have labels (1 element)

    Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

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

  • Alternative text of images should not be repeated as text (3 elements)

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

2 checks passed
  • Every image has alt text

    All 39 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

4 to fixGoogle 9275
  • No meta description

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

  • Title is short (6 characters)

    Your title is only 6 characters: “Kandii”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • One H1 headline

    Your <h1> is empty.

  • 178 internal links, 15 external

    The homepage links to 178 pages on kandii.dk and 15 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization, Product 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://kandii.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 (943 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://kandii.dk/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://kandii.dk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 13 pages without a meta description

    https://kandii.dk/collections/all, https://kandii.dk/customer_authentication/redirect, https://kandii.dk/policies/shipping-policy, https://kandii.dk/collections/xtreme, https://kandii.dk/collections/low-chemistry and https://kandii.dk/collections/acryl-gel-tilbehor and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://kandii.dk/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://kandii.dk/customer_authentication/redirect took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

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

Best practices

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    28 of 29 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 468 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop the look” and “Shop Soak-off Polish”.

  • 23 short forms

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 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.

  • 32 other companies contacted

    Loading the homepage contacts 32 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 kandii.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 12 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Rimix Product Badges · Selecty · Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · Aftersell · Ultimate Trust Badge · Restockrocket · Biscuits Bundles · Wishlist Automations · Free Contact Form · conversionbear.com · ablestar.app

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

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 26 issues on kandii.dk, including 7 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