Website review, no card needed

gearheadoutfitters.com logo

gearheadoutfitters.com website review

Visit site (opens in a new tab)Reviewed 7 November 202634 issues · 80 checks

This review found 34 issues worth fixing on gearheadoutfitters.com, 15 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.1 s1.8 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.9 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.1 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
114 ms89 msMay 16Oct 31111 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202692 ms
May 23, 202695 ms
May 30, 202695 ms
Jun 6, 202695 ms
Jun 13, 202695 ms
Jun 20, 202695 ms
Jun 27, 202695 ms
Jul 4, 202695 ms
Jul 11, 202696 ms
Jul 18, 202697 ms
Jul 25, 202697 ms
Aug 1, 202698 ms
Aug 8, 202699 ms
Aug 15, 202699 ms
Aug 22, 202698 ms
Aug 29, 202699 ms
Sep 5, 202696 ms
Sep 12, 202696 ms
Sep 19, 202696 ms
Sep 26, 202696 ms
Oct 3, 2026101 ms
Oct 10, 2026104 ms
Oct 17, 2026106 ms
Oct 24, 2026110 ms
Oct 31, 2026111 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of gearheadoutfitters.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gearheadoutfitters.com at 0.6 s0.6 s
  2. gearheadoutfitters.com at 1.1 s1.1 s
  3. gearheadoutfitters.com at 1.7 s1.7 s
  4. gearheadoutfitters.com at 2.3 s2.3 s
  5. gearheadoutfitters.com at 2.8 s2.8 s
  6. gearheadoutfitters.com at 3.4 s3.4 s
  7. gearheadoutfitters.com at 3.9 s3.9 s
  8. gearheadoutfitters.com at 4.5 s4.5 s

Speed

13 to fix24
  • Reduce unused JavaScript

    5.4 s · 1.0 MB

    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.

  • Use efficient cache lifetimes

    3.5 s · 729 KiB

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

  • Mobile performance score: 24

    24/100

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

  • Main-thread work: 6.7 s

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

  • 4,032 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Azure Web Services and Klaviyo and others), adding 2.4 MB and 1.6 s of main-thread time.

  • Render-blocking requests

    750 ms

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

  • Improve image delivery

    500 ms · 155 KiB

    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 500 ms faster on a phone.

  • Google CDN adds 406 ms

    406 ms

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

  • Azure Web Services adds 377 ms

    377 ms

    Azure Web Services costs a phone 377 ms of main-thread work and 176 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.

  • Minify JavaScript

    300 ms · 39 KiB

    39 KiB could be saved by minifying JavaScript.

  • Klaviyo adds 200 ms

    200 ms

    Klaviyo costs a phone 200 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 adds 149 ms

    149 ms

    tidio.co costs a phone 149 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.

  • Legacy JavaScript

    250 ms · 68 KiB

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

  • Reduce unused CSS

    150 ms · 66 KiB

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

  • 20 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Duplicated JavaScript

    22 KiB

    22 KiB JavaScript is shipped twice across bundles.

  • Minify CSS

    10 KiB

    10 KiB could be saved by minifying CSS.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 7 ms

    7 ms

    Your server sent the HTML in 7 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user CLS: 0.28

    0.28

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

  • Largest Contentful Paint: 49.3 s

    49.3 s

    Your largest element takes 49.3 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…”.

  • Time to Interactive: 49.3 s

    49.3 s

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

  • Speed Index: 12.1 s

    12.1 s

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

  • Total Blocking Time: 969 ms

    969 ms

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Cumulative Layout Shift: 0.26

    0.26

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

  • Real-user LCP: 2.6 s

    2.6 s

    Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • 2 images without width and height

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

  • Tap response (INP) got 18% slower for real visitors

    +18%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

3 checks passed
  • Real-user INP: 103 ms

    103 ms

    Real visitors wait 103 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.3 s

    1.3 s

    Real visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 589 ms

    589 ms

    Real visitors wait 589 ms for your server to start answering (75th percentile). Good is under 800 ms.

Images and page weight

2 to fix60
  • Page weight: 9.3 MB in 288 requests

    9.3 MB

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

  • 1 image far larger than shown

    28 KiB

    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 below the first screen load straight away

    1 image further down the page (22 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.6 g of CO₂ per visit

    2.63 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

Google 100100
2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 18 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 18 WCAG 2.2 A/AA and best-practice rules on the phone render: 18 passed and 0 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9279
  • No meta description

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

  • Title is short (19 characters)

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

  • Structured data has 1 problem

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

  • Open Graph partly set

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

  • 466 internal links, 18 external

    The homepage links to 466 pages on gearheadoutfitters.com and 18 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Gearhead Outfitters”.

  • Canonical URL set

    The canonical URL is https://gearheadoutfitters.com/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://gearheadoutfitters.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (816 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://gearheadoutfitters.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 12 pages without a meta description

    https://gearheadoutfitters.com/pages/gh-locations, https://gearheadoutfitters.com/pages/customer-service, https://gearheadoutfitters.com/collections/men, https://gearheadoutfitters.com/collections/women, https://gearheadoutfitters.com/collections/kids and https://gearheadoutfitters.com/collections/camp-hike and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    36 of 37 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    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 detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 298 words of copy

    The homepage carries about 298 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP MEN”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Join the Team”, “Sign In / Sign Up” and “SHOP MEN”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    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.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 40 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at gearheadoutfitters.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 13 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Attentive · Google Youtube · Klaviyo Email Marketing Sms · Userway Website Accessibility · azureedge.net · trustpilot.com · one.store · gatsby.tech · storeify.app · cloudfront.net · attn.tv · digitaloceanspaces.com · Swym Wishlist Plus

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Gatsby
E-commerce
Shopify
Hosting
Shopify

Hiring

Hiring
39 open roles
Teams
The District (4), Bentonville (3), North Shore (3), Cleveland (2)
Job board
rippling

Company

Headquarters
Jonesboro

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on gearheadoutfitters.com, including 23 speed issues, 3 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25