univera.com website review

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

8 third-party services load with your homepage (Clarity, Klaviyo and gotolstoy.com and others), adding 2.1 MB and 1.0 s of main-thread time.

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

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

9 images could be 511 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Clarity costs a phone 341 ms of main-thread work and 30 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,179 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

LiveChat costs a phone 72 ms of main-thread work and 366 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.

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

11 long tasks block the main thread while loading, the longest for 167 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.

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

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

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

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.

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.

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

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

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

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

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

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

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

Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your homepage downloads 3.9 MB in 312 requests on a phone: scripts 1.7 MB (128), images 1.1 MB (39) and other files 858 KiB (124). Under 2 MB keeps phones on slow connections fast.

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

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

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

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

The homepage links to 97 pages on univera.com and 15 external pages.

https://newunivera.com/pages/guided-product-finder, https://newunivera.com/blogs/blogs and https://newunivera.com/blogs/press have no meta description, so Google writes the search snippet from whatever text it finds.

https://newunivera.com/pages/guided-product-finder, https://newunivera.com/pages/subscribe-and-save and https://newunivera.com/pages/new-website-guide have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Social proof on the homepage: 194 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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