Website review, no card needed
stagprovision.com website review
Visit site (opens in a new tab)Reviewed 6 November 202623 issues · 64 checks
This review found 23 issues worth fixing on stagprovision.com, 7 of them high impact, across 64 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 149 ms |
| May 23, 2026 | 141 ms |
| May 30, 2026 | 141 ms |
| Jun 6, 2026 | 141 ms |
| Jun 13, 2026 | 145 ms |
| Jun 20, 2026 | 151 ms |
| Jun 27, 2026 | 155 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 141 ms |
| Jul 18, 2026 | 141 ms |
| Jul 25, 2026 | 140 ms |
| Aug 1, 2026 | 145 ms |
| Aug 8, 2026 | 145 ms |
| Aug 15, 2026 | 153 ms |
| Aug 22, 2026 | 149 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 142 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 145 ms |
| Sep 26, 2026 | 147 ms |
| Oct 3, 2026 | 158 ms |
| Oct 10, 2026 | 163 ms |
| Oct 17, 2026 | 170 ms |
| Oct 24, 2026 | 171 ms |
| Oct 31, 2026 | 161 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
Speed
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user CLS: 0.19
0.19For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 149 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 159 ms
159 msReal visitors wait 159 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 413 ms
413 msReal visitors wait 413 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 7.0 MB
7.0 MBYour homepage downloads 7.0 MB on a phone, 3.6 MB of it images (51%). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
RGT_Desktop_4caa15be-6008-4228-9c43-b469e0a61cf1_1.webp weighs 808 KiB. On a phone connection a single image that size takes seconds.
12 images in older formats
12 images (2.7 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.
An image on the first screen is lazy-loaded
Ruddick_Matt_Mobile.jpg 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).
2 images far larger than shown
186 KiB2 images are downloaded at several times the size a phone draws them, for example RGT_Mobile_4c62fb99-3860-4844-a5e1-02a129e6fd53_1.webp at 1,187 px wide, shown at 390 px. Resized copies would save about 186 KiB.
1 image below the first screen load straight away
1 image further down the page (439 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.0 g of CO₂ per visit
1.98 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.98 g of CO₂e: 237.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
30 buttons without a name
30 buttons have no accessible name, so screen readers announce just “button”.
20 text elements with low contrast
20 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (81 elements)
All page content should be contained by landmarks: 81 elements on the page fail this check, rated moderate by axe-core.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
51 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: 51 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (82 characters)
Your title is 82 characters, so Google will cut it off around 60: “Contemporary Men's Clothing With Classic Roots. Always In Style. – STAG Provisions”.
Structured data has 1 problem
Structured data found (LocalBusiness, Organization and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("stagprovisions.com")”.
376 internal links, 5 external
The homepage links to 376 pages on stagprovision.com and 5 external pages.
6 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Named a "Top 10 Men's Store In America" by GQ & Esquire Magazines, STAG specializes in contemporary clothing with class…”.
One H1 headline
Your main headline reads: “FALL'S TAKEN HOLD”.
Canonical URL set
The canonical URL is https://stagprovisions.com/.
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://stagprovisions.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://stagprovisions.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: 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 (1,309 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without an H1
https://stagprovisions.com/collections/new-arrivals and https://stagprovisions.com/collections/tops have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 139 found) and read each the way a search engine does.
6 checks passed
Linked pages load
7 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 7 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
37 small tap targets
37 of 183 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “AOS is not defined”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: “75+ Brands”. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 690 words of copy
The homepage carries about 690 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop All Brands” and “Contact”.
28 calls to action
The homepage has 28 calls to action, for example “SHOP RRL”, “Shop All 75+ Brands” and “Shop All-Time Bestsellers”.
75 short forms
75 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.
19 cookies set on arrival
19Opening the homepage sets 19 cookies (measured from a US location before any click).
57 other companies contacted
Loading the homepage contacts 57 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Osano
A consent management tool (Osano) 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 stagprovision.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on stagprovision.com, including 2 speed issues, 2 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.