Website review, no card needed
meetjovi.com website review
Visit site (opens in a new tab)Reviewed 16 November 202633 issues · 87 checks
This review found 33 issues worth fixing on meetjovi.com, 6 of them high impact, across 87 checks. The most urgent: page weight: 10.7 MB in 320 requests. 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
88B- #5,449 of 113,933 reviewed websitesbeats 93%
- #3,069 of 65,819 online storesbeats 93%
- #2,978 of 60,228 Shopify storesbeats 92%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.8 s |
| Nov 14, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 123 ms |
| Jun 6, 2026 | 128 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 130 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 128 ms |
| Jul 11, 2026 | 128 ms |
| Jul 18, 2026 | 122 ms |
| Jul 25, 2026 | 121 ms |
| Aug 1, 2026 | 116 ms |
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 120 ms |
| Aug 22, 2026 | 119 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 120 ms |
| Sep 12, 2026 | 115 ms |
| Sep 19, 2026 | 113 ms |
| Sep 26, 2026 | 119 ms |
| Oct 3, 2026 | 113 ms |
| Oct 10, 2026 | 120 ms |
| Oct 17, 2026 | 120 ms |
| Oct 24, 2026 | 114 ms |
| Oct 31, 2026 | 112 ms |
| Nov 7, 2026 | 111 ms |
| Nov 14, 2026 | 112 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
Speed
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 1.6 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 (Yotpo, rebuyengine.com and Shopify and others), adding 1.3 MB and 1.1 s of main-thread time.
Improve image delivery
1,003 KiB13 images could be 1,003 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 75
75/100Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
666 KiBAbout 666 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
300 ms · 337 KiB27 files are served with short cache lifetimes, so returning visitors download them again (337 KiB).
Render-blocking requests
300 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
rebuyengine.com adds 191 ms
191 msrebuyengine.com costs a phone 191 ms of main-thread work and 331 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,738 HTML elements
The page has 1,738 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 198 ms. During a long task the page ignores taps.
Reduce unused CSS
91 KiBAbout 91 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
72 KiBPolyfills for old browsers add 72 KiB JavaScript that modern phones do not need.
Minify JavaScript
10 ms · 26 KiB26 KiB could be saved by minifying JavaScript.
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: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 23.2 s
23.2 sThe page becomes fully interactive after 23.2 s. Good is under 3.8 s.
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 371 ms
371 msScripts block taps and scrolling for 371 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 2.8 s
2.8 sYour largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “You’ve pushed through period cramps long enough.”. Most of its time is element render delay (2.6 s).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 113 ms
113 msReal visitors wait 113 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 742 ms
742 msReal visitors wait 742 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 123 ms to 112 ms 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: 10.7 MB in 320 requests
10.7 MBYour homepage downloads 10.7 MB in 320 requests on a phone: media 5.9 MB (1), images 1.8 MB (27) and scripts 1.6 MB (121). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
313 KiB3 images are downloaded at several times the size a phone draws them, for example 028A9299_websize_067d0662-0c98-422d-bea4-893e0aaf4f1a.jpg at 1,067 px wide, shown at 147 px. Resized copies would save about 313 KiB.
About 3.0 g of CO₂ per visit
3.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.04 g of CO₂e: 365.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Scrollable region must have keyboard access (7 elements)
Scrollable region must have keyboard access: 7 elements on the page fail this check, rated serious by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
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.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Headings skip levels
Headings skip levels (h3 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 53 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (184 characters)
Your meta description is 184 characters; Google truncates after about 160, so the end of your pitch is cut.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
80 internal links, 8 external
The homepage links to 80 pages on meetjovi.com and 8 external pages.
7 checks passed
One H1 headline
Your main headline reads: “You’ve pushed through period cramps long enough.”.
Title: 59 characters
Your title is a healthy 59 characters: “Meet Jovi | Drug-free, reusable relief for menstrual cramps”.
Canonical URL set
The canonical URL is https://meetjovi.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.
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://meetjovi.com/sitemap.xml.
AI search readiness
4 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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,509 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://meetjovi.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://meetjovi.com/products/band-patch-pack is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://meetjovi.com/pages/faq and https://meetjovi.com/apps/postscript/landing_pages/19024/BFCM26 have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages share a meta description
https://meetjovi.com/collections/jovi-homepage, https://meetjovi.com/pages/how-it-works-1, https://meetjovi.com/blogs/news, https://meetjovi.com/collections/adhesive, https://meetjovi.com/collections/accessories and https://meetjovi.com/pages/how-to-use use the same meta description. A description written for each page earns more clicks.
10 pages without an H1
https://meetjovi.com/collections/jovi-homepage, https://meetjovi.com/pages/how-it-works-1, https://meetjovi.com/pages/our-story, https://meetjovi.com/pages/faq, https://meetjovi.com/collections/shop and https://meetjovi.com/collections/adhesive and 4 others 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 26 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.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 broken images
3 images failed to load on a phone, for example https://meetjovi.com/.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
3 JavaScript errors while loading
3 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
21 of 24 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
About 1,133 words of copy
The homepage carries about 1,133 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “TRY JOVI”.
14 calls to action
The homepage has 14 calls to action, for example “Shop Jovi”, “Shop All” and “Shop Jovi Show menu”.
19 short forms
19 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 34 testimonial or review blocks, a star rating and “Trusted by 200,000+ customers”.
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
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
34 cookies set on arrival
34Opening the homepage sets 34 cookies, 3 of them by other companies (measured from a US location before any click).
91 other companies contacted
Loading the homepage contacts 91 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 meetjovi.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 25 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Cookieyes Gdpr · Yotpo Loyalty Rewards · Postscript Sms Marketing · Paywhirl Subscriptions · Pagefly Ai Page Builder · Yotpo Product Reviews · Mntn · Brella · Klaviyo Email Marketing Sms · Test Sms · Freegifts · meetjovi.com · crazyegg.com · nfcube.com · upsell-apps.com · yottaa.com · powr.io · amazonaws.com · retention.com · hikeorders.com · rechargecdn.com · rebuyengine.com · govx.com · bogos.io · merchantyard.com
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
- Hosting
- Shopify
Company
- Headquarters
- Rexburg
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on meetjovi.com, including 14 speed issues, 2 SEO issues and 1 conversion gap. 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.