om.fr website review

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

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

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

Polyfills for old browsers add 59 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.

3 third-party services load with your homepage (Google Tag Manager, Dailymotion and axept.io), adding 217 KiB and 144 ms of main-thread time.

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

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

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.

Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Next home match: OM 🆚 TOULOUSE (Sun 01 Nov)”.

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

Real visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.3 s 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.

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

image 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.56 g of CO₂e: 67.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

3 tap targets are too small or too close together to hit reliably with a finger.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

Tables do not use <caption> instead of cells with the [colspan] attribute to indicate a caption. (1 element).

<td> elements in a large <table> do not have table headers. (1 element).

Your title is only 22 characters: “Olympique de Marseille”. 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.

Your <h1> is empty.

The homepage links to 23 pages on om.fr and 56 external pages.

Your robots.txt shuts out Claude search (Claude-SearchBot) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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.om.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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

https://www.om.fr/en/news/om-4-3-hac-bruno-genesio-s-reaction, https://www.om.fr/en/news/watch-the-bayer-leverkusen-v-marseille-match-from-the-training-ground, https://www.om.fr/en/news/om-vs-tfc-the-press-conference, https://www.om.fr/en/news/om-tfc-the-2024-2025-victory, https://www.om.fr/en/news/mcdonald-s-is-extending-its-partnership-with-olympique-de-marseille-as-an-official-supplier and https://www.om.fr/en/news/the-weekend-fixtures-31-10-01-11-2026 and 9 others use the same meta description. A description written for each page earns more clicks.

https://www.om.fr/en/news/om-4-3-hac-bruno-genesio-s-reaction, https://www.om.fr/en/news/watch-the-bayer-leverkusen-v-marseille-match-from-the-training-ground, https://www.om.fr/en/news/om-vs-tfc-the-press-conference, https://www.om.fr/en/news/om-tfc-the-2024-2025-victory, https://www.om.fr/en/news/mcdonald-s-is-extending-its-partnership-with-olympique-de-marseille-as-an-official-supplier and https://www.om.fr/en/news/the-weekend-fixtures-31-10-01-11-2026 and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.om.fr/en/news/om-4-3-hac-bruno-genesio-s-reaction, https://www.om.fr/en/news/watch-the-bayer-leverkusen-v-marseille-match-from-the-training-ground, https://www.om.fr/en/news/om-vs-tfc-the-press-conference, https://www.om.fr/en/news/om-tfc-the-2024-2025-victory, https://www.om.fr/en/news/mcdonald-s-is-extending-its-partnership-with-olympique-de-marseille-as-an-official-supplier and https://www.om.fr/en/news/the-weekend-fixtures-31-10-01-11-2026 and 3 others 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 22 found) and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.”.

Chrome logged issues while loading the page (“Content security policy”).

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

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