Website review, no card needed

harklinikken.is logo

harklinikken.is website review

Visit site (opens in a new tab)Reviewed 8 November 202651 issues · 88 checks

This review found 51 issues worth fixing on harklinikken.is, 21 of them high impact, across 88 checks. The most urgent: audioeye.com adds 1.6 s. 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

Full-page screenshot of harklinikken.is (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

13 to fix39
  • audioeye.com adds 1.6 s

    1.6 s

    audioeye.com costs a phone 1.6 s of main-thread work and 301 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.

  • Mobile performance score: 39

    39/100

    Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 7.4 s

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

  • 5,474 HTML elements

    The page has 5,474 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.2 MB and 2.9 s of main-thread time.

  • Reduce unused JavaScript

    910 ms · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 910 ms faster on a phone.

  • Render-blocking requests

    750 ms

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

  • Use efficient cache lifetimes

    697 KiB

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

  • Legacy JavaScript

    300 ms · 95 KiB

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

  • ZenDesk adds 290 ms

    290 ms

    ZenDesk costs a phone 290 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 259 ms

    259 ms

    rebuyengine.com costs a phone 259 ms of main-thread work and 467 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 195 ms

    195 ms

    Klaviyo costs a phone 195 ms of main-thread work and 325 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 136 ms

    136 ms

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

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    109 KiB

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

  • 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

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

6 to fix33
  • Time to Interactive: 26.0 s

    26.0 s

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

  • Largest Contentful Paint: 6.3 s

    6.3 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Speed Index: 7.2 s

    7.2 s

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

  • Cumulative Layout Shift: 0.179

    0.179

    The layout shifts by 0.179 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 2 images without width and height

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

  • Not enough real-visitor data yet

    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.

1 checks passed
  • First Contentful Paint: 1.1 s

    1.1 s

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

Images and page weight

2 to fix64
  • Page weight: 4.2 MB in 261 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 261 requests on a phone: scripts 2.9 MB (168), other files 672 KiB (65) and fonts 236 KiB (5). 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).

  • About 1.2 g of CO₂ per visit

    1.18 g

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

14 to fixGoogle 7483
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

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

  • <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 commands must have an accessible name (4 elements)

    ARIA commands must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (4 elements)

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

  • ARIA input fields must have an accessible name (3 elements)

    ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

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

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

  • 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
  • 52 automated accessibility rules passed

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

SEO

5 to fixGoogle 8577
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (175 characters)

    Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.

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

  • 93 internal links, 6 external

    The homepage links to 93 pages on harklinikken.is and 6 external pages.

4 checks passed
  • Title: 63 characters

    Your title is a healthy 63 characters: “Hair Growth Products | Harklinikken IS – Hårklinikken á Íslandi”.

  • Canonical URL set

    The canonical URL is https://harklinikken.is/.

  • 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.is/sitemap.xml.

AI search readiness

1 to fix88
  • 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 (635 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix79
  • 1 linked page hidden from search

    https://harklinikken.is/collections/all is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://harklinikken.is/products/hair-supplement and https://harklinikken.is/pages/supplement all use the title “Hair Supplement – Hårklinikken á Íslandi”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://harklinikken.is/pages/extract and https://harklinikken.is/pages/supplement have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://harklinikken.is/products/the-extract-serum and https://harklinikken.is/pages/hxc-4-extract-serum use the same meta description. A description written for each page earns more clicks.

  • 7 pages slow to respond

    https://harklinikken.is/pages/boka-radgjof, https://harklinikken.is/pages/before-and-after, https://harklinikken.is/pages/clinics, https://harklinikken.is/collections/extract, https://harklinikken.is/collections/cleansing and https://harklinikken.is/collections/conditioner and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 8 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 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 537 words of copy

    The homepage carries about 537 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Log in / Register”.

  • 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

1 to fix
  • 4 trackers load before any consent

    4

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

  • 12 cookies set on arrival

    12

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

  • 27 other companies contacted

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

Apps your storefront loads

Klaviyo Email Marketing Sms · Eg Auto Add To Cart · Regios Discounts · Rebuy Personalization Engine · Judge Me Reviews · rechargecdn.com · 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 51 issues on harklinikken.is, including 19 speed issues, 5 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