downtownpetsupply.com website review

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

38 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.

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

8 third-party services load with your homepage (Shopify, rebuyengine.com and Clarity and others), adding 2.2 MB and 1.3 s of main-thread time.

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

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

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

Shopify costs a phone 569 ms of main-thread work and 990 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.

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

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

32 KiB could be saved by minifying JavaScript.

rebuyengine.com costs a phone 235 ms of main-thread work and 735 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,975 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

7 long tasks block the main thread while loading, the longest for 138 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).

7 KiB JavaScript is shipped twice across bundles.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 33.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Unlock 10% Off Subscribe to receive 10% OFF your first orde…”.

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

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

Real visitors wait 801 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Your homepage downloads 5.7 MB in 509 requests on a phone: scripts 2.2 MB (161), other files 1.4 MB (236) and images 1.3 MB (27). Under 2 MB keeps phones on slow connections fast.

DTP_Pup-kinSeason_WebsiteBanner-Fullscreen.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).

2 images (82 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 (28 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 1.60 g of CO₂e: 192.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

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

Your title is 91 characters, so Google will cut it off around 60: “All the best for your dog — premium treats, gear, & more in one place – Downtown Pet Supp…”.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/2024-DTPS_Logos-Charcoal.svg")”.

Your <h1> is empty.

The homepage links to 197 pages on downtownpetsupply.com and 11 external pages.

Your homepage links to https://downtownpetsupply.com/pages/downtown-barkery-air-dried-treats, which answers with an error. Visitors hit a dead end and search engines drop it.

https://downtownpetsupply.com/products/cow-ears declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://downtownpetsupply.com/products/cow-ears all use the title “All the best for your dog — premium treats, gear, & more in one place…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://downtownpetsupply.com/products/downtown-barkery-freeze-dried-treats, https://downtownpetsupply.com/products/dental-yak-chew-cranberry-and-blueberry-yak-cheese-for-dogs, https://downtownpetsupply.com/products/chicken-and-bone-broth-jerky-bites, https://downtownpetsupply.com/products/air-dried-jerky-sticks, https://downtownpetsupply.com/collections/downtown-barkery-premium-functional-dog-treats and https://downtownpetsupply.com/products/junior-bully-sticks and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://d3k81ch9hvuctc.cloudfront.net/company/aTyPvs/images/d2b1403f-b531-4cc9-992b-48a34001fafa.png.

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

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

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 911 words of visible text.

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