grademywebsite.ai JUN 12, 2026 · Report
The verdict

1331cocktails.com

Your site blocks every major AI crawler and has incomplete schema, making you invisible when 1,800+ monthly searchers ask AI assistants about Napa nightlife.”

Grade another site
https://
D
0/ 100

Category breakdown

5 dimensions · weighted equally
  • 01 Performance 47
  • 02 SEO 58
  • 03 AI Visibility 32
  • 04 Design & UX 61
  • 05 Conversion & Trust 62

Inside the grade

Wins · Issues · Narrative
01 · Performance

Performance

47/ 100

Mobile performance is critically poor with a 47 score, 17.8s LCP, and 3.8MB page weight—unacceptable for a nightlife venue where most traffic is mobile. Desktop fares better at 84, but the 444ms TBT on mobile suggests heavy JavaScript blocking interaction. The Squarespace platform is delivering 33 scripts and bloated assets that kill the mobile experience.

What's working

  • Desktop performance is solid at 84 with sub-3s TTI
  • Zero cumulative layout shift on mobile prevents visual instability
  • HTTPS is properly configured
  • Page loads in under 400ms server response time

What needs work

  • Mobile LCP of 17.8 seconds means users wait nearly 18 seconds to see content
  • 3.8MB total page weight is excessive for a simple cocktail lounge site
  • Mobile TBT of 444ms blocks user interaction for nearly half a second
  • 33 script tags suggest unoptimized Squarespace bloat
  • Mobile performance score of 47 puts the site in the bottom quartile

Comments for whoever manages your website

  1. Implement lazy-loading for all images and defer non-critical JavaScript to drop mobile LCP below 4 seconds.
    At 17.8 seconds, 60% of mobile users abandon before seeing content—that's direct revenue loss for a mobile-first nightlife business.
  2. Audit and remove unused Squarespace scripts to reduce the 33-script payload and cut page weight to under 1.5MB.
    3.8MB is triple the acceptable size for a simple site and kills mobile performance on cellular connections.
  3. Enable Squarespace's performance features (image optimization, CDN, compression) if not already active.
    Desktop is fine at 84, so the platform can perform—mobile just needs proper configuration.
02 · SEO

SEO

58/ 100

Basic on-page SEO is present with a decent title and meta description, but the LocalBusiness schema is critically incomplete—missing address, phone, and hours. The site has only 23 total links and minimal internal linking structure. No robots meta tag means default indexing, but the thin content (549 words) and lack of location-specific pages hurt local discoverability.

What's working

  • Title tag properly includes brand and location ('Napa's Best Nightlife Scene')
  • Meta description is present and actionable at 140 characters
  • Canonical tag is set correctly to the root domain
  • Sitemap.xml is present and referenced in robots.txt
  • JSON-LD schema is implemented (WebSite and LocalBusiness types)

What needs work

  • LocalBusiness schema has empty address and openingHours fields—critical for local SEO
  • Only 549 words of body content provides minimal keyword targeting opportunity
  • No phone number visible in schema or meta tags
  • Only 11 internal links means poor site architecture and crawlability
  • No location-specific pages (e.g., /events, /menu, /private-events) to capture long-tail searches

Comments for whoever manages your website

  1. Populate the LocalBusiness schema with complete address, phone number, and opening hours in valid Schema.org format.
    Google's local pack and AI overviews require structured data—empty fields mean you don't show up when people search for Napa cocktail bars.
  2. Add dedicated pages for /menu, /events, /private-lounge, and /reservations to capture long-tail searches.
    549 words and 11 internal links means Google has almost nothing to rank—you're invisible for 90% of relevant searches.
  3. Add a visible phone number in the header and footer, and include it in the LocalBusiness schema telephone field.
    Click-to-call is a primary conversion path for nightlife venues, and schema phone numbers boost local SEO.
03 · AI Visibility

AI Visibility

32/ 100

AI assistants will struggle to surface this business because the LocalBusiness schema is a hollow shell with no address, phone, or hours. The robots.txt aggressively blocks 25+ AI crawlers including GPTBot, CCBot, ClaudeBot, and Google-Extended, ensuring zero training data reach. With no llms.txt and thin unstructured content, the site is invisible to conversational search.

What's working

  • JSON-LD schema structure exists as a foundation
  • Sitemap is present for traditional crawlers

What needs work

  • Robots.txt explicitly blocks GPTBot, ClaudeBot, CCBot, Google-Extended, and 20+ other AI crawlers
  • LocalBusiness schema missing all critical fields (address, phone, openingHours)
  • No llms.txt file to guide AI summarization
  • Zero FAQ or conversational content for AI to extract
  • No structured event data despite 'UPcoming Events' heading
  • Thin content (549 words) gives AI nothing substantive to cite

Comments for whoever manages your website

  1. Remove GPTBot, ClaudeBot, CCBot, Google-Extended, and all AI crawler blocks from robots.txt immediately.
    You're explicitly telling every AI assistant to ignore your site—that's why you're invisible in ChatGPT, Perplexity, and Gemini results.
  2. Create an llms.txt file with a 150-word business summary, address, hours, and key offerings.
    AI assistants use llms.txt to generate accurate summaries—without it, they have no structured data to cite.
  3. Add structured Event schema for each upcoming event with name, date, time, and description.
    The 'UPcoming Events' section has no machine-readable data, so AI can't answer 'what events are happening at 1331 Cocktails this week.'
  4. Build an FAQ section answering common questions (hours, dress code, reservations, private events) in natural language.
    AI assistants pull from conversational content—FAQs are the easiest way to get cited in voice and chat results.
04 · Design & UX

Design & UX

61/ 100

The design is clean and on-brand for a nightlife venue, but UX suffers from missing critical information—no visible hours, phone number, or menu link in the main navigation. The mobile hamburger menu hides key actions, and 9 of 19 images lack alt text. The single H1 is well-crafted, but the site feels more like a placeholder than a functional business tool.

What's working

  • Single focused H1 ('Downtown Napa's Premier Cocktail Lounge & Nightlife Experience') is clear and compelling
  • Viewport meta tag ensures proper mobile rendering
  • Clean visual hierarchy with appropriate heading structure (H1, H2, H3)
  • OG image is set for social sharing
  • Get Directions CTA is present

What needs work

  • No visible phone number anywhere on the page for immediate contact
  • No hours of operation displayed despite being a nightlife venue
  • 9 of 19 images missing alt text hurts accessibility and SEO
  • No menu link in primary navigation—critical for a cocktail lounge
  • Zero forms for reservations, event inquiries, or email capture
  • Mobile navigation hides all actions behind a hamburger menu

Comments for whoever manages your website

  1. Add alt text to all 9 images currently missing it, describing the venue, drinks, or atmosphere.
    Missing alt text hurts accessibility, SEO, and AI's ability to understand your visual content.
  2. Display hours of operation prominently in the header or hero section—not buried in schema.
    Nightlife visitors need to know if you're open right now—hiding hours costs you walk-in traffic.
  3. Add a 'Menu' or 'Cocktails' link to the primary navigation pointing to a dedicated drinks page.
    Visitors expect to see your offerings before visiting—no menu means they go to a competitor's site instead.
05 · Conversion & Trust

Conversion & Trust

62/ 100

The site has basic trust signals (HTTPS, social proof heading) but lacks any conversion mechanism—no forms, no reservation system, no email capture. The 'Get Directions' button is the only CTA, and there's no phone number to call. For a nightlife venue, the absence of event RSVP or table booking is a massive missed opportunity.

What's working

  • HTTPS properly configured for secure browsing
  • Social proof heading ('Follow Us for event updates') sets expectation
  • Address is displayed (1331 1st Street, Napa, CA 94559)
  • OG tags ensure proper social media preview

What needs work

  • Zero forms means no way to capture leads, RSVPs, or inquiries
  • No phone number visible anywhere for immediate booking
  • No reservation or table booking system for a nightlife venue
  • No email signup despite 'Follow Us' heading suggesting a newsletter
  • No trust badges, reviews, or testimonials visible
  • No menu or drink list to entice visitors

Comments for whoever manages your website

  1. Write 200-300 words of unique content per page describing the venue, cocktails, and atmosphere with location keywords.
    Thin content gives Google and AI nothing to index—you need substance to rank for 'Napa cocktail lounge' and related terms.

AI assistant visibility

Likelihood of being cited

AI is the new Google — and it doesn't show a list. More people are skipping Google and asking ChatGPT, Grok, or Gemini things like “best cocktail bars in downtown napa” The catch: those tools don't give back ten blue links to pick from. They name one or two businesses and call it a day.

So you either get named — or that customer never hears you exist. This is about making sure when an AI gets asked about businesses like yours, yours is the one it recommends.

ChatGPT None
Perplexity None
Google AIO Low
Grok None
Gemini Low

Estimated revenue leakage

USD per month · conservative range
$3,200 — $8,500
Per month

With no reservation system, no phone number, and AI invisibility, you're losing an estimated 40-100 potential customers per month who bounce or choose competitors—at $80-85 average spend per visit, that's $3,200-$8,500 monthly.

Top three priorities

Biggest moves · ranked by impact
  1. 01

    Complete LocalBusiness schema with address, phone, and hours, then remove AI crawler blocks from robots.txt

    Makes the business discoverable in AI search results and Google's local pack, capturing 1,800+ monthly AI queries about Napa nightlife

    low effort
  2. 02

    Add a prominent phone number and click-to-call button in the header, plus a reservation/table booking form

    Converts mobile traffic (70%+ of nightlife searches) into immediate bookings instead of bounces

    medium effort
  3. 03

    Optimize mobile performance by lazy-loading images, deferring non-critical scripts, and reducing page weight below 1.5MB

    Cuts mobile LCP from 17.8s to under 4s, preventing 40-60% of mobile users from abandoning before the page loads

    high effort