Website review, no card needed
vagyrejuvenation.com website review
Visit site (opens in a new tab)Reviewed 9 November 202643 issues · 90 checks
This review found 43 issues worth fixing on vagyrejuvenation.com, 13 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
80B- #49,053 of 126,287 reviewed websitesbeats 55%
- #32,161 of 70,419 online storesbeats 48%
- #30,881 of 63,932 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 104 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 106 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 113 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 121 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 121 ms |
| Sep 5, 2026 | 122 ms |
| Sep 12, 2026 | 123 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 126 ms |
| Oct 17, 2026 | 131 ms |
| Oct 24, 2026 | 138 ms |
| Oct 31, 2026 | 143 ms |
| Nov 7, 2026 | 143 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.1 s
2.2 s
3.2 s
4.3 s
5.4 s
6.5 s
7.5 s
8.6 s
Speed
Reduce unused JavaScript
4.0 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.
Use efficient cache lifetimes
3.5 s · 1.2 MB16 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.6 s
A phone's processor spends 6.6 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (route.com, rebuyengine.com and Shopify and others), adding 2.4 MB and 1.6 s of main-thread time.
route.com adds 905 ms
905 msroute.com costs a phone 905 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 526 ms. During a long task the page ignores taps.
Duplicated JavaScript
486 KiB486 KiB JavaScript is shipped twice across bundles.
Improve image delivery
350 ms · 86 KiB2 images could be 86 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.
Reduce unused CSS
300 ms · 80 KiBAbout 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
rebuyengine.com adds 301 ms
301 msrebuyengine.com costs a phone 301 ms of main-thread work and 767 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.
Render-blocking requests
300 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
2,150 HTML elements
The page has 2,150 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 127 ms
127 msShopify costs a phone 127 ms of main-thread work and 347 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.
Legacy JavaScript
150 ms · 62 KiBPolyfills for old browsers add 62 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 21.0 s
21.0 sYour largest element takes 21.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Vagy Rejuvenation”.
Time to Interactive: 24.2 s
24.2 sThe page becomes fully interactive after 24.2 s. Good is under 3.8 s.
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Tap response (INP) got 38% slower for real visitors
+38%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 104 ms to 143 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 143 ms
143 msReal visitors wait 143 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 509 ms
509 msReal visitors wait 509 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.3 MB in 271 requests
7.3 MBYour homepage downloads 7.3 MB in 271 requests on a phone: scripts 2.3 MB (93), media 2.0 MB (1) and images 1.9 MB (34). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
BANNER_MOBIL_VAGY_BLACK_FRIDAY_NOVIEMBRE.jpg 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).
3 images far larger than shown
136 KiB3 images are downloaded at several times the size a phone draws them, for example ChatGPT_Image_9_sept_2026_17_56_20.png at 938 px wide, shown at 235 px. Resized copies would save about 136 KiB.
8 images below the first screen load straight away
8 images further down the page (360 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.1 g of CO₂ per visit
2.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.08 g of CO₂e: 249.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (27 elements)
All page content should be contained by landmarks: 27 elements on the page fail this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 4 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (17 characters)
Your title is only 17 characters: “Vagy Rejuvenation”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“.logo_image { max-height: unset!important; width:…” and “.logo_image { max-height: unset!important; width:…”). One clear main headline is easier for people and search engines.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
133 internal links, 5 external
The homepage links to 133 pages on vagyrejuvenation.com and 5 external pages.
5 checks passed
Meta description: 117 characters
Your meta description is 117 characters: “We are a Latina-owned, woman-owned and founded business dedicated to the intimate health care of women and men alike.”.
Canonical URL set
The canonical URL is https://vagyrejuvenation.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://vagyrejuvenation.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (927 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://vagyrejuvenation.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages point its canonical at the homepage
https://vagyrejuvenation.com/products/v-balance-esencial, https://vagyrejuvenation.com/products/vagylactic-neutral, https://vagyrejuvenation.com/products/jabon-intimo-la-flor and https://vagyrejuvenation.com/products/lubrilove declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
5 pages share a title
/, https://vagyrejuvenation.com/products/v-balance-esencial, https://vagyrejuvenation.com/products/vagylactic-neutral, https://vagyrejuvenation.com/products/jabon-intimo-la-flor and https://vagyrejuvenation.com/products/lubrilove all use the title “Vagy Rejuvenation”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://vagyrejuvenation.com/collections/store-page has no meta description, so Google writes the search snippet from whatever text it finds.
8 pages share a meta description
https://vagyrejuvenation.com/collections/cuida, https://vagyrejuvenation.com/collections/limpia, https://vagyrejuvenation.com/collections/dale-placer and https://vagyrejuvenation.com/collections/complementa use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://vagyrejuvenation.com/collections/store-page, https://vagyrejuvenation.com/collections/cuida, https://vagyrejuvenation.com/collections/limpia, https://vagyrejuvenation.com/collections/dale-placer and https://vagyrejuvenation.com/collections/complementa have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 44 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
31 of 36 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 39 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 313 words of copy
The homepage carries about 313 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop” and “Contact us”.
11 calls to action
The homepage has 11 calls to action, for example “Shop”, “Shop all” and “Contact us”.
9 short forms
9 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Microsoft Clarity.
Phone number on the homepage
Your phone number is on the homepage.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 4 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.
25 cookies set on arrival
25Opening the homepage sets 25 cookies (measured from a US location before any click).
No consent tool detected
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.
46 other companies contacted
Loading the homepage contacts 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at vagyrejuvenation.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Weglot Translate Your Store · Sc Easy Redirects · Microsoft Clarity · Rebuy Personalization Engine · Pagefly Ai Page Builder · Judge Me Reviews · Gift Box · Inbox · Route Protection Tracking · klaviyo.com · nfcube.com · nice-team.net · hyros.com · cloudfront.net
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on vagyrejuvenation.com, including 21 speed issues, 3 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.