shopfurme.com website review

About 451 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

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

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

8 third-party services load with your homepage (rebuyengine.com, Klaviyo and loox.io and others), adding 1.9 MB and 698 ms of main-thread time.

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

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

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

rebuyengine.com costs a phone 203 ms of main-thread work and 638 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.

loox.io costs a phone 152 ms of main-thread work and 617 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.

Klaviyo costs a phone 171 ms of main-thread work and 315 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.

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

About 68 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 170 ms faster on a phone.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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.

4 KiB could be saved by minifying CSS.

Your largest element takes 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “101,728+ happy pet owners FALL SALE! 🍂 Premium FurMe® Vacu…”.

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

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

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

32 images have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 4.0 MB in 266 requests on a phone: scripts 1.5 MB (103), images 1.3 MB (62) and other files 678 KiB (79). Under 2 MB keeps phones on slow connections fast.

6 images (693 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.

3 images are downloaded at several times the size a phone draws them, for example Using_furme_AirClipper_on_Dog-optimized_300x300.webp at 300 px wide, shown at 64 px. Resized copies would save about 171 KiB.

3 images further down the page (80 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

4 buttons have no accessible name, so screen readers announce just “button”.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 129 pages on shopfurme.com and 9 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://shopfurme.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.

https://shopfurme.com/collections/furme-grooming-vacuum-sets and https://shopfurme.com/collections/cleaning use the same meta description. A description written for each page earns more clicks.

https://shopfurme.com/collections/sale, https://shopfurme.com/collections/frontpage, https://shopfurme.com/collections/furme-grooming-vacuum-sets, https://shopfurme.com/collections/cleaning, https://shopfurme.com/collections/furme-grooming-vacuum-accessories and https://shopfurme.com/collections/pet-beds-and-carriers and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

Large scripts ship without source maps.

1 image is served at too low a resolution for sharp phone screens.

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

The homepage carries about 737 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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 35 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 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.