Website review, no card needed
peacelily.com website review
Visit site (opens in a new tab)Reviewed 11 November 202620 issues · 72 checks
This review found 20 issues worth fixing on peacelily.com, 4 of them high impact, across 72 checks. The most urgent: 4 text elements with low contrast. 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
One score from every part of this review. How it works
Speed
Improve image delivery
850 ms · 606 KiB13 images could be 606 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Intercom and Affirm and others), adding 1.3 MB and 909 ms of main-thread time.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Google Tag Manager adds 403 ms
403 msGoogle Tag Manager costs a phone 403 ms of main-thread work and 512 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.
Reduce unused JavaScript
411 KiBAbout 411 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
150 ms · 77 KiBAbout 77 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 210 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
171 KiB10 files are served with short cache lifetimes, so returning visitors download them again (171 KiB).
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need.
Minify CSS
7 KiB7 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
2 KiB2 KiB could be saved by minifying JavaScript.
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
Time to Interactive: 16.0 s
16.0 sThe page becomes fully interactive after 16.0 s. Good is under 3.8 s.
Largest Contentful Paint: 5.6 s
5.6 sYour largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Peace Lily mattress on a wooden bed frame in a rubber tree …”.
Total Blocking Time: 298 ms
298 msScripts block taps and scrolling for 298 ms in total while the page loads. Good is under 200 ms.
4 images without width and height
4 images 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.
3 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.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.6 MB in 261 requests
3.6 MBYour homepage downloads 3.6 MB in 261 requests on a phone: scripts 1.4 MB (112), images 1.2 MB (43) and other files 794 KiB (93). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (431 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
4 images below the first screen load straight away
4 images further down the page (289 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
1.03 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.03 g of CO₂e: 123.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 85 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
68 internal links, 2 external
The homepage links to 68 pages on peacelily.com and 2 external pages.
8 checks passed
Meta description: 130 characters
Your meta description is 130 characters: “Peace Lily helps the US sleep better with sustainable sleep products, 100% natural latex mattresses and certified organ…”.
One H1 headline
Your main headline reads: “Tap Into Nature's Comfort: From Tree to Mattress”.
Title: 61 characters
Your title is a healthy 61 characters: “Latex Mattresses & Organic Bedding - Peace Lily United States”.
Canonical URL set
The canonical URL is https://peacelily.com/.
Structured data in place
Structured data found: Organization.
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://peacelily.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,424 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://peacelily.com/llms.txt (7 KiB, 26 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 28 found) and read each the way a search engine does.
7 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 a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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 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=56363957&tm=gtm002&Ver=2&mid=d8f1b83d-22e0-43c7-8629-7d4006d9de4e&bo=1&sid=5e28cd20dd8011f18db21b3448a63861&vid=5e2fd450dd8011f1999aef3a13300551&vids=1&msclkid=N>m_t.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'querySelector') https://peacelily.com/:7739:41”.
2 checks passed
Tap targets are thumb-sized
9 of 10 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
About 942 words of copy
The homepage carries about 942 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP LATEX MATTRESS”.
10 calls to action
The homepage has 10 calls to action, for example “Our Honest Pricing Policy”, “FAQs / Contact Us” and “SHOP LATEX MATTRESS”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 21 testimonial or review blocks, 1 customer or partner logo and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 2 email links.
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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
19 cookies set on arrival
19Opening the homepage sets 19 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.
26 other companies contacted
Loading the homepage contacts 26 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 peacelily.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Analyzify Ga4 Ads Tracking · Intercom · shareasale.com · stamped.io · klaviyo.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
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Melbourne
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on peacelily.com, including 11 speed issues and 1 SEO issue. 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.