Website review, no card needed

amen.fr logo

amen.fr website review

Visit site (opens in a new tab)Reviewed 19 October 202653 issues · 99 checks

This review found 53 issues worth fixing on amen.fr, 26 of them high impact, across 99 checks. The most urgent: reduce unused JavaScript. 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
4.1 s3.3 sMay 2Oct 173.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.4 s
May 9, 20263.4 s
May 16, 20263.6 s
May 23, 20263.6 s
May 30, 20263.7 s
Jun 6, 20263.8 s
Jun 13, 20263.8 s
Jun 20, 20263.9 s
Jun 27, 20263.9 s
Jul 4, 20263.9 s
Jul 11, 20263.9 s
Jul 18, 20263.8 s
Jul 25, 20263.9 s
Aug 1, 20263.9 s
Aug 8, 20263.9 s
Aug 15, 20264.0 s
Aug 22, 20263.9 s
Aug 29, 20263.9 s
Sep 5, 20263.8 s
Sep 12, 20263.7 s
Sep 19, 20263.7 s
Sep 26, 20263.6 s
Oct 3, 20263.4 s
Oct 10, 20263.4 s
Oct 17, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
391 ms303 msMay 2Oct 17381 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026315 ms
May 9, 2026313 ms
May 16, 2026333 ms
May 23, 2026330 ms
May 30, 2026344 ms
Jun 6, 2026351 ms
Jun 13, 2026346 ms
Jun 20, 2026344 ms
Jun 27, 2026345 ms
Jul 4, 2026355 ms
Jul 11, 2026358 ms
Jul 18, 2026363 ms
Jul 25, 2026360 ms
Aug 1, 2026354 ms
Aug 8, 2026363 ms
Aug 15, 2026363 ms
Aug 22, 2026373 ms
Aug 29, 2026376 ms
Sep 5, 2026355 ms
Sep 12, 2026347 ms
Sep 19, 2026344 ms
Sep 26, 2026353 ms
Oct 3, 2026368 ms
Oct 10, 2026375 ms
Oct 17, 2026381 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 amen.fr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amen.fr at 1.2 s1.2 s
  2. amen.fr at 2.3 s2.3 s
  3. amen.fr at 3.5 s3.5 s
  4. amen.fr at 4.7 s4.7 s
  5. amen.fr at 5.9 s5.9 s
  6. amen.fr at 7.0 s7.0 s
  7. amen.fr at 8.2 s8.2 s
  8. amen.fr at 9.4 s9.4 s

Speed

10 to fix32
  • Reduce unused JavaScript

    3.3 s · 781 KiB

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

  • Improve image delivery

    1.3 s · 1.6 MB

    6 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

  • Render-blocking requests

    2.9 s

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

  • Use efficient cache lifetimes

    1.1 s · 334 KiB

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

  • Mobile performance score: 32

    32/100

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

  • Main-thread work: 5.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, ZenDesk and Accessibe Accessibility Overlay and others), adding 1.8 MB and 1.9 s of main-thread time.

  • Google Tag Manager adds 868 ms

    868 ms

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

  • ZenDesk adds 477 ms

    477 ms

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

  • 1,597 HTML elements

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

  • 16 long tasks on the main thread

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

  • Legacy JavaScript

    64 KiB

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

  • Reduce unused CSS

    56 KiB

    About 56 KiB of CSS is downloaded but never applied on this page.

  • Font display

    50 ms

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

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

    240 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 21.8 s

    21.8 s

    Your largest element takes 21.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NOUVEAU MACALY AI Un prompt = Un site web Décrivez votre id…”.

  • Speed Index: 16.4 s

    16.4 s

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

  • Time to Interactive: 36.8 s

    36.8 s

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

  • Total Blocking Time: 794 ms

    794 ms

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

  • First Contentful Paint: 3.0 s

    3.0 s

    The first text or image appears after 3.0 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 INP: 260 ms

    260 ms

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

  • Real-user CLS: 0.14

    0.14

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

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

    +20%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 979 ms

    979 ms

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

  • Cumulative Layout Shift: 0.19

    0.19

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

  • 33 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    0%

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

Images and page weight

5 to fix18
  • Page weight: 7.7 MB in 144 requests

    7.7 MB

    Your homepage downloads 7.7 MB in 144 requests on a phone: images 5.5 MB (62), scripts 1.9 MB (42) and fonts 152 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 4.5 MB together. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    3.0 MB

    8 images are downloaded at several times the size a phone draws them, for example shopbuilder-hp.png at 964 px wide, shown at 205 px. Resized copies would save about 3.0 MB.

  • 9 images in older formats

    9 images (4.9 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 7 images below the first screen load straight away

    7 images further down the page (4.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.19 g

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

Accessibility

15 to fixGoogle 7079
  • Certain ARIA roles must contain particular children (4 elements)

    Certain ARIA roles must contain particular children: 4 elements on the page fail this check, rated critical by axe-core.

  • 2 buttons without a name

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

  • 66 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • Inline text spacing must be adjustable with custom stylesheets (4 elements)

    Inline text spacing must be adjustable with custom stylesheets: 4 elements on the page fail this check, rated serious by axe-core.

  • ARIA input fields must have an accessible name (3 elements)

    ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • 28 images without alt text

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

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

  • Headings should not be empty (2 elements)

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

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

  • Headings skip levels

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

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • No social preview image

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

  • No XML sitemap

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

  • 233 internal links, 24 external

    The homepage links to 233 pages on amen.fr and 24 external pages.

6 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Découvrez les offres amen.fr en noms de domaine, hébergement web, création du site internet, boutique en ligne ou WordP…”.

  • One H1 headline

    Your main headline reads: “Accélérez la croissance de votre entreprise avec l'IA”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Nom de Domaine, Hébergement Web, Design Site Web - amen.fr”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

100
  • No llms.txt

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

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.

  • Organization data: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 5 pages without a meta description

    https://www.amen.fr/hebergement-web/web-hosting, https://www.amen.fr/hebergement-web-gratuit, https://www.amen.fr/serveur/cloud-backup, https://www.amen.fr/hebergement-web/linux/wepanel and https://www.amen.fr/support-prioritaire have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.amen.fr/support/hebergement has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.amen.fr/support/hebergement 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 152 found) and read each the way a search engine does.

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

  • 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 7376
  • 3 broken images

    3 images failed to load on a phone, for example https://trk.amen.fr/server/he-man_server?tkq=dHJrQ19lU0YlM0R3d3cuYW1lbi5mciUyNTJGJTI2dHJrQ19lU1VCJTNEd3d3LmFtZW4uZnIlMjZjRE9NJTNELmFtZW4uZnIlMjZ0cmtDX2VIUiUzRCUyNnRya0NfZVVBJTNETW96aWxsYSUyNTJGNS4wJTI.

  • Deprecated browser APIs

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 2 low-resolution images

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

2 checks passed
  • Tap targets are thumb-sized

    14 of 16 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

6 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Flexmail”, “Contact” and “Contact agences”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo, 5 trust badges and “3,3M+ clients”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 4 trackers load before any consent

    4

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

  • 11 cookies set on arrival

    11

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

  • 26 other companies contacted

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

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) 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 amen.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager

Company

Founded
1999

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on amen.fr, including 24 speed issues, 2 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