getdogface.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and Klaviyo and others), adding 18.0 MB and 647 ms of main-thread time.

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

Your mobile performance score is 59. 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 800 ms.

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

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

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

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

About 34 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.

5 KiB could be saved by minifying JavaScript.

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

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

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

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

17 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 104 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 51.3 MB in 321 requests on a phone: media 39.6 MB (3), images 9.0 MB (70) and scripts 1.6 MB (85). Under 2 MB keeps phones on slow connections fast.

23_0901_IMG_5497_Brush_Gel_in_shower_rotate_forGIF_V2_1_587a weighs 8.4 MB. On a phone connection a single image that size takes seconds.

7 images are downloaded at several times the size a phone draws them, for example 23_0901_IMG_5497_Brush_Gel_in_shower_rotate_forGIF_V2_1_587a at 1,920 px wide, shown at 390 px. Resized copies would save about 5.4 MB.

8 images further down the page (8.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (8.4 MB) is 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 14.54 g of CO₂e: 1744.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 dropdown has no label.

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your meta description is only 46 characters: “Smart Skincare. Specifically Designed for Men.”. 70 to 160 characters is enough to sell the click.

There are 4 <h1> headlines (“<img src="//www.getdogface.com/cdn/shop/files/LOG…”, “” and “Upgrade to a Deluxe Kit for only $30.00”). One clear main headline is easier for people and search engines.

1 link has no real href, so search engines can't follow it.

The homepage links to 57 pages on getdogface.com and 3 external pages.

https://www.getdogface.com/products/wake-up-gel-upsell and https://www.getdogface.com/products/wake-up-gel-3-tier-pricing all use the title “Wake-Up Gel * – Dogface for Men”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.getdogface.com/pages/devices, https://www.getdogface.com/pages/kits, https://www.getdogface.com/pages/product-select-formulation, https://www.getdogface.com/pages/fragrance, https://www.getdogface.com/pages/product-select-hardware and https://www.getdogface.com/products/epic-masculinity and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.getdogface.com/products/deluxe-kit-with-technobrush-80 and https://www.getdogface.com/products/age-defying-kit use the same meta description. A description written for each page earns more clicks.

https://www.getdogface.com/pages/fragrance has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://event.havasedge.com/track-event?emeta=eyJwIjoiaHR0cHM6Ly93d3cuZ2V0ZG9nZmFjZS5jb20vIiwibyI6Imh0dHBzOi8vd3d3LmdldGRvZ2ZhY2UuY29tIiwiYW8iOltdLCJwYXJtcyI6e30sInByIjoiIiwiaW5mIjpmYWxzZSwibGNraWQiOi.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 524 words of visible text.

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 33 cookies, 2 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 47 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.