suvera.com website review

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

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

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

8 third-party services load with your homepage (framerusercontent.com, Mixpanel and Cookiebot and others), adding 1.9 MB and 1.0 s of main-thread time.

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

framerusercontent.com costs a phone 760 ms of main-thread work and 1.1 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.

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

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

Cookiebot costs a phone 90 ms of main-thread work and 325 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.

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

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

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

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

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 12.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BG Image”.

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

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

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

Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

1 image is downloaded at several times the size a phone draws it, for example D9Jv535WXPtY3IHT2SZOPGxBkNQ.jpg at 1,514 px wide, shown at 350 px. Resized copies would save about 36 KiB.

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

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

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

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

There are 2 <h1> headlines (“Proactive care on autopilot” and “Proactive care on autopilot”). One clear main headline is easier for people and search engines.

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

The homepage links to 96 pages on suvera.com and 3 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://suvera.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.

https://suvera.com/resources/reports and https://suvera.com/tools all use the title “Reports”. Search engines can't tell which page to show for a search, so each competes with the others.

https://suvera.com/resources/reports and https://suvera.com/tools use the same meta description. A description written for each page earns more clicks.

https://suvera.com/winter-release-2026, https://suvera.com/pricing, https://suvera.com/resources/blog, https://suvera.com/resources/reports, https://suvera.com/tools and https://suvera.com/safety and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://assets.calendly.com/assets/external/widget.css' from origin 'https://suvera.com' h…”.

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

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

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

Before a visitor clicks anything, the page loads Mixpanel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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