Website review, no card needed
lampeagenten.dk website review
Visit site (opens in a new tab)Reviewed 16 November 202629 issues · 81 checks
This review found 29 issues worth fixing on lampeagenten.dk, 15 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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
83B- #26,057 of 112,654 reviewed websitesbeats 72%
- #17,376 of 64,753 online storesbeats 67%
- #16,866 of 59,198 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.7 s |
| Nov 14, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 129 ms |
| Jun 6, 2026 | 131 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 142 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 149 ms |
| Jul 18, 2026 | 147 ms |
| Jul 25, 2026 | 151 ms |
| Aug 1, 2026 | 151 ms |
| Aug 8, 2026 | 145 ms |
| Aug 15, 2026 | 146 ms |
| Aug 22, 2026 | 141 ms |
| Aug 29, 2026 | 139 ms |
| Sep 5, 2026 | 139 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 142 ms |
| Sep 26, 2026 | 141 ms |
| Oct 3, 2026 | 142 ms |
| Oct 10, 2026 | 143 ms |
| Oct 17, 2026 | 140 ms |
| Oct 24, 2026 | 141 ms |
| Oct 31, 2026 | 144 ms |
| Nov 7, 2026 | 142 ms |
| Nov 14, 2026 | 144 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
3.5 s
7.1 s
10.6 s
14.1 s
17.6 s
21.2 s
24.7 s
28.2 s
Speed
Reduce unused JavaScript
1.5 s · 267 KiBAbout 267 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Use efficient cache lifetimes
1.2 s · 250 KiB16 files are served with short cache lifetimes, so returning visitors download them again (250 KiB).
4,030 HTML elements
The page has 4,030 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, Google Tag Manager and Klaviyo and others), adding 798 KiB and 586 ms of main-thread time.
Render-blocking requests
600 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
300 ms · 13 KiB1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 179 ms
179 msGoogle Tag Manager costs a phone 179 ms of main-thread work and 314 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
260 ms · 34 KiBAbout 34 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 260 ms faster on a phone.
Legacy JavaScript
150 ms · 33 KiBPolyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
110 ms · 18 KiB18 KiB could be saved by minifying JavaScript.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 90 ms. During a long task the page ignores taps.
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
Largest Contentful Paint: 11.6 s
11.6 sYour largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Vi og vores samarbejdspartnere bruger cookies for at forbed…”.
Time to Interactive: 11.6 s
11.6 sThe page becomes fully interactive after 11.6 s. Good is under 3.8 s.
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 129 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 152 ms
152 msReal visitors wait 152 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 352 ms
352 msReal visitors wait 352 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 92 ms
92 msScripts block the page for only 92 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.8 MB in 359 requests
2.8 MBYour homepage downloads 2.8 MB in 359 requests on a phone: other files 1.3 MB (253), scripts 964 KiB (62) and images 299 KiB (29). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.80 g of CO₂e: 95.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
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 (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 8 failed. 3 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.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
513 internal links, 1 external
The homepage links to 513 pages on lampeagenten.dk and 1 external page.
6 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Køb designer lamper fra kendte mærker. 40 års erfaring med lamper. Altid skarpe priser og tilbyder prismatch. Gratis fr…”.
One H1 headline
Your main headline reads: “Lampeagenten”.
Title: 57 characters
Your title is a healthy 57 characters: “Designer lamper 2000+ lamper til skarpe priser online her”.
Canonical URL set
The canonical URL is https://lampeagenten.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://lampeagenten.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,853 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://lampeagenten.dk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 195 found) and read each the way a search engine does.
7 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 a meta description
All 15 pages 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.
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
6 broken images
6 images failed to load on a phone, for example https://lampeagenten.dk/.
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 404 ()”.
2 checks passed
Tap targets are thumb-sized
39 of 41 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 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 674 words of copy
The homepage carries about 674 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Shop efter kategori”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and Matomo.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
23 cookies set on arrival
23Opening the homepage sets 23 cookies, 2 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 lampeagenten.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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
klaviyo.com · profitmetrics.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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Matomo | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on lampeagenten.dk, including 13 speed issues, 2 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.