ultraceuticals.com website review

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

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

8 third-party services load with your homepage (alia-prod.com, rebuyengine.com and Reviews.io and others), adding 2.3 MB and 1.3 s of main-thread time.

About 890 KiB of JavaScript is downloaded but never used on this page.

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

alia-prod.com costs a phone 455 ms of main-thread work and 417 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.

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

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

rebuyengine.com costs a phone 298 ms of main-thread work and 692 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.

Reviews.io costs a phone 239 ms of main-thread work and 332 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,603 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Google CDN costs a phone 158 ms of main-thread work and 297 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 28 ms of main-thread work and 425 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 long tasks block the main thread while loading, the longest for 244 ms. During a long task the page ignores taps.

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

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

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

7 KiB could be saved by minifying JavaScript.

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 32.1 s. Good is under 3.8 s.

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

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

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

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

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

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

5 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' tap response (inp) went from 159 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.3 MB in 304 requests on a phone: media 4.3 MB (4), images 2.6 MB (88) and scripts 2.0 MB (86). Under 2 MB keeps phones on slow connections fast.

23 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

7 images are downloaded at several times the size a phone draws them, for example 1080 at 1,080 px wide, shown at 170 px. Resized copies would save about 470 KiB.

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

38 buttons have no accessible name, so screen readers announce just “button”.

Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

Headings skip levels (h2 → h5 and h2 → h5), 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.

There are 9 <h1> headlines (“FREE GIFT WHEN YOU SPEND $200”, “COMPLEX SCIENCE SIMPLE SOLUTIONS” and “MASTERING THE COMPLEXITY OF SKIN SCIENCE”). One clear main headline is easier for people and search engines.

Your meta description is 315 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.

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

The homepage links to 147 pages on ultraceuticals.com and 6 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.

https://ultraceuticals.com/pages/holiday-gift-sets has no meta description, so Google writes the search snippet from whatever text it finds.

https://ultraceuticals.com/pages/offers, https://ultraceuticals.com/collections/sets, https://ultraceuticals.com/collections/all, https://ultraceuticals.com/collections/best-sellers, https://ultraceuticals.com/collections/serums and https://ultraceuticals.com/collections/face-sunscreen and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

The page uses urgency cues (a countdown or limited-time wording).

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