Website review, no card needed
harklinikken.dk website review
Visit site (opens in a new tab)Reviewed 17 November 202652 issues · 97 checks
This review found 52 issues worth fixing on harklinikken.dk, 20 of them high impact, across 97 checks. The most urgent: audioeye.com adds 2.1 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76C- #71,944 of 117,690 reviewed websitesbeats 34%
- #46,461 of 66,925 online storesbeats 26%
- #44,078 of 61,020 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.3 s |
| Nov 14, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 171 ms |
| Jun 6, 2026 | 175 ms |
| Jun 13, 2026 | 170 ms |
| Jun 20, 2026 | 170 ms |
| Jun 27, 2026 | 177 ms |
| Jul 4, 2026 | 184 ms |
| Jul 11, 2026 | 183 ms |
| Jul 18, 2026 | 176 ms |
| Jul 25, 2026 | 170 ms |
| Aug 1, 2026 | 154 ms |
| Aug 8, 2026 | 156 ms |
| Aug 15, 2026 | 163 ms |
| Aug 22, 2026 | 164 ms |
| Aug 29, 2026 | 171 ms |
| Sep 5, 2026 | 173 ms |
| Sep 12, 2026 | 172 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 170 ms |
| Oct 3, 2026 | 167 ms |
| Oct 10, 2026 | 163 ms |
| Oct 17, 2026 | 170 ms |
| Oct 24, 2026 | 170 ms |
| Oct 31, 2026 | 173 ms |
| Nov 7, 2026 | 179 ms |
| Nov 14, 2026 | 170 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
How it loaded on a phone
0.5 s
1.1 s
1.6 s
2.1 s
2.7 s
3.2 s
3.7 s
4.2 s
Speed
audioeye.com adds 2.1 s
2.1 saudioeye.com costs a phone 2.1 s of main-thread work and 887 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Improve image delivery
1.0 s · 1.0 MB7 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.
Main-thread work: 6.8 s
A phone's processor spends 6.8 s on main-thread work while loading, 4.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6,123 HTML elements
The page has 6,123 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 (audioeye.com, ZenDesk and rebuyengine.com and others), adding 2.9 MB and 3.0 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
150 ms · 746 KiB18 files are served with short cache lifetimes, so returning visitors download them again (746 KiB).
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
ZenDesk adds 194 ms
194 msZenDesk costs a phone 194 ms of main-thread work and 439 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.
rebuyengine.com adds 176 ms
176 msrebuyengine.com costs a phone 176 ms of main-thread work and 472 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.
Klaviyo adds 136 ms
136 msKlaviyo costs a phone 136 ms of main-thread work and 326 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.
Shopify adds 107 ms
107 msShopify costs a phone 107 ms of main-thread work and 391 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.
Reduce unused CSS
150 ms · 109 KiBAbout 109 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
150 ms · 95 KiBPolyfills for old browsers add 95 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 151 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
45 KiB45 KiB could be saved by minifying JavaScript.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 40 ms
40 msYour server sent the HTML in 40 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 32.6 s
32.6 sThe page becomes fully interactive after 32.6 s. Good is under 3.8 s.
Speed Index: 9.6 s
9.6 sVisually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.0 s
5.0 sYour largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user CLS: 0.20
0.20For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.
Total Blocking Time: 425 ms
425 msScripts block taps and scrolling for 425 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 171 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 161 ms
161 msReal visitors wait 161 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 408 ms
408 msReal visitors wait 408 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 6.2 MB in 333 requests
6.2 MBYour homepage downloads 6.2 MB in 333 requests on a phone: scripts 3.7 MB (208), images 1.4 MB (12) and other files 700 KiB (82). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Hybrid_4x5_4.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).
3 images in older formats
3 images (728 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
3 images far larger than shown
307 KiB3 images are downloaded at several times the size a phone draws them, for example case1.jpg at 1,413 px wide, shown at 358 px. Resized copies would save about 307 KiB.
About 1.8 g of CO₂ per visit
1.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.77 g of CO₂e: 212.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
15 buttons without a name
15 buttons have no accessible name, so screen readers announce just “button”.
ARIA attributes must conform to valid values (2 elements)
ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.
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 (13 elements)
Interactive controls must not be nested: 13 elements on the page fail this check, rated serious by axe-core.
<dt> and <dd> elements must be contained by a <dl> (6 elements)
<dt> and <dd> elements must be contained by a <dl>: 6 elements on the page fail this check, rated serious by axe-core.
ARIA input fields must have an accessible name (5 elements)
ARIA input fields must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (1 element)
<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 1 element on the page fails this check, rated serious by axe-core.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
3 links without text
3 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.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 68 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 17 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (78 characters)
Your title is 78 characters, so Google will cut it off around 60: “Hårklinikken DK | Din Hårspecialist i Hårpleje & Hårtab – Hårklinikken Denmark”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
94 internal links, 4 external
The homepage links to 94 pages on harklinikken.dk and 4 external pages.
4 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Hårklinikken er Danmarks førende hårspecialist med over 40 års erfaring. Køb hårplejeprodukter. Få behandling af hårtab…”.
Canonical URL set
The canonical URL is https://harklinikken.dk/.
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://harklinikken.dk/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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 (1,225 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://harklinikken.dk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://harklinikken.dk/collections/all is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
6 checks passed
Linked pages load
1 page of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 1 page that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 1 page that loaded have a <title>.
Best practices
13 small tap targets
13 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 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 1,105 words of copy
The homepage carries about 1,105 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book Konsultation”.
7 calls to action
The homepage has 7 calls to action, for example “Book Konsultation”, “Shop” and “Book en Konsultation”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (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.
16 cookies set on arrival
16Opening the homepage sets 16 cookies, 1 of them by other companies (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.
33 other companies contacted
Loading the homepage contacts 33 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 harklinikken.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Rebuy Personalization Engine · Regios Discounts · Klaviyo Email Marketing Sms · Eg Auto Add To Cart · rechargecdn.com · nice-team.net · rebuyengine.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
Hiring
- Hiring
- 3 open roles
- Teams
- Digital (2), Copenhagen Clinic (1)
- Job board
- bamboohr
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on harklinikken.dk, including 20 speed issues, 5 SEO issues and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.