voldt.it website review

29 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 11.3 s faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and azurefd.net and others), adding 1.1 MB and 646 ms of main-thread time.

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

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

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

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

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

azurefd.net costs a phone 53 ms of main-thread work and 337 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 long tasks block the main thread while loading, the longest for 134 ms. During a long task the page ignores taps.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 23.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Grey Polestar 2 charging with a Voldt EV charging cable at …”.

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

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

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

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

Your homepage downloads 6.8 MB in 388 requests on a phone: images 4.1 MB (67), other files 1.3 MB (241) and scripts 1.1 MB (68). Under 2 MB keeps phones on slow connections fast.

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

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 10 elements on the page fail this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 68 characters, so Google will cut it off around 60: “Voldt® Vendita Cavi di ricarica e adattatori per ogni auto elettrica”.

The homepage links to 150 pages on voldt.it and 5 external pages.

https://voldt.it/blogs/notizie and https://voldt.it/pages/diventare-partner have no meta description, so Google writes the search snippet from whatever text it finds.

https://voldt.it/pages/chi-siamo and https://voldt.it/pages/diventare-partner have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

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

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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.

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

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