tsg-hoffenheim.de website review

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

About 375 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

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

Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.

8 images could be 576 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

5 third-party services load with your homepage (Google Tag Manager, eye-able.com and Usercentrics CMP and others), adding 1.5 MB and 211 ms of main-thread time.

58 KiB could be saved by minifying JavaScript.

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

Instagram costs a phone 0 ms of main-thread work and 1.0 MB 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.

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

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 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

40 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' largest content (lcp) went from 1.1 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.5 MB in 110 requests on a phone: images 2.2 MB (56), scripts 717 KiB (16) and fonts 375 KiB (6). Under 2 MB keeps phones on slow connections fast.

10 images (1.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.

6 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images are downloaded at several times the size a phone draws them, for example 871123017_18643943533004611_3239305590945506547_n.jpg at 1,088 px wide, shown at 290 px. Resized copies would save about 479 KiB.

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

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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

Headings skip levels (h2 → h4 and h3 → h6), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is only 21 characters: “Home » TSG Hoffenheim”. Between 30 and 65 characters leaves room to say what you do and for whom.

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.

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

9 links have no real href, so search engines can't follow them.

Open Graph is missing og:description, so shared links fall back to guesses.

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

The homepage links to 53 pages on tsg-hoffenheim.de and 23 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.tsg-hoffenheim.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.tsg-hoffenheim.de/en all use the title “Home » TSG Hoffenheim”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tsg-hoffenheim.de/tsg-radio and https://www.tsg-hoffenheim.de/en have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tsg-hoffenheim.de/tickets and https://www.tsg-hoffenheim.de/tickets/ticketcenter use the same meta description. A description written for each page earns more clicks.

https://www.tsg-hoffenheim.de/tsg-radio, https://www.tsg-hoffenheim.de/tickets, https://www.tsg-hoffenheim.de/en and https://www.tsg-hoffenheim.de/tickets/ticketcenter have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.tsg-hoffenheim.de/en has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 error was logged to the browser console while the page loaded, for example “AbortError: The play() request was interrupted because the media was removed from the document. https://goo.gl/LdLk22”.

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.

Social proof on the homepage: 32 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.

The homepage has only about 234 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

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