Website review, no card needed

autoscout24.de logo

autoscout24.de website review

Visit site (opens in a new tab)Reviewed 31 October 202633 issues · 87 checks

This review found 33 issues worth fixing on autoscout24.de, 6 of them high impact, across 87 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
1.6 s1.4 sMay 9Oct 241.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
237 ms209 msMay 9Oct 24234 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026219 ms
May 16, 2026213 ms
May 23, 2026212 ms
May 30, 2026213 ms
Jun 6, 2026213 ms
Jun 13, 2026213 ms
Jun 20, 2026213 ms
Jun 27, 2026216 ms
Jul 4, 2026222 ms
Jul 11, 2026228 ms
Jul 18, 2026229 ms
Jul 25, 2026222 ms
Aug 1, 2026217 ms
Aug 8, 2026213 ms
Aug 15, 2026215 ms
Aug 22, 2026217 ms
Aug 29, 2026219 ms
Sep 5, 2026220 ms
Sep 12, 2026222 ms
Sep 19, 2026225 ms
Sep 26, 2026225 ms
Oct 3, 2026225 ms
Oct 10, 2026224 ms
Oct 17, 2026228 ms
Oct 24, 2026234 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 autoscout24.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. autoscout24.de at 0.4 s0.4 s
  2. autoscout24.de at 0.8 s0.8 s
  3. autoscout24.de at 1.1 s1.1 s
  4. autoscout24.de at 1.5 s1.5 s
  5. autoscout24.de at 1.9 s1.9 s
  6. autoscout24.de at 2.3 s2.3 s
  7. autoscout24.de at 2.6 s2.6 s
  8. autoscout24.de at 3.0 s3.0 s

Speed

5 to fix93
  • 3,843 HTML elements

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

  • Render-blocking requests

    500 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

  • Reduce unused JavaScript

    150 ms · 301 KiB

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

  • Main-thread work: 2.3 s

    A phone's processor spends 2.3 s on main-thread work while loading, 909 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • autoscout24.com adds 0 ms

    0 ms

    autoscout24.com costs a phone 0 ms of main-thread work and 381 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.

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 8 KiB

    Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    140 ms · 18 KiB

    About 18 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.

  • 4 third-party services on the page

    4 third-party services load with your homepage (seroundprince.com, Amazon Web Services and autoscout24.com and others), adding 587 KiB and 97 ms of main-thread time.

  • Use efficient cache lifetimes

    86 KiB

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

  • Improve image delivery

    13 KiB

    3 images could be 13 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.

2 checks passed
  • Mobile performance score: 93

    93/100

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

  • Server response: 25 ms

    25 ms

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

Core Web Vitals

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

  • Time to Interactive: 10.1 s

    10.1 s

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

  • Real-user INP: 454 ms

    454 ms

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

  • Real-user TTFB: 868 ms

    868 ms

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

  • Speed Index: 5.4 s

    5.4 s

    Visually, the page fills in at 5.4 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.

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

6 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Total Blocking Time: 142 ms

    142 ms

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

  • 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 “Um Ihnen die bestmögliche Benutzererfahrung auf unseren Ang…”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix93
  • 5 images below the first screen load straight away

    5 images further down the page (301 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.56 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.56 g of CO₂e: 67.8 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: 2.0 MB in 108 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 108 requests on a phone: images 1,002 KiB (55), scripts 795 KiB (23) and HTML 179 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

7 to fixGoogle 9793
  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • All page content should be contained by landmarks (43 elements)

    All page content should be contained by landmarks: 43 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.

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

  • ARIA role should be appropriate for the element (18 elements)

    ARIA role should be appropriate for the element: 18 elements on the page fail this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (16 elements)

    Alternative text of images should not be repeated as text: 16 elements on the page fail this check, rated minor by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (17 elements).

2 checks passed
  • Every image has alt text

    All 73 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 10093
  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.autoscout24.de/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 204 internal links, 8 external

    The homepage links to 204 pages on autoscout24.de and 8 external pages.

6 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Neu- und Gebrauchtwagen sowie Motorräder, Wohnmobile und Nutzfahrzeuge finden Sie auf AutoScout24, dem europaweit größt…”.

  • One H1 headline

    Your main headline reads: “Finde Gebrauchtfahrzeuge und Neufahrzeuge”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Gebrauchtwagen und Neuwagen bei AutoScout24”.

  • Canonical URL set

    The canonical URL is https://www.autoscout24.de/.

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, 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://www.autoscout24.de/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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.autoscout24.de/favorites is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.autoscout24.de/favorites has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.autoscout24.de/favorites has 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 169 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Minified React error #421; visit https://reactjs.org/docs/error-decoder.html?invariant=421 for the full message or use …”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    42 of 47 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix50
  • 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.

  • Local business without LocalBusiness data

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 1,585 words of copy

    The homepage carries about 1,585 words of visible text.

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Meta Pixel, Microsoft Ads and The Trade Desk (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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 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.

  • 14 other companies contacted

    Loading the homepage contacts 14 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 autoscout24.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
CloudFront

Hiring

Hiring
37 open roles
Teams
Engineering (8), Sales (7), Data & Analytics (5), Product & Design (4)
Job board
greenhouse

Company

Employees
600
Founded
1998
Headquarters
Grünwald

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on autoscout24.de, including 11 speed issues, 2 SEO issues and 6 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