mrfluffyandfriends.com website review

About 169 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

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

26 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

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

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

7 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 150 ms faster on a phone.

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

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

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.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 29.5 MB in 289 requests on a phone: media 26.2 MB (4), fonts 1.2 MB (17) and scripts 820 KiB (86). Under 2 MB keeps phones on slow connections fast.

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

5 images (224 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.

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

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

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

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 on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

Your title is 87 characters, so Google will cut it off around 60: “MrFluffyFriend – Premium Pet Essentials for Happy & Anxiety-Free Pets – MrFluffyFriend™”.

Your canonical URL points to mrfluffyfriend.com, not mrfluffyandfriends.com, so Google may credit that host instead.

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

The homepage links to 49 pages on mrfluffyandfriends.com and 3 external pages.

Your homepage links to https://mrfluffyandfriends.com/products/giftcard, which answers with an error. Visitors hit a dead end and search engines drop it.

https://mrfluffyandfriends.com/collections/sleep-and-comfort has no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187144377&tm=gtm002&Ver=2&mid=3c9ff430-fdd8-4859-9cd8-c63a39a601f4&bo=1&sid=f807f8a0db8b11f1a93ea79a13d4804f&vid=f8082040db8b11f192395747ccf25187&vids=1&msclkid=N&pi=9.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

The homepage carries about 901 words of visible text.

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

Opening the homepage sets 26 cookies, 3 of them by other companies (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 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.