svww.de website review

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

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

18 images could be 4.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

Your mobile performance score is 87 (desktop: 80). Pages that score under 90 lose visitors before the first paint.

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

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

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

1 third-party service load with your homepage (treibstoff.software), adding 59 KiB and 7 ms of main-thread time.

11 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (1.7 s).

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

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

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

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

Your homepage downloads 9.5 MB in 77 requests on a phone: images 8.9 MB (58), fonts 440 KiB (6) and scripts 63 KiB (5). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.9 MB together. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example NEU_BRITA_aktualisierte_Öffnungszeiten.png at 1,920 px wide, shown at 358 px. Resized copies would save about 1.6 MB.

8 images (4.4 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.

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

OrgaHinweise26_SliderMobil.jpg 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).

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

Interactive controls must not be nested: 27 elements on the page fail this check, rated serious by axe-core.

All page content should be contained by landmarks: 9 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 on the page fail this check, rated moderate by axe-core.

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

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

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

Your title is 66 characters, so Google will cut it off around 60: “SVWW - SV Wehen Wiesbaden - Aktuelle News, Spielpläne & Ergebnisse”.

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

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

The homepage links to 143 pages on svww.de and 29 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://svww.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.

https://svww.de/fans/auswaertsfahrten and https://svww.de/fans/gaeste-fans are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

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

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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 830 words of visible text.

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.

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