universal-music.de website review

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

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

26 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 64. 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 950 ms).

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

About 543 KiB of JavaScript is downloaded but never used on this page.

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

3 third-party services load with your homepage (consentmanager.net, Google Tag Manager and Google/Doubleclick Ads), adding 346 KiB and 424 ms of main-thread time.

About 22 KiB of CSS is downloaded but never applied on this page.

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

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

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.

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

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

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

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

1 image 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 158 ms to 164 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 4.7 MB in 55 requests on a phone: images 3.3 MB (38), scripts 1.2 MB (10) and HTML 69 KiB (2). Under 2 MB keeps phones on slow connections fast.

14 images (948 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.

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

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

34 elements use ARIA attributes their role does not allow, which confuses screen readers.

32 buttons have no accessible name, so screen readers announce just “button”.

ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

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

Your meta description is only 53 characters: “Willkommen bei der Universal Music Group Deutschland.”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 72 pages on universal-music.de and 29 external pages.

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.

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

Your homepage links to https://www.universal-music.de/kontrak/musik/aus-der-asche-1296645, which answers with an error. Visitors hit a dead end and search engines drop it.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.universal-music.de/termine, whose canonical is https://www.universal-music.de/termine/live. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.universal-music.de/kuenstler, https://www.universal-music.de/termine and https://www.universal-music.de/gewinnspiele have 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 51 found) and read each the way a search engine does.

1 image is 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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Before a visitor clicks anything, the page loads Google Ads and 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 4 cookies, 1 of them by other companies (measured from a US location before any click).

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