Website review, no card needed
silae.fr website review
Visit site (opens in a new tab)Reviewed 29 October 202624 issues · 76 checks
This review found 24 issues worth fixing on silae.fr, 6 of them high impact, across 76 checks. The most urgent: page weight: 4.5 MB in 53 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
92AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.4 s |
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 946 ms |
| Jul 4, 2026 | 952 ms |
| Jul 11, 2026 | 954 ms |
| Jul 18, 2026 | 999 ms |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 961 ms |
| Sep 12, 2026 | 981 ms |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 139 ms |
| May 16, 2026 | 139 ms |
| May 23, 2026 | 139 ms |
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 137 ms |
| Jun 13, 2026 | 137 ms |
| Jun 20, 2026 | 138 ms |
| Jun 27, 2026 | 144 ms |
| Jul 4, 2026 | 150 ms |
| Jul 11, 2026 | 153 ms |
| Jul 18, 2026 | 156 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 159 ms |
| Aug 8, 2026 | 161 ms |
| Aug 15, 2026 | 157 ms |
| Aug 22, 2026 | 159 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 153 ms |
| Sep 12, 2026 | 153 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 154 ms |
| Oct 3, 2026 | 158 ms |
| Oct 10, 2026 | 156 ms |
| Oct 17, 2026 | 157 ms |
| Oct 24, 2026 | 157 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
Speed
Render-blocking requests
700 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Reduce unused CSS
300 ms · 38 KiBAbout 38 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.
Reduce unused JavaScript
259 KiBAbout 259 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
250 KiB12 images could be 250 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1,686 HTML elements
The page has 1,686 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Matomo and dastra.eu and others), adding 314 KiB and 250 ms of main-thread time.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 120 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
26 KiB8 files are served with short cache lifetimes, so returning visitors download them again (26 KiB).
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.
3 checks passed
Mobile performance score: 96
96/100Your mobile performance score is 96. That is in Google's “good” band (90 and up).
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 427 ms of it running JavaScript. That is comfortably low.
Server response: 102 ms
102 msYour server sent the HTML in 102 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 5.5 s
5.5 sThe page becomes fully interactive after 5.5 s. Good is under 3.8 s.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 139 ms to 157 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
11 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 169 ms
169 msReal visitors wait 169 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 512 ms
512 msReal visitors wait 512 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 1.8 s
1.8 sYour largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “8 millions”.
Total Blocking Time: 106 ms
106 msScripts block the page for only 106 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
Page weight: 4.5 MB in 53 requests
4.5 MBYour homepage downloads 4.5 MB in 53 requests on a phone: media 3.1 MB (1), scripts 481 KiB (11) and images 461 KiB (30). Under 2 MB keeps phones on slow connections fast.
About 1.3 g of CO₂ per visit
1.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.27 g of CO₂e: 152.7 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
<svg> elements with an img or image role must have alternative text (25 elements)
<svg> elements with an img or image role must have alternative text: 25 elements on the page fail this check, rated serious by axe-core.
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.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 123 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Logiciel de Paie + RH SILAE : Conformité & automatisations | 0 erreur”.
Meta description is long (169 characters)
Your meta description is 169 characters; Google truncates after about 160, so the end of your pitch is cut.
162 internal links, 6 external
The homepage links to 162 pages on silae.fr and 6 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Logiciel de Paie & RH pour cabinets et intégrateurs”.
Canonical URL set
The canonical URL is https://www.silae.fr/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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.silae.fr/sitemap_index.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,308 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.silae.fr/llms.txt (3 KiB, 19 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.silae.fr/contacter-silae/partenaires is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://www.silae.fr/silae-dematerialisation and https://www.silae.fr/silae-dematerialisation/pour-le-secteur-public all use the title “Coffre-fort numérique certifié et sécurisé pour vos documents”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.silae.fr/silae-dematerialisation and https://www.silae.fr/silae-dematerialisation/pour-le-secteur-public use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.silae.fr/silae-dematerialisation/pour-le-secteur-public, whose canonical is https://www.silae.fr/silae-dematerialisation. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 70 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 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”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
26 of 27 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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,099 words of copy
The homepage carries about 1,099 words of visible text.
4 checks passed
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: 41 testimonial or review blocks, 86 customer or partner logos and 5 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and Xandr (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.
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.
8 other companies contacted
Loading the homepage contacts 8 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 silae.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
- WordPress
- Analytics
- Google Tag Manager
- Hosting
- Azure
Company
- Founded
- 2010
- Headquarters
- Aix-en-Provence
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on silae.fr, including 8 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.