Website review, no card needed

camperboys.com logo

camperboys.com website review

Visit site (opens in a new tab)Reviewed 21 November 202621 issues · 75 checks

This review found 21 issues worth fixing on camperboys.com, 7 of them high impact, across 75 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
14.5 s222 msMay 30Nov 1412.8 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.1 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20261.9 s
Aug 1, 20262.1 s
Aug 8, 20262.3 s
Aug 15, 20262.6 s
Aug 22, 20263.5 s
Aug 29, 20264.5 s
Sep 5, 20266.1 s
Sep 12, 20269.7 s
Sep 19, 202612.9 s
Sep 26, 202611.8 s
Oct 3, 202610.0 s
Oct 10, 20268.8 s
Oct 17, 20269.0 s
Oct 24, 202611.0 s
Oct 31, 20269.9 s
Nov 7, 20269.8 s
Nov 14, 202612.8 s
Real-visitor tap response (INP)75th percentile, phones
229 ms109 msMay 30Nov 14137 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026210 ms
Jun 6, 2026212 ms
Jun 13, 2026210 ms
Jun 20, 2026211 ms
Jun 27, 2026210 ms
Jul 4, 2026212 ms
Jul 11, 2026213 ms
Jul 18, 2026215 ms
Jul 25, 2026214 ms
Aug 1, 2026212 ms
Aug 8, 2026210 ms
Aug 15, 2026199 ms
Aug 22, 2026184 ms
Aug 29, 2026154 ms
Sep 5, 2026134 ms
Sep 12, 2026128 ms
Sep 19, 2026136 ms
Sep 26, 2026134 ms
Oct 3, 2026123 ms
Oct 10, 2026128 ms
Oct 17, 2026128 ms
Oct 24, 2026129 ms
Oct 31, 2026141 ms
Nov 7, 2026137 ms
Nov 14, 2026137 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

Full-page screenshot of camperboys.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. camperboys.com at 1.4 s1.4 s
  2. camperboys.com at 2.7 s2.7 s
  3. camperboys.com at 4.1 s4.1 s
  4. camperboys.com at 5.5 s5.5 s
  5. camperboys.com at 6.9 s6.9 s
  6. camperboys.com at 8.2 s8.2 s
  7. camperboys.com at 9.6 s9.6 s
  8. camperboys.com at 11.0 s11.0 s

Speed

1 to fix95
  • 2,902 HTML elements

    The page has 2,902 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Render-blocking requests

    200 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 200 ms.

  • Reduce unused JavaScript

    183 KiB

    About 183 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    129 KiB

    5 files are served with short cache lifetimes, so returning visitors download them again (129 KiB).

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Tag Manager), adding 177 KiB and 78 ms of main-thread time.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 75 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    12 KiB

    About 12 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.

3 checks passed
  • Mobile performance score: 95

    95/100

    Your mobile performance score is 95. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 822 ms of it running JavaScript. That is comfortably low.

  • Server response: 363 ms

    363 ms

    Your server sent the HTML in 363 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix67
  • 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 LCP: 13.8 s

    13.8 s

    Real visitors wait 13.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 12.8 s

    12.8 s

    Real visitors see the first content after 12.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 12.7 s

    12.7 s

    Real visitors wait 12.7 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Time to Interactive: 8.5 s

    8.5 s

    The page becomes fully interactive after 8.5 s. Good is under 3.8 s.

  • Largest content (LCP) got 416% slower for real visitors

    +416%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.2 s to 12.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 4.6 s

    4.6 s

    Visually, the page fills in at 4.6 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 1.8 s

    1.8 s

    The first text or image appears after 1.8 s on a phone. Good is under 1.8 s.

6 checks passed
  • Real-user INP: 141 ms

    141 ms

    Real visitors wait 141 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 35% faster for real visitors

    -35%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 210 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest Contentful Paint: 1.8 s

    1.8 s

    Your largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Cookies are essential for the smooth and secure operation o…”.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 17 ms

    17 ms

    Scripts block the page for only 17 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    ueberwintern_in_portugal_5_davidferk_vwcaliforniabeach_surfe is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.3 g of CO₂ per visit

    0.25 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.25 g of CO₂e: 30.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Page weight: 921 KiB in 57 requests

    921 KiB

    Your homepage downloads 921 KiB in 57 requests on a phone: scripts 454 KiB (35), fonts 213 KiB (4) and HTML 195 KiB (1). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9696
  • 25 text elements with low contrast

    25 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 14 form fields without a label

    14 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 53 images in the HTML carry an alt attribute.

  • 31 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 32 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9290
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No XML sitemap

    No XML sitemap at https://vanever.com/sitemap.xml, so Google discovers your pages only by following links.

  • 19 links with vague text

    19 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 118 internal links, 14 external

    The homepage links to 118 pages on camperboys.com and 14 external pages.

6 checks passed
  • Meta description: 123 characters

    Your meta description is 123 characters: “Hire premium Vanever Camper ✅ no mileage limit, all European countries and all drivers included ✅ large selection of mo…”.

  • One H1 headline

    Your main headline reads: “Camper & motorhome rental”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Camper and motorhome rental - Vanever in Hamburg & Munich”.

  • Canonical URL set

    The canonical URL is https://vanever.com/en.

  • 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.

AI search readiness

1 to fix88
  • 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.

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 (2,247 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 1 page slow to respond

    https://vanever.com/en/insolvency took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 60 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    2 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 2 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 2 pages that loaded have a <title>.

Best practices

Google 96100
  • 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

    51 of 56 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a map 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.

  • 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 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 2,255 words of copy

    The homepage carries about 2,255 words of visible text.

4 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact & help”, “Book a camper now” and “Subscribe”.

  • 23 short forms

    23 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (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.

  • 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 other company contacted

    Loading the homepage contacts 1 host 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 camperboys.com, 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
Analytics
Google Tag Manager
Hosting
Hetzner

Company

Headquarters
Munich

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on camperboys.com, including 9 speed issues, 3 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25