Website review, no card needed

noblerot.co.uk logo

noblerot.co.uk website review

Visit site (opens in a new tab)Reviewed 21 October 202645 issues · 82 checks

This review found 45 issues worth fixing on noblerot.co.uk, 18 of them high impact, across 82 checks. The most urgent: improve image delivery. 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.7 s1.6 sMay 2Oct 172.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.7 s
May 9, 20261.9 s
May 16, 20262.0 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.4 s
Jul 11, 20262.5 s
Jul 18, 20262.6 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.5 s
Oct 10, 20262.6 s
Oct 17, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
166 ms114 msMay 2Oct 17137 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026152 ms
May 9, 2026154 ms
May 16, 2026160 ms
May 23, 2026149 ms
May 30, 2026144 ms
Jun 6, 2026139 ms
Jun 13, 2026132 ms
Jun 20, 2026138 ms
Jun 27, 2026137 ms
Jul 4, 2026136 ms
Jul 11, 2026137 ms
Jul 18, 2026132 ms
Jul 25, 2026130 ms
Aug 1, 2026136 ms
Aug 8, 2026128 ms
Aug 15, 2026129 ms
Aug 22, 2026129 ms
Aug 29, 2026120 ms
Sep 5, 2026122 ms
Sep 12, 2026127 ms
Sep 19, 2026129 ms
Sep 26, 2026131 ms
Oct 3, 2026136 ms
Oct 10, 2026137 ms
Oct 17, 2026137 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 noblerot.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. noblerot.co.uk at 0.6 s0.6 s
  2. noblerot.co.uk at 1.2 s1.2 s
  3. noblerot.co.uk at 1.8 s1.8 s
  4. noblerot.co.uk at 2.4 s2.4 s
  5. noblerot.co.uk at 2.9 s2.9 s
  6. noblerot.co.uk at 3.5 s3.5 s
  7. noblerot.co.uk at 4.1 s4.1 s
  8. noblerot.co.uk at 4.7 s4.7 s

Speed

8 to fix44
  • Improve image delivery

    3.8 s · 1.8 MB

    11 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.8 s faster on a phone.

  • Reduce unused JavaScript

    4.5 s · 989 KiB

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

  • Use efficient cache lifetimes

    4.3 s · 709 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (709 KiB).

  • Mobile performance score: 44

    44/100

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (sevenrooms.com, Google Tag Manager and Google Analytics), adding 883 KiB and 589 ms of main-thread time.

  • 9 long tasks on the main thread

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

  • sevenrooms.com adds 394 ms

    394 ms

    sevenrooms.com costs a phone 394 ms of main-thread work and 717 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.

  • Main-thread work: 3.5 s

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

  • Reduce unused CSS

    170 ms · 17 KiB

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

  • Legacy JavaScript

    100 ms · 51 KiB

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

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

11 to fix33
  • 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: 17.3 s

    17.3 s

    Your largest element takes 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Noble Rot Magazine Issue 42”.

  • Time to Interactive: 20.3 s

    20.3 s

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

  • Speed Index: 7.0 s

    7.0 s

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

  • Total Blocking Time: 837 ms

    837 ms

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user CLS: 0.13

    0.13

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

  • Largest content (LCP) got 40% slower for real visitors

    +40%

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • 4 images without width and height

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

4 checks passed
  • Real-user INP: 143 ms

    143 ms

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

  • Real-user FCP: 1.4 s

    1.4 s

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

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

    -10%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 5.5 MB in 85 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 85 requests on a phone: images 3.0 MB (17), scripts 1.8 MB (32) and other files 383 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    635 KiB

    4 images are downloaded at several times the size a phone draws them, for example AP-NR-42-COVER.jpg at 1,004 px wide, shown at 201 px. Resized copies would save about 635 KiB.

  • 1 image in older formats

    1 image (807 KiB) is 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.

  • 7 images below the first screen load straight away

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

  • About 1.5 g of CO₂ per visit

    1.55 g

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

Accessibility

6 to fixGoogle 7888
  • Images must have alternative text (3 elements)

    Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 7 text elements with low contrast

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 4 links without text

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

1 checks passed
  • 33 automated accessibility rules passed

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

SEO

4 to fixGoogle 8389
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 16 links crawlers can't follow

    16 links have no real href, so search engines can't follow them.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 40 internal links, 10 external

    The homepage links to 40 pages on noblerot.co.uk and 10 external pages.

6 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Noble Rot is three award-winning restaurants in London's Bloomsbury, Soho and Mayfair. It's also a magazine about wine,…”.

  • One H1 headline

    Your main headline reads: “Reserve a table”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “Noble Rot | Shrine to the Vine”.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://noblerot.co.uk/sitemap.xml.

AI search readiness

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

  • Some text only appears after JavaScript runs

    58%

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

  • No llms.txt

    There is no https://noblerot.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.

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

Other pages

4 to fix55
  • 1 linked page is broken

    Your homepage links to https://noblerot.co.uk/media/menus/undefined, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a title

    https://noblerot.co.uk/faq has no <title>, so Google invents the link text in results.

  • 5 pages without a meta description

    https://noblerot.co.uk/shop/magazine, https://noblerot.co.uk/careers, https://noblerot.co.uk/contact, https://noblerot.co.uk/faq and https://noblerot.co.uk/shop/stockists have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://noblerot.co.uk/shop/books/wine-from-another-galaxy and https://noblerot.co.uk/shop/books/whos-afraid-of-romanee-conti use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

4 checks passed
  • 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9687
  • 10 small tap targets

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

  • 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 401 (Unauthorized)”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 452 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Reserve a table” and “Subscribe”.

  • 20 calls to action

    The homepage has 20 calls to action, for example “Reserve a table”, “Contact us” and “Shop”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 3 other companies contacted

    Loading the homepage contacts 3 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 noblerot.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

Framework
Next.js
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on noblerot.co.uk, including 19 speed issues, 4 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