Website review, no card needed
mysexmd.com website review
Visit site (opens in a new tab)Reviewed 6 November 202644 issues · 96 checks
This review found 44 issues worth fixing on mysexmd.com, 17 of them high impact, across 96 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
Speed
Reduce unused JavaScript
2.7 s · 694 KiBAbout 694 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Render-blocking requests
2.8 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Mobile performance score: 23
23/100Your mobile performance score is 23. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.2 s
A phone's processor spends 7.2 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,968 HTML elements
The page has 4,968 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Clarity and Shopify and others), adding 668 KiB and 748 ms of main-thread time.
Use efficient cache lifetimes
300 ms · 341 KiB34 files are served with short cache lifetimes, so returning visitors download them again (341 KiB).
Improve image delivery
449 KiB48 images could be 449 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 338 ms. During a long task the page ignores taps.
Reduce unused CSS
300 ms · 27 KiBAbout 27 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.
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.
Minify JavaScript
150 ms · 17 KiB17 KiB could be saved by minifying JavaScript.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
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: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 17.3 s
17.3 sYour largest element takes 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Trusted By 250k+ Users Evidence-Based Sexual Healthcare Awa…”.
Time to Interactive: 25.1 s
25.1 sThe page becomes fully interactive after 25.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.459
0.459The layout shifts by 0.459 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 908 ms
908 msScripts block taps and scrolling for 908 ms in total while the page loads. Good is under 200 ms.
65 images without width and height
65 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 101 ms
101 msReal visitors wait 101 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (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: 343 ms
343 msReal visitors wait 343 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 146 ms to 124 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 4.6 MB in 351 requests
4.6 MBYour homepage downloads 4.6 MB in 351 requests on a phone: scripts 2.3 MB (101), images 1.4 MB (145) and other files 661 KiB (79). Under 2 MB keeps phones on slow connections fast.
About 1.3 g of CO₂ per visit
1.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.32 g of CO₂e: 157.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
9 images without alt text
9 images have 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.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails 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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (226 characters)
Your meta description is 226 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (Organization) but with 2 problems, for example “Organization: logo is not an absolute URL ("//mv.health/cdn/shop/files/MV.Health-Logo-Horisontal-Gr…”.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
119 internal links, 40 external
The homepage links to 119 pages on mysexmd.com and 40 external pages.
5 checks passed
Title: 52 characters
Your title is a healthy 52 characters: “Leader in Women's & Men's Health Devices | MV.Health”.
Canonical URL set
The canonical URL is https://mv.health/.
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://mv.health/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 description; sameAs (social profiles) and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (10,339 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://mv.health/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://mv.health/pages/molto-for-women is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages share a title
https://mv.health/collections/all-products, https://mv.health/collections/for-women and https://mv.health/collections/for-men all use the title “Award - MV.Health: Leader in Women's & Men's Health”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://mv.health/pages/awards, https://mv.health/pages/reviews, https://mv.health/pages/press, https://mv.health/pages/faq, https://mv.health/pages/contact-us and https://mv.health/pages/molto-for-women have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 34 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.
Every page has an H1
Each page we checked has a main headline.
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://bat.bing.com/action/0?ti=343003509&tm=gtm002&Ver=2&mid=7057ef74-7b04-480b-9146-73677d000d74&bo=1&sid=33959c80d9f311f1a13e61e32ee15d0c&vid=3395bb40d9f311f1a1b4f34d8ec4ea20&vids=1&msclkid=N>m_.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.
Missing source maps
Large scripts ship without source maps.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
30 of 32 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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 2,016 words of copy
The homepage carries about 2,016 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 All” and “Contact Us”.
12 calls to action
The homepage has 12 calls to action, for example “Contact Us”, “Shop” and “Shop All”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 531 testimonial or review blocks, 56 customer or partner logos, 242 trust badges and “Trusted By 250k+ Users”.
Analytics in place
Analytics detected: Google Tag Manager.
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
14 trackers load before any consent
14Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Tag Manager, Klaviyo and Microsoft Ads and 9 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.
28 cookies set on arrival
28Opening the homepage sets 28 cookies, 1 of them by other companies (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.
55 other companies contacted
Loading the homepage contacts 55 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 mysexmd.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on mysexmd.com, including 17 speed issues, 5 SEO issues and 3 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.