Website review, no card needed
whiskeybenthatco.com website review
Visit site (opens in a new tab)Reviewed 9 November 202632 issues · 85 checks
This review found 32 issues worth fixing on whiskeybenthatco.com, 7 of them high impact, across 85 checks. The most urgent: fails Core Web Vitals for real visitors. 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
88B- #6,033 of 126,428 reviewed websitesbeats 93%
- #3,204 of 70,467 online storesbeats 93%
- #3,102 of 63,968 Shopify storesbeats 93%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 992 ms |
| Aug 22, 2026 | 979 ms |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.1 s |
| Nov 7, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 88 ms |
| May 30, 2026 | 88 ms |
| Jun 6, 2026 | 91 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 95 ms |
| Jul 4, 2026 | 96 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 96 ms |
| Aug 1, 2026 | 97 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 99 ms |
| Aug 29, 2026 | 102 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 111 ms |
| Sep 19, 2026 | 111 ms |
| Sep 26, 2026 | 120 ms |
| Oct 3, 2026 | 129 ms |
| Oct 10, 2026 | 130 ms |
| Oct 17, 2026 | 137 ms |
| Oct 24, 2026 | 134 ms |
| Oct 31, 2026 | 131 ms |
| Nov 7, 2026 | 133 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.2 s
1.6 s
2.0 s
2.4 s
2.7 s
3.1 s
Speed
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
500 ms · 1.0 MB4 images could be 1.0 MB 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.
Mobile performance score: 76
76/100Your mobile performance score is 76. 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 (Shopify, Clarity and POWr and others), adding 974 KiB and 824 ms of main-thread time.
Render-blocking requests
450 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Shopify adds 363 ms
363 msShopify costs a phone 363 ms of main-thread work and 611 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 JavaScript
346 KiBAbout 346 KiB of JavaScript is downloaded but never used on this page.
1,863 HTML elements
The page has 1,863 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 224 ms. During a long task the page ignores taps.
Reduce unused CSS
130 ms · 56 KiBAbout 56 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 130 ms faster on a phone.
Minify JavaScript
130 ms · 7 KiB7 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
83 KiB18 files are served with short cache lifetimes, so returning visitors download them again (83 KiB).
Legacy JavaScript
40 KiBPolyfills for old browsers add 40 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: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 17.4 s
17.4 sThe page becomes fully interactive after 17.4 s. Good is under 3.8 s.
Largest Contentful Paint: 5.0 s
5.0 sYour largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Tap response (INP) got 50% slower for real visitors
+50%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 88 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 879 ms
879 msReal visitors wait 879 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.6 s
3.6 sVisually, the page fills in at 3.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 227 ms
227 msScripts block taps and scrolling for 227 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 128 ms
128 msReal visitors wait 128 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.01
0.01The layout barely moves while loading (CLS 0.01, good is under 0.1).
Images and page weight
Page weight: 3.5 MB in 273 requests
3.5 MBYour homepage downloads 3.5 MB in 273 requests on a phone: images 1.4 MB (38), scripts 1.2 MB (90) and other files 874 KiB (120). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
1.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.01 g of CO₂e: 120.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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 (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 49 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 2 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 short (24 characters)
Your title is only 24 characters: “Whiskey Bent Hat Company”. Between 30 and 65 characters leaves room to say what you do and for whom.
91 internal links, 7 external
The homepage links to 91 pages on whiskeybenthatco.com and 7 external pages.
7 checks passed
Meta description: 122 characters
Your meta description is 122 characters: “Whiskey Bent Hat Company makes high quality hats and outerwear for old school people that live simple, hard-working liv…”.
One H1 headline
Your main headline reads: “Free Hat & KOOZIE On Us”.
Canonical URL set
The canonical URL is https://whiskeybenthatco.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://whiskeybenthatco.com/sitemap.xml.
AI search readiness
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 (1,548 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://whiskeybenthatco.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://whiskeybenthatco.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://whiskeybenthatco.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
6 pages without a meta description
https://whiskeybenthatco.com/collections/new-hats, https://whiskeybenthatco.com/collections/hoodies, https://whiskeybenthatco.com/collections/fall-collection, https://whiskeybenthatco.com/collections/buckles, https://whiskeybenthatco.com/collections/sale and https://whiskeybenthatco.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages share a meta description
https://whiskeybenthatco.com/products/the-drover, https://whiskeybenthatco.com/products/the-tombstone, https://whiskeybenthatco.com/products/the-elko, https://whiskeybenthatco.com/products/the-cimarron, https://whiskeybenthatco.com/products/the-winnemucca and https://whiskeybenthatco.com/products/the-blanco use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://whiskeybenthatco.com/collections/sale and https://whiskeybenthatco.com/customer_authentication/redirect 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 45 found) and read each the way a search engine does.
3 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.
Best practices
23 small tap targets
23 of 91 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Framing 'https://www.facebook.com/' violates the following report-only Content Security Policy directive: "default-src …”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
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 1,078 words of copy
The homepage carries about 1,078 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 NOW” and “Shop Hats”.
7 calls to action
The homepage has 7 calls to action, for example “SHOP NOW”, “Shop Hats” and “Shop Now – our best-selling hats”.
3 short forms
3 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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.
24 cookies set on arrival
24Opening the homepage sets 24 cookies, 1 of them by other companies (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.
41 other companies contacted
Loading the homepage contacts 41 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 whiskeybenthatco.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 18 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Postscript Sms Marketing · Klaviyo Email Marketing Sms · Microsoft Clarity · Test Sms · Frontend · Unlimited Smart Upsell Offers · Freegifts · Slide Cart · powr.io · revy.io · b-cdn.net · snapchat.com · nfcube.com · richpanel.com · salesreps.io · mailmunch.co · cloudfront.net · bogos.io
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
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Brownsboro
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on whiskeybenthatco.com, including 15 speed issues, 1 SEO issue 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.