getwuffes.com website review

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

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

The page goes through 2 redirects before it starts loading, costing about 1.7 s. Link and advertise the final URL directly.

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

8 third-party services load with your homepage (alia-prod.com, wuffes.com and Google Tag Manager and others), adding 4.0 MB and 1.7 s of main-thread time.

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

wuffes.com costs a phone 378 ms of main-thread work and 2.3 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.

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

18 images could be 540 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

alia-prod.com costs a phone 473 ms of main-thread work and 616 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 49 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

Google Tag Manager costs a phone 290 ms of main-thread work and 348 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.

The page has 1,846 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

The HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB JavaScript is shipped twice across bundles.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 20.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A curly red poodle waiting in a dark hallway by the front d…”.

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

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

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

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

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

Your homepage downloads 6.9 MB in 256 requests on a phone: media 2.3 MB (1), scripts 1.9 MB (135) and images 1.7 MB (48). Under 2 MB keeps phones on slow connections fast.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

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

Your title is 69 characters, so Google will cut it off around 60: “Dog Health Supplements | Joint, Calming, Gut, Allergy & More | Wuffes”.

Your canonical URL points to shop.wuffes.com, not getwuffes.com, so Google may credit that host instead.

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

The homepage links to only 3 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

A phone browser shows 1,164 words, but the HTML your server sends has only 229. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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://www.getwuffes.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.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,164 words of visible text.

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