Website review, no card needed
kalkknuser.dk website review
Visit site (opens in a new tab)Reviewed 5 November 202636 issues · 83 checks
This review found 36 issues worth fixing on kalkknuser.dk, 10 of them high impact, across 83 checks. The most urgent: render-blocking requests. 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
86B- #10,229 of 102,670 reviewed websitesbeats 86%
- #6,176 of 57,056 online storesbeats 85%
- #5,988 of 51,912 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 104 ms |
| May 23, 2026 | 115 ms |
| May 30, 2026 | 123 ms |
| Jun 6, 2026 | 122 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 143 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 125 ms |
| Jul 18, 2026 | 120 ms |
| Jul 25, 2026 | 119 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 119 ms |
| Aug 15, 2026 | 122 ms |
| Aug 22, 2026 | 125 ms |
| Aug 29, 2026 | 124 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 122 ms |
| Sep 26, 2026 | 122 ms |
| Oct 3, 2026 | 122 ms |
| Oct 10, 2026 | 125 ms |
| Oct 17, 2026 | 132 ms |
| Oct 24, 2026 | 133 ms |
| Oct 31, 2026 | 137 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
Speed
Render-blocking requests
1.1 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 80
80/100Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
474 KiBAbout 474 KiB of JavaScript is downloaded but never used on this page.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 394 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
356 KiB22 files are served with short cache lifetimes, so returning visitors download them again (356 KiB).
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 943 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 53 ms
53 msShopify costs a phone 53 ms of main-thread work and 368 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Trust Pilot and others), adding 920 KiB and 248 ms of main-thread time.
Reduce unused CSS
150 ms · 30 KiBAbout 30 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.
Improve image delivery
91 KiB5 images could be 91 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 40 ms
40 msYour server sent the HTML in 40 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 12.1 s
12.1 sThe page becomes fully interactive after 12.1 s. Good is under 3.8 s.
Tap response (INP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 104 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 3.7 s
3.7 sYour largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 372 ms
372 msScripts block taps and scrolling for 372 ms in total while the page loads. Good is under 200 ms.
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
10 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.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 129 ms
129 msReal visitors wait 129 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 426 ms
426 msReal visitors wait 426 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 3.1 s
3.1 sVisually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.02
0.02The layout barely moves while loading (CLS 0.02, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.7 MB in 204 requests
2.7 MBYour homepage downloads 2.7 MB in 204 requests on a phone: scripts 1.0 MB (62), other files 896 KiB (91) and images 456 KiB (32). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
3 KiB1 image is downloaded at several times the size a phone draws it, for example DK_1024x1024.webp at 1,023 px wide, shown at 330 px. Resized copies would save about 3 KiB.
1 image in older formats
1 image (53 KiB) is 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.
1 image below the first screen load straight away
1 image further down the page (81 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.75 g of CO₂e: 90.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
53 text elements with low contrast
53 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
16 images without alt text
16 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 (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 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.
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.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 8 failed. 7 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“<img src="//kalkknuser.dk/cdn/shop/files/Kalkknus…” and “”). One clear main headline is easier for people and search engines.
38 internal links, 5 external
The homepage links to 38 pages on kalkknuser.dk and 5 external pages.
6 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Har du problemer med kalk? Køb den originale Kalkknuser og slip for kalkgener med en kemikaliefri løsning, som er nem a…”.
Title: 63 characters
Your title is a healthy 63 characters: “Kalkknuser.dk | Slip for kalkgener med den originale Kalkknuser”.
Canonical URL set
The canonical URL is https://kalkknuser.dk/.
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://kalkknuser.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.
No llms.txt
There is no https://kalkknuser.dk/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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 (2,378 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://kalkknuser.dk/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://kalkknuser.dk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://kalkknuser.dk/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://kalkknuser.dk/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://kalkknuser.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 18 found) and read each the way a search engine does.
3 checks passed
Linked pages load
5 pages 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.
Titles are unique
Every page we checked has its own title.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) Error: YouTube player element ID required.”.
2 checks passed
Tap targets are thumb-sized
22 of 27 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 1,479 words of copy
The homepage carries about 1,479 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
2 checks passed
5 short forms
5 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 65 testimonial or review blocks, 2 customer or partner logos and 2 trust badges.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok 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.
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.
30 other companies contacted
Loading the homepage contacts 30 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 kalkknuser.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
Hulk Form Builder · Ez Terms And Conditions Checkbox · Announcement Bar Maker By Apphero · Countdown Timer · Forms · Stape Remix · trustpilot.com · powr.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
- jQuery
- 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 36 issues on kalkknuser.dk, including 12 speed issues, 2 SEO issues and 4 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.