uviron.com website review

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

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

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

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

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

8 third-party services load with your homepage (Intercom, Shopify and omnisnippet1.com and others), adding 2.3 MB and 423 ms of main-thread time.

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

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

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

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

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

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

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.

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.

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

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

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

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

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

Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

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

Your homepage downloads 4.9 MB in 216 requests on a phone: images 2.9 MB (33), scripts 884 KiB (69) and other files 850 KiB (93). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.40 g of CO₂e: 168.0 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”.

Some list items are not inside a list.

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

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

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

8 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

Structured data found (AutoPartsStore, Organization, ProfessionalService and WebSite) but with 2 problems, for example “WebSite: missing name”.

5 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 68 pages on uviron.com and 14 external pages.

A phone browser shows 1,230 words, but the HTML your server sends has only 335. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

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

1 error was logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'dataset')”.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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