saraglove.com website review

8 third-party services load with your homepage (chatra.io, Google Tag Manager and Shopify and others), adding 1.4 MB and 1.1 s of main-thread time.

24 images could be 994 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.

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

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

chatra.io costs a phone 495 ms of main-thread work and 388 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 343 ms of main-thread work and 509 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 3.2 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

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

3 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

Your largest element takes 14.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Aurelia Disposable Gloves Exam Grade Gloves w/ Pallet Prici…”.

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

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

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

Visually, the page fills in at 3.9 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 137 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.1 MB in 368 requests on a phone: images 4.5 MB (93), scripts 1.5 MB (72) and other files 990 KiB (192). Under 2 MB keeps phones on slow connections fast.

16 images are downloaded at several times the size a phone draws them, for example 6898CB.jpg at 1,695 px wide, shown at 330 px. Resized copies would save about 1.2 MB.

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

5 images (671 KiB) are 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 2.00 g of CO₂e: 239.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

54 elements hidden from screen readers can still receive keyboard focus.

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

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

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

Alternative text of images should not be repeated as text: 10 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 → h6, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

Your title is 68 characters, so Google will cut it off around 60: “Sara Glove Company | Work Gloves, Safety Supplies, Rain Wear, Towels”.

Structured data found (Organization, Store and WebSite) but with 5 problems, for example “Organization: sameAs is not an absolute URL ("https")”.

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

Your <h1> is empty.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 237 pages on saraglove.com and 11 external pages.

https://www.saraglove.com/collections/clearance and https://www.saraglove.com/collections/hearing-protection have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5213823&Ver=2&mid=48efaa97-98a3-496b-a612-c0f4617029a0&bo=1&sid=97d0f0e0db3311f1a0e6550e0e36a465&vid=97d12080db3311f1bfb54dc7fd06e467&vids=1&msclkid=N&pi=918639831&lg=.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

The homepage shows no opening hours. If customers visit or call, show when.

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 844 words of visible text.

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