Website review, no card needed
bassins.com website review
Visit site (opens in a new tab)Reviewed 7 November 202640 issues · 85 checks
This review found 40 issues worth fixing on bassins.com, 15 of them high impact, across 85 checks. The most urgent: 13,479 HTML elements. 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
80B- #47,378 of 121,016 reviewed websitesbeats 55%
- #31,469 of 68,495 online storesbeats 48%
- #30,262 of 62,417 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 115 ms |
| May 23, 2026 | 119 ms |
| May 30, 2026 | 118 ms |
| Jun 6, 2026 | 115 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 122 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 132 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 133 ms |
| Aug 1, 2026 | 140 ms |
| Aug 8, 2026 | 147 ms |
| Aug 15, 2026 | 146 ms |
| Aug 22, 2026 | 153 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 144 ms |
| Sep 12, 2026 | 141 ms |
| Sep 19, 2026 | 139 ms |
| Sep 26, 2026 | 141 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 145 ms |
| Oct 17, 2026 | 147 ms |
| Oct 24, 2026 | 148 ms |
| Oct 31, 2026 | 146 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
13,479 HTML elements
The page has 13,479 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
1.1 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Main-thread work: 7.9 s
A phone's processor spends 7.9 s on main-thread work while loading, 2.7 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 (Google Tag Manager, Google CDN and Facebook and others), adding 1.6 MB and 1.1 s of main-thread time.
Improve image delivery
1.0 MB6 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 486 KiBAbout 486 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.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 571 ms. During a long task the page ignores taps.
Google Tag Manager adds 497 ms
497 msGoogle Tag Manager costs a phone 497 ms of main-thread work and 545 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 · 79 KiBAbout 79 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.
Use efficient cache lifetimes
338 KiB19 files are served with short cache lifetimes, so returning visitors download them again (338 KiB).
Google CDN adds 190 ms
190 msGoogle CDN costs a phone 190 ms of main-thread work and 331 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.
Shopify adds 95 ms
95 msShopify costs a phone 95 ms of main-thread work and 369 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
31 KiBPolyfills for old browsers add 31 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.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 22.3 s
22.3 sThe page becomes fully interactive after 22.3 s. Good is under 3.8 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.7 s
4.7 sYour largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s.
Tap response (INP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 115 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.4 s
5.4 sVisually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
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.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 178 ms
178 msReal visitors wait 178 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (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.
Real-user TTFB: 479 ms
479 msReal visitors wait 479 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 4.9 MB in 196 requests
4.9 MBYour homepage downloads 4.9 MB in 196 requests on a phone: scripts 2.4 MB (95), images 1.4 MB (13) and other files 658 KiB (68). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
810 KiB6 images are downloaded at several times the size a phone draws them, for example holidayH_2000x.png at 2,000 px wide, shown at 390 px. Resized copies would save about 810 KiB.
An image on the first screen is lazy-loaded
holidayH_2000x.png 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).
About 1.4 g of CO₂ per visit
1.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.39 g of CO₂e: 166.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 use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
24 text elements with low contrast
24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 99 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
556 internal links, 0 external
The homepage links to 556 pages on bassins.com and 0 external pages.
6 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Washington DC's leading fine wine shop and spirit importer since 1957. Visit Addy Bassin's MacArthur Beverages in DC or…”.
Title: 56 characters
Your title is a healthy 56 characters: “MacArthur Beverages Fine Wine & Spirits | Washington, DC”.
Canonical URL set
The canonical URL is https://bassins.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://bassins.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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.
Text is in the HTML
Your server sends the page's text in the HTML (7,599 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bassins.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://bassins.com/collections/bordeaux, https://bassins.com/collections/burgundy, https://bassins.com/collections/rhone, https://bassins.com/collections/alsace, https://bassins.com/collections/champagne and https://bassins.com/collections/loire and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://bassins.com/collections/bordeaux, https://bassins.com/collections/burgundy, https://bassins.com/collections/rhone, https://bassins.com/collections/champagne, https://bassins.com/collections/loire and https://bassins.com/collections/mosel and 4 others 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 175 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 broken images
2 images failed to load on a phone, for example https://bassins.com/.
13 small tap targets
13 of 57 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 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 3,745 words of copy
The homepage carries about 3,745 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
79 calls to action
The homepage has 79 calls to action, for example “Quick shop”, “Shop Staff Picks” and “NV Pol Roger - Champagne Brut Reserve”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
19 cookies set on arrival
19Opening the homepage sets 19 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.
25 other companies contacted
Loading the homepage contacts 25 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 bassins.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Smart Filter Search · Google Youtube · Smart Product Filters · The Shop Calendar
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
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on bassins.com, including 19 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.