imagem.com website review

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

4 third-party services load with your homepage (privacy-mgmt.com, Google Tag Manager and Google Analytics and others), adding 9.1 MB and 298 ms of main-thread time.

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

ctfassets.net costs a phone 0 ms of main-thread work and 8.7 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.

7 files are served with short cache lifetimes, so returning visitors download them again (124 KiB).

1 image could be 255 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

Polyfills for old browsers add 41 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.

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

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

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

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

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

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

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

Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A new global music company with the scale, expertise, and t…”. Most of its time is element render delay (2.5 s).

Your homepage downloads 14.3 MB in 59 requests on a phone: images 8.7 MB (19), other files 4.3 MB (12) and scripts 776 KiB (18). Under 2 MB keeps phones on slow connections fast.

15 images are downloaded at several times the size a phone draws them, for example Jason_Aldean_Photo_Credit_Spidey_Smith_-_Main_Press_Image.jp at 8,192 px wide, shown at 294 px. Resized copies would save about 8.1 MB.

6 images weigh 6.5 MB together. On a phone connection a single image that size takes seconds.

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

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

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

Your title is only 3 characters: “BMG”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 44 characters: “A Global Music Publishing and Record Company”. 70 to 160 characters is enough to sell the click.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 24 pages on imagem.com and 5 external pages.

Your robots.txt lets Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

/homepage, /publishing, /recording, /sync, /who-we-are and /careers and 8 others use the same meta description. A description written for each page earns more clicks.

/publishing, /recording, /sync, /who-we-are, /careers and /news and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 14 pages linked from your homepage and read each the way a search engine does.

Large scripts ship without source maps.

Opening https://imagem.com goes through 2 redirects before the homepage loads.

2 links go through two or more redirects, for example http://youtube.com/bmg.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

bmg.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

There is no form on the homepage, so every lead has to click through to another page first.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.