nuvocares.com website review

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

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

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

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

6 third-party services load with your homepage (Hubspot, hsappstatic.net and usemessages.com and others), adding 280 KiB and 150 ms of main-thread time.

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

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

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

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.

Your largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “INVU™ BY NUVO The non-stress test, taken at home. Nuvo is a…”.

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

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

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

7 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-17, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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.

6 images are downloaded at several times the size a phone draws them, for example if-cover-gvmh-dawn-v4.png at 1,200 px wide, shown at 112 px. Resized copies would save about 592 KiB.

Your homepage downloads 2.6 MB in 89 requests on a phone: images 2.1 MB (49), scripts 219 KiB (19) and fonts 169 KiB (4). Under 2 MB keeps phones on slow connections fast.

7 images further down the page (709 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (99 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 0.74 g of CO₂e: 88.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

34 images have no alt text, which hurts accessibility and image search.

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

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

Your meta description is 169 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 110 pages on nuvocares.com and 14 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.nuvocares.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.

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

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads HubSpot (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 6 cookies (measured from a US location before any click).

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