Website review, no card needed

audiens.org logo

audiens.org website review

Visit site (opens in a new tab)Reviewed 30 October 202643 issues · 89 checks

This review found 43 issues worth fixing on audiens.org, 18 of them high impact, across 89 checks. The most urgent: document request latency. 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
2.2 s1.9 sMay 9Oct 242.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.9 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
168 ms145 msMay 9Oct 24153 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026148 ms
May 16, 2026150 ms
May 23, 2026151 ms
May 30, 2026152 ms
Jun 6, 2026154 ms
Jun 13, 2026155 ms
Jun 20, 2026155 ms
Jun 27, 2026157 ms
Jul 4, 2026158 ms
Jul 11, 2026160 ms
Jul 18, 2026160 ms
Jul 25, 2026160 ms
Aug 1, 2026161 ms
Aug 8, 2026161 ms
Aug 15, 2026164 ms
Aug 22, 2026163 ms
Aug 29, 2026165 ms
Sep 5, 2026164 ms
Sep 12, 2026163 ms
Sep 19, 2026162 ms
Sep 26, 2026158 ms
Oct 3, 2026156 ms
Oct 10, 2026153 ms
Oct 17, 2026154 ms
Oct 24, 2026153 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 audiens.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. audiens.org at 1.1 s1.1 s
  2. audiens.org at 2.2 s2.2 s
  3. audiens.org at 3.3 s3.3 s
  4. audiens.org at 4.4 s4.4 s
  5. audiens.org at 5.5 s5.5 s
  6. audiens.org at 6.6 s6.6 s
  7. audiens.org at 7.7 s7.7 s
  8. audiens.org at 8.8 s8.8 s

Speed

11 to fix54
  • Document request latency

    5.3 s · 282 KiB

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

  • Reduce initial server response time

    5.3 s

    Reduce initial server response time. Google estimates savings of 5.3 s on a phone.

  • Render-blocking requests

    4.0 s

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

  • Use efficient cache lifetimes

    3.0 s · 686 KiB

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

  • Reduce unused JavaScript

    1.4 s · 478 KiB

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

  • Server response: 5.4 s

    5.4 s

    Your server takes 5.4 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Improve image delivery

    800 ms · 204 KiB

    1 image could be 204 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

  • Mobile performance score: 54

    54/100

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

  • Minify JavaScript

    300 ms · 75 KiB

    75 KiB could be saved by minifying JavaScript.

  • 2,856 HTML elements

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

  • Google Tag Manager adds 179 ms

    179 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, inbenta.io and Clarity and others), adding 695 KiB and 422 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 51 KiB

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

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    53 KiB

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

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

  • 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
  • Main-thread work: 1.8 s

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

Core Web Vitals

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

  • Speed Index: 17.9 s

    17.9 s

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

  • 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 image. Most of its time is time to first byte (5.4 s).

  • Time to Interactive: 22.5 s

    22.5 s

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

  • First Contentful Paint: 6.7 s

    6.7 s

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

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

  • 49 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

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

    +12%

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

6 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 150 ms

    150 ms

    Real visitors wait 150 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 TTFB: 628 ms

    628 ms

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

  • Cumulative Layout Shift: 0.08

    0.08

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

  • Total Blocking Time: 89 ms

    89 ms

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

Images and page weight

3 to fix53
  • Page weight: 4.5 MB in 87 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 87 requests on a phone: images 2.6 MB (42), scripts 1.2 MB (14) and HTML 424 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 14 images in older formats

    14 images (2.5 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.

  • 8 images below the first screen load straight away

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

  • About 1.3 g of CO₂ per visit

    1.28 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8893
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 4 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (3 elements)

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

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 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 7574
  • Title is short (24 characters)

    Your title is only 24 characters: “Accueil - Groupe Audiens”. 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.

  • Meta description is long (202 characters)

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

  • No XML sitemap

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

  • No robots.txt

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

  • 8 links crawlers can't follow

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

  • 144 internal links, 49 external

    The homepage links to 144 pages on audiens.org and 49 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “Pour la création. Pour l’information. Pour celles et ceux qui la font.”.

  • Canonical URL set

    The canonical URL is https://www.audiens.org/accueil.html.

  • Open Graph tags complete

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

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.

  • No llms.txt

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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

4 to fix62
  • 1 linked page is broken

    Your homepage links to https://www.audiens.org/google.fr, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 6 linked pages hidden from search

    https://www.audiens.org/accueil/lot2/page-offres/offres-entreprise-100-synthese.html, https://www.audiens.org/accueil/lot2/page-offres/offres-entreprise-synthese.html, https://www.audiens.org/accueil/lot2/page-offres/page-intermittents.html, https://www.audiens.org/accueil/lot2/page-offres/page-pigistes.html, https://www.audiens.org/accueil/lot2/page-offres/page-salaries.html and https://www.audiens.org/accueil/lot2/page-offres/page-retraites.html are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 6 pages without a meta description

    https://www.audiens.org/accueil/lot2/page-offres/offres-entreprise-100-synthese.html, https://www.audiens.org/accueil/lot2/page-offres/offres-entreprise-synthese.html, https://www.audiens.org/accueil/lot2/page-offres/page-intermittents.html, https://www.audiens.org/accueil/lot2/page-offres/page-pigistes.html, https://www.audiens.org/accueil/lot2/page-offres/page-salaries.html and https://www.audiens.org/accueil/lot2/page-offres/page-retraites.html have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.audiens.org/articles/la-designation-de-beneficiaires-en-prevoyance.html and https://www.audiens.org/articles/comprendre-la-dsn.html use the same meta description. A description written for each page earns more clicks.

  • 6 pages slow to respond

    https://www.audiens.org/accueil/lot2/page-offres/offres-entreprise-synthese.html, https://www.audiens.org/accueil/lot2/page-offres/page-pigistes.html, https://www.audiens.org/articles/interet-de-la-surcomplementaire.html, https://www.audiens.org/articles/la-designation-de-beneficiaires-en-prevoyance.html, https://www.audiens.org/solutions/sante-et-bien-etre-au-travail-actions-de-prevention-en-entreprise.html and https://www.audiens.org/accueil/solutions/pagecontent/liste-des-offres-audiens/webi-socio.html took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 54 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 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10078
  • 4 broken images

    4 images failed to load on a phone, for example https://www.audiens.org/accueil.html.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://sdk.inbenta.io/km/2.5.0/neutral.css' from origin 'https://www.audiens.org' has bee…”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No opening hours

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

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

    The homepage carries about 2,489 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact et Plan du site”.

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 14 cookies set on arrival

    14

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

  • 22 other companies contacted

    Loading the homepage contacts 22 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 audiens.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Probtp

Company

Founded
2003
Headquarters
Vanves

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on audiens.org, including 18 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