renuebyscience.com website review

25 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

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

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

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

31 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

8 third-party services load with your homepage (sealsubscriptions.com, Shopify and avada.io and others), adding 2.3 MB and 1.3 s of main-thread time.

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

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

sealsubscriptions.com costs a phone 353 ms of main-thread work and 79 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.

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

About 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

40 KiB could be saved by minifying JavaScript.

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.

1 KiB JavaScript is shipped twice across bundles.

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 17.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Close-up of a person holding a supplement bottle labeled 'R…”.

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

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

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

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

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

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

Your homepage downloads 8.9 MB in 479 requests on a phone: images 3.6 MB (64), scripts 2.1 MB (181) and fonts 1.8 MB (28). Under 2 MB keeps phones on slow connections fast.

16 images are downloaded at several times the size a phone draws them, for example content_yearly-graph.webp at 2,752 px wide, shown at 358 px. Resized copies would save about 5.5 MB.

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

19 images (7.7 MB) 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.

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

hero_pets-mobile.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (3 elements).

Your title is only 16 characters: “Renue By Science”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

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

Your <h1> is empty.

The homepage links to 128 pages on renuebyscience.com and 7 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.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

There is no /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.

/pages/hsa-fsa-eligibility-on-renue-by-science, /collections/pets and /collections/regenerate have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/pets and /collections/regenerate have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

renuebyscience.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

renuebyscience.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

DMARC is set to p=none, so mail pretending to be renuebyscience.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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