Website review, no card needed
lillepus.dk website review
Visit site (opens in a new tab)Reviewed 19 November 202628 issues · 67 checks
This review found 28 issues worth fixing on lillepus.dk, 7 of them high impact, across 67 checks. The most urgent: page weight: 19.2 MB in 45 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
82BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
500 ms · 16.9 MB24 images could be 16.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Mobile performance score: 88
88/100Your mobile performance score is 88. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
700 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Reduce unused JavaScript
150 ms · 42 KiBAbout 42 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
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 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 25 KiB and 2 ms of main-thread time.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 197 ms of it running JavaScript. That is comfortably low.
Server response: 28 ms
28 msYour server sent the HTML in 28 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 3.2 s
3.2 sYour largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Denne hjemmeside bruger cookies for at forbedre din oplevel…”. Most of its time is element render delay (2.5 s).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
4 checks passed
Time to Interactive: 3.2 s
3.2 sThe page is fully interactive after 3.2 s.
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
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 19.2 MB in 45 requests
19.2 MBYour homepage downloads 19.2 MB in 45 requests on a phone: images 19.0 MB (24), scripts 125 KiB (12) and fonts 22 KiB (1). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
image weighs 982 KiB. On a phone connection a single image that size takes seconds.
2 images in older formats
2 images (1.1 MB) 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.
2 images far larger than shown
482 KiB2 images are downloaded at several times the size a phone draws them, for example image at 1,440 px wide, shown at 390 px. Resized copies would save about 482 KiB.
About 5.4 g of CO₂ per visit
5.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.45 g of CO₂e: 653.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
61 buttons without a name
61 buttons have no accessible name, so screen readers announce just “button”.
43 tap targets too small
43 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (49 elements)
All page content should be contained by landmarks: 49 elements on the page fail this check, rated moderate by axe-core.
8 form fields without a label
8 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 3 images in the HTML carry an alt attribute.
30 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 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 structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://lillepus.dk/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at lillepus.dk/robots.txt, the first file search crawlers ask for.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
9 internal links, 3 external
The homepage links to 9 pages on lillepus.dk and 3 external pages.
3 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “Professionel vinduespolering i Randers og omegn. Trænger dine ruder til nus? Ring til Lillepus på 50 13 92 80 for et gr…”.
One H1 headline
Your main headline reads: “Lillepus Vinduespolering”.
Title: 49 characters
Your title is a healthy 49 characters: “Lillepus - Professionel Vinduespolering i Randers”.
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.
Some text only appears after JavaScript runs
48%The HTML your server sends has 142 of the 294 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://lillepus.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.
1 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Other pages
4 pages with very little text
https://lillepus.dk/ydelser, https://lillepus.dk/daekning, https://lillepus.dk/galleri and https://lillepus.dk/blog have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
7 checks passed
Linked pages load
All 9 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 9 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 9 pages that loaded have a <title>.
Best practices
57 small tap targets
57 of 66 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-m…”.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 11-field form
Your longest form asks for 11 fields (7 required). Every extra field lowers completion.
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 294 words of copy
The homepage carries about 294 words of visible text.
1 checks passed
Direct contact links
Visitors can reach you directly: 3 phone links and 2 email links.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 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 lillepus.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
- Tailwind CSS
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on lillepus.dk, including 5 speed issues, 5 SEO issues 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.