muttsandco.com website review

25 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

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

104 KiB could be saved by minifying JavaScript.

2 third-party services load with your homepage (franpos.com and Azure Web Services), adding 2.0 MB and 73 ms of main-thread time.

franpos.com costs a phone 73 ms of main-thread work and 1.1 MB 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.

Azure Web Services costs a phone 0 ms of main-thread work and 867 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.

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 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

Your homepage downloads 2.0 MB in 48 requests on a phone: images 1.8 MB (32), scripts 162 KiB (11) and HTML 38 KiB (1). Under 2 MB keeps phones on slow connections fast.

640w.8d8209f8c19a.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).

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

5 visible links have no text or label, so screen readers cannot say where they go.

Elements with visible text labels do not have matching accessible names. (1 element).

The homepage links to 77 pages on muttsandco.com and 17 external pages.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, 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.

/wishlist and /astro-offers are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/categories/holiday-pet-shop, /categories/dog, /categories/dog-supplies, /categories/dog-food, /categories/collars-leashes-training and /categories/dog-toys and 1 other all use the title “Choose a store to shop | Mutts & Co.”. Search engines can't tell which page to show for a search, so each competes with the others.

/astro-offers has no meta description, so Google writes the search snippet from whatever text it finds.

/stores, /categories/holiday-pet-shop, /categories/dog, /categories/dog-supplies, /categories/dog-food and /categories/collars-leashes-training and 2 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 7 pages by a URL that isn't their canonical one, for example /categories/holiday-pet-shop, whose canonical is /stores. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/categories/dog, /categories/dog-supplies, /categories/dog-food, /categories/collars-leashes-training, /categories/dog-toys and /categories/cat took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://assets.franpos.com/assets/site.0d4dc82b11e7a3c3.css' violates the following Content Security Pol…”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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 carries about 519 words of visible text.

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