Website review, no card needed
imerco.dk website review
Visit site (opens in a new tab)Reviewed 18 November 202633 issues · 82 checks
This review found 33 issues worth fixing on imerco.dk, 13 of them high impact, across 82 checks. The most urgent: 13,163 HTML elements. 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.0 s |
| Jun 6, 2026 | 4.2 s |
| Jun 13, 2026 | 4.5 s |
| Jun 20, 2026 | 4.8 s |
| Jun 27, 2026 | 4.7 s |
| Jul 4, 2026 | 4.6 s |
| Jul 11, 2026 | 4.3 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 3.8 s |
| Aug 22, 2026 | 3.8 s |
| Aug 29, 2026 | 3.7 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.8 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.2 s |
| Oct 31, 2026 | 3.2 s |
| Nov 7, 2026 | 3.3 s |
| Nov 14, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 700 ms |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 758 ms |
| Jul 18, 2026 | 473 ms |
| Jul 25, 2026 | 431 ms |
| Aug 1, 2026 | 430 ms |
| Aug 8, 2026 | 436 ms |
| Aug 15, 2026 | 439 ms |
| Aug 22, 2026 | 447 ms |
| Aug 29, 2026 | 450 ms |
| Sep 5, 2026 | 447 ms |
| Sep 12, 2026 | 447 ms |
| Sep 19, 2026 | 446 ms |
| Sep 26, 2026 | 445 ms |
| Oct 3, 2026 | 455 ms |
| Oct 10, 2026 | 462 ms |
| Oct 17, 2026 | 470 ms |
| Oct 24, 2026 | 482 ms |
| Oct 31, 2026 | 483 ms |
| Nov 7, 2026 | 477 ms |
| Nov 14, 2026 | 464 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
13,163 HTML elements
The page has 13,163 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
1.1 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.2 s
A phone's processor spends 9.2 s on main-thread work while loading, 4.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
938 KiBAbout 938 KiB of JavaScript is downloaded but never used on this page.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 906 ms. During a long task the page ignores taps.
Reduce unused CSS
300 ms · 36 KiBAbout 36 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (dialogintelligens.dk, cookieinformation.com and spiffcommerce.com and others), adding 136 KiB and 152 ms of main-thread time.
Improve image delivery
94 KiB3 images could be 94 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
78 KiB3 files are served with short cache lifetimes, so returning visitors download them again (78 KiB).
Legacy JavaScript
37 KiBPolyfills for old browsers add 37 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
13 KiB13 KiB JavaScript is shipped twice across bundles.
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: 276 ms
276 msYour server sent the HTML in 276 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.
Real-user INP: 757 ms
757 msReal visitors wait 757 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 2.2 s
2.2 sReal visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 3.0 s
3.0 sScripts block taps and scrolling for 3.0 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 19.2 s
19.2 sThe page becomes fully interactive after 19.2 s. Good is under 3.8 s.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BLACK WEEKS ER I GANG!”.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Tap response (INP) got 50% faster for real visitors
-50%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 700 ms to 464 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.055
0.055The layout barely moves while loading (CLS 0.055, good is under 0.1).
Images and page weight
Page weight: 2.8 MB in 92 requests
2.8 MBYour homepage downloads 2.8 MB in 92 requests on a phone: scripts 1.9 MB (41), fonts 371 KiB (9) and images 270 KiB (12). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.79 g of CO₂e: 94.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 849 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
718 internal links, 6 external
The homepage links to 718 pages on imerco.dk and 6 external pages.
7 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Hos Imerco finder du et stort udvalg af køkkenudstyr, borddækning, boligtilbehør og gaver til enhver anledning. Besøg i…”.
One H1 headline
Your main headline reads: “Forslag til dig”.
Title: 58 characters
Your title is a healthy 58 characters: “Gaver, køkkenudstyr, borddækning, boligindretning | Imerco”.
Canonical URL set
The canonical URL is https://www.imerco.dk/.
Structured data in place
Structured data found: MemberProgram, MemberProgramTier, MerchantReturnPolicy, OnlineStore and ShippingService.
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://www.imerco.dk/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.imerco.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.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,737 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.imerco.dk/favoritter is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://www.imerco.dk/favoritter and https://www.imerco.dk/julepris have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.imerco.dk/find-imerco, https://www.imerco.dk/tilbudsavis, https://www.imerco.dk/favoritter, https://www.imerco.dk/black-friday, https://www.imerco.dk/prismatch and https://www.imerco.dk/brands and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.imerco.dk/tilbud/medlemstilbud, https://www.imerco.dk/superpris and https://www.imerco.dk/julepris took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 198 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.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
30 of 37 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 14 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 962 words of copy
The homepage carries about 962 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop her”.
5 calls to action
The homepage has 5 calls to action, for example “Shop her”.
1 short form
A short form (1 field at most) is right on the homepage.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 imerco.dk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Hosting
- Cloudflare
Company
- Employees
- 842
- Founded
- 1928
- Headquarters
- Herlev Municipality
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on imerco.dk, including 18 speed issues, 1 SEO issue and 5 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.