tidytechpet.com website review

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

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

8 third-party services load with your homepage (Shopify, JSDelivr CDN and nfcube.com and others), adding 1.1 MB and 483 ms of main-thread time.

Shopify costs a phone 418 ms of main-thread work and 915 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 359 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

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

Polyfills for old browsers add 7 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.

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 CSS.

3 KiB could be saved by minifying JavaScript.

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

Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A woman relaxes in a brown leather armchair next to a large…”.

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

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

1 image 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 99 ms to 106 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 292 requests on a phone: scripts 1.1 MB (75), other files 1.0 MB (126) and images 788 KiB (54). Under 2 MB keeps phones on slow connections fast.

2 images further down the page (46 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

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.

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

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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. (1 element).

Your <h1> is empty.

The homepage links to 110 pages on tidytechpet.com and 10 external pages.

A phone browser shows 2,693 words, but the HTML your server sends has only 741. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

/ and https://www.tidytechpet.com/collections/automatic-dog-doors all use the title “Automatic Dog Door – TidyTechPet”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tidytechpet.com/collections/sensor-dog-door, https://www.tidytechpet.com/collections/accessories and https://www.tidytechpet.com/pages/troubleshooting have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tidytechpet.com/products/automatic-dog-doors-for-door-mount, https://www.tidytechpet.com/products/automatic-dog-doors-for-wall-mount, https://www.tidytechpet.com/products/automatic-dog-doors-for-sliding-glass-door, https://www.tidytechpet.com/products/automatic-dog-doors-custom-size, https://www.tidytechpet.com/pages/contact-us and https://www.tidytechpet.com/pages/smart-pet-door-measurement-guide and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.tidytechpet.com/products/automatic-dog-doors-custom-size, https://www.tidytechpet.com/pages/smart-pet-door-measurement-guide and https://www.tidytechpet.com/pages/warranty-registration took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://www.tidytechpet.com/.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 2,693 words of visible text.

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