Website review, no card needed
greatoutdoorprovision.com website review
Visit site (opens in a new tab)Reviewed 24 October 202636 issues · 86 checks
This review found 36 issues worth fixing on greatoutdoorprovision.com, 9 of them high impact, across 86 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84B- #22,130 of 124,214 reviewed websitesbeats 77%
- #14,248 of 69,818 online storesbeats 74%
- #13,817 of 63,496 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.3 s |
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 80 ms |
| May 9, 2026 | 80 ms |
| May 16, 2026 | 82 ms |
| May 23, 2026 | 83 ms |
| May 30, 2026 | 83 ms |
| Jun 6, 2026 | 83 ms |
| Jun 13, 2026 | 81 ms |
| Jun 20, 2026 | 82 ms |
| Jun 27, 2026 | 83 ms |
| Jul 4, 2026 | 85 ms |
| Jul 11, 2026 | 86 ms |
| Jul 18, 2026 | 85 ms |
| Jul 25, 2026 | 86 ms |
| Aug 1, 2026 | 84 ms |
| Aug 8, 2026 | 85 ms |
| Aug 15, 2026 | 83 ms |
| Aug 22, 2026 | 83 ms |
| Aug 29, 2026 | 82 ms |
| Sep 5, 2026 | 81 ms |
| Sep 12, 2026 | 81 ms |
| Sep 19, 2026 | 81 ms |
| Sep 26, 2026 | 81 ms |
| Oct 3, 2026 | 82 ms |
| Oct 10, 2026 | 87 ms |
| Oct 17, 2026 | 87 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
2.5 s · 3.9 MB10 images could be 3.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.
Mobile performance score: 68
68/100Your mobile performance score is 68 (desktop: 84). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, tabarn.app and speaz.com and others), adding 1.9 MB and 639 ms of main-thread time.
Reduce unused JavaScript
150 ms · 686 KiBAbout 686 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
YouTube adds 329 ms
329 msYouTube costs a phone 329 ms of main-thread work and 962 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.
Reduce unused CSS
300 ms · 122 KiBAbout 122 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.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,438 HTML elements
The page has 2,438 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 13 ms
13 msShopify costs a phone 13 ms of main-thread work and 662 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.
Render-blocking requests
150 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Use efficient cache lifetimes
125 KiB16 files are served with short cache lifetimes, so returning visitors download them again (125 KiB).
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 120 ms. During a long task the page ignores taps.
Minify JavaScript
12 KiB12 KiB could be saved by minifying JavaScript.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.4 s
11.4 sYour largest element takes 11.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 16.6 s
16.6 sThe page becomes fully interactive after 16.6 s. Good is under 3.8 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
Speed Index: 4.8 s
4.8 sVisually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 80 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 101 ms
101 msReal visitors wait 101 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 735 ms
735 msReal visitors wait 735 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Total Blocking Time: 51 ms
51 msScripts block the page for only 51 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 8.6 MB in 322 requests
8.6 MBYour homepage downloads 8.6 MB in 322 requests on a phone: images 5.9 MB (108), scripts 1.5 MB (62) and other files 849 KiB (127). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.
3 images in older formats
3 images (2.4 MB) 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.
10 images below the first screen load straight away
10 images further down the page (304 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.4 g of CO₂ per visit
2.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.44 g of CO₂e: 292.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Summary elements must have discernible text (1 element)
Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
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 (h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 46 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Great Outdoor Provision Co. | Outdoor Clothing & Gear + Expert Advice”.
5 H1 headlines
There are 5 <h1> headlines (“VoyaX: MOSSA 128”, “OldTown Sportsman PDL 120 Pro” and “Yakima Cargo Box Rental”). One clear main headline is easier for people and search engines.
Meta description is long (243 characters)
Your meta description is 243 characters; Google truncates after about 160, so the end of your pitch is cut.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
276 internal links, 9 external
The homepage links to 276 pages on greatoutdoorprovision.com and 9 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.greatoutdoorprovision.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://www.greatoutdoorprovision.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
20%A phone browser shows 4,070 words, but the HTML your server sends has only 825. 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.
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://www.greatoutdoorprovision.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
11 pages without a meta description
https://www.greatoutdoorprovision.com/collections/kuhl, https://www.greatoutdoorprovision.com/collections/patagonia, https://www.greatoutdoorprovision.com/collections/toad-co, https://www.greatoutdoorprovision.com/collections/mens-shirts, https://www.greatoutdoorprovision.com/collections/mens-sweaters and https://www.greatoutdoorprovision.com/collections/mens-pants and 5 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 130 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
12 small tap targets
12 of 47 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. 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 4,070 words of copy
The homepage carries about 4,070 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: “LEARN MORE” and “SHOP NOW”.
16 calls to action
The homepage has 16 calls to action, for example “MULEgear Demo Program”, “Join MULEteam” and “Shop to Wear”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and 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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
27 other companies contacted
Loading the homepage contacts 27 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 greatoutdoorprovision.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
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on greatoutdoorprovision.com, including 13 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.