proconcept.ch website review

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

Your mobile performance score is 71 (desktop: 83). Pages that score under 90 lose visitors before the first paint.

6 third-party services load with your homepage (Google CDN, Usercentrics CMP and Google Tag Manager and others), adding 1.9 MB and 722 ms of main-thread time.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

About 725 KiB of JavaScript is downloaded but never used on this page.

Google CDN costs a phone 432 ms of main-thread work and 733 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.

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

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

forterro.com costs a phone 0 ms of main-thread work and 751 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.

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

About 61 KiB of CSS is downloaded but never applied on this page.

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

2 KiB could be saved by minifying CSS.

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

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

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

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

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

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 3.0 MB in 123 requests on a phone: scripts 1.5 MB (30), images 764 KiB (62) and other files 512 KiB (20). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example pexels-fauxels-3183197-1.jpg.webp at 2,000 px wide, shown at 390 px. Resized copies would save about 164 KiB.

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

5 buttons have no accessible name, so screen readers announce just “button”.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is 68 characters, so Google will cut it off around 60: “L'ERP suisse pour PME et ETI industrielles et de services | Forterro”.

Structured data found (FAQPage, Organization, WebPage and WebSite) but with 2 problems, for example “Organization: sameAs is not an absolute URL ("ProConcept ERP")”.

Open Graph is missing og:title, so shared links fall back to guesses.

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

The homepage links to 61 pages on proconcept.ch and 10 external pages.

There is no https://www.proconcept.ch/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://www.proconcept.ch/fr/ressource/demande-demo has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.proconcept.ch/fr/ressource/demande-demo has 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.

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

Large scripts ship without source maps.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

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