neova.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and Google Tag Manager and others), adding 1.4 MB and 1.0 s of main-thread time.

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

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

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

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

Klaviyo costs a phone 293 ms of main-thread work and 659 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.

Shopify costs a phone 330 ms of main-thread work and 182 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.

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

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

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

Desktop scores 91 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.

6 KiB could be saved by minifying CSS.

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.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 19.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “NEOVA - Tricomin - National Hair Day - Two white Tricomin h…”.

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

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

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

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

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

Your homepage downloads 4.4 MB in 280 requests on a phone: images 1.8 MB (39), scripts 1.6 MB (106) and other files 780 KiB (120). Under 2 MB keeps phones on slow connections fast.

2 images (133 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.

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

17 tap targets are too small or too close together to hit reliably with a finger.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 166 pages on neova.com and 5 external pages.

https://www.neova.com/products/body-repair is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

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.

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

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