dogsportgear.com website review

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

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

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

8 third-party services load with your homepage (Google CDN, Privy and Facebook and others), adding 1.9 MB and 1.5 s of main-thread time.

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

Google CDN costs a phone 872 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.

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

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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.

4 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.5 MB in 379 requests on a phone: images 3.1 MB (148), scripts 1.8 MB (59) and other files 1.1 MB (126). Under 2 MB keeps phones on slow connections fast.

dsg_igp_slide.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).

1 image further down the page (75 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.83 g of CO₂e: 219.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 buttons have no accessible name, so screen readers announce just “button”.

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

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

ARIA progressbar nodes must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

Some list items are not inside a list.

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.

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

Your title is only 13 characters: “DogSport Gear”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

4 links have no real href, so search engines can't follow them.

Your <h1> is empty.

The homepage links to 257 pages on dogsportgear.com and 0 external pages.

Your homepage links to https://www.dogsportgear.com/collections/bungee-toys, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.dogsportgear.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

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

https://www.dogsportgear.com/apps/todays-deals, https://www.dogsportgear.com/customer_authentication/redirect, https://www.dogsportgear.com/collections/chew-toys, https://www.dogsportgear.com/collections/prey-building-toys, https://www.dogsportgear.com/collections/magnet-toys and https://www.dogsportgear.com/collections/bite-pillows-wedges and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.dogsportgear.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://d.adroll.com/uev/SYC4MTEPXZDOPHOKRIH6NQ/2UWFXV7JAREOZKZGN42OPG/?adroll_tpc=lx3%3Dlex-875dcf7e-8824-4efd-8dd5-36b3b8e5e127&af0=0fe6f973&adroll_fpc=eff26909eb716e452aba300424bf5ec8-1794469534181.

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

1 image is served at too low a resolution for sharp phone screens.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Before a visitor clicks anything, the page loads Meta Pixel and The Trade Desk (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 10 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.