Website review, no card needed

1010wineandevents.com logo

1010wineandevents.com website review

Visit site (opens in a new tab)Reviewed 10 November 202628 issues · 81 checks

This review found 28 issues worth fixing on 1010wineandevents.com, 9 of them high impact, across 81 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

Real-visitor load time (LCP)75th percentile, phones
4.1 s1.9 sMay 23Nov 72.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.5 s
May 30, 20263.7 s
Jun 6, 20263.6 s
Jun 13, 20263.6 s
Jun 20, 20263.7 s
Jun 27, 20263.6 s
Jul 4, 20263.5 s
Jul 11, 20263.4 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Sep 19, 20263.4 s
Sep 26, 20263.6 s
Oct 3, 20263.8 s
Oct 10, 20263.7 s
Oct 17, 20263.1 s
Oct 24, 20262.4 s
Oct 31, 20262.2 s
Nov 7, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
97 ms78 msMay 23Nov 794 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202688 ms
May 30, 202694 ms
Jun 6, 202688 ms
Jun 13, 202695 ms
Jun 20, 202687 ms
Jun 27, 202687 ms
Jul 4, 202687 ms
Jul 11, 202687 ms
Jul 18, 202680 ms
Jul 25, 202680 ms
Sep 26, 202694 ms
Oct 3, 202695 ms
Oct 10, 202695 ms
Oct 17, 202694 ms
Oct 24, 202688 ms
Oct 31, 202692 ms
Nov 7, 202694 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

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

How it loaded on a phone

  1. 1010wineandevents.com at 0.4 s0.4 s
  2. 1010wineandevents.com at 0.8 s0.8 s
  3. 1010wineandevents.com at 1.3 s1.3 s
  4. 1010wineandevents.com at 1.7 s1.7 s
  5. 1010wineandevents.com at 2.1 s2.1 s
  6. 1010wineandevents.com at 2.5 s2.5 s
  7. 1010wineandevents.com at 2.9 s2.9 s
  8. 1010wineandevents.com at 3.4 s3.4 s

Speed

6 to fix60
  • Render-blocking requests

    4.3 s

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

  • Reduce unused CSS

    1.3 s · 264 KiB

    About 264 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.3 s faster on a phone.

  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    280 ms · 270 KiB

    About 270 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 280 ms faster on a phone.

  • Improve image delivery

    400 ms · 113 KiB

    2 images could be 113 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • Font display

    300 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Google Tag Manager and JSDelivr CDN and others), adding 651 KiB and 336 ms of main-thread time.

  • Legacy JavaScript

    200 ms · 72 KiB

    Polyfills for old browsers add 72 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • Use efficient cache lifetimes

    221 KiB

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

  • Minify CSS

    130 ms · 7 KiB

    7 KiB could be saved by minifying CSS.

  • Minify JavaScript

    120 ms · 13 KiB

    13 KiB could be saved by minifying JavaScript.

  • 5 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 1.6 s

    A phone's processor spends 1.6 s on main-thread work while loading, 635 ms of it running JavaScript. That is comfortably low.

  • Server response: 96 ms

    96 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 5.9 s

    5.9 s

    Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The first and only wine bar in Inglewood, CA. OUR STORY 101…”.

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Speed Index: 8.0 s

    8.0 s

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

  • Time to Interactive: 10.0 s

    10.0 s

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

  • Real-user FCP: 1.8 s

    1.8 s

    Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.3 s

    1.3 s

    Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

  • 18 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 88 ms to 94 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

    Real visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 94 ms

    94 ms

    Real visitors wait 94 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 39% faster for real visitors

    -39%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 3.5 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 175 ms

    175 ms

    Scripts block the page for only 175 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.008

    0.008

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

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 163 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 163 requests on a phone: scripts 1.1 MB (93), images 361 KiB (29) and stylesheets 353 KiB (31). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

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

  • About 0.6 g of CO₂ per visit

    0.59 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.59 g of CO₂e: 71.0 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

3 to fixGoogle 9395
  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (26 elements)

    All page content should be contained by landmarks: 26 elements on the page fail this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 32 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 9290
  • Meta description is long (205 characters)

    Your meta description is 205 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 74 internal links, 23 external

    The homepage links to 74 pages on 1010wineandevents.com and 23 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “The first and only wine bar in Inglewood, CA.”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “1010 Wine & Events - Inglewood's first and only wine bar”.

  • Canonical URL set

    The canonical URL is https://1010wineandevents.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage 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://1010wineandevents.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://1010wineandevents.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 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 (857 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 13 pages without a meta description

    https://1010wineandevents.com/reservations, https://1010wineandevents.com/menu, https://1010wineandevents.com/events, https://1010wineandevents.com/press, https://1010wineandevents.com/shop and https://1010wineandevents.com/product/black-wine-makers-second-edition-sweatshirt-blue and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://1010wineandevents.com/reservations, https://1010wineandevents.com/menu, https://1010wineandevents.com/events, https://1010wineandevents.com/press, https://1010wineandevents.com/shop and https://1010wineandevents.com/product/black-wine-makers-second-edition-sweatshirt-blue and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 13 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 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 2 small tap targets

    2 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.exploretock.com/tock.css' from origin 'https://1010wineandevents.com' has been…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 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 790 words of copy

    The homepage carries about 790 words of visible text.

  • Urgency cues

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

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Order Pickup or Delivery here!” and “Skip the line. Reserve your table now!”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Order Pickup or Delivery here!”, “Skip the line. Reserve your table now!” and “Order Online”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 18 customer or partner logos and 23 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 14 cookies set on arrival

    14

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 1010wineandevents.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics
Hosting
Newfold Digital

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on 1010wineandevents.com, including 14 speed issues, 3 SEO issues and 1 conversion gap. 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