puffy.ca website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and Klaviyo and others), adding 957 KiB and 1.1 s of main-thread time.

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

1 image could be 56 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

Clarity costs a phone 305 ms of main-thread work and 30 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.

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

Your largest element takes 7.4 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”.

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

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

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

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

Your homepage downloads 6.1 MB in 167 requests on a phone: scripts 5.4 MB (97), HTML 347 KiB (1) and images 250 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

3 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: 4 elements on the page fail this check, rated serious by axe-core.

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

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

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

3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 59 pages on puffy.ca and 6 external pages.

https://puffy.ca/products/puffy-capri-bed-frame-+-headboard and https://puffy.ca/products/puffy-capri-bed-frame all use the title “Official Puffy™ Canada Capri Bed Frame | Luxury Solid European Oak”. Search engines can't tell which page to show for a search, so each competes with the others.

https://puffy.ca/products/puffy-capri-bed-frame-+-headboard and https://puffy.ca/products/puffy-capri-bed-frame use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://puffy.ca/products/puffy-capri-bed-frame-+-headboard, whose canonical is https://puffy.ca/products/puffy-capri-bed-frame. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://puffy.ca/pages/puffy-mattress-reviews, https://puffy.ca/products/puffy-mattress, https://puffy.ca/products/puffy-lux-mattress, https://puffy.ca/products/puffy-royal-mattress, https://puffy.ca/products/puffy-adjustable-base and https://puffy.ca/products/puffy-milan-bed-frame and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://puffy.ca/pages/puffy-mattress-and-puffy-lux, https://puffy.ca/collections/bed-frames, https://puffy.ca/collections/bedding, https://puffy.ca/pages/puffy-mattress-reviews, https://puffy.ca/products/puffy-mattress and https://puffy.ca/products/puffy-lux-mattress and 7 others 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.

https://puffy.ca/products/puffy-capri-bed-frame took over 3 s to send its HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

Large scripts ship without source maps.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 202 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Microsoft Clarity (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.

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

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.

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