Website review, no card needed
meadowivy.com website review
Visit site (opens in a new tab)Reviewed 16 November 202635 issues · 78 checks
This review found 35 issues worth fixing on meadowivy.com, 8 of them high impact, across 78 checks. The most urgent: improve image delivery. 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- #45,944 of 116,487 reviewed websitesbeats 55%
- #30,819 of 66,776 online storesbeats 47%
- #29,661 of 60,929 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
1.8 s · 591 KiB5 images could be 591 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
1.3 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Reduce unused JavaScript
750 ms · 346 KiBAbout 346 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
500 ms · 384 KiB21 files are served with short cache lifetimes, so returning visitors download them again (384 KiB).
amaicdn.com adds 262 ms
262 msamaicdn.com costs a phone 262 ms of main-thread work and 402 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.
2,313 HTML elements
The page has 2,313 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 26 ms
26 msShopify costs a phone 26 ms of main-thread work and 363 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.
7 third-party services on the page
7 third-party services load with your homepage (amaicdn.com, Shopify and useamp.com and others), adding 828 KiB and 309 ms of main-thread time.
Legacy JavaScript
150 ms · 76 KiBPolyfills for old browsers add 76 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 219 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 25 KiBAbout 25 KiB of CSS is downloaded but never applied on this page. 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).
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
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: 6.7 s
6.7 sYour largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 10.2 s
10.2 sThe page becomes fully interactive after 10.2 s. Good is under 3.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
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.
4 checks passed
Speed Index: 3.4 s
3.4 sVisually, the page fills in at 3.4 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 195 ms
195 msScripts block the page for only 195 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.041
0.041The layout barely moves while loading (CLS 0.041, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.9 MB in 181 requests
2.9 MBYour homepage downloads 2.9 MB in 181 requests on a phone: images 1.1 MB (11), scripts 869 KiB (48) and other files 801 KiB (111). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
158 KiB1 image is downloaded at several times the size a phone draws it, for example meadow_ivy_pink_heart_sweater_romper_d3d125cb-e06d-4446-a3cb at 1,800 px wide, shown at 390 px. Resized copies would save about 158 KiB.
About 0.8 g of CO₂ per visit
0.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.83 g of CO₂e: 99.2 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
27 text elements with low contrast
27 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
52 images without alt text
52 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (50 elements)
All page content should be contained by landmarks: 50 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.
20 form fields without a label
20 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.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (10 characters)
Your title is only 10 characters: “Meadow Ivy”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (175 characters)
Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (ItemList, Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://www.meadowivy.com/search?q={search_term_string}")”.
147 internal links, 5 external
The homepage links to 147 pages on meadowivy.com and 5 external pages.
5 checks passed
One H1 headline
Your main headline reads: “VALENTINE'S DAY COLLECTION”.
Canonical URL set
The canonical URL is https://www.meadowivy.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://www.meadowivy.com/sitemap.xml.
AI search readiness
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.
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.
llms.txt published
The site publishes https://www.meadowivy.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.meadowivy.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.meadowivy.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
12 pages without a meta description
https://www.meadowivy.com/customer_authentication/redirect, https://www.meadowivy.com/collections/new-arrivals, https://www.meadowivy.com/collections/bunny-collection, https://www.meadowivy.com/collections/spring-collection-1, https://www.meadowivy.com/collections/valentines-day-collection and https://www.meadowivy.com/collections/organic and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.meadowivy.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://www.meadowivy.com/collections/organic, https://www.meadowivy.com/collections/mommy-and-me, https://www.meadowivy.com/collections/swaddle-blankets and https://www.meadowivy.com/collections/sleepwear have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
4 pages slow to respond
https://www.meadowivy.com/collections/socks, https://www.meadowivy.com/collections/swaddle-blankets, https://www.meadowivy.com/collections/sleepwear and https://www.meadowivy.com/collections/accessories took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 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.
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.
Best practices
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
13 of 13 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 12 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 10-field form
Your longest form asks for 10 fields (0 required). Every extra field lowers completion.
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.
Only about 141 words
The homepage has only about 141 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
3 calls to action
The homepage has 3 calls to action, for example “SHOP NOW”, “Contact Us” and “Sign Up”.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Pinterest Tag (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
11 other companies contacted
Loading the homepage contacts 11 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 meadowivy.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
chimpstatic.com · zooomyapps.com · privy.com · nfcube.com · mailmunch.co · useamp.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on meadowivy.com, including 12 speed issues, 3 SEO issues and 5 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.