Website review, no card needed
savvy-viva.com website review
Visit site (opens in a new tab)Reviewed 6 November 202634 issues · 72 checks
This review found 34 issues worth fixing on savvy-viva.com, 18 of them high impact, across 72 checks. The most urgent: reduce unused CSS. 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
63D- #119,824 of 126,210 reviewed websitesbeats 4%
- #68,824 of 70,393 online storesbeats 2%
- #62,780 of 63,915 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused CSS
80.8 s · 1.1 MBAbout 1.1 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 80.8 s faster on a phone.
Use efficient cache lifetimes
35.3 s · 8.2 MB289 files are served with short cache lifetimes, so returning visitors download them again (8.2 MB).
Reduce unused JavaScript
11.1 s · 1.8 MBAbout 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.1 s faster on a phone.
Render-blocking requests
7.8 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.8 s.
Google Tag Manager adds 1.4 s
1.4 sGoogle Tag Manager costs a phone 1.4 s of main-thread work and 2.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 33
33/100Your mobile performance score is 33. 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.8 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 (Google Tag Manager, trackcollect.com and cloudfront.net and others), adding 3.7 MB and 2.4 s of main-thread time.
trackcollect.com adds 274 ms
274 mstrackcollect.com costs a phone 274 ms of main-thread work and 143 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.
cloudfront.net adds 169 ms
169 mscloudfront.net costs a phone 169 ms of main-thread work and 525 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.
Klaviyo adds 140 ms
140 msKlaviyo costs a phone 140 ms of main-thread work and 411 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.
1,639 HTML elements
The page has 1,639 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 247 ms. During a long task the page ignores taps.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Legacy JavaScript
100 ms · 49 KiBPolyfills for old browsers add 49 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Improve image delivery
66 KiB1 image could be 66 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 28 ms
28 msYour server sent the HTML in 28 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 53.6 s
53.6 sThe first text or image appears after 53.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 117.8 s
117.8 sYour largest element takes 117.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Type of error: The URLs you aimed to whitelist in our Dashb…”.
Speed Index: 53.6 s
53.6 sVisually, the page fills in at 53.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 126.0 s
126.0 sThe page becomes fully interactive after 126.0 s. Good is under 3.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Not enough real-visitor data yet
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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 26.8 MB in 1,376 requests
26.8 MBYour homepage downloads 26.8 MB in 1,376 requests on a phone: images 8.8 MB (515), stylesheets 7.4 MB (125) and scripts 7.1 MB (361). Under 2 MB keeps phones on slow connections fast.
About 7.6 g of CO₂ per visit
7.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.61 g of CO₂e: 912.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
37 images without alt text
37 images have no alt text, which hurts accessibility and image search.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h4 → h6, h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 24 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 4 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No XML sitemap
No XML sitemap at https://savvy-viva.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at savvy-viva.com/robots.txt, the first file search crawlers ask for.
102 internal links, 8 external
The homepage links to 102 pages on savvy-viva.com and 8 external pages.
6 checks passed
Meta description: 107 characters
Your meta description is 107 characters: “VIVA Products is a female products company on a mission to reshape the culture surrouding female sexuality.”.
One H1 headline
Your main headline reads: “Your pleasure, your rules.”.
Title: 43 characters
Your title is a healthy 43 characters: “Redefining Female Sexuality | VIVA Products”.
Canonical URL set
The canonical URL is https://savvy-viva.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
No llms.txt
There is no https://savvy-viva.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.
1 checks passed
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Other pages
2 pages share a title
https://savvy-viva.com/products/lube and https://savvy-viva.com/products/bundle-lube all use the title “Water Based Lube – VIVA”. 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://savvy-viva.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://savvy-viva.com/products/lube, https://savvy-viva.com/products/bundle-lube-1 and https://savvy-viva.com/products/bundle-lube use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://savvy-viva.com/pages/senna-1 has 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 47 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
1 broken image
1 image failed to load on a phone, for example https://cdn.shrinetheme.com/IMG_6535.png.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Only about 114 words
The homepage has only about 114 words of visible text; thin pages give Google and first-time buyers little to go on.
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 risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
4 checks passed
10 calls to action
The homepage has 10 calls to action, for example “SHOP BESTSELLERS”, “Shipping treshold $77.56 BUY NOW” and “15$ Gift Card $0.00 BUY NOW”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 62 testimonial or review blocks, 5 trust badges and “100k+ Customers”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and Cloudflare Web Analytics.
Privacy and tracking
5 trackers load before any consent
5Before 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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
44 other companies contacted
Loading the homepage contacts 44 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 savvy-viva.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Black Crow Ai That Delivers · Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · Gempages Builder · One Click Upsell · postscript.io
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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on savvy-viva.com, including 17 speed issues, 2 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.