staffizy.com website review

31 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

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

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

About 177 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 770 ms faster on a phone.

2 images could be 90 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

8 third-party services load with your homepage (LinkedIn, Google Tag Manager and LinkedIn Ads and others), adding 536 KiB and 139 ms of main-thread time.

About 29 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 30 ms faster on a phone.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB could be saved by minifying JavaScript.

3 KiB could be saved by minifying CSS.

Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Intérim”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 images (148 KiB) 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.

1 image further down the page (53 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

1 image has no alt text, which hurts accessibility and image search.

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

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

25 form fields have no label, so screen readers announce an empty box and autofill guesses.

Your title is only 19 characters: “Accueil :: Staffizy”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://staffizy.com/sitemap.xml, so Google discovers your pages only by following links.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 15 pages on staffizy.com and 3 external pages.

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.

There is no https://staffizy.com/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.

https://staffizy.com/interim-digital, https://staffizy.com/qui-sommes-nous and https://staffizy.com/contact all use the title “Staffizy”. Search engines can't tell which page to show for a search, so each competes with the others.

https://staffizy.com/interim-digital, https://staffizy.com/qui-sommes-nous and https://staffizy.com/contact have no meta description, so Google writes the search snippet from whatever text it finds.

https://staffizy.com/qui-sommes-nous, https://staffizy.com/contact, https://staffizy.com/mentions-legales and https://staffizy.com/politique-de-confidentialite have no <h1> headline, so visitors and search engines get no clear main topic.

https://staffizy.com/qui-sommes-nous and https://staffizy.com/mentions-legales have 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.

https://staffizy.com/gestion-digitale, https://staffizy.com/interim-digital, https://staffizy.com/qui-sommes-nous and https://staffizy.com/contact took over 3 s to send their HTML from our server.

We fetched 6 pages linked from your homepage and read each the way a search engine does.

1 image failed to load on a phone, for example https://www.joblink.fr/sites/joblink/files/2017-07/logo.png.

6 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 image is served at too low a resolution for sharp phone screens.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your longest form asks for 11 fields (0 required). Every extra field lowers completion.

The homepage has only about 209 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Opening the homepage sets 3 cookies, 1 of them by other companies (measured from a US location before any click).

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.

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