mtouton.com website review

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

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

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

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

6 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Hubspot and others), adding 982 KiB and 540 ms of main-thread time.

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

Google Tag Manager costs a phone 316 ms of main-thread work and 361 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.

FontAwesome CDN costs a phone 104 ms of main-thread work and 490 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.

5 long tasks block the main thread while loading, the longest for 179 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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

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

Real visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.

Real visitors wait 883 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1920x850 Wilde Irish Gin.jpg.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image (65 KiB) is 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 0.51 g of CO₂e: 61.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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.

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

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

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

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

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

Your title is 103 characters, so Google will cut it off around 60: “Premium Wine & Spirits Importer and Distributor | Monsieur Touton Selection | Monsieur To…”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

5 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 26 pages on mtouton.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.mtouton.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.mtouton.com/producers, https://www.mtouton.com/products, https://www.mtouton.com/locations, https://www.mtouton.com/team, https://www.mtouton.com/careers and https://www.mtouton.com/contact and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.mtouton.com/products, whose canonical is https://www.mtouton.com/products/state/NY. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.mtouton.com/products, https://www.mtouton.com/careers, https://www.mtouton.com/non-alcoholic, https://www.mtouton.com/producers/familia-fernandez-rivera, https://www.mtouton.com/products/ireland/15546-nv/wilde-irish-gin and https://www.mtouton.com/producers/champagne-charles-de-cazanove and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Microsoft Clarity (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 (measured from a US location before any click).

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