houndsy.com website review

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

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

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

About 307 KiB of JavaScript is downloaded but never used on this page.

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

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

8 third-party services load with your homepage (Shopify, Accessibe Accessibility Overlay and Klaviyo and others), adding 976 KiB and 380 ms of main-thread time.

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

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

1 image could be 19 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

About 11 KiB of CSS is downloaded but never applied on this page.

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.

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

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

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

Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “homepage banner”.

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

The layout shifts by 0.151 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Scripts block taps and scrolling for 206 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' largest content (lcp) went from 2.0 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 19.3 MB in 331 requests on a phone: media 16.3 MB (2), other files 1.2 MB (185) and scripts 1,016 KiB (84). Under 2 MB keeps phones on slow connections fast.

cart-img.jpg 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).

4 images (223 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.

1 image further down the page (32 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

8 tap targets are too small or too close together to hit reliably with a finger.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your meta description is only 57 characters: “A mid-century modern kibble storage and dispenser system.”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“Houndsy” and “The Most Convenient & Beautiful Dog Feeders”). One clear main headline is easier for people and search engines.

Structured data found (Organization, WebPage and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:Liquid error (snippets/json-structured-data line …”.

The homepage links to 66 pages on houndsy.com and 18 external pages.

Your homepage links to /pages/accessories, which answers with an error. Visitors hit a dead end and search engines drop it.

/customer_authentication/redirect has no <title>, so Google invents the link text in results.

/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/pages/5-reasons-why and /customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/accessories, /pages/reviews-1, /pages/contact and /pages/about-us use the same meta description. A description written for each page earns more clicks.

/pages/5-reasons-why, /customer_authentication/redirect and /pages/reviews-1 have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

4 errors were 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.

1 link from your homepage to your own site is broken, for example https://www.houndsy.com/pages/accessories (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://www.houndsy.com/customer_authentication/redirect?locale=en&region_country=US.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

houndsy.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 20 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 607 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 5 mores (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 35 cookies (measured from a US location before any click).

Loading the homepage contacts 52 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.