Website review, no card needed

alabamaoutdoors.com logo

alabamaoutdoors.com website review

Visit site (opens in a new tab)Reviewed 19 October 202639 issues · 84 checks

This review found 39 issues worth fixing on alabamaoutdoors.com, 17 of them high impact, across 84 checks. The most urgent: improve image delivery. 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
3.7 s2.3 sApr 25Oct 102.8 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.5 s
May 2, 20262.5 s
May 9, 20262.6 s
May 16, 20262.9 s
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20263.1 s
Jun 27, 20263.4 s
Jul 4, 20263.5 s
Jul 11, 20263.6 s
Jul 18, 20263.6 s
Jul 25, 20263.5 s
Aug 1, 20263.0 s
Aug 8, 20262.7 s
Aug 15, 20262.6 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.6 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
145 ms99 msApr 25Oct 10118 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026104 ms
May 2, 2026104 ms
May 9, 2026113 ms
May 16, 2026126 ms
May 23, 2026129 ms
May 30, 2026129 ms
Jun 6, 2026128 ms
Jun 13, 2026125 ms
Jun 20, 2026129 ms
Jun 27, 2026138 ms
Jul 4, 2026140 ms
Jul 11, 2026140 ms
Jul 18, 2026140 ms
Jul 25, 2026137 ms
Aug 1, 2026127 ms
Aug 8, 2026120 ms
Aug 15, 2026115 ms
Aug 22, 2026112 ms
Aug 29, 2026112 ms
Sep 5, 2026112 ms
Sep 12, 2026113 ms
Sep 19, 2026112 ms
Sep 26, 2026114 ms
Oct 3, 2026118 ms
Oct 10, 2026118 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 alabamaoutdoors.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alabamaoutdoors.com at 0.8 s0.8 s
  2. alabamaoutdoors.com at 1.6 s1.6 s
  3. alabamaoutdoors.com at 2.4 s2.4 s
  4. alabamaoutdoors.com at 3.2 s3.2 s
  5. alabamaoutdoors.com at 4.0 s4.0 s
  6. alabamaoutdoors.com at 4.8 s4.8 s
  7. alabamaoutdoors.com at 5.6 s5.6 s
  8. alabamaoutdoors.com at 6.4 s6.4 s

Speed

14 to fix43
  • Improve image delivery

    18.3 s · 3.7 MB

    14 images could be 3.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 18.3 s faster on a phone.

  • Use efficient cache lifetimes

    8.6 s · 2.3 MB

    75 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).

  • Reduce unused JavaScript

    5.5 s · 1.1 MB

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

  • Render-blocking requests

    1.8 s

    8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

  • Mobile performance score: 43

    43/100

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

  • Main-thread work: 5.8 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Freshchat, Google Tag Manager and Cookiebot and others), adding 6.5 MB and 1.2 s of main-thread time.

  • Reduce unused CSS

    860 ms · 161 KiB

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

  • Minify JavaScript

    600 ms · 118 KiB

    118 KiB could be saved by minifying JavaScript.

  • Bigcommerce adds 151 ms

    151 ms

    Bigcommerce costs a phone 151 ms of main-thread work and 4.5 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.

  • Freshchat adds 319 ms

    319 ms

    Freshchat costs a phone 319 ms of main-thread work and 807 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.

  • 2,915 HTML elements

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

  • 17 long tasks on the main thread

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

  • Google Tag Manager adds 187 ms

    187 ms

    Google Tag Manager costs a phone 187 ms of main-thread work and 560 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

    33 KiB

    Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need.

  • Duplicated JavaScript

    8 KiB

    8 KiB JavaScript is shipped twice across bundles.

  • 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.

1 checks passed
  • Server response: 25 ms

    25 ms

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

Core Web Vitals

9 to fix67
  • 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 LCP: 5.1 s

    5.1 s

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

  • Largest Contentful Paint: 44.2 s

    44.2 s

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

  • Time to Interactive: 45.1 s

    45.1 s

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

  • First Contentful Paint: 7.4 s

    7.4 s

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

  • Speed Index: 14.6 s

    14.6 s

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

  • Real-user FCP: 2.8 s

    2.8 s

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

  • Total Blocking Time: 487 ms

    487 ms

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

  • 11 images without width and height

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

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

    +13%

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

  • Largest content (LCP) got 11% slower for real visitors

    +11%

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

4 checks passed
  • Real-user INP: 154 ms

    154 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user TTFB: 784 ms

    784 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 7.6 MB in 201 requests

    7.6 MB

    Your homepage downloads 7.6 MB in 201 requests on a phone: images 4.4 MB (58), scripts 2.7 MB (65) and stylesheets 261 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    5hometowntees.jpg weighs 1.1 MB. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    1.0 MB

    6 images are downloaded at several times the size a phone draws them, for example 5hometowntees.jpg at 1,362 px wide, shown at 369 px. Resized copies would save about 1.0 MB.

  • 5 images below the first screen load straight away

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

  • 5 images in older formats

    5 images (992 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.

  • About 2.2 g of CO₂ per visit

    2.16 g

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

Accessibility

2 to fixGoogle 9595
  • 10 text elements with low contrast

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 59 images in the HTML carry an alt attribute.

  • 29 automated accessibility rules passed

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

SEO

4 to fixGoogle 10080
  • Title is short (16 characters)

    Your title is only 16 characters: “Alabama Outdoors”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

  • Meta description is long (306 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

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

  • 338 internal links, 9 external

    The homepage links to 338 pages on alabamaoutdoors.com and 9 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: ClothingStore, OnlineStore, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

AI search readiness

100
  • No llms.txt

    There is no https://alabamaoutdoors.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.

3 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: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

3 to fixGoogle 6976
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187197042&Ver=2&mid=4b0275f2-4285-42f9-b563-ec9db5114b43&bo=1&sid=cbb01b50cb8511f1990e03e6cb92db22&vid=cbb059f0cb8511f1bce0411e9df28a6b&vids=1&msclkid=N&pi=918639831&l.

  • 7 third-party cookies

    7 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Unexpected token '%'”.

  • Missing source maps

    Large scripts ship without source maps.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    48 of 55 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • Local business without LocalBusiness data

    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.

  • Thin social proof

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

  • No opening hours

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 284 words of copy

    The homepage carries about 284 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Return Policy/Start A Return”, “All Return Policy/Start A Return” and “Start a return”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 32 cookies set on arrival

    32

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

  • 46 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 alabamaoutdoors.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
BigCommerce
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on alabamaoutdoors.com, including 23 speed issues, 4 SEO issues and 2 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