Website review, no card needed

gallimard.fr logo

gallimard.fr website review

Visit site (opens in a new tab)Reviewed 26 October 202632 issues · 84 checks

This review found 32 issues worth fixing on gallimard.fr, 12 of them high impact, across 84 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.6 s2.8 sMay 9Oct 242.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.5 s
May 16, 20263.5 s
May 23, 20263.4 s
May 30, 20263.3 s
Jun 6, 20263.3 s
Jun 13, 20263.2 s
Jun 20, 20263.3 s
Jun 27, 20263.3 s
Jul 4, 20263.3 s
Jul 11, 20263.3 s
Jul 18, 20263.4 s
Jul 25, 20263.4 s
Aug 1, 20263.4 s
Aug 8, 20263.4 s
Aug 15, 20263.4 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.1 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20263.0 s
Oct 17, 20262.9 s
Oct 24, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
146 ms139 msMay 9Oct 24144 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026140 ms
May 16, 2026141 ms
May 23, 2026144 ms
May 30, 2026145 ms
Jun 6, 2026144 ms
Jun 13, 2026142 ms
Jun 20, 2026141 ms
Jun 27, 2026141 ms
Jul 4, 2026142 ms
Jul 11, 2026143 ms
Jul 18, 2026142 ms
Jul 25, 2026143 ms
Aug 1, 2026142 ms
Aug 8, 2026141 ms
Aug 15, 2026140 ms
Aug 22, 2026140 ms
Aug 29, 2026140 ms
Sep 5, 2026141 ms
Sep 12, 2026143 ms
Sep 19, 2026143 ms
Sep 26, 2026143 ms
Oct 3, 2026143 ms
Oct 10, 2026142 ms
Oct 17, 2026144 ms
Oct 24, 2026144 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of gallimard.fr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gallimard.fr at 0.5 s0.5 s
  2. gallimard.fr at 1.0 s1.0 s
  3. gallimard.fr at 1.5 s1.5 s
  4. gallimard.fr at 1.9 s1.9 s
  5. gallimard.fr at 2.4 s2.4 s
  6. gallimard.fr at 2.9 s2.9 s
  7. gallimard.fr at 3.4 s3.4 s
  8. gallimard.fr at 3.9 s3.9 s

Speed

5 to fix59
  • Render-blocking requests

    5.2 s

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.2 s.

  • Mobile performance score: 59

    59/100

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

  • Improve image delivery

    300 ms · 599 KiB

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

  • 2,690 HTML elements

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

  • Adobe TypeKit adds 0 ms

    0 ms

    Adobe TypeKit costs a phone 0 ms of main-thread work and 678 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.

  • Reduce unused CSS

    150 ms · 55 KiB

    About 55 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Document request latency

    175 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 4 third-party services on the page

    4 third-party services load with your homepage (madrigall.fr, YouTube and Business Message and others), adding 747 KiB and 50 ms of main-thread time.

  • Reduce unused JavaScript

    124 KiB

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

  • Font display

    100 ms

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

  • 2 long tasks on the main thread

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

  • Use efficient cache lifetimes

    36 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 86 but mobile only 59. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

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

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 221 ms of it running JavaScript. That is comfortably low.

  • Server response: 380 ms

    380 ms

    Your server sent the HTML in 380 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • First Contentful Paint: 7.0 s

    7.0 s

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

  • Largest Contentful Paint: 7.7 s

    7.7 s

    Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ce que nous pouvons savoir - Ian McEwan”.

  • Speed Index: 7.5 s

    7.5 s

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

  • Time to Interactive: 8.9 s

    8.9 s

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

  • Tap response (INP) held steady for real visitors

    +2%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 162 ms

    162 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 538 ms

    538 ms

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

  • Largest content (LCP) got 18% faster for real visitors

    -18%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.5 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.002

    0.002

    The layout barely moves while loading (CLS 0.002, good is under 0.1).

  • Total Blocking Time: 23 ms

    23 ms

    Scripts block the page for only 23 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix81
  • Page weight: 3.0 MB in 105 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 105 requests on a phone: images 1.8 MB (81), fonts 676 KiB (8) and HTML 263 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    133440.png.webp 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).

  • About 0.9 g of CO₂ per visit

    0.86 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8791
  • 10 buttons without a name

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

  • 37 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • All page content should be contained by landmarks (49 elements)

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

  • 3 form fields without a label

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 134 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 8576
  • Title is short (19 characters)

    Your title is only 19 characters: “Accueil | Gallimard”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at gallimard.fr/robots.txt, the first file search crawlers ask for.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 227 internal links, 81 external

    The homepage links to 227 pages on gallimard.fr and 81 external pages.

3 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “Le site des Éditions Gallimard : catalogue, agenda des auteurs, actualités de la maison d'édition, vidéos et documents,…”.

  • One H1 headline

    Your main headline reads: “Gallimard : éditeur de littérature française et étrangère, et de sciences humaines”.

  • Canonical URL set

    The canonical URL is https://www.gallimard.fr/.

AI search readiness

1 to fix81
  • No Organization structured data

    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.

  • No llms.txt

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

1 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (3,145 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix63
  • 8 linked pages are broken

    Your homepage links to https://www.gallimard.fr/recherche-au-coeur-des-livres, https://www.gallimard.fr/livres/litterature-francaise/romans-nouvelles-et-recits, https://www.gallimard.fr/livres/litterature-francaise/theatre, https://www.gallimard.fr/livres/litterature-etrangere/allemandes, https://www.gallimard.fr/livres/litterature-etrangere/anglophones and https://www.gallimard.fr/livres/litterature-etrangere/espagne and 2 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 linked page hidden from search

    https://www.gallimard.fr/inscription-a-la-newsletter is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.gallimard.fr/inscription-a-la-newsletter has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://www.gallimard.fr/livres/litterature-francaise, https://www.gallimard.fr/livres/litterature-francaise/memoires-et-autobiographies and https://www.gallimard.fr/livres/litterature-francaise/poesie took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 18 low-resolution images

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

2 checks passed
  • Tap targets are thumb-sized

    233 of 276 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

    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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 3,099 words of copy

    The homepage carries about 3,099 words of visible text.

3 checks passed
  • 1 short form

    A short form (3 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 1 trust badge.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

  • 8 cookies set on arrival

    8

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

  • No consent tool detected

    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.

  • 6 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at gallimard.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Madrigall

Company

Founded
1911
Headquarters
Paris

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on gallimard.fr, including 9 speed issues, 6 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25