Website review, no card needed
staffme.fr website review
Visit site (opens in a new tab)Reviewed 18 November 202626 issues · 81 checks
This review found 26 issues worth fixing on staffme.fr, 8 of them high impact, across 81 checks. The most urgent: render-blocking 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.3 s |
| Nov 14, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 226 ms |
| Jun 6, 2026 | 226 ms |
| Jun 13, 2026 | 226 ms |
| Jun 20, 2026 | 230 ms |
| Jun 27, 2026 | 232 ms |
| Jul 4, 2026 | 236 ms |
| Jul 11, 2026 | 242 ms |
| Jul 18, 2026 | 246 ms |
| Jul 25, 2026 | 247 ms |
| Aug 1, 2026 | 246 ms |
| Aug 8, 2026 | 246 ms |
| Aug 15, 2026 | 241 ms |
| Aug 22, 2026 | 239 ms |
| Aug 29, 2026 | 242 ms |
| Sep 5, 2026 | 239 ms |
| Sep 12, 2026 | 228 ms |
| Sep 19, 2026 | 227 ms |
| Sep 26, 2026 | 227 ms |
| Oct 3, 2026 | 226 ms |
| Oct 10, 2026 | 241 ms |
| Oct 17, 2026 | 245 ms |
| Oct 24, 2026 | 245 ms |
| Oct 31, 2026 | 252 ms |
| Nov 7, 2026 | 247 ms |
| Nov 14, 2026 | 245 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
1.5 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, TikTok and openai.com and others), adding 971 KiB and 558 ms of main-thread time.
Google Tag Manager adds 404 ms
404 msGoogle Tag Manager costs a phone 404 ms of main-thread work and 542 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.
Reduce unused JavaScript
397 KiBAbout 397 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 971 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 190 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 32 KiBAbout 32 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.
Improve image delivery
163 KiB2 images could be 163 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
33 KiB4 files are served with short cache lifetimes, so returning visitors download them again (33 KiB).
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
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: 44 ms
44 msYour server sent the HTML in 44 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 13.4 s
13.4 sThe page becomes fully interactive after 13.4 s. Good is under 3.8 s.
Largest Contentful Paint: 5.3 s
5.3 sYour largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user INP: 256 ms
256 msReal visitors wait 256 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 893 ms
893 msReal visitors wait 893 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 271 ms
271 msScripts block taps and scrolling for 271 ms in total while the page loads. Good is under 200 ms.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 226 ms to 245 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.3 MB in 56 requests
2.3 MBYour homepage downloads 2.3 MB in 56 requests on a phone: scripts 967 KiB (14), fonts 756 KiB (5) and images 268 KiB (17). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
119 KiB1 image is downloaded at several times the size a phone draws it, for example fr_fr_b2c_vacancy_slideview.avif at 3,000 px wide, shown at 342 px. Resized copies would save about 119 KiB.
1 image below the first screen load straight away
1 image further down the page (135 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.64 g of CO₂e: 77.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 use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
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. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
53 internal links, 20 external
The homepage links to 53 pages on staffme.fr and 20 external pages.
8 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Découvrez StaffMe : la plateforme unique en Europe pour trouver du renfort ou des missions en freelance et en intérim. …”.
One H1 headline
Your main headline reads: “Trouve du renfort ou des candidats”.
Title: 56 characters
Your title is a healthy 56 characters: “Trouvez un job ou du renfort, sans le chercher | Staffme”.
Canonical URL set
The canonical URL is https://www.staffme.fr/fr.
Structured data in place
Structured data found: 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.staffme.fr/sitemap.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (605 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.staffme.fr/llms.txt (54 KiB, 221 links), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://www.staffme.fr/fr/cadre-juridique has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 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.
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
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
8 of 9 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.
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 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.
Thin social proof
Social proof on the homepage: 28 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 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 796 words of copy
The homepage carries about 796 words of visible text.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and TikTok Pixel (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.
20 cookies set on arrival
20Opening the homepage sets 20 cookies, 2 of them by other companies (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.
10 other companies contacted
Loading the homepage contacts 10 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 staffme.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Combell NV
Company
- Headquarters
- Paris
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on staffme.fr, including 14 speed issues and 5 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.