leprogres.fr website review

About 187 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.6 s.

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

8 third-party services load with your homepage (prsmedia.fr, Google Tag Manager and Didomi and others), adding 1.5 MB and 984 ms of main-thread time.

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

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

prsmedia.fr costs a phone 296 ms of main-thread work and 613 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.

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

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

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

Didomi costs a phone 210 ms of main-thread work and 347 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.

4 images could be 41 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

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.

4 KiB could be saved by minifying JavaScript.

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 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Bienvenue sur Le Progrès ! Chaque jour, nos journalistes s’…”. Most of its time is element render delay (4.8 s).

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

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

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

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

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

14 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' tap response (inp) went from 225 ms to 258 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 1.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.

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

Your title is 89 characters, so Google will cut it off around 60: “Le Progrès : info et actu nationale et régionale - Rhône, Loire, Ain, Haute-Loire et Jura”.

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

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

The homepage links to 641 pages on leprogres.fr and 149 external pages.

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

robots.txt blocks GPTBot, 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.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.leprogres.fr/nos-offres-abonnements, whose canonical is https://www.leprogres.fr/nos-offres-abonnements?utm_source=meta&utm_medium=social_ads&utm_campaign=OP_FilRouge_Abonnement_MID&utm_content=Kit1_05_NoIA. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

2 images failed to load on a phone, for example https://www.leprogres.fr/.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://www.leprogres.fr' has been blo…”.

4 images are served at too low a resolution for sharp phone screens.

Requests the geolocation permission on page load.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your longest form asks for 13 fields (0 required). Every extra field lowers completion.

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

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

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

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