movework.fr website review

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

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

About 691 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

Google Tag Manager costs a phone 1.4 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 5.2 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

5 third-party services load with your homepage (Google Tag Manager, Hubspot and LinkedIn Ads and others), adding 1.2 MB and 1.5 s of main-thread time.

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

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

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

Polyfills for old browsers add 14 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 17.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Réinventez vos services avec une plateforme d’exigence Du t…”. Most of its time is resource load delay (8.6 s).

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

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

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

Scripts block taps and scrolling for 675 ms in total while the page loads. Good is under 200 ms.

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

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.

Your homepage downloads 4.5 MB in 138 requests on a phone: images 2.2 MB (14), scripts 1.6 MB (52) and fonts 457 KiB (6). Under 2 MB keeps phones on slow connections fast.

gemini_generated_image_e4nhlje4nhlje4nh-scaled.png weighs 902 KiB. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example gemini_generated_image_e4nhlje4nhlje4nh-scaled.png at 2,000 px wide, shown at 330 px. Resized copies would save about 1.2 MB.

7 images (1.9 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.

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

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

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

7 tap targets are too small or too close together to hit reliably with a finger.

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

4 visible links have no text or label, so screen readers cannot say where they go.

Your title is 72 characters, so Google will cut it off around 60: “MoveWORK | Plateforme SaaS all-in-one de pilotage du Facility Management”.

The homepage links to 76 pages on movework.fr and 7 external pages.

/extensions-add-ons, /technologies, /grands-groupes and /engagements-rse took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.

4 images failed to load on a phone, for example https://movework.fr/wp-content/uploads/2025/08/sc-client-01.png.

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

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 (Not Found)”.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

movework.fr has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Social proof on the homepage: 5 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

The homepage carries about 739 words of visible text.

DMARC is set to p=none, so mail pretending to be movework.fr is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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