Website review, no card needed

the-vineyard.co.uk logo

the-vineyard.co.uk website review

Visit site (opens in a new tab)Reviewed 27 October 202634 issues · 86 checks

This review found 34 issues worth fixing on the-vineyard.co.uk, 12 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. 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
2.8 s460 msMay 9Oct 24757 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.4 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.4 s
Jul 11, 20262.1 s
Jul 18, 20261.5 s
Jul 25, 2026983 ms
Aug 1, 2026760 ms
Aug 8, 2026740 ms
Aug 15, 2026809 ms
Aug 22, 2026790 ms
Aug 29, 2026784 ms
Sep 5, 2026777 ms
Sep 12, 2026767 ms
Sep 19, 2026754 ms
Sep 26, 2026734 ms
Oct 3, 2026811 ms
Oct 10, 2026772 ms
Oct 17, 2026763 ms
Oct 24, 2026757 ms
Real-visitor tap response (INP)75th percentile, phones
132 ms90 msMay 9Oct 24106 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026118 ms
May 16, 2026121 ms
May 23, 2026122 ms
May 30, 2026127 ms
Jun 6, 2026124 ms
Jun 13, 2026120 ms
Jun 20, 2026120 ms
Jun 27, 2026117 ms
Jul 4, 2026114 ms
Jul 11, 2026112 ms
Jul 18, 2026105 ms
Jul 25, 202697 ms
Aug 1, 202695 ms
Aug 8, 202698 ms
Aug 15, 202697 ms
Aug 22, 202698 ms
Aug 29, 202699 ms
Sep 5, 202697 ms
Sep 12, 202699 ms
Sep 19, 2026101 ms
Sep 26, 2026105 ms
Oct 3, 2026112 ms
Oct 10, 2026107 ms
Oct 17, 2026110 ms
Oct 24, 2026106 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 the-vineyard.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. the-vineyard.co.uk at 0.4 s0.4 s
  2. the-vineyard.co.uk at 0.8 s0.8 s
  3. the-vineyard.co.uk at 1.2 s1.2 s
  4. the-vineyard.co.uk at 1.6 s1.6 s
  5. the-vineyard.co.uk at 2.1 s2.1 s
  6. the-vineyard.co.uk at 2.5 s2.5 s
  7. the-vineyard.co.uk at 2.9 s2.9 s
  8. the-vineyard.co.uk at 3.3 s3.3 s

Speed

10 to fix30
  • Use efficient cache lifetimes

    1.8 s · 837 KiB

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

  • Reduce unused JavaScript

    1.8 s · 470 KiB

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

  • Render-blocking requests

    2.0 s

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

  • Mobile performance score: 30

    30/100

    Your mobile performance score is 30 (desktop: 68). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and triptease.io and others), adding 1.5 MB and 1.3 s of main-thread time.

  • Improve image delivery

    750 ms · 246 KiB

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

  • Google Tag Manager adds 733 ms

    733 ms

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

    360 ms · 71 KiB

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

  • Legacy JavaScript

    300 ms · 34 KiB

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

  • Main-thread work: 2.4 s

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

  • 10 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 68 but mobile only 30. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 2 ms

    2 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 15.8 s

    15.8 s

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

  • Time to Interactive: 17.8 s

    17.8 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

    The first text or image appears after 4.4 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.

  • Cumulative Layout Shift: 0.313

    0.313

    The layout shifts by 0.313 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 522 ms

    522 ms

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

  • 8 images without width and height

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

8 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.1 s

    1.1 s

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

  • Real-user INP: 113 ms

    113 ms

    Real visitors wait 113 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.

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 257 ms

    257 ms

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

  • Tap response (INP) got 10% faster for real visitors

    -10%

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

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

    -70%

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

Images and page weight

3 to fix68
  • Page weight: 2.7 MB in 156 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 156 requests on a phone: scripts 1.4 MB (40), images 919 KiB (26) and fonts 134 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    122 KiB

    2 images are downloaded at several times the size a phone draws them, for example monogramcollective_white.png at 2,790 px wide, shown at 153 px. Resized copies would save about 122 KiB.

  • 5 images below the first screen load straight away

    5 images further down the page (312 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 5 images in older formats

    5 images (353 KiB) are 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.

  • About 0.8 g of CO₂ per visit

    0.76 g

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

Accessibility

6 to fixGoogle 8392
  • 29 text elements with low contrast

    29 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 8 images without alt text

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

3 to fixGoogle 6981
  • No meta description

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

  • Title is short (8 characters)

    Your title is only 8 characters: “Vineyard”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 38 internal links, 7 external

    The homepage links to 38 pages on the-vineyard.co.uk and 7 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Something New is Coming in February 2027”.

  • Canonical URL set

    The canonical URL is https://www.the-vineyard.co.uk/.

  • Structured data in place

    Structured data found: WebPage.

  • 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://www.the-vineyard.co.uk/sitemap.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://www.the-vineyard.co.uk/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 (449 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.the-vineyard.co.uk/stay, https://www.the-vineyard.co.uk/food-drink, https://www.the-vineyard.co.uk/food-drink/the-brasserie, https://www.the-vineyard.co.uk/food-drink/seyval-restaurant, https://www.the-vineyard.co.uk/food-drink/afternoon-tea and https://www.the-vineyard.co.uk/food-drink/the-wine-shop-cellar and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.the-vineyard.co.uk/privacy-policy, https://www.the-vineyard.co.uk/terms-conditions, https://www.the-vineyard.co.uk/sustainability and https://www.the-vineyard.co.uk/modern-slavery-act-statement 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 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

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    13 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 5 customer or partner logos. 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.

  • 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 436 words of copy

    The homepage carries about 436 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “RESERVE A ROOM” and “CONTACT US”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “The Wine Shop & Cellar”, “Contact us” and “Book”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (measured from a US location before any click).

  • 16 other companies contacted

    Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 the-vineyard.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
London, Great Britain

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on the-vineyard.co.uk, including 17 speed issues, 3 SEO issues and 2 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