Website review, no card needed

epsor.fr logo

epsor.fr website review

Visit site (opens in a new tab)Reviewed 20 October 202632 issues · 79 checks

This review found 32 issues worth fixing on epsor.fr, 6 of them high impact, across 79 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
1.4 s1.0 sMay 2Oct 171.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.1 s
May 9, 20261.1 s
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.1 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
128 ms69 msMay 2Oct 17120 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202679 ms
May 9, 202677 ms
May 16, 202677 ms
May 23, 202676 ms
May 30, 202677 ms
Jun 6, 202678 ms
Jun 13, 202678 ms
Jun 20, 202679 ms
Jun 27, 202679 ms
Jul 4, 202682 ms
Jul 11, 202694 ms
Jul 18, 2026103 ms
Jul 25, 2026108 ms
Aug 1, 2026113 ms
Aug 8, 2026114 ms
Aug 15, 2026115 ms
Aug 22, 2026119 ms
Aug 29, 2026121 ms
Sep 5, 2026120 ms
Sep 12, 2026118 ms
Sep 19, 2026117 ms
Sep 26, 2026116 ms
Oct 3, 2026117 ms
Oct 10, 2026119 ms
Oct 17, 2026120 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 epsor.fr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix62
  • Render-blocking requests

    3.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (hsappstatic.net, Google Tag Manager and website-files.com and others), adding 2.0 MB and 980 ms of main-thread time.

  • Mobile performance score: 62

    62/100

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

  • Reduce unused JavaScript

    150 ms · 486 KiB

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

  • Use efficient cache lifetimes

    450 ms · 118 KiB

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

  • Improve image delivery

    300 ms · 166 KiB

    5 images could be 166 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.

  • Reduce unused CSS

    300 ms · 125 KiB

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

  • hsappstatic.net adds 351 ms

    351 ms

    hsappstatic.net costs a phone 351 ms of main-thread work and 710 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 adds 233 ms

    233 ms

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

  • Main-thread work: 2.4 s

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

  • website-files.com adds 140 ms

    140 ms

    website-files.com costs a phone 140 ms of main-thread work and 836 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.

  • 9 long tasks on the main thread

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

  • 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: 3 ms

    3 ms

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

Core Web Vitals

7 to fix100
  • Time to Interactive: 15.5 s

    15.5 s

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

  • Largest Contentful Paint: 5.4 s

    5.4 s

    Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Employee savings and retirement at last valued!”.

  • First Contentful Paint: 3.9 s

    3.9 s

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

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

    +53%

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

  • Speed Index: 4.3 s

    4.3 s

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

  • Total Blocking Time: 269 ms

    269 ms

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

  • 13 images without width and height

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

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

    +13%

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

7 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.5 s

    1.5 s

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

  • Real-user INP: 92 ms

    92 ms

    Real visitors wait 92 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.5 s

    1.5 s

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

  • Real-user TTFB: 482 ms

    482 ms

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

  • Cumulative Layout Shift: 0.095

    0.095

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

Images and page weight

1 to fix85
  • Page weight: 2.2 MB in 92 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 92 requests on a phone: scripts 1.3 MB (31), images 319 KiB (31) and fonts 254 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.61 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9296
  • 16 text elements with low contrast

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

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

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

  • 3 links without text

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

2 checks passed
  • Every image has alt text

    All 84 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 9289
  • No structured data

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

  • Meta description is long (239 characters)

    Your meta description is 239 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 41 internal links, 9 external

    The homepage links to 41 pages on epsor.fr and 9 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “L’épargne salariale et retraite enfin valorisée !”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Epsor - L’épargne salariale et retraite enfin valorisée”.

  • Canonical URL set

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

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.epsor.fr/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.epsor.fr/llms.txt (6 KiB, 32 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix93
  • 1 linked page hidden from search

    https://www.epsor.fr/contact is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page with very little text

    https://www.epsor.fr/prendre-rendez-vous has 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 25 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7389
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

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

3 checks passed
  • 2 calls to action

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

  • Social proof on the page

    Social proof on the homepage: 9 testimonial or review blocks, 33 customer or partner logos, a star rating and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and 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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies (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.

  • 23 other companies contacted

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

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

Upkeep, stack and company

Stack

CMS
Webflow
Analytics
Google Analytics | Google Tag Manager

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 epsor.fr, including 18 speed issues, 3 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