saugear.com website review

About 736 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 590 ms faster on a phone.

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

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

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

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

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

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

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

7 third-party services load with your homepage (Google Tag Manager, Hubspot and Shopify and others), adding 635 KiB and 288 ms of main-thread time.

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

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 JavaScript is shipped twice across bundles.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.1 MB in 165 requests on a phone: images 1.6 MB (38), scripts 747 KiB (48) and other files 631 KiB (71). Under 2 MB keeps phones on slow connections fast.

chantal.sallade-4_6.jpg 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).

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

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

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

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

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

Your title is 89 characters, so Google will cut it off around 60: “Official SAU Campus Store | Spring Arbor University Bookstore – Spring Arbor Campus Store”.

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

Your <h1> is empty.

The homepage links to 236 pages on saugear.com and 5 external pages.

There is no https://saugear.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://saugear.com/collections/mens-show-all, https://saugear.com/collections/mens-tshirts, https://saugear.com/collections/mens-sweatshirts, https://saugear.com/collections/mens-tops and https://saugear.com/collections/mens-bottoms have no meta description, so Google writes the search snippet from whatever text it finds.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

Before a visitor clicks anything, the page loads HubSpot and Meta Pixel (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 18 cookies, 7 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.