aazio.com website review

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

Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

13 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

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

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

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

4 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Google Analytics and others), adding 378 KiB and 234 ms of main-thread time.

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

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.

5 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

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

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

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

Visually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 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.

Your homepage downloads 23.8 MB in 89 requests on a phone: images 23.4 MB (73), scripts 381 KiB (8) and fonts 48 KiB (3). Under 2 MB keeps phones on slow connections fast.

14 images weigh 13.6 MB together. On a phone connection a single image that size takes seconds.

16 images are downloaded at several times the size a phone draws them, for example MICKEY-BOITE_Leonidas.jpg at 2,100 px wide, shown at 390 px. Resized copies would save about 6.8 MB.

40 images (20.5 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.

29 images further down the page (14.3 MB) 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 6.74 g of CO₂e: 809.2 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”.

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

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 form field has 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.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://aazio.com/sitemap.xml, so Google discovers your pages only by following links.

Open Graph is missing og:description, 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 37 pages on aazio.com and 1 external page.

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://aazio.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://aazio.com/en/home, https://aazio.com/en, https://aazio.com/en/case/cristal, https://aazio.com/en/case/liefmans, https://aazio.com/en/case/lupulus and https://aazio.com/en/case/danone and 5 others all use the title “Home”. Search engines can't tell which page to show for a search, so each competes with the others.

https://aazio.com/en, https://aazio.com/en/services/product-media, https://aazio.com/en/services/ownable-product, https://aazio.com/en/products, https://aazio.com/en/csr-sustainability and https://aazio.com/en/team and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://aazio.com/en/team and https://aazio.com/en/case/paix-dieu have 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 23 found) and read each the way a search engine does.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

Social proof on the homepage: 24 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 650 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 6 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.