mecatran.com website review

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

5 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.7 s faster on a phone.

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

About 276 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

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

Polyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

5 third-party services load with your homepage (Google Tag Manager, Google Maps and Google Analytics and others), adding 293 KiB and 190 ms of main-thread time.

42 KiB could be saved by minifying CSS.

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

34 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.

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

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

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

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

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

The layout shifts by 0.125 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 8.3 MB in 126 requests on a phone: images 6.9 MB (71), scripts 719 KiB (38) and stylesheets 312 KiB (9). Under 2 MB keeps phones on slow connections fast.

2 images weigh 3.4 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example hand_mobile.jpg at 1,904 px wide, shown at 360 px. Resized copies would save about 2.2 MB.

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

18 images (4.4 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.

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

32 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 34 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.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 8 characters: “Mecatran”. 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.

There are 13 <h1> headlines (“Urbineris”, “Urbiplan” and “Urbiplan”). One clear main headline is easier for people and search engines.

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://www.mecatran.com/sitemap.xml, so Google discovers your pages only by following links.

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

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 14 pages on mecatran.com and 5 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://www.mecatran.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://www.mecatran.com/en and https://www.mecatran.com/fr all use the title “Mecatran”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mecatran.com/fr, https://www.mecatran.com/about/company, https://www.mecatran.com/about/philosophy, https://www.mecatran.com/about/products, https://www.mecatran.com/work/montpellier and https://www.mecatran.com/work/paris have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mecatran.com/about/company, https://www.mecatran.com/about/philosophy and https://www.mecatran.com/about/products have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mecatran.com/work/paris 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 6 pages linked from your homepage and read each the way a search engine does.

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

5 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://www.mecatran.com/en/' was loaded over HTTPS, but requested an insecure stylesheet '…”.

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

Chrome logged issues while loading the page (“Mixed content”).

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage carries about 1,074 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and 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 4 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.