Website review, no card needed
lisen.dk website review
Visit site (opens in a new tab)Reviewed 7 November 202636 issues · 87 checks
This review found 36 issues worth fixing on lisen.dk, 13 of them high impact, across 87 checks. The most urgent: fails Core Web Vitals for real visitors. 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
77C- #69,532 of 125,476 reviewed websitesbeats 39%
- #44,793 of 70,188 online storesbeats 31%
- #42,573 of 63,771 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.7 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.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 115 ms |
| May 23, 2026 | 114 ms |
| May 30, 2026 | 114 ms |
| Jun 6, 2026 | 114 ms |
| Jun 13, 2026 | 116 ms |
| Jun 20, 2026 | 118 ms |
| Jun 27, 2026 | 119 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 120 ms |
| Jul 25, 2026 | 121 ms |
| Aug 1, 2026 | 120 ms |
| Aug 8, 2026 | 122 ms |
| Aug 15, 2026 | 123 ms |
| Aug 22, 2026 | 124 ms |
| Aug 29, 2026 | 123 ms |
| Sep 5, 2026 | 122 ms |
| Sep 12, 2026 | 122 ms |
| Sep 19, 2026 | 123 ms |
| Sep 26, 2026 | 125 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 136 ms |
| Oct 17, 2026 | 138 ms |
| Oct 24, 2026 | 138 ms |
| Oct 31, 2026 | 136 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
Main-thread work: 4.8 s
A phone's processor spends 4.8 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
1.5 MB36 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms16 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Clarity and Klaviyo and others), adding 796 KiB and 760 ms of main-thread time.
Reduce unused JavaScript
420 ms · 363 KiBAbout 363 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 420 ms faster on a phone.
2,373 HTML elements
The page has 2,373 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 121 KiB18 files are served with short cache lifetimes, so returning visitors download them again (121 KiB).
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 219 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
120 ms · 23 KiBAbout 23 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 120 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Duplicated JavaScript
7 KiB7 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.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 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: 16.9 s
16.9 sThe page becomes fully interactive after 16.9 s. Good is under 3.8 s.
Largest Contentful Paint: 5.3 s
5.3 sYour largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MATERIALE_Hope”.
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 115 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
78 images without width and height
78 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 453 ms
453 msScripts block taps and scrolling for 453 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 183 ms
183 msReal visitors wait 183 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 335 ms
335 msReal visitors wait 335 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, 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: 8.3 MB in 373 requests
8.3 MBYour homepage downloads 8.3 MB in 373 requests on a phone: media 3.2 MB (2), images 2.5 MB (62) and scripts 1.4 MB (97). Under 2 MB keeps phones on slow connections fast.
5 images far larger than shown
186 KiB5 images are downloaded at several times the size a phone draws them, for example r132r13geew3t1t31t31_45d3e58c-4dee-494a-a20b-290be48aeccf_60 at 600 px wide, shown at 174 px. Resized copies would save about 186 KiB.
2 images in older formats
2 images (138 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.
1 image below the first screen load straight away
1 image further down the page (24 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.3 g of CO₂ per visit
2.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.34 g of CO₂e: 280.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
77 tap targets too small
77 tap targets are too small or too close together to hit reliably with a finger.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 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 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.
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Lisen.dk | Modetøj, sko & accessories med danske og nordiske brands”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
473 internal links, 5 external
The homepage links to 473 pages on lisen.dk and 5 external pages.
6 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Stort & eksklusivt udvalg af modetøj til kvinder fra danske og nordiske brands; Mos Mosh, Co'couture, Gustav, Marta du …”.
One H1 headline
Your main headline reads: “Lisen.dk”.
Canonical URL set
The canonical URL is https://lisen.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://lisen.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.
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 (1,242 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://lisen.dk/collections/spar20 and https://lisen.dk/collections/sko-stovler have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages slow to respond
https://lisen.dk/collections/all, https://lisen.dk/collections/sko-stovler, https://lisen.dk/collections/ballerina-sko and https://lisen.dk/collections/stiletter took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 161 found) and read each the way a search engine does.
6 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.
Every page has an H1
Each page we checked has a main headline.
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 broken images
2 images failed to load on a phone, for example https://lisen.dk/.
61 small tap targets
61 of 169 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Requests the notification permission on page load
Requests the notification permission on page load.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 922 words of copy
The homepage carries about 922 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOVA HER” and “SHOP HER”.
7 calls to action
The homepage has 7 calls to action, for example “SHOP”, “Shop Nova her” and “SHOP JEANS HER”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.
27 cookies set on arrival
27Opening the homepage sets 27 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.
45 other companies contacted
Loading the homepage contacts 45 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 lisen.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · Stape Remix · cloudfront.net · snapchat.com · wheelio-app.com · sprii.io · shopthelook.app · pushowl.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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics
- 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 lisen.dk, including 15 speed issues, 2 SEO issues and 1 conversion gap. 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.