livenation.fr website review

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

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

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

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

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

5 third-party services load with your homepage (Google Tag Manager, ketchjs.com and livenationinternational.com and others), adding 1.4 MB and 374 ms of main-thread time.

Google Tag Manager costs a phone 272 ms of main-thread work and 205 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.

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

livenationinternational.com costs a phone 0 ms of main-thread work and 1.1 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.

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

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

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

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 11.9 s. Good is under 3.8 s.

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

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

For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

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

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

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

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

Your homepage downloads 2.1 MB in 103 requests on a phone: images 1.1 MB (27), scripts 888 KiB (55) and HTML 83 KiB (1). Under 2 MB keeps phones on slow connections fast.

88e4a90a-5a95-4d5f-ba3a-e61b3c8dad76.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 0.61 g of CO₂e: 73.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Your title is 70 characters, so Google will cut it off around 60: “Dates et billetterie de concerts et de spectacles | Live Nation France”.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.livenation.fr/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 93 pages on livenation.fr and 14 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.livenation.fr/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://www.livenation.fr/event/allevents and https://www.livenation.fr/festival 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 72 found) and read each the way a search engine does.

6 images failed to load on a phone, for example https://ids4.ad.gt/api/v1/ip_match?id=AU1D0200001792818484ROKIJZDB4HIO.

6 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-m…”.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Snap Pixel and 3 mores (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 21 cookies, 2 of them by other companies (measured from a US location before any click).

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