Website review, no card needed
applusbilsyn.dk website review
Visit site (opens in a new tab)Reviewed 24 October 202637 issues · 89 checks
This review found 37 issues worth fixing on applusbilsyn.dk, 17 of them high impact, across 89 checks. The most urgent: render-blocking 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
74C- #82,331 of 117,121 reviewed websitesbeats 26%
- #52,377 of 66,867 online storesbeats 18%
- #1,469 of 2,688 WooCommerce storesbeats 39%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.6 s |
| May 9, 2026 | 5.7 s |
| May 16, 2026 | 5.4 s |
| May 23, 2026 | 5.0 s |
| May 30, 2026 | 4.6 s |
| Jun 6, 2026 | 4.1 s |
| Jun 13, 2026 | 4.0 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 4.2 s |
| Jul 25, 2026 | 4.4 s |
| Aug 1, 2026 | 4.5 s |
| Aug 8, 2026 | 4.4 s |
| Aug 15, 2026 | 4.4 s |
| Aug 22, 2026 | 4.4 s |
| Aug 29, 2026 | 4.4 s |
| Sep 5, 2026 | 4.2 s |
| Sep 12, 2026 | 4.0 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 3.9 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.6 s |
| Oct 17, 2026 | 4.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 152 ms |
| May 9, 2026 | 151 ms |
| May 16, 2026 | 150 ms |
| May 23, 2026 | 151 ms |
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 155 ms |
| Jun 13, 2026 | 156 ms |
| Jun 20, 2026 | 158 ms |
| Jun 27, 2026 | 156 ms |
| Jul 4, 2026 | 155 ms |
| Jul 11, 2026 | 154 ms |
| Jul 18, 2026 | 153 ms |
| Jul 25, 2026 | 153 ms |
| Aug 1, 2026 | 153 ms |
| Aug 8, 2026 | 153 ms |
| Aug 15, 2026 | 153 ms |
| Aug 22, 2026 | 154 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 156 ms |
| Sep 12, 2026 | 157 ms |
| Sep 19, 2026 | 160 ms |
| Sep 26, 2026 | 161 ms |
| Oct 3, 2026 | 161 ms |
| Oct 10, 2026 | 162 ms |
| Oct 17, 2026 | 162 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
1.4 s
2.8 s
4.2 s
5.6 s
7.0 s
8.4 s
9.8 s
11.2 s
Speed
Render-blocking requests
1.9 s46 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Reduce initial server response time
1.5 sReduce initial server response time. Google estimates savings of 1.5 s on a phone.
Document request latency
1.5 sThe HTML itself could arrive about 1.5 s sooner: redirects, a slow server response or missing compression delay everything after it.
Mobile performance score: 47
47/100Your mobile performance score is 47 (desktop: 84). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.9 s
A phone's processor spends 6.9 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,089 HTML elements
The page has 3,089 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, chatbot.com and Clarity and others), adding 1.2 MB and 1.6 s of main-thread time.
Use efficient cache lifetimes
650 ms · 661 KiB122 files are served with short cache lifetimes, so returning visitors download them again (661 KiB).
Google Tag Manager adds 982 ms
982 msGoogle Tag Manager costs a phone 982 ms of main-thread work and 533 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 483 ms. During a long task the page ignores taps.
Reduce unused JavaScript
423 KiBAbout 423 KiB of JavaScript is downloaded but never used on this page.
Server response: 1.6 s
1.6 sYour server takes 1.6 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
openstreetmap.org adds 0 ms
0 msopenstreetmap.org costs a phone 0 ms of main-thread work and 377 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.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Legacy JavaScript
150 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
140 KiB6 images could be 140 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
13 KiBAbout 13 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 84 but mobile only 47. A gap that wide usually means heavy scripts and images that hit phones hardest.
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 CSS
3 KiB3 KiB could be saved by minifying CSS.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
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 FCP: 3.8 s
3.8 sReal visitors see the first content after 3.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.9 s
2.9 sReal visitors wait 2.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 14.6 s
14.6 sVisually, the page fills in at 14.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 14.6 s
14.6 sThe page becomes fully interactive after 14.6 s. Good is under 3.8 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.9 s
3.9 sReal visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 3.8 s
3.8 sYour largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Book bilsyn tæt på dig - nemt og hurtigt”. Most of its time is element render delay (4.3 s).
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 152 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 144 ms
144 msReal visitors wait 144 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.
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.6 s to 4.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
4 images in older formats
4 images (154 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.
6 images below the first screen load straight away
6 images further down the page (206 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.53 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.53 g of CO₂e: 64.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.9 MB in 162 requests
1.9 MBYour homepage downloads 1.9 MB in 162 requests on a phone: scripts 1.1 MB (62), images 490 KiB (32) and fonts 133 KiB (8). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Form elements should have a visible label (3 elements)
Form elements should have a visible label: 3 elements on the page fail this check, rated serious 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 7 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: “Velkommen - Applus+ Bilsyn”. Between 30 and 65 characters leaves room to say what you do and for whom.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
106 internal links, 15 external
The homepage links to 106 pages on applusbilsyn.dk and 15 external pages.
7 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Skal din bil til syn? Hos Applus+ Bilsyn får du bilsyn og biltest i over 130 synshaller i Danmark. Find din nærmeste sy…”.
One H1 headline
Your main headline reads: “Book bilsyn tæt på dig- nemt og hurtigt”.
Canonical URL set
The canonical URL is https://applusbilsyn.dk/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage 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://applusbilsyn.dk/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (700 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://applusbilsyn.dk/llms.txt (62 KiB, 221 links), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://applusbilsyn.dk/find-synshal has no <h1> headline, so visitors and search engines get no clear main topic.
6 pages slow to respond
https://applusbilsyn.dk/find-synshal, https://applusbilsyn.dk/bilsyn/kom-godt-igennem-synet, https://applusbilsyn.dk/bilsyn/syn-af-elbil, https://applusbilsyn.dk/bilsyn/bilsynspriser, https://applusbilsyn.dk/attester and https://applusbilsyn.dk/om-applus-bilsyn/efteruddannelse-af-synsmedarbejdere took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 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.
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.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
24 of 29 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 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 683 words of copy
The homepage carries about 683 words of visible text.
2 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Book tid”, “Shop” and “Shop Videre”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
19 other companies contacted
Loading the homepage contacts 19 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 applusbilsyn.dk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager
Company
- Employees
- 250
- Founded
- 1996
- Headquarters
- Madrid
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on applusbilsyn.dk, including 23 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.