sobrogoods.com website review

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

23 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

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

8 third-party services load with your homepage (omnisnippet1.com, Shopify and Attentive and others), adding 2.0 MB and 207 ms of main-thread time.

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

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

Soundest costs a phone 0 ms of main-thread work and 1.1 MB 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.

Shopify costs a phone 45 ms of main-thread work and 461 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 52 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 120 ms faster on a phone.

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.

Your largest element takes 20.5 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 21.5 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 5.7 MB in 263 requests on a phone: images 3.7 MB (48), other files 1.1 MB (87) and scripts 650 KiB (89). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example RockdustF_70aed3dc-4432-45ef-80b2-661f0c7b9216.jpg at 1,452 px wide, shown at 238 px. Resized copies would save about 1.1 MB.

RockdustF_70aed3dc-4432-45ef-80b2-661f0c7b9216.jpg weighs 518 KiB. On a phone connection a single image that size takes seconds.

Deer_Camp_Web_Banner.png 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 (518 KiB) is 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.

2 images further down the page (110 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.60 g of CO₂e: 192.3 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.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Your title is 69 characters, so Google will cut it off around 60: “Sobro Goods | Performance Hats & Apparel for the Outdoors – Sobro LLC”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“.logo_image { max-height: unset!important; width:…” and “.logo_image { max-height: unset!important; width:…”). One clear main headline is easier for people and search engines.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 72 pages on sobrogoods.com and 5 external pages.

A phone browser shows 825 words, but the HTML your server sends has only 228. 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.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://sobrogoods.com/collections/all, https://sobrogoods.com/collections/sobro-new-arrivals, https://sobrogoods.com/collections/blank-apparel-1, https://sobrogoods.com/collections/branded-apparel, https://sobrogoods.com/pages/custom-order-form and https://sobrogoods.com/pages/faq have no meta description, so Google writes the search snippet from whatever text it finds.

https://sobrogoods.com/collections/all, https://sobrogoods.com/collections/sobro-new-arrivals, https://sobrogoods.com/pages/find-your-fit, https://sobrogoods.com/collections/blank-apparel-1, https://sobrogoods.com/collections/branded-apparel and https://sobrogoods.com/collections/clearance and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://sobrogoods.com/pages/wholesale-application has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

17 of 63 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

Requests the notification permission on page load.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

Before a visitor clicks anything, the page loads 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 18 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.