Website review, no card needed

naturepedic.com logo

naturepedic.com website review

Visit site (opens in a new tab)Reviewed 20 October 202639 issues · 89 checks

This review found 39 issues worth fixing on naturepedic.com, 17 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
2.3 s1.3 sMay 2Oct 171.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.0 s
May 9, 20262.0 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.1 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.0 s
Aug 15, 20261.8 s
Aug 22, 20261.6 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
232 ms136 msMay 2Oct 17208 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026147 ms
May 9, 2026149 ms
May 16, 2026149 ms
May 23, 2026153 ms
May 30, 2026161 ms
Jun 6, 2026164 ms
Jun 13, 2026170 ms
Jun 20, 2026170 ms
Jun 27, 2026170 ms
Jul 4, 2026162 ms
Jul 11, 2026158 ms
Jul 18, 2026156 ms
Jul 25, 2026156 ms
Aug 1, 2026161 ms
Aug 8, 2026171 ms
Aug 15, 2026186 ms
Aug 22, 2026196 ms
Aug 29, 2026209 ms
Sep 5, 2026213 ms
Sep 12, 2026220 ms
Sep 19, 2026221 ms
Sep 26, 2026219 ms
Oct 3, 2026217 ms
Oct 10, 2026212 ms
Oct 17, 2026208 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 naturepedic.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. naturepedic.com at 0.9 s0.9 s
  2. naturepedic.com at 1.7 s1.7 s
  3. naturepedic.com at 2.6 s2.6 s
  4. naturepedic.com at 3.4 s3.4 s
  5. naturepedic.com at 4.3 s4.3 s
  6. naturepedic.com at 5.2 s5.2 s
  7. naturepedic.com at 6.0 s6.0 s
  8. naturepedic.com at 6.9 s6.9 s

Speed

15 to fix29
  • Use efficient cache lifetimes

    4.7 s · 1.4 MB

    42 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

  • Reduce unused JavaScript

    4.1 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.

  • Main-thread work: 12.4 s

    A phone's processor spends 12.4 s on main-thread work while loading, 8.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Signyfyd adds 1.2 s

    1.2 s

    Signyfyd costs a phone 1.2 s of main-thread work and 242 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 29

    29/100

    Your mobile performance score is 29 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Signyfyd, Google Tag Manager and osano.com and others), adding 2.1 MB and 4.3 s of main-thread time.

  • Google Tag Manager adds 889 ms

    889 ms

    Google Tag Manager costs a phone 889 ms of main-thread work and 560 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.

  • Improve image delivery

    400 ms · 518 KiB

    10 images could be 518 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • osano.com adds 544 ms

    544 ms

    osano.com costs a phone 544 ms of main-thread work and 82 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.

  • route.com adds 487 ms

    487 ms

    route.com costs a phone 487 ms of main-thread work and 566 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.

  • cloudfront.net adds 528 ms

    528 ms

    cloudfront.net costs a phone 528 ms of main-thread work and 105 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 CSS

    450 ms · 76 KiB

    About 76 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • 2,171 HTML elements

    The page has 2,171 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    100 ms · 95 KiB

    Polyfills for old browsers add 95 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Minify CSS

    7 KiB

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

1 checks passed
  • Server response: 17 ms

    17 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 29.1 s

    29.1 s

    Your largest element takes 29.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner image”.

  • Time to Interactive: 39.0 s

    39.0 s

    The page becomes fully interactive after 39.0 s. Good is under 3.8 s.

  • Total Blocking Time: 3.6 s

    3.6 s

    Scripts block taps and scrolling for 3.6 s in total while the page loads. Good is under 200 ms.

  • Speed Index: 10.6 s

    10.6 s

    Visually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 3.7 s

    3.7 s

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

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

    +42%

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

8 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: 2.3 s

    2.3 s

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

  • Real-user INP: 141 ms

    141 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 732 ms

    732 ms

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

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

    -26%

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix70
  • Page weight: 6.8 MB in 364 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 364 requests on a phone: scripts 3.1 MB (111), images 2.4 MB (45) and other files 870 KiB (188). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.9 g of CO₂ per visit

    1.93 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.93 g of CO₂e: 231.7 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 are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9192
  • <svg> elements with an img or image role must have alternative text (3 elements)

    <svg> elements with an img or image role must have alternative text: 3 elements on the page fail this check, rated serious by axe-core.

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

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

  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

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

1 checks passed
  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8593
  • 2 H1 headlines

    There are 2 <h1> headlines (“Naturepedic” and “Organic Mattresses and Bedding For Cleaner, Healt…”). One clear main headline is easier for people and search engines.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 262 internal links, 11 external

    The homepage links to 262 pages on naturepedic.com and 11 external pages.

7 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Shop Naturepedic certified organic mattresses, bedding, pillows, furniture, and baby products for healthier, better sle…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Organic Mattresses & Bedding for Healthier Sleep | Naturepedic”.

  • Canonical URL set

    The canonical URL is https://www.naturepedic.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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://www.naturepedic.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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,169 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://www.naturepedic.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

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

  • 8 pages without a meta description

    https://www.naturepedic.com/pages/about-us, https://www.naturepedic.com/pages/farm-to-bed, https://www.naturepedic.com/pages/faqs, https://www.naturepedic.com/pages/shipping-delivery, https://www.naturepedic.com/pages/returns and https://www.naturepedic.com/pages/layer-swap and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://www.naturepedic.com/pages/shipping-delivery, https://www.naturepedic.com/pages/returns, https://www.naturepedic.com/pages/product-care, https://www.naturepedic.com/pages/warranty, https://www.naturepedic.com/customer_authentication/redirect and https://www.naturepedic.com/collections/adult-organic-mattresses 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 106 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

3 to fixGoogle 7785
  • 12 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “__SCRIPTLOADER__ ERROR MESSAGE: A profile is currently in flight. pageView() / reset() were called before the previous …”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix90
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 772 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Mattresses”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop by Fabric”, “Shop Mattresses” and “Contact Us”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks and 6 trust badges.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and TikTok Pixel (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 cookies (measured from a US location before any click).

  • 47 other companies contacted

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

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) loads with the page.

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 naturepedic.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on naturepedic.com, including 21 speed issues, 2 SEO issues and 2 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

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