elspet.com website review

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

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

8 third-party services load with your homepage (Klaviyo, trytadapp.com and Facebook and others), adding 2.5 MB and 978 ms of main-thread time.

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

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

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

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

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

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

trytadapp.com costs a phone 140 ms of main-thread work and 751 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.

ZenDesk costs a phone 134 ms of main-thread work and 431 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 130 ms of main-thread work and 341 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.

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

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

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

About 39 KiB of CSS is downloaded but never applied on this page.

11 KiB could be saved by minifying CSS.

10 KiB could be saved by minifying JavaScript.

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.

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

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

Your largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (4.2 s).

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your homepage downloads 6.0 MB in 381 requests on a phone: scripts 3.6 MB (149), images 1.1 MB (61) and other files 795 KiB (133). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

All page content should be contained by landmarks: 36 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Headings should not be empty: 28 elements on the page fail this check, rated minor by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 155 pages on elspet.com and 11 external pages.

https://www.elspet.com/collections/bundles, https://www.elspet.com/collections/accessories, https://www.elspet.com/collections/subscription, https://www.elspet.com/collections/cat-litter-box-waste-drawer-liners, https://www.elspet.com/collections/cat-litter and https://www.elspet.com/collections/accessories-for-orbitie-litter-box and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.elspet.com/apps/17TRACK, whose canonical is https://www.elspet.com/apps/17track. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

6 errors were logged to the browser console while the page loaded, for example “Swiper is not defined”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Requests the notification permission on page load.

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 1,012 words of visible text.

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