staenk.com website review

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

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

The page has 2,133 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.

1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.

2 third-party services load with your homepage (Google Fonts and FontAwesome CDN), adding 272 KiB and 1 ms of main-thread time.

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 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Partner-RGB”.

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

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

1 image 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.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

Interactive controls must not be nested: 7 elements on the page fail this check, rated serious by axe-core.

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

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

There are 2 <h1> headlines (“NOUS SOMMES L'AGENCE WEBMARKETINGQUE VOUS ATTENDI…” and “WHAT'SSTÆNK?”). One clear main headline is easier for people and search engines.

The homepage links to 92 pages on staenk.com and 12 external pages.

There is no https://staenk.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://staenk.com/agence-pour-les-organismes-de-formation has no <h1> headline, so visitors and search engines get no clear main topic.

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

5 of 17 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.

Your longest form asks for 21 fields (9 required). Every extra field lowers completion.

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 1,742 words of visible text.

Opening the homepage sets 3 cookies (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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.