technocoach.io website review

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

The HTML itself could arrive about 1.0 s sooner: redirects, a slow server response or missing compression delay everything after it.

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

Reduce initial server response time. Google estimates savings of 999 ms on a phone.

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

Your server takes 1.1 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

86 files are served with short cache lifetimes, so returning visitors download them again (203 KiB).

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

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

2 images could be 46 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

6 KiB could be saved by minifying JavaScript.

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 third-party service load with your homepage (Adobe TypeKit), adding 13 KiB and 1 ms of main-thread time.

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

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

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 text “Libérez-vous de votre dépendance technologique”. Most of its time is element render delay (6.1 s).

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

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 (87 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.

2 images further down the page (87 KiB) 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 0.19 g of CO₂e: 22.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.

No XML sitemap at https://technocoach.io/sitemaps.xml, so Google discovers your pages only by following links.

The homepage links to 18 pages on technocoach.io and 10 external pages.

There is no /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.

Your homepage links to /eShop, which answers with an error. Visitors hit a dead end and search engines drop it.

/opera has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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.

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