Programmable

Website review, no card needed

puffy.com logo

puffy.com website review

Visit site (opens in a new tab)Reviewed 6 November 202627 issues · 94 checks

This review found 27 issues worth fixing on puffy.com, 11 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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

Site score

79C

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.2 s1.6 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.0 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
379 ms295 msMay 16Oct 31312 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026321 ms
May 23, 2026335 ms
May 30, 2026353 ms
Jun 6, 2026361 ms
Jun 13, 2026363 ms
Jun 20, 2026363 ms
Jun 27, 2026362 ms
Jul 4, 2026369 ms
Jul 11, 2026362 ms
Jul 18, 2026349 ms
Jul 25, 2026339 ms
Aug 1, 2026327 ms
Aug 8, 2026327 ms
Aug 15, 2026339 ms
Aug 22, 2026344 ms
Aug 29, 2026338 ms
Sep 5, 2026331 ms
Sep 12, 2026325 ms
Sep 19, 2026318 ms
Sep 26, 2026313 ms
Oct 3, 2026310 ms
Oct 10, 2026305 ms
Oct 17, 2026305 ms
Oct 24, 2026311 ms
Oct 31, 2026312 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

puffy.com (opens in a new tab)
Full-page screenshot of puffy.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. puffy.com at 0.6 s0.6 s
  2. puffy.com at 1.3 s1.3 s
  3. puffy.com at 1.9 s1.9 s
  4. puffy.com at 2.5 s2.5 s
  5. puffy.com at 3.1 s3.1 s
  6. puffy.com at 3.8 s3.8 s
  7. puffy.com at 4.4 s4.4 s
  8. puffy.com at 5.0 s5.0 s

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

Speed

5 to fix53

  • Reduce unused JavaScript

    19.8 s · 3.9 MB

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

  • Mobile performance score: 53

    53/100

    Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    700 ms · 178 KiB

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

  • Main-thread work: 2.5 s

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

  • 1,560 HTML elements

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (iubenda, Shopify and cloudfunctions.net and others), adding 329 KiB and 184 ms of main-thread time.

  • 9 long tasks on the main thread

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

  • Reduce unused CSS

    103 KiB

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

  • Use efficient cache lifetimes

    15 KiB

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

  • Legacy JavaScript

    14 KiB

    Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need.

  • 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: 58 ms

    58 ms

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

Core Web Vitals

7 to fix67

  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 30.2 s

    30.2 s

    Your largest element takes 30.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Puffy Lux Mattress Hero Image”.

  • Time to Interactive: 30.2 s

    30.2 s

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

  • Speed Index: 10.1 s

    10.1 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user INP: 311 ms

    311 ms

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

  • Total Blocking Time: 289 ms

    289 ms

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

5 checks passed

  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 684 ms

    684 ms

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

  • Cumulative Layout Shift: 0.073

    0.073

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

Images and page weight

1 to fix70

  • Page weight: 5.5 MB in 103 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 103 requests on a phone: scripts 4.6 MB (65), HTML 370 KiB (1) and images 358 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • About 1.5 g of CO₂ per visit

    1.55 g

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

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

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9193

  • Invalid ARIA attributes

    5 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • <svg> elements with an img or image role must have alternative text (10 elements)

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

  • Elements must only use permitted ARIA attributes (3 elements)

    Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (12 elements)

    All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

2 checks passed

  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

3 to fixGoogle 9287

  • Title is short (23 characters)

    Your title is only 23 characters: “Official Puffy Mattress”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 5 problems

    Structured data found (FAQPage, ItemList, Organization and WebPage) but with 5 problems, for example “Organization: image is not an absolute URL ("[object Object]")”.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 101 internal links, 6 external

    The homepage links to 101 pages on puffy.com and 6 external pages.

6 checks passed

  • Meta description: 146 characters

    Your meta description is 146 characters: “Puffy Mattress: America's #1 Luxury Mattress. Rated 4.9 stars by 22k+ verified reviewers. Save $1,350 + get a 365-night…”.

  • One H1 headline

    Your main headline reads: “Puffy Mattress: America’s #1 Award‑Winning Luxury Mattresses”.

  • Canonical URL set

    The canonical URL is https://puffy.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://puffy.com/sitemap.xml.

AI search readiness

100
4 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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (760 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

3 to fix75

  • 7 pages without a title

    /products/puffy-mattress, /products/puffy-lux-mattress, /products/puffy-royal-mattress, /products/puffy-monarch-mattress, /products/puffy-legacy-mattress and /products/puffy-adjustable-base and 1 other have no <title>, so Google invents the link text in results.

  • 7 pages without a meta description

    /products/puffy-mattress, /products/puffy-lux-mattress, /products/puffy-royal-mattress, /products/puffy-monarch-mattress, /products/puffy-legacy-mattress and /products/puffy-adjustable-base and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    /products/puffy-mattress, /products/puffy-lux-mattress, /products/puffy-royal-mattress, /products/puffy-monarch-mattress, /products/puffy-legacy-mattress and /products/puffy-adjustable-base and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    /pages/puffy-mattress-and-puffy-lux, /collections/smart-bed-sets, /collections/bed-frames, /collections/bedding and /pages/contact-puffy-mattress 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 80 found) and read each the way a search engine does.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 10093

  • 6 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100

  • No security.txt

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

8 checks passed

  • Served over HTTPS

    The homepage is served over HTTPS (puffy.com).

  • Valid certificate (71 days left)

    The certificate from Let's Encrypt · YR1 verifies for puffy.com and is valid for another 71 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.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • http:// redirects to https

    http://puffy.com redirects to the secure version.

  • HTTP/2

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

  • All 46 links work

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

Domain and trust

  • No CAA record

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

    puffy.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 23 years old

    23 years

    puffy.com was registered in Sep 2003 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

  • Registered until Sep 2027

    puffy.com is registered until Sep 2027.

Content and conversion

3 to fix75

  • Thin social proof

    Social proof on the homepage: a star rating. 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.

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • About 354 words of copy

    The homepage carries about 354 words of visible text.

3 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Puffy puffy-lux-mattress” and “Shop Puffy puffy-royal-mattress”.

  • 23 calls to action

    The homepage has 23 calls to action, for example “Shop Puffy puffy-mattress”, “Shop Puffy Cloud” and “Shop Puffy puffy-lux-mattress”.

  • 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.elasticemail.com include:mail.zendesk.com include:_spf.google.com include:sendgrid.net include:tran…”.

  • DKIM signing found

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

Privacy and tracking

  • 18 cookies set on arrival

    18

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

  • 5 other companies contacted

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

2 checks passed

  • Consent tool: iubenda

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

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

Apps on your store

No apps were seen in the code your storefront loads.

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
Next.js
E-commerce
Shopify
Hosting
Vercel

Company

Employees
40
Headquarters
Los Angeles

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on puffy.com, including 12 speed issues, 3 SEO issues and 3 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