Website review, no card needed

uriage.fr logo

uriage.fr website review

Visit site (opens in a new tab)Reviewed 17 November 202648 issues · 87 checks

This review found 48 issues worth fixing on uriage.fr, 17 of them high impact, across 87 checks. The most urgent: 48,882 HTML elements. 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.5 sMay 30Nov 143.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20263.0 s
Jun 20, 20263.2 s
Jun 27, 20263.5 s
Jul 4, 20263.3 s
Jul 11, 20262.9 s
Jul 18, 20262.7 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.9 s
Aug 15, 20263.1 s
Aug 22, 20263.3 s
Aug 29, 20263.4 s
Sep 5, 20263.4 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20262.9 s
Oct 10, 20263.1 s
Oct 17, 20263.0 s
Oct 24, 20263.1 s
Oct 31, 20263.3 s
Nov 7, 20263.5 s
Nov 14, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
517 ms156 msMay 30Nov 14362 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026226 ms
Jun 6, 2026298 ms
Jun 13, 2026314 ms
Jun 20, 2026341 ms
Jun 27, 2026355 ms
Jul 4, 2026325 ms
Jul 11, 2026294 ms
Jul 18, 2026251 ms
Jul 25, 2026211 ms
Aug 1, 2026198 ms
Aug 8, 2026246 ms
Aug 15, 2026317 ms
Aug 22, 2026392 ms
Aug 29, 2026431 ms
Sep 5, 2026404 ms
Sep 12, 2026371 ms
Sep 19, 2026315 ms
Sep 26, 2026274 ms
Oct 3, 2026300 ms
Oct 10, 2026367 ms
Oct 17, 2026432 ms
Oct 24, 2026475 ms
Oct 31, 2026474 ms
Nov 7, 2026402 ms
Nov 14, 2026362 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 uriage.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. uriage.fr at 0.6 s0.6 s
  2. uriage.fr at 1.1 s1.1 s
  3. uriage.fr at 1.7 s1.7 s
  4. uriage.fr at 2.3 s2.3 s
  5. uriage.fr at 2.8 s2.8 s
  6. uriage.fr at 3.4 s3.4 s
  7. uriage.fr at 4.0 s4.0 s
  8. uriage.fr at 4.5 s4.5 s

Speed

11 to fix38
  • 48,882 HTML elements

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

  • Improve image delivery

    1.2 s · 779 KiB

    25 images could be 779 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 38

    38/100

    Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused JavaScript

    610 ms · 586 KiB

    About 586 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 610 ms faster on a phone.

  • 7 long tasks on the main thread

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, ZenDesk and Cookiebot and others), adding 1.4 MB and 595 ms of main-thread time.

  • Use efficient cache lifetimes

    300 ms · 311 KiB

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

  • Main-thread work: 3.5 s

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

  • ZenDesk adds 143 ms

    143 ms

    ZenDesk costs a phone 143 ms of main-thread work and 431 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.

  • Cookiebot adds 132 ms

    132 ms

    Cookiebot costs a phone 132 ms of main-thread work and 468 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 · 62 KiB

    About 62 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.

  • Font display

    50 ms

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

  • Legacy JavaScript

    29 KiB

    Polyfills for old browsers add 29 KiB JavaScript that modern phones do not need.

  • Minify CSS

    13 KiB

    13 KiB could be saved by minifying CSS.

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 421 ms

    421 ms

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

Core Web Vitals

15 to fix0
  • Fails Core Web Vitals for real visitors

    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-user INP: 518 ms

    518 ms

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

  • Largest Contentful Paint: 9.1 s

    9.1 s

    Your largest element takes 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 14.8 s

    14.8 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user CLS: 0.19

    0.19

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

  • Tap response (INP) got 46% slower for real visitors

    +46%

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

  • Largest content (LCP) got 26% slower for real visitors

    +26%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Total Blocking Time: 559 ms

    559 ms

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

  • Cumulative Layout Shift: 0.202

    0.202

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

  • 31 images without width and height

    31 images have no width and height attributes, so the layout jumps as each one loads.

Images and page weight

1 to fix67
  • Page weight: 3.4 MB in 145 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 145 requests on a phone: scripts 1.5 MB (42), images 1.4 MB (66) and HTML 220 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.96 g

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

Accessibility

9 to fixGoogle 8689
  • 35 text elements with low contrast

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

  • 7 tap targets too small

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

  • <html> element must have a valid value for the lang attribute (1 element)

    <html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 5 images without alt text

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

  • 138 links without text

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

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

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

  • 27 form fields without a label

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

  • Page language is “fr_FR”

    The page declares lang=“fr_FR”, which is not a usable language code, so screen readers and translation tools guess.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

5 to fixGoogle 9274
  • No H1 headline

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

  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “Laboratoires dermatologiques Uriage : Eau thermale et dermo-cosmétique”.

  • 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.uriage.fr/sitemap.xml, so Google discovers your pages only by following links.

  • 1 link crawlers can't follow

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

  • 117 internal links, 2 external

    The homepage links to 117 pages on uriage.fr and 2 external pages.

4 checks passed
  • Meta description: 70 characters

    Your meta description is 70 characters: “Laboratoires dermatologiques Uriage : Eau thermale et dermo-cosmétique”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    50%

    The HTML your server sends has 654 of the 1,307 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

Other pages

1 to fix95
  • 2 pages without an H1

    https://www.uriage.fr/blog and https://www.uriage.fr/faq have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.uriage.fr/produits and https://www.uriage.fr/blog took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9271
  • 2 broken images

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

  • 99 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Unsafe attempt to load URL https://cdn.uriage.fr/assets/images/temp/sprite-icons.svg from frame with URL https://www.ur…”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 1,307 words of copy

    The homepage carries about 1,307 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 trackers load before any consent

    3

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

  • 8 cookies set on arrival

    8

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

  • 13 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 uriage.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on uriage.fr, including 26 speed issues, 5 SEO issues and 2 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