Website review, no card needed

pillow-haven.com logo

pillow-haven.com website review

Visit site (opens in a new tab)Reviewed 5 November 202624 issues · 98 checks

This review found 24 issues worth fixing on pillow-haven.com, 3 of them high impact, across 98 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.2 s839 msMay 16Oct 31886 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.2 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.0 s
Oct 3, 2026988 ms
Oct 10, 2026946 ms
Oct 17, 2026933 ms
Oct 24, 2026914 ms
Oct 31, 2026886 ms
Real-visitor tap response (INP)75th percentile, phones
200 ms156 msMay 16Oct 31189 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026166 ms
May 23, 2026168 ms
May 30, 2026171 ms
Jun 6, 2026174 ms
Jun 13, 2026176 ms
Jun 20, 2026171 ms
Jun 27, 2026165 ms
Jul 4, 2026165 ms
Jul 11, 2026163 ms
Jul 18, 2026161 ms
Jul 25, 2026162 ms
Aug 1, 2026162 ms
Aug 8, 2026163 ms
Aug 15, 2026166 ms
Aug 22, 2026165 ms
Aug 29, 2026170 ms
Sep 5, 2026171 ms
Sep 12, 2026177 ms
Sep 19, 2026180 ms
Sep 26, 2026179 ms
Oct 3, 2026184 ms
Oct 10, 2026188 ms
Oct 17, 2026188 ms
Oct 24, 2026195 ms
Oct 31, 2026189 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

Full-page screenshot of pillow-haven.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pillow-haven.com at 0.5 s0.5 s
  2. pillow-haven.com at 1.0 s1.0 s
  3. pillow-haven.com at 1.5 s1.5 s
  4. pillow-haven.com at 2.0 s2.0 s
  5. pillow-haven.com at 2.4 s2.4 s
  6. pillow-haven.com at 2.9 s2.9 s
  7. pillow-haven.com at 3.4 s3.4 s
  8. pillow-haven.com at 3.9 s3.9 s

pillow-haven.com does not allow embedding, so this is Google's rendering of the page.

Speed

2 to fix98
  • Render-blocking requests

    1.1 s

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Improve image delivery

    578 KiB

    16 images could be 578 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 3 long tasks on the main thread

    3 long tasks block the main thread while loading, the longest for 79 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    37 KiB

    10 files are served with short cache lifetimes, so returning visitors download them again (37 KiB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, JSDelivr CDN and jQuery CDN and others), adding 214 KiB and 8 ms of main-thread time.

  • Reduce unused CSS

    27 KiB

    About 27 KiB of CSS is downloaded but never applied on this page.

  • 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 CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

3 checks passed
  • Mobile performance score: 98

    98/100

    Your mobile performance score is 98. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 78 ms of it running JavaScript. That is comfortably low.

  • Server response: 38 ms

    38 ms

    Your server sent the HTML in 38 ms, well inside Google's 600 ms guideline.

Core Web Vitals

2 to fix100
  • First Contentful Paint: 1.9 s

    1.9 s

    The first text or image appears after 1.9 s on a phone. Good is under 1.8 s.

  • 5 images without width and height

    5 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 15% slower for real visitors

    +15%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 166 ms to 189 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

12 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.0 s

    1.0 s

    Real visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 133 ms

    133 ms

    Real visitors wait 133 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 772 ms

    772 ms

    Real visitors wait 772 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 25% faster for real visitors

    -25%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.2 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Time to Interactive: 3.4 s

    3.4 s

    The page is fully interactive after 3.4 s.

  • Speed Index: 2.7 s

    2.7 s

    Visually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.

  • Largest Contentful Paint: 1.9 s

    1.9 s

    Your largest element renders in 1.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.

  • Cumulative Layout Shift: 0.005

    0.005

    The layout barely moves while loading (CLS 0.005, good is under 0.1).

  • Total Blocking Time: 19 ms

    19 ms

    Scripts block the page for only 19 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix68
  • Page weight: 3.4 MB in 81 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 81 requests on a phone: images 2.0 MB (38), fonts 1,001 KiB (3) and scripts 356 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • 7 images far larger than shown

    158 KiB

    7 images are downloaded at several times the size a phone draws them, for example imagea.png at 1,120 px wide, shown at 145 px. Resized copies would save about 158 KiB.

  • 4 images below the first screen load straight away

    4 images further down the page (358 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.98 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.98 g of CO₂e: 117.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 8994
  • 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 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.

  • 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 should not be empty (3 elements)

    Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 38 images in the HTML carry an alt attribute.

  • 42 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: 42 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10090
  • 4 H1 headlines

    There are 4 <h1> headlines (“Pillow Haven”, “Better Support” and “Give It the Support It Deserves”). One clear main headline is easier for people and search engines.

  • Meta description is long (164 characters)

    Your meta description is 164 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 44 internal links, 11 external

    The homepage links to 44 pages on pillow-haven.com and 11 external pages.

6 checks passed
  • Title: 62 characters

    Your title is a healthy 62 characters: “Pillow Haven Sleep Solution: The #1 World's Pain Relief Pillow”.

  • Canonical URL set

    The canonical URL is https://pillow-haven.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, 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://pillow-haven.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, 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,099 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix63
  • 1 page without a title

    /customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    /customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 9 pages without a meta description

    /collections/pillow-case-navigation, /products/kid-ergonomic-posture-pillow-fix-the-problem-before-it-starts-copy, /collections/bestsellers-pillow-haven, /customer_authentication/redirect, /collections/all and /products/kid-posture-pillow and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example /products/premium-sleep-alignment-pillow%E2%84%A2-new-year-sale-60-off, whose canonical is /products/premium-sleep-alignment-pillow. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages without an H1

    /collections/pillow-case-navigation, /collections/bestsellers-pillow-haven, /apps/parcelpanel, /customer_authentication/redirect, /collections/all and /pages/about-us and 1 other 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 22 found) and read each the way a search engine does.

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

Best practices

3 to fixGoogle 9285
  • 4 small tap targets

    4 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • 2 links through redirect chains

    2 links go through two or more redirects, for example https://pillow-haven.com/customer_authentication/redirect?locale=en&region_country=US.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (pillow-haven.com).

  • Valid certificate (74 days left)

    The certificate from Let's Encrypt · YE2 verifies for pillow-haven.com and is valid for another 74 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://pillow-haven.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 33 links work

    All 33 links checked from your homepage (27 internal, 6 external) answered without errors.

Domain and trust

  • No CAA record

    pillow-haven.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    pillow-haven.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed
  • Domain is 1 year old

    1 year

    pillow-haven.com was registered in Feb 2025 through NameCheap, Inc.. An established domain carries more trust with email providers and search engines.

  • Registered until Feb 2027

    pillow-haven.com is registered until Feb 2027.

Content and conversion

100
  • 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 757 words of copy

    The homepage carries about 757 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 NOW”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Track Your Order”, “Shop Now” and “Shop & Plant a Tree Today”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 31 testimonial or review blocks, a star rating, 1 trust badge and “183k+ customers”.

  • 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.

Email authentication

85
  • Email authentication score: 85/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:spf.privateemail.com ~all”.

  • DKIM signing found

    A DKIM key is published (selector “default”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 10 other companies contacted

    Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Apps on your store

Your storefront loads 11 apps. Each one is code from another company running for your shoppers.

None of the apps your storefront loads is on the list of apps with a known security problem.

Apps your storefront loads

Intelligems A B Testing · Lucky Orange · Kaching Bundles · Klaviyo Email Marketing Sms · Instafeed · Aftersell · Applovin Shop Integration · loox.io · thegoodapi.com · archive-digger.com · wetracked.io

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

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on pillow-haven.com, including 4 speed issues and 2 SEO issues. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25