Website review, no card needed
fluffyfriendshop.com website review
Visit site (opens in a new tab)Reviewed 16 November 202622 issues · 74 checks
This review found 22 issues worth fixing on fluffyfriendshop.com, 7 of them high impact, across 74 checks. The most urgent: page weight: 29.5 MB in 317 requests. 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
86B- #11,274 of 114,375 reviewed websitesbeats 86%
- #7,045 of 66,168 online storesbeats 85%
- #6,838 of 60,561 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.0 s |
| Nov 14, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 139 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 161 ms |
| Jul 4, 2026 | 170 ms |
| Jul 11, 2026 | 178 ms |
| Jul 18, 2026 | 177 ms |
| Jul 25, 2026 | 170 ms |
| Aug 1, 2026 | 155 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 144 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 145 ms |
| Sep 12, 2026 | 142 ms |
| Sep 19, 2026 | 142 ms |
| Sep 26, 2026 | 143 ms |
| Oct 3, 2026 | 147 ms |
| Oct 10, 2026 | 152 ms |
| Oct 17, 2026 | 153 ms |
| Oct 24, 2026 | 147 ms |
| Oct 31, 2026 | 144 ms |
| Nov 7, 2026 | 139 ms |
| Nov 14, 2026 | 138 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
800 ms · 120 KiB9 files are served with short cache lifetimes, so returning visitors download them again (120 KiB).
Reduce unused JavaScript
470 ms · 143 KiBAbout 143 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 470 ms faster on a phone.
Render-blocking requests
450 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 931 ms 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 (Clarity, Google Tag Manager and Klaviyo and others), adding 581 KiB and 392 ms of main-thread time.
Improve image delivery
200 ms · 163 KiB7 images could be 163 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Legacy JavaScript
150 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 106 ms. During a long task the page ignores taps.
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: 39 ms
39 msYour server sent the HTML in 39 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.4 s
15.4 sYour largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hero Background Image”.
Time to Interactive: 15.5 s
15.5 sThe page becomes fully interactive after 15.5 s. Good is under 3.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 136 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.9 s 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: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 89 ms
89 msReal visitors wait 89 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 502 ms
502 msReal visitors wait 502 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 60 ms
60 msScripts block the page for only 60 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 29.5 MB in 317 requests
29.5 MBYour homepage downloads 29.5 MB in 317 requests on a phone: media 26.2 MB (4), fonts 1.1 MB (11) and other files 874 KiB (137). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
moderndog_mff.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
6 images in older formats
6 images (261 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 8.4 g of CO₂ per visit
8.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.35 g of CO₂e: 1002.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
33 text elements with low contrast
33 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 2 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (87 characters)
Your title is 87 characters, so Google will cut it off around 60: “MrFluffyFriend – Premium Pet Essentials for Happy & Anxiety-Free Pets – MrFluffyFriend™”.
Meta description is long (227 characters)
Your meta description is 227 characters; Google truncates after about 160, so the end of your pitch is cut.
52 internal links, 0 external
The homepage links to 52 pages on fluffyfriendshop.com and 0 external pages.
6 checks passed
One H1 headline
Your main headline reads: “The number one fluffy dog bed”.
Canonical URL set
The canonical URL is https://mrfluffyfriend.com/.
Structured data in place
Structured data found: BreadcrumbList, FAQPage, OnlineStore 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://mrfluffyfriend.com/sitemap.xml.
AI search readiness
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 (1,041 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://mrfluffyfriend.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://mrfluffyfriend.com/collections/sleep-and-comfort has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://mrfluffyfriend.com/apps/trackorder and https://mrfluffyfriend.com/products/dogbed 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 20 found) and read each the way a search engine does.
5 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187144377&tm=gtm002&Ver=2&mid=2b8c1a53-272f-4729-9a8b-55f50648fb4c&bo=1&sid=17d5b420e1ee11f19337b1ea3014b1f2&vid=17d5e5e0e1ee11f18a6f8d79b18a5857&vids=1&msclkid=N&pi=9.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
21 of 23 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
About 901 words of copy
The homepage carries about 901 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now”.
15 calls to action
The homepage has 15 calls to action, for example “Shop”, “Contact” and “Track Order”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 19 testimonial or review blocks and 5 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email 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
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 mores (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.
30 cookies set on arrival
30Opening the homepage sets 30 cookies, 3 of them by other companies (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.
38 other companies contacted
Loading the homepage contacts 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 fluffyfriendshop.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Judge Me Reviews · Klaviyo Email Marketing Sms · goaffpro.com · archive-digger.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
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 22 issues on fluffyfriendshop.com, including 9 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.