renault.it website review

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

About 495 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

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

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

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

4 third-party services load with your homepage (Optanon, Google Tag Manager and Amazon Ads and others), adding 1.6 MB and 172 ms of main-thread time.

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

The page has 2,301 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Optanon costs a phone 116 ms of main-thread work and 444 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.

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

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

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

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

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.

Real visitors wait 608 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.26 (75th percentile). Good is under 0.1.

Your largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Il nostro sito utilizza cookie tecnici, necessari al corret…”.

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

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

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

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

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

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

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

Your homepage downloads 4.2 MB in 108 requests on a phone: images 3.0 MB (34), scripts 719 KiB (34) and fonts 307 KiB (6). Under 2 MB keeps phones on slow connections fast.

a150a947a4.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).

12 images (583 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.

1 image is downloaded at several times the size a phone draws it, for example renault-logo-0-1.png at 4,096 px wide, shown at 43 px. Resized copies would save about 187 KiB.

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

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

Your <h1> is empty.

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

The homepage links to 184 pages on renault.it and 25 external pages.

There is no https://www.renault.it/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.renault.it/comparatore-multi-modello.html, https://www.renault.it/veicoli-elettrici-ibridi/twingo-e-tech-elec/pre-configuratore.html and https://www.renault.it/veicoli-elettrici-ibridi/r4-e-tech-electric/pre-configuratore.html are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.renault.it/comparatore-multi-modello.html and https://www.renault.it/veicoli-elettrici-ibridi/twingo-e-tech-elec/pre-configuratore.html have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.renault.it/comparatore-multi-modello.html has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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.

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

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

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

Opening the homepage sets 2 cookies (measured from a US location before any click).

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