thepuppysphere.com website review

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

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

Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

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

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

alia-prod.com costs a phone 303 ms of main-thread work and 469 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.

Google Tag Manager costs a phone 265 ms of main-thread work and 317 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 183 ms of main-thread work and 514 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,783 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

16 KiB could be saved by minifying JavaScript.

6 KiB could be saved by minifying CSS.

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

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

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

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

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

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

2026_BFCM_Asset-Waitlist_Heading.webp weighs 664 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 4.0 MB in 270 requests on a phone: scripts 2.0 MB (116), other files 760 KiB (107) and images 622 KiB (26). Under 2 MB keeps phones on slow connections fast.

3 images (929 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.

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

6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 link inside paragraphs relies on colour alone to stand out.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h4), 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.

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

The homepage links to 178 pages on thepuppysphere.com and 11 external pages.

https://thepuppysphere.com/products/puppy-yoga-hoboken and https://thepuppysphere.com/products/puppy-yoga-lakeview are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://thepuppysphere.com/collections/hoboken-classes and https://thepuppysphere.com/products/puppy-yoga-hoboken all use the title “Hoboken Puppy Yoga Classes | Wellness Puppy Yoga NJ”. Search engines can't tell which page to show for a search, so each competes with the others.

https://thepuppysphere.com/products/class-packs and https://thepuppysphere.com/collections/california-classes use the same meta description. A description written for each page earns more clicks.

https://thepuppysphere.com/products/puppy-yoga-hoboken and https://thepuppysphere.com/products/puppy-yoga-lakeview have no <h1> headline, so visitors and search engines get no clear main topic.

https://thepuppysphere.com/pages/puppy-yoga, https://thepuppysphere.com/collections/puppy-yoga-nyc, https://thepuppysphere.com/products/puppy-pilates-flatiron, https://thepuppysphere.com/products/puppy-yoga-flatiron, https://thepuppysphere.com/products/puppy-yoga-lower-manhattan and https://thepuppysphere.com/products/puppy-yoga-long-island took over 3 s to send their HTML from our server.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

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

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.

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

Social proof on the homepage: 2 trust badges. 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.

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.

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