Website review, no card needed
looad.dk website review
Visit site (opens in a new tab)Reviewed 17 November 202631 issues · 78 checks
This review found 31 issues worth fixing on looad.dk, 9 of them high impact, across 78 checks. The most urgent: main-thread work: 4.3 s. 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
82B- #33,154 of 117,615 reviewed websitesbeats 66%
- #22,156 of 66,923 online storesbeats 60%
- #21,424 of 61,018 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 976 ms |
| Jun 6, 2026 | 964 ms |
| Jun 13, 2026 | 961 ms |
| Jun 20, 2026 | 969 ms |
| Jun 27, 2026 | 981 ms |
| Jul 4, 2026 | 961 ms |
| Jul 11, 2026 | 976 ms |
| Jul 18, 2026 | 986 ms |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 998 ms |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 993 ms |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 990 ms |
| Oct 10, 2026 | 965 ms |
| Oct 17, 2026 | 960 ms |
| Oct 24, 2026 | 961 ms |
| Oct 31, 2026 | 968 ms |
| Nov 7, 2026 | 955 ms |
| Nov 14, 2026 | 931 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 103 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 104 ms |
| Jun 20, 2026 | 106 ms |
| Jun 27, 2026 | 113 ms |
| Jul 4, 2026 | 118 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 120 ms |
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 120 ms |
| Aug 22, 2026 | 121 ms |
| Aug 29, 2026 | 126 ms |
| Sep 5, 2026 | 126 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 131 ms |
| Sep 26, 2026 | 134 ms |
| Oct 3, 2026 | 136 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 139 ms |
| Oct 24, 2026 | 142 ms |
| Oct 31, 2026 | 145 ms |
| Nov 7, 2026 | 145 ms |
| Nov 14, 2026 | 138 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.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
750 ms · 793 KiBAbout 793 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Use efficient cache lifetimes
600 ms · 565 KiB21 files are served with short cache lifetimes, so returning visitors download them again (565 KiB).
Mobile performance score: 64
64/100Your mobile performance score is 64. 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 (Google Tag Manager, Clarity and Cookiebot and others), adding 1.4 MB and 642 ms of main-thread time.
Reduce unused CSS
300 ms · 66 KiBAbout 66 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.
Render-blocking requests
300 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.
Google Tag Manager adds 218 ms
218 msGoogle Tag Manager costs a phone 218 ms of main-thread work and 303 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.
1,803 HTML elements
The page has 1,803 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 59 ms
59 msShopify costs a phone 59 ms of main-thread work and 504 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 130 ms. During a long task the page ignores taps.
Improve image delivery
101 KiB4 images could be 101 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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 JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 24 ms
24 msYour server sent the HTML in 24 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 17.8 s
17.8 sThe page becomes fully interactive after 17.8 s. Good is under 3.8 s.
Largest Contentful Paint: 6.8 s
6.8 sYour largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “mobil_hovedside_900x1200_hero.jpg”.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 37% slower for real visitors
+37%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 103 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 296 ms
296 msScripts block taps and scrolling for 296 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 125 ms
125 msReal visitors wait 125 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 311 ms
311 msReal visitors wait 311 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.6 MB in 262 requests
3.6 MBYour homepage downloads 3.6 MB in 262 requests on a phone: scripts 1.8 MB (72), other files 1.1 MB (156) and images 429 KiB (15). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
1.02 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.02 g of CO₂e: 122.2 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
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.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (26 characters)
Your title is only 26 characters: “Looad - Tid til at lade op”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“” and “Lad bilen op ude.”). One clear main headline is easier for people and search engines.
65 internal links, 10 external
The homepage links to 65 pages on looad.dk and 10 external pages.
6 checks passed
Meta description: 116 characters
Your meta description is 116 characters: “Bestil en skræddersyet ladeløsning, som passer til dit behov. Få en komplet ladeløsning med eller uden installation.”.
Canonical URL set
The canonical URL is https://looad.dk/.
Structured data in place
Structured data found: Organization and WebSite.
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://looad.dk/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (671 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://looad.dk/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
/ and https://looad.dk/da-erhverv all use the title “Looad - Tid til at lade op”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://looad.dk/pages/vaelg-din-ladelosning has no meta description, so Google writes the search snippet from whatever text it finds.
12 pages share a meta description
https://looad.dk/da-erhverv, https://looad.dk/pages/mit-looad, https://looad.dk/pages/prisberegner, https://looad.dk/pages/serviceaftale, https://looad.dk/pages/elaftale and https://looad.dk/pages/produktionsaftale and 6 others use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://looad.dk/da-erhverv, https://looad.dk/pages/mit-looad, https://looad.dk/pages/vaelg-din-ladelosning, https://looad.dk/pages/prisberegner, https://looad.dk/pages/serviceaftale and https://looad.dk/pages/elaftale and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 24 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.
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
5 small tap targets
5 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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 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 534 words of copy
The homepage carries about 534 words of visible text.
3 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
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 Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
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).
26 other companies contacted
Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 looad.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Microsoft Clarity · Powerful Form Builder · Avada Order Limit · Stape Remix · Forms · elfsight.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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Analytics | 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 31 issues on looad.dk, including 15 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.