renewalliance.com website review

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

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

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

12 images could be 397 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

8 third-party services load with your homepage (Facebook, Klaviyo and Google/Doubleclick Ads and others), adding 1.4 MB and 395 ms of main-thread time.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 350 ms.

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

manuscdn.com costs a phone 0 ms of main-thread work and 852 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.

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

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

About 16 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 12.0 s. Good is under 3.8 s.

Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Fall Rejuvenation Special. Save 15 percent on all three-box…”.

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

7 images have no width and height attributes, so the layout jumps as each one loads.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.1 MB in 85 requests on a phone: scripts 1.1 MB (35), images 855 KiB (26) and fonts 131 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

Table header text should not be empty: 1 element on the page fails this check, rated minor by axe-core.

<td> elements in a large <table> do not have table headers. (1 element).

Your title is 66 characters, so Google will cut it off around 60: “Official Taut® Collagen USA | Beautiful Skin Without The Guesswork”.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

A phone browser shows 1,222 words, but the HTML your server sends has only 46. 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.

There is no https://www.renewskinco.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.

2 of 8 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 “Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR”.

Large scripts ship without source maps.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

Before a visitor clicks anything, the page loads Klaviyo (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.

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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.