Website review, no card needed
armeedusalut.fr website review
Visit site (opens in a new tab)Reviewed 1 November 202635 issues · 85 checks
This review found 35 issues worth fixing on armeedusalut.fr, 17 of them high impact, across 85 checks. The most urgent: improve image delivery. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.5 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 163 ms |
| May 16, 2026 | 169 ms |
| May 23, 2026 | 162 ms |
| May 30, 2026 | 164 ms |
| Jun 6, 2026 | 161 ms |
| Jun 13, 2026 | 157 ms |
| Jun 20, 2026 | 155 ms |
| Jun 27, 2026 | 155 ms |
| Jul 4, 2026 | 165 ms |
| Jul 11, 2026 | 174 ms |
| Jul 18, 2026 | 181 ms |
| Jul 25, 2026 | 182 ms |
| Aug 1, 2026 | 183 ms |
| Aug 8, 2026 | 183 ms |
| Aug 15, 2026 | 181 ms |
| Aug 22, 2026 | 185 ms |
| Aug 29, 2026 | 183 ms |
| Sep 5, 2026 | 180 ms |
| Sep 12, 2026 | 178 ms |
| Sep 19, 2026 | 179 ms |
| Sep 26, 2026 | 183 ms |
| Oct 3, 2026 | 192 ms |
| Oct 10, 2026 | 201 ms |
| Oct 17, 2026 | 203 ms |
| Oct 24, 2026 | 210 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
How it loaded on a phone
0.5 s
1.0 s
1.5 s
2.0 s
2.5 s
2.9 s
3.4 s
3.9 s
Speed
Improve image delivery
1.2 s · 2.3 MB16 images could be 2.3 MB 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.
Reduce unused JavaScript
1.1 s · 660 KiBAbout 660 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.7 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.4 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, Google CDN and Clarity and others), adding 1.7 MB and 1.5 s of main-thread time.
Google Tag Manager adds 805 ms
805 msGoogle Tag Manager costs a phone 805 ms of main-thread work and 683 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 CDN adds 529 ms
529 msGoogle CDN costs a phone 529 ms of main-thread work and 736 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 280 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 72 KiBAbout 72 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.
Legacy JavaScript
150 ms · 10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
23 KiB9 files are served with short cache lifetimes, so returning visitors download them again (23 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.
1 checks passed
Server response: 133 ms
133 msYour server sent the HTML in 133 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.1 s
11.1 sYour largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “boxe-dunkerque-mobile”.
Time to Interactive: 20.6 s
20.6 sThe page becomes fully interactive after 20.6 s. Good is under 3.8 s.
Total Blocking Time: 916 ms
916 msScripts block taps and scrolling for 916 ms in total while the page loads. Good is under 200 ms.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 163 ms to 210 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.6 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.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 193 ms
193 msReal visitors wait 193 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 515 ms
515 msReal visitors wait 515 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.025
0.025The layout barely moves while loading (CLS 0.025, good is under 0.1).
Images and page weight
Page weight: 6.7 MB in 108 requests
6.7 MBYour homepage downloads 6.7 MB in 108 requests on a phone: images 4.3 MB (43), scripts 1.5 MB (28) and other files 577 KiB (24). Under 2 MB keeps phones on slow connections fast.
11 images far larger than shown
912 KiB11 images are downloaded at several times the size a phone draws them, for example armeedusalut-image-site-internet-champs-daction-grand-age-1- at 1,200 px wide, shown at 351 px. Resized copies would save about 912 KiB.
18 images in older formats
18 images (3.7 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.
12 images below the first screen load straight away
12 images further down the page (2.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.9 g of CO₂ per visit
1.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.89 g of CO₂e: 226.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (51 elements)
All page content should be contained by landmarks: 51 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
8 form fields without a label
8 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
158 internal links, 32 external
The homepage links to 158 pages on armeedusalut.fr and 32 external pages.
8 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “L'Armée du Salut œuvre chaque jour pour venir en aide à ceux qui en ont le plus besoin. Soutenez nos actions et contrib…”.
One H1 headline
Your main headline reads: “Transformer des vies”.
Title: 53 characters
Your title is a healthy 53 characters: “L'Armée du Salut : Organisation humanitaire en France”.
Canonical URL set
The canonical URL is https://www.armeedusalut.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://armeedusalut.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: 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 (1,031 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.armeedusalut.fr/llms.txt (6 KiB, 48 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
6 pages without a meta description
https://www.armeedusalut.fr/actualites, https://www.armeedusalut.fr/contact, https://www.armeedusalut.fr/vous-etes-donateurs, https://www.armeedusalut.fr/vous-etes-salutiste, https://www.armeedusalut.fr/gouvernance and https://www.armeedusalut.fr/documents-de-reference have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 68 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.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=20264448&tm=gtm002&Ver=2&mid=fb3471f7-707f-4e35-be94-312d80902680&bo=3&page_path=%2F&tpp=1&spa=Y&r=<=2214&p=https%3A%2F%2Fwww.armeedusalut.fr%2F&pi=918639831&lg=en-U.
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 ()”.
2 checks passed
Tap targets are thumb-sized
12 of 12 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 505 words of copy
The homepage carries about 505 words of visible text.
5 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
4 short forms
4 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and Matomo.
Direct contact links
Visitors can reach you directly: 1 phone link 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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Microsoft Clarity and 1 more (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
29 other companies contacted
Loading the homepage contacts 29 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 armeedusalut.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 | Matomo | Microsoft Clarity
- Hosting
- Infomaniak
Company
- Employees
- 42
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on armeedusalut.fr, including 16 speed 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.