equusnow.com website review

Shopify costs a phone 1.2 s of main-thread work and 965 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 4.3 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (Shopify, Klaviyo and crazyrocket.io and others), adding 1.8 MB and 1.6 s of main-thread time.

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

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

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

About 612 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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.

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

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

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

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

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

Your homepage downloads 3.7 MB in 307 requests on a phone: scripts 1.8 MB (149), other files 804 KiB (114) and images 801 KiB (26). Under 2 MB keeps phones on slow connections fast.

e427c2d8d05c1fe01887a4665903bc508a0fbc08da88aab27ae3b0d59c6a 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 (44 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.04 g of CO₂e: 124.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h1 → h3), 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 title is 69 characters, so Google will cut it off around 60: “Online English Tack & Riding Apparel | Shop Horse Gear & More - Equus”.

There are 2 <h1> headlines (“Equus Now!” and “Since 1999, Equus Now! has been committed to prov…”). One clear main headline is easier for people and search engines.

The homepage links to 416 pages on equusnow.com and 4 external pages.

/collections/new-arrivals-sort_by-created-descending-filter-v-price-gte-filter-v-price-lte-filter-v-availability-1-sort_by-created-descending-filter-v-price-gte-filter-v-price-lte-filter-v-availability-1, /collections/saddles-fittings, /collections/strap-goods, /collections/training-aids, /collections/horse-bits and /collections/horse-boots-and-leg-protection and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://option.ymq.cool/option/bottom.css' from origin 'https://equusnow.com' has been blo…”.

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.

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.

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

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