Website review, no card needed
morvyn.com website review
Visit site (opens in a new tab)Reviewed 11 November 202632 issues · 70 checks
This review found 32 issues worth fixing on morvyn.com, 9 of them high impact, across 70 checks. The most urgent: render-blocking 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
81B- #36,032 of 106,118 reviewed websitesbeats 60%
- #23,914 of 59,793 online storesbeats 53%
- #23,070 of 54,510 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 91 ms |
| May 30, 2026 | 95 ms |
| Jun 6, 2026 | 92 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 102 ms |
| Jul 11, 2026 | 120 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
Render-blocking requests
1.4 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 85
85/100Your mobile performance score is 85. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
940 ms · 48 KiBAbout 48 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 940 ms faster on a phone.
Use efficient cache lifetimes
450 ms · 278 KiB17 files are served with short cache lifetimes, so returning visitors download them again (278 KiB).
2,989 HTML elements
The page has 2,989 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
150 ms · 109 KiBAbout 109 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (Shopify, JSDelivr CDN and Cloudflare and others), adding 268 KiB and 137 ms of main-thread time.
Minify CSS
150 ms · 7 KiB7 KiB could be saved by minifying CSS.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 125 ms. During a long task the page ignores taps.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
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.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 560 ms of it running JavaScript. That is comfortably low.
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 7.5 s
7.5 sThe page becomes fully interactive after 7.5 s. Good is under 3.8 s.
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.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 2.9 s
2.9 sYour largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shipping, taxes, and discount codes calculated at checkout.”. Most of its time is element render delay (2.3 s).
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 91 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
2 checks passed
Total Blocking Time: 84 ms
84 msScripts block the page for only 84 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.3 g of CO₂ per visit
0.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.29 g of CO₂e: 35.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.0 MB in 51 requests
1.0 MBYour homepage downloads 1.0 MB in 51 requests on a phone: scripts 715 KiB (18), stylesheets 173 KiB (8) and other files 127 KiB (24). That is a lean page.
Accessibility
491 tap targets too small
491 tap targets are too small or too close together to hit reliably with a finger.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
Orphan list items
Some list items are not inside a list.
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.
All page content should be contained by landmarks (244 elements)
All page content should be contained by landmarks: 244 elements on the page fail 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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (6 characters)
Your title is only 6 characters: “Morvyn”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“MorvynMorvyn” and “Women's Probiotic & Slippery Elm”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://morvyn.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at morvyn.com/robots.txt, the first file search crawlers ask for.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
26 internal links, 3 external
The homepage links to 26 pages on morvyn.com and 3 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://morvyn.com/.
Structured data in place
Structured data found: Product.
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.
No llms.txt
There is no https://morvyn.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
Text is in the HTML
Your server sends the page's text in the HTML (1,904 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages point its canonical at the homepage
https://morvyn.com/pages/contact, https://morvyn.com/policies/shipping-policy, https://morvyn.com/policies/privacy-policy, https://morvyn.com/policies/terms-of-service, https://morvyn.com/policies/refund-policy and https://morvyn.com/pages/data-sale-opt-out 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.
7 pages share a title
/, https://morvyn.com/pages/contact, https://morvyn.com/policies/shipping-policy, https://morvyn.com/policies/privacy-policy, https://morvyn.com/policies/terms-of-service and https://morvyn.com/policies/refund-policy and 1 other all use the title “Morvyn”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://morvyn.com/products/probiotic, https://morvyn.com/pages/contact, https://morvyn.com/policies/shipping-policy, https://morvyn.com/policies/privacy-policy, https://morvyn.com/policies/terms-of-service and https://morvyn.com/policies/refund-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
7 internal pages checked
We fetched 7 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 7 pages we checked loaded without an error.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
249 small tap targets
249 of 259 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 1,656 words of copy
The homepage carries about 1,656 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: “TRACK ORDER” and “CONTACT”.
5 calls to action
The homepage has 5 calls to action, for example “Track Order”, “Contact” and “Shop Now”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 84 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
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
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.
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 morvyn.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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Triplewhale · Trustoo Io Reviews · Kaching Bundles
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
- The footer still says © 2025.
Stack
- E-commerce
- Shopify
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on morvyn.com, including 9 speed issues, 7 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.