Website review, no card needed

basiccellars.com logo

basiccellars.com website review

Visit site (opens in a new tab)Reviewed 16 November 202627 issues · 68 checks

This review found 27 issues worth fixing on basiccellars.com, 8 of them high impact, across 68 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of basiccellars.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. basiccellars.com at 0.4 s0.4 s
  2. basiccellars.com at 0.8 s0.8 s
  3. basiccellars.com at 1.1 s1.1 s
  4. basiccellars.com at 1.5 s1.5 s
  5. basiccellars.com at 1.9 s1.9 s
  6. basiccellars.com at 2.3 s2.3 s
  7. basiccellars.com at 2.6 s2.6 s
  8. basiccellars.com at 3.0 s3.0 s

Speed

6 to fix62
  • Render-blocking requests

    3.6 s

    18 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.

  • Reduce unused JavaScript

    1.7 s · 380 KiB

    About 380 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62. 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 (Hotjar, Google Tag Manager and Adroll and others), adding 860 KiB and 622 ms of main-thread time.

  • Main-thread work: 2.4 s

    A phone's processor spends 2.4 s on main-thread work while loading, 867 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Google Tag Manager adds 174 ms

    174 ms

    Google Tag Manager costs a phone 174 ms of main-thread work and 344 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.

  • Use efficient cache lifetimes

    150 ms · 121 KiB

    14 files are served with short cache lifetimes, so returning visitors download them again (121 KiB).

  • Minify JavaScript

    240 ms · 14 KiB

    14 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    150 ms · 44 KiB

    About 44 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 175 ms. During a long task the page ignores taps.

  • Improve image delivery

    48 KiB

    6 images could be 48 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    35 KiB

    Polyfills for old browsers add 35 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.

1 checks passed
  • Server response: 7 ms

    7 ms

    Your server sent the HTML in 7 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix64
  • Largest Contentful Paint: 6.5 s

    6.5 s

    Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 14.3 s

    14.3 s

    The page becomes fully interactive after 14.3 s. Good is under 3.8 s.

  • First Contentful Paint: 4.0 s

    4.0 s

    The first text or image appears after 4.0 s on a phone. Good is under 1.8 s.

  • Speed Index: 4.1 s

    4.1 s

    Visually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 263 ms

    263 ms

    Scripts block taps and scrolling for 263 ms in total while the page loads. Good is under 200 ms.

  • 6 images without width and height

    6 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.029

    0.029

    The layout barely moves while loading (CLS 0.029, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 2.4 MB in 254 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 254 requests on a phone: scripts 996 KiB (63), other files 727 KiB (109) and images 403 KiB (43). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (50 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.7 g of CO₂ per visit

    0.69 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.69 g of CO₂e: 82.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9294
  • 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.

  • 6 images without alt text

    6 images have no alt text, which hurts accessibility and image search.

  • 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.

  • 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.

  • Headings skip levels

    Headings skip levels (h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8575
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (13 characters)

    Your title is only 13 characters: “Basic Cellars”. 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.

  • 35 internal links, 4 external

    The homepage links to 35 pages on basiccellars.com and 4 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://basiccellars.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://basiccellars.com/sitemap.xml.

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    59%

    The HTML your server sends has 545 of the 930 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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://basiccellars.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    14 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix83
  • 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 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: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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.

  • About 930 words of copy

    The homepage carries about 930 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP THE SALE”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact”, “Shop the Sale” and “Shop Now”.

  • 5 short forms

    5 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo 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.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 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.

  • 22 other companies contacted

    Loading the homepage contacts 22 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 basiccellars.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 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Instafeed · Klaviyo Email Marketing Sms · Promotion Popup Allnew · Applovin Shop Integration · adroll.com · nfcube.com · loox.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

  • The footer still says © 2025.

Stack

E-commerce
Shopify
Analytics
Google Analytics | Hotjar
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on basiccellars.com, including 12 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25