replenzalabs.com website review

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

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

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

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

8 third-party services load with your homepage (Klaviyo, Google Tag Manager and Unpkg and others), adding 1.0 MB and 215 ms of main-thread time.

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

Klaviyo costs a phone 78 ms of main-thread work and 317 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 21 ms of main-thread work and 361 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 long tasks block the main thread while loading, the longest for 67 ms. During a long task the page ignores taps.

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

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

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

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

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

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

Your largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nutritional Support for your GLP-1 Weight Loss Journey”. Most of its time is element render delay (2.5 s).

Your homepage downloads 4.2 MB in 231 requests on a phone: images 2.5 MB (28), scripts 809 KiB (86) and other files 706 KiB (71). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.

7 images are downloaded at several times the size a phone draws them, for example frother-bundle-image_2.webp at 1,231 px wide, shown at 350 px. Resized copies would save about 592 KiB.

1 image (647 KiB) is 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.

8 images further down the page (677 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 1.20 g of CO₂e: 144.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

Your title is only 9 characters: “Replenza™”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

Your <h1> is empty.

The homepage links to 32 pages on replenzalabs.com and 6 external pages.

https://www.replenzalabs.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.replenzalabs.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.replenzalabs.com/products/replenza-duo-bundle and https://www.replenzalabs.com/products/replenza-bundle all use the title “Replenza Bundle”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.replenzalabs.com/customer_authentication/redirect, https://www.replenzalabs.com/pages/the-science, https://www.replenzalabs.com/pages/backed-by-our-advisory-board, https://www.replenzalabs.com/pages/why-replenza, https://www.replenzalabs.com/blogs/news and https://www.replenzalabs.com/pages/faq and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.replenzalabs.com/products/replenza-duo-bundle and https://www.replenzalabs.com/products/replenza-bundle use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.replenzalabs.com/products/replenza-duo-bundle, whose canonical is https://www.replenzalabs.com/products/replenza-bundle. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.replenzalabs.com/customer_authentication/redirect, https://www.replenzalabs.com/pages/the-science, https://www.replenzalabs.com/pages/backed-by-our-advisory-board, https://www.replenzalabs.com/pages/why-replenza, https://www.replenzalabs.com/pages/faq and https://www.replenzalabs.com/pages/answers have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

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

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

The homepage carries about 586 words of visible text.

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