Website review, no card needed
bobautowas.nl website review
Visit site (opens in a new tab)Reviewed 18 October 202620 issues · 73 checks
This review found 20 issues worth fixing on bobautowas.nl, 3 of them high impact, across 73 checks. The most urgent: fails Core Web Vitals for real visitors. 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
89BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 947 ms |
| May 2, 2026 | 927 ms |
| May 9, 2026 | 948 ms |
| May 16, 2026 | 978 ms |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 113 ms |
| May 2, 2026 | 113 ms |
| May 9, 2026 | 114 ms |
| May 16, 2026 | 114 ms |
| May 23, 2026 | 115 ms |
| May 30, 2026 | 115 ms |
| Jun 6, 2026 | 116 ms |
| Jun 13, 2026 | 117 ms |
| Jun 20, 2026 | 116 ms |
| Jun 27, 2026 | 118 ms |
| Jul 4, 2026 | 114 ms |
| Jul 11, 2026 | 113 ms |
| Jul 18, 2026 | 123 ms |
| Jul 25, 2026 | 122 ms |
| Aug 1, 2026 | 123 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 125 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 131 ms |
| Sep 5, 2026 | 130 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 131 ms |
| Sep 26, 2026 | 132 ms |
| Oct 3, 2026 | 135 ms |
| Oct 10, 2026 | 136 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
Render-blocking requests
500 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Reduce unused JavaScript
150 ms · 24 KiBAbout 24 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 131 ms. During a long task the page ignores taps.
Reduce unused CSS
22 KiBAbout 22 KiB of CSS is downloaded but never applied on this page.
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.
3 checks passed
Mobile performance score: 93
93/100Your mobile performance score is 93 (desktop: 40). That is in Google's “good” band (90 and up).
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 169 ms of it running JavaScript. That is comfortably low.
Server response: 174 ms
174 msYour server sent the HTML in 174 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.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 113 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.0 s
3.0 sYour largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ERVAAR HET GELUK VAN EEN SCHONE AUTO”. Most of its time is element render delay (1.5 s).
9 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 124 ms
124 msReal visitors wait 124 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.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Speed Index: 3.1 s
3.1 sVisually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.
Time to Interactive: 3.0 s
3.0 sThe page is fully interactive after 3.0 s.
Cumulative Layout Shift: 0.046
0.046The layout barely moves while loading (CLS 0.046, 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
About 0.2 g of CO₂ per visit
0.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.16 g of CO₂e: 18.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 570 KiB in 16 requests
570 KiBYour homepage downloads 570 KiB in 16 requests on a phone: fonts 437 KiB (8), HTML 56 KiB (1) and scripts 44 KiB (3). That is a lean page.
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
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Contentinfo landmark should not be contained in another landmark (3 elements)
Contentinfo landmark should not be contained in another landmark: 3 elements on the page fail this check, rated moderate by axe-core.
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.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 3 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“ervaar het geluk van een schone auto” and “Ervaar het geluk van een schone auto”). One clear main headline is easier for people and search engines.
63 internal links, 14 external
The homepage links to 63 pages on bobautowas.nl and 14 external pages.
7 checks passed
Meta description: 121 characters
Your meta description is 121 characters: “Bezoek één van onze vestigingen voor een grondige, veilige en milieuvriendelijke manier om de auto weer te laten strale…”.
Title: 46 characters
Your title is a healthy 46 characters: “Autowas beleving bij BOB Autowas - BOB Autowas”.
Canonical URL set
The canonical URL is https://bobautowas.nl/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, 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://bobautowas.nl/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing 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.
No llms.txt
There is no https://bobautowas.nl/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.
2 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 (291 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://bobautowas.nl/magazine has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://bobautowas.nl/wasclub has no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://bobautowas.nl/diensten, https://bobautowas.nl/wasclub, https://bobautowas.nl/inschrijving-nieuwsbrief and https://bobautowas.nl/magazine 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 42 found) and read each the way a search engine does.
5 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.
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
24 small tap targets
24 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 194 words
The homepage has only about 194 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact” and “neem contact op”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
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.
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 bobautowas.nl, 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
- Analytics
- Google Tag Manager
Company
- Headquarters
- Weesp
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on bobautowas.nl, including 6 speed issues, 1 SEO issue 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.