vfb.de website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.8 s faster on a phone.

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.8 s.

138 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

23 images could be 594 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

224 KiB could be saved by minifying JavaScript.

Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (consentmanager.net, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.1 MB and 800 ms of main-thread time.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 850 ms).

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

consentmanager.net costs a phone 333 ms of main-thread work and 147 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.

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

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

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

19 KiB could be saved by minifying CSS.

Polyfills for old browsers add 7 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 22.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies and similar technologies to technically oper…”.

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

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

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

Scripts block taps and scrolling for 582 ms in total while the page loads. Good is under 200 ms.

The layout shifts by 0.101 while loading, so content jumps under the reader's thumb. Good is under 0.1.

2 images have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 5.8 MB in 162 requests on a phone: images 3.9 MB (125), scripts 1.7 MB (14) and stylesheets 112 KiB (3). Under 2 MB keeps phones on slow connections fast.

40 images (2.7 MB) 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.

3 images are downloaded at several times the size a phone draws them, for example Jubel_LEV-Fans_00000_fr_1168x657.jpeg at 1,168 px wide, shown at 344 px. Resized copies would save about 102 KiB.

1 image further down the page (122 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

110 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 120 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

2 visible links have no text or label, so screen readers cannot say where they go.

Table header text should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

<td> elements in a large <table> do not have table headers. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

1 link has no real href, so search engines can't follow it.

The homepage links to 199 pages on vfb.de and 52 external pages.

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.

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

/ and https://www.vfb.de/de all use the title “VfB Stuttgart | Offizielle Webseite des VfB Stuttgart”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.vfb.de/de, https://www.vfb.de/de/1893/aktuell/vfb-magazine/magazine/stadion-aktuell, https://www.vfb.de/de/1893/aktuell/news-archiv, https://www.vfb.de/de/1893/profis/kader/saisonen/2026-2027/kader, https://www.vfb.de/de/1893/profis/kader/saisonen/2026-2027/listenansicht and https://www.vfb.de/de/1893/profis/kader/saisonen/2026-2027/statistik and 3 others use the same meta description. A description written for each page earns more clicks.

https://www.vfb.de/de, https://www.vfb.de/de/1893/aktuell/neues and https://www.vfb.de/de/1893/aktuell/news-archiv have no <h1> headline, so visitors and search engines get no clear main topic.

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

26 of 42 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “WebSocket connection to 'wss://aws.mycrocast.de:20022/mqtt' failed: Establishing a tunnel via proxy server failed.”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 images are served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 674 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 2 cookies (measured from a US location before any click).

Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.