Website review, no card needed

thebeefyboys.com logo

thebeefyboys.com website review

Visit site (opens in a new tab)Reviewed 28 October 202631 issues · 79 checks

This review found 31 issues worth fixing on thebeefyboys.com, 7 of them high impact, across 79 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
1.2 s849 msMay 9Oct 24945 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.1 s
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 2026988 ms
Jul 18, 2026934 ms
Jul 25, 2026926 ms
Aug 1, 2026940 ms
Aug 8, 2026950 ms
Aug 15, 2026976 ms
Aug 22, 2026985 ms
Aug 29, 2026979 ms
Sep 5, 2026946 ms
Sep 12, 2026928 ms
Sep 19, 2026904 ms
Sep 26, 2026886 ms
Oct 3, 2026898 ms
Oct 10, 2026909 ms
Oct 17, 2026942 ms
Oct 24, 2026945 ms
Real-visitor tap response (INP)75th percentile, phones
85 ms69 msMay 9Oct 2483 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202672 ms
May 16, 202672 ms
May 23, 202672 ms
May 30, 202672 ms
Jun 6, 202671 ms
Jun 13, 202671 ms
Jun 20, 202672 ms
Jun 27, 202672 ms
Jul 4, 202673 ms
Jul 11, 202673 ms
Jul 18, 202672 ms
Jul 25, 202672 ms
Aug 1, 202673 ms
Aug 8, 202674 ms
Aug 15, 202676 ms
Aug 22, 202678 ms
Aug 29, 202679 ms
Sep 5, 202678 ms
Sep 12, 202678 ms
Sep 19, 202678 ms
Sep 26, 202677 ms
Oct 3, 202678 ms
Oct 10, 202679 ms
Oct 17, 202681 ms
Oct 24, 202683 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 thebeefyboys.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thebeefyboys.com at 0.5 s0.5 s
  2. thebeefyboys.com at 1.0 s1.0 s
  3. thebeefyboys.com at 1.5 s1.5 s
  4. thebeefyboys.com at 2.0 s2.0 s
  5. thebeefyboys.com at 2.5 s2.5 s
  6. thebeefyboys.com at 3.0 s3.0 s
  7. thebeefyboys.com at 3.5 s3.5 s
  8. thebeefyboys.com at 4.0 s4.0 s

Speed

8 to fix54
  • Render-blocking requests

    2.2 s

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

  • Reduce unused CSS

    900 ms · 239 KiB

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

  • Reduce unused JavaScript

    600 ms · 459 KiB

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

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54 (desktop: 40). 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 (Google Tag Manager, Facebook and JSDelivr CDN and others), adding 898 KiB and 669 ms of main-thread time.

  • Google Tag Manager adds 414 ms

    414 ms

    Google Tag Manager costs a phone 414 ms of main-thread work and 575 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: 2.6 s

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

  • Use efficient cache lifetimes

    252 KiB

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

  • Improve image delivery

    150 ms · 74 KiB

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

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 44 KiB

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

  • Minify JavaScript

    9 KiB

    9 KiB could be saved by minifying JavaScript.

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

    104 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 20.5 s

    20.5 s

    Your largest element takes 20.5 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: 21.0 s

    21.0 s

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

  • Speed Index: 8.5 s

    8.5 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Total Blocking Time: 281 ms

    281 ms

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

  • 3 images without width and height

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

  • Tap response (INP) got 14% slower for real visitors

    +14%

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

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: 2.3 s

    2.3 s

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

  • Real-user INP: 87 ms

    87 ms

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

  • Real-user CLS: 0.00

    0.00

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

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

  • Real-user TTFB: 668 ms

    668 ms

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

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

    -15%

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

  • Cumulative Layout Shift: 0.022

    0.022

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

Images and page weight

3 to fix53
  • Page weight: 5.5 MB in 117 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 117 requests on a phone: images 3.6 MB (31), scripts 1.4 MB (68) and stylesheets 240 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 6 images in older formats

    6 images (882 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.

  • 3 images below the first screen load straight away

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

  • About 1.6 g of CO₂ per visit

    1.57 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

5 to fixGoogle 9294
  • 9 text elements with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 7 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 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

Google 100100
  • 109 internal links, 13 external

    The homepage links to 109 pages on thebeefyboys.com and 13 external pages.

8 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “National Burger Award winning burgers. Join us for the ultimate burger experience at our restaurants in Hereford, Shrew…”.

  • One H1 headline

    Your main headline reads: “Award-winning Burger, Beer & Cocktail Joint”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “The Beefy Boys - The Burger Experts”.

  • Canonical URL set

    The canonical URL is https://thebeefyboys.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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://thebeefyboys.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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

Other pages

4 to fix81
  • 2 pages share a title

    https://thebeefyboys.com/about/diy-boxes and https://thebeefyboys.com/about-us/diy-boxes all use the title “Craft Your Own Burger Masterpiece with The DIY Boxes | The Beefy Boys”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://thebeefyboys.com/about/diy-boxes and https://thebeefyboys.com/about-us/diy-boxes use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://thebeefyboys.com/about/diy-boxes, whose canonical is https://thebeefyboys.com/about-us/diy-boxes. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://thebeefyboys.com/about/diy-boxes, https://thebeefyboys.com/about-us/our-burgers, https://thebeefyboys.com/the-beefy-bbq and https://thebeefyboys.com/about-us/diy-boxes 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 (of 28 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to set referrer policy: The value '“no-referrer-when-downgrade”' is not one of 'no-referrer', 'no-referrer-w…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 5 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 144 words

    The homepage has only about 144 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book a Table” and “Shop”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Shop”, “Contact” and “Learn more”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 11 cookies set on arrival

    11

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

  • 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 thebeefyboys.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 | Google Tag Manager
Hosting
Whg Lon

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on thebeefyboys.com, including 14 speed 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