Website review, no card needed
asspocketwhiskey.com website review
Visit site (opens in a new tab)Reviewed 7 November 202624 issues · 78 checks
This review found 24 issues worth fixing on asspocketwhiskey.com, 8 of them high impact, across 78 checks. The most urgent: page weight: 16.5 MB in 195 requests. 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
86B- #12,017 of 123,940 reviewed websitesbeats 87%
- #7,284 of 69,726 online storesbeats 85%
- #7,056 of 63,429 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 829 ms |
| May 23, 2026 | 828 ms |
| May 30, 2026 | 768 ms |
| Jun 6, 2026 | 731 ms |
| Jun 13, 2026 | 782 ms |
| Jun 20, 2026 | 828 ms |
| Jun 27, 2026 | 888 ms |
| Jul 4, 2026 | 936 ms |
| Jul 11, 2026 | 926 ms |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 960 ms |
| Aug 1, 2026 | 926 ms |
| Aug 8, 2026 | 929 ms |
| Aug 15, 2026 | 912 ms |
| Aug 22, 2026 | 870 ms |
| Aug 29, 2026 | 871 ms |
| Sep 5, 2026 | 872 ms |
| Sep 12, 2026 | 812 ms |
| Sep 19, 2026 | 788 ms |
| Sep 26, 2026 | 771 ms |
| Oct 3, 2026 | 741 ms |
| Oct 10, 2026 | 807 ms |
| Oct 17, 2026 | 828 ms |
| Oct 24, 2026 | 856 ms |
| Oct 31, 2026 | 871 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 75 ms |
| May 23, 2026 | 71 ms |
| May 30, 2026 | 72 ms |
| Jun 6, 2026 | 78 ms |
| Jun 13, 2026 | 81 ms |
| Jun 20, 2026 | 85 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 88 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 86 ms |
| Jul 25, 2026 | 85 ms |
| Aug 1, 2026 | 83 ms |
| Aug 8, 2026 | 85 ms |
| Aug 15, 2026 | 85 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 88 ms |
| Sep 5, 2026 | 91 ms |
| Sep 12, 2026 | 91 ms |
| Sep 19, 2026 | 88 ms |
| Sep 26, 2026 | 87 ms |
| Oct 3, 2026 | 87 ms |
| Oct 10, 2026 | 87 ms |
| Oct 17, 2026 | 87 ms |
| Oct 24, 2026 | 87 ms |
| Oct 31, 2026 | 84 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.9 s
1.3 s
1.7 s
2.2 s
2.6 s
3.0 s
3.5 s
Speed
Mobile performance score: 88
88/100Your mobile performance score is 88. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
450 ms · 148 KiB5 images could be 148 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Render-blocking requests
450 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
1,750 HTML elements
The page has 1,750 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 134 ms
134 msKlaviyo costs a phone 134 ms of main-thread work and 328 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.
cloudfront.net adds 0 ms
0 mscloudfront.net costs a phone 0 ms of main-thread work and 436 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.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, stockist.co and Shopify and others), adding 997 KiB and 212 ms of main-thread time.
Use efficient cache lifetimes
110 KiB8 files are served with short cache lifetimes, so returning visitors download them again (110 KiB).
Reduce unused JavaScript
108 KiBAbout 108 KiB of JavaScript is downloaded but never used on this page.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 71 ms. During a long task the page ignores taps.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 573 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 8.4 s
8.4 sThe page becomes fully interactive after 8.4 s. Good is under 3.8 s.
Largest Contentful Paint: 3.8 s
3.8 sYour largest element takes 3.8 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 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 75 ms to 84 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 87 ms
87 msReal visitors wait 87 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: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 361 ms
361 msReal visitors wait 361 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 2.7 s
2.7 sVisually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 21 ms
21 msScripts block the page for only 21 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 16.5 MB in 195 requests
16.5 MBYour homepage downloads 16.5 MB in 195 requests on a phone: media 14.3 MB (1), images 853 KiB (9) and other files 681 KiB (79). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (436 KiB) is 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.
2 images below the first screen load straight away
2 images further down the page (94 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.7 g of CO₂ per visit
4.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.69 g of CO₂e: 562.5 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
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 4 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (18 characters)
Your title is only 18 characters: “Ass Pocket Whiskey”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
50 internal links, 11 external
The homepage links to 50 pages on asspocketwhiskey.com and 11 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://asspocketwhiskey.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://asspocketwhiskey.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,101 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://asspocketwhiskey.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without a meta description
https://asspocketwhiskey.com/pages/about-apw, https://asspocketwhiskey.com/pages/apw-original, https://asspocketwhiskey.com/pages/limited-releases, https://asspocketwhiskey.com/pages/store-locator and https://asspocketwhiskey.com/pages/merch have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://asspocketwhiskey.com/products/ass-pocket-release-no-7-two-pack, https://asspocketwhiskey.com/products/bundle-save-20-apw-no-7-two-pack-original-three-pack, https://asspocketwhiskey.com/products/ass-pocket-release-no-7-two-pack-no-7-bottle and https://asspocketwhiskey.com/products/ass-pocket-release-no-7-single-bottle use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://asspocketwhiskey.com/pages/about-apw, https://asspocketwhiskey.com/pages/apw-original, https://asspocketwhiskey.com/pages/limited-releases, https://asspocketwhiskey.com/pages/store-locator, https://asspocketwhiskey.com/pages/merch and https://asspocketwhiskey.com/pages/corporate-and-bulk-gifting have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://asspocketwhiskey.com/pages/store-locator has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.
5 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.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
2 checks passed
Tap targets are thumb-sized
9 of 10 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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,281 words of copy
The homepage carries about 1,281 words of visible text.
3 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Shop Original”, “Shop Limited Releases” and “Shop Merch”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 0 phone links and 3 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Klaviyo 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
19 other companies contacted
Loading the homepage contacts 19 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 asspocketwhiskey.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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Hulk Form Builder · Klaviyo Email Marketing Sms
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
- Bootstrap
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on asspocketwhiskey.com, including 8 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.