Website review, no card needed

autostadt.de logo

autostadt.de website review

Visit site (opens in a new tab)Reviewed 30 October 202619 issues · 73 checks

This review found 19 issues worth fixing on autostadt.de, 5 of them high impact, across 73 checks. The most urgent: 1 linked page is broken. 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
929 ms618 msMay 9Oct 24654 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026758 ms
May 16, 2026790 ms
May 23, 2026808 ms
May 30, 2026794 ms
Jun 6, 2026756 ms
Jun 13, 2026736 ms
Jun 20, 2026720 ms
Jun 27, 2026739 ms
Jul 4, 2026770 ms
Jul 11, 2026820 ms
Jul 18, 2026843 ms
Jul 25, 2026849 ms
Aug 1, 2026867 ms
Aug 8, 2026893 ms
Aug 15, 2026882 ms
Aug 22, 2026867 ms
Aug 29, 2026842 ms
Sep 5, 2026744 ms
Sep 12, 2026718 ms
Sep 19, 2026721 ms
Sep 26, 2026686 ms
Oct 3, 2026683 ms
Oct 10, 2026677 ms
Oct 17, 2026659 ms
Oct 24, 2026654 ms
Real-visitor tap response (INP)75th percentile, phones
85 ms78 msMay 9Oct 2479 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202684 ms
May 16, 202684 ms
May 23, 202683 ms
May 30, 202683 ms
Jun 6, 202683 ms
Jun 13, 202682 ms
Jun 20, 202682 ms
Jun 27, 202681 ms
Jul 4, 202682 ms
Jul 11, 202683 ms
Jul 18, 202683 ms
Jul 25, 202683 ms
Aug 1, 202682 ms
Aug 8, 202682 ms
Aug 15, 202682 ms
Aug 22, 202681 ms
Aug 29, 202681 ms
Sep 5, 202680 ms
Sep 12, 202679 ms
Sep 19, 202679 ms
Sep 26, 202679 ms
Oct 3, 202679 ms
Oct 10, 202679 ms
Oct 17, 202679 ms
Oct 24, 202679 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 autostadt.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix94
  • Render-blocking requests

    950 ms

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

  • Reduce unused CSS

    310 ms · 55 KiB

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

  • Azure Web Services adds 0 ms

    0 ms

    Azure Web Services costs a phone 0 ms of main-thread work and 597 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.

  • Improve image delivery

    150 ms · 55 KiB

    2 images could be 55 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused JavaScript

    160 ms · 22 KiB

    About 22 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 160 ms faster on a phone.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Azure Web Services), adding 597 KiB and 0 ms of main-thread time.

  • 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: 94

    94/100

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

  • Main-thread work: 0.4 s

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

  • Server response: 11 ms

    11 ms

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

Core Web Vitals

1 to fix100
  • Largest Contentful Paint: 2.9 s

    2.9 s

    Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Tap response (INP) held steady for real visitors

    -6%

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

12 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.9 s

    0.9 s

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

  • Real-user INP: 80 ms

    80 ms

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

  • 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: 0.8 s

    0.8 s

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

  • Real-user TTFB: 458 ms

    458 ms

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

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • Speed Index: 2.9 s

    2.9 s

    Visually, the page fills in at 2.9 s (Speed Index), inside the 3.4 s “good” threshold.

  • Time to Interactive: 2.9 s

    2.9 s

    The page is fully interactive after 2.9 s.

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

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

    symbolbild-rendering-sommer-festival-buehne-close-ki.webp 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).

  • 5 images in older formats

    5 images (224 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.

  • About 0.2 g of CO₂ per visit

    0.23 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.23 g of CO₂e: 27.2 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: 820 KiB in 22 requests

    820 KiB

    Your homepage downloads 820 KiB in 22 requests on a phone: images 597 KiB (12), scripts 72 KiB (3) and fonts 69 KiB (3). 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

6 to fixGoogle 9192
  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

  • ARIA role should be appropriate for the element (1 element)

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

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

1 to fixGoogle 9296
  • No structured data

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

  • No X (Twitter) card tag

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

  • 213 internal links, 10 external

    The homepage links to 213 pages on autostadt.de and 10 external pages.

7 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Willkommen in der Welt der Mobilität. Alles zu Neuwagenabholung, Gastronomie, Events, Veranstaltungen, Elektromobilität…”.

  • One H1 headline

    Your main headline reads: “Winterzauber”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “Autostadt in Wolfsburg - Autostadt”.

  • Canonical URL set

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

  • 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://autostadt.de/sitemap.xml.

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.

  • No llms.txt

    There is no https://www.autostadt.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.

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

Other pages

1 to fix75
  • 1 linked page is broken

    Your homepage links to https://www.autostadt.de/c/portal/update_language, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 15 internal pages checked

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

6 checks passed
  • Canonical URLs point to themselves

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

  • Every page has a meta description

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

Best practices

2 to fixGoogle 10087
  • 6 small tap targets

    6 of 24 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 “Failed to load resource: the server responded with a status of 503 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 analytics detected

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

  • 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 416 words of copy

    The homepage carries about 416 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “moment! Marken und Erlebnis-Shop”, “Ticket Shop” and “PDF-Download”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Direct contact links

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

Privacy and tracking

  • 4 cookies set on arrival

    4

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

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

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

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
Azure

Company

Founded
2000

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on autostadt.de, including 4 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

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