gho.com website review

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.4 s faster on a phone.

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

Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (Google CDN, Klaviyo and Attentive and others), adding 2.4 MB and 926 ms of main-thread time.

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

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

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

Google CDN costs a phone 328 ms of main-thread work and 919 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.

Polyfills for old browsers add 68 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

39 KiB could be saved by minifying JavaScript.

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

tidio.co costs a phone 82 ms of main-thread work and 515 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.

10 KiB could be saved by minifying CSS.

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

22 KiB JavaScript is shipped twice across bundles.

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.

For real visitors the layout shifts by 0.28 (75th percentile). Good is under 0.1.

Your largest element takes 48.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Male wearing Kuhl 1/4 zip fleece pullover in wintery enviro…”.

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

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

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

The layout shifts by 0.261 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

Your homepage downloads 9.3 MB in 299 requests on a phone: fonts 5.1 MB (14), scripts 2.6 MB (114) and other files 865 KiB (122). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example gearhead_outfitters.webp at 1,376 px wide, shown at 390 px. Resized copies would save about 28 KiB.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 19 characters: “Gearhead Outfitters”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your canonical URL points to gearheadoutfitters.com, not gho.com, so Google may credit that host instead.

Structured data found (Corporation, Organization and WebSite) but with 2 problems, for example “WebSite: potentialAction.target is not an absolute URL ("/search?q={search_term_string}")”.

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

The homepage links to 465 pages on gho.com and 19 external pages.

/pages/gh-locations, /pages/customer-service, /collections/men, /collections/women, /collections/kids and /collections/camp-hike and 6 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.

4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'replace')”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

gho.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

gho.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

DMARC is set to p=none, so mail pretending to be gho.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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