Website review, no card needed
downandfeather.com website review
Visit site (opens in a new tab)Reviewed 7 November 202629 issues · 90 checks
This review found 29 issues worth fixing on downandfeather.com, 12 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. 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
Site score
82B- #33,184 of 117,790 reviewed websitesbeats 66%
- #22,164 of 66,966 online storesbeats 60%
- #21,430 of 61,055 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 121 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 119 ms |
| Jun 6, 2026 | 119 ms |
| Jun 13, 2026 | 119 ms |
| Jun 20, 2026 | 119 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 124 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 123 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 123 ms |
| Sep 26, 2026 | 127 ms |
| Oct 3, 2026 | 135 ms |
| Oct 10, 2026 | 138 ms |
| Oct 17, 2026 | 135 ms |
| Oct 24, 2026 | 133 ms |
| Oct 31, 2026 | 128 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
How it loaded on a phone
1.1 s
2.3 s
3.4 s
4.5 s
5.6 s
6.8 s
7.9 s
9.0 s
Speed
Reduce unused JavaScript
2.7 s · 845 KiBAbout 845 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Use efficient cache lifetimes
2.1 s · 811 KiB39 files are served with short cache lifetimes, so returning visitors download them again (811 KiB).
Render-blocking requests
1.0 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, heatmap.com and OptiMonk and others), adding 2.0 MB and 1.4 s of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 505 ms
505 msGoogle Tag Manager costs a phone 505 ms of main-thread work and 689 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.
heatmap.com adds 268 ms
268 msheatmap.com costs a phone 268 ms of main-thread work and 101 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.
OptiMonk adds 196 ms
196 msOptiMonk costs a phone 196 ms of main-thread work and 467 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
280 ms · 73 KiBAbout 73 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.
Legacy JavaScript
200 ms · 84 KiBPolyfills for old browsers add 84 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Duplicated JavaScript
200 ms · 17 KiB17 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 200 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 164 ms. During a long task the page ignores taps.
Improve image delivery
131 KiB4 images could be 131 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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
3 KiB3 KiB could be saved by minifying CSS.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 21.1 s
21.1 sYour largest element takes 21.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Luxury Defined. Sleep Perfected. Elevate your sleep experie…”.
Time to Interactive: 27.5 s
27.5 sThe page becomes fully interactive after 27.5 s. Good is under 3.8 s.
Speed Index: 12.9 s
12.9 sVisually, the page fills in at 12.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 328 ms
328 msScripts block taps and scrolling for 328 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 121 ms to 128 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.0 MB in 508 requests
4.0 MBYour homepage downloads 4.0 MB in 508 requests on a phone: scripts 2.2 MB (131), fonts 825 KiB (17) and images 561 KiB (31). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
65 KiB1 image is downloaded at several times the size a phone draws it, for example oeko-tex-standard-100_2d89f309-e892-4b0f-9d97-75c357e2a62a.p at 792 px wide, shown at 54 px. Resized copies would save about 65 KiB.
2 images in older formats
2 images (99 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.
About 1.1 g of CO₂ per visit
1.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.14 g of CO₂e: 136.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
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.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
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.
Users should be able to zoom and scale the text up to 500% (1 element)
Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 23 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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
Structured data has 1 problem
Structured data found (Organization) but with 1 problem, for example “ld+json block 2 is not valid JSON (Bad control character in string literal in JSON at position )”.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
131 internal links, 10 external
The homepage links to 131 pages on downandfeather.com and 10 external pages.
6 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Shop for down and feather pillows, duvets, feather beds and more at Down & Feather Co. Everything responsibly made in A…”.
One H1 headline
Your main headline reads: “Luxury Defined. Sleep Perfected.”.
Title: 52 characters
Your title is a healthy 52 characters: “"Down and Feather Pillows - Down \u0026 Feather Co."”.
Canonical URL set
The canonical URL is https://www.downandfeathercompany.com/.
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.downandfeathercompany.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.downandfeathercompany.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
Opted out of AI training for 1 crawler
robots.txt blocks GPTBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
2 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,545 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 61 found) and read each the way a search engine does.
7 checks passed
Linked pages load
12 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 12 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 12 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot assign to read only property 'protect' of object '#<Object>'”.
4 distorted images
4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
43 of 45 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 973 words of copy
The homepage carries about 973 words of visible text.
7 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Contact Us”, “Shop” and “Q: What does made-to-order mean?”.
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 11 testimonial or review blocks and 2 trust badges.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
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
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
23 cookies set on arrival
23Opening the homepage sets 23 cookies (measured from a US location before any click).
48 other companies contacted
Loading the homepage contacts 48 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 downandfeather.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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Cookieyes Gdpr · Schema App Total Schema Markup · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · Df0bec95 Opensend · Optimonk Popup Cro A B Test · Seo Manager Venntov · Event Promotion Bar · downandfeathercompany.com · stamped.io · cart-bot.net · searchserverapi.com · hextom.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
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify Hosted
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on downandfeather.com, including 14 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.