Website review, no card needed

mrbeastburger.com logo

mrbeastburger.com website review

Visit site (opens in a new tab)Reviewed 6 November 202616 issues · 70 checks

This review found 16 issues worth fixing on mrbeastburger.com, 3 of them high impact, across 70 checks. The most urgent: fails Core Web Vitals for real visitors. 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.8 s1.1 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.3 s
Aug 1, 20261.4 s
Aug 8, 20261.5 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
152 ms90 msMay 16Oct 31127 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202698 ms
May 23, 202697 ms
May 30, 202699 ms
Jun 6, 2026100 ms
Jun 13, 2026100 ms
Jun 20, 2026102 ms
Jun 27, 2026100 ms
Jul 4, 202698 ms
Jul 11, 2026105 ms
Jul 18, 2026110 ms
Jul 25, 2026117 ms
Aug 1, 2026126 ms
Aug 8, 2026131 ms
Aug 15, 2026137 ms
Aug 22, 2026137 ms
Aug 29, 2026137 ms
Sep 5, 2026138 ms
Sep 12, 2026138 ms
Sep 19, 2026140 ms
Sep 26, 2026145 ms
Oct 3, 2026143 ms
Oct 10, 2026143 ms
Oct 17, 2026141 ms
Oct 24, 2026133 ms
Oct 31, 2026127 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 mrbeastburger.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mrbeastburger.com at 0.4 s0.4 s
  2. mrbeastburger.com at 0.8 s0.8 s
  3. mrbeastburger.com at 1.1 s1.1 s
  4. mrbeastburger.com at 1.5 s1.5 s
  5. mrbeastburger.com at 1.9 s1.9 s
  6. mrbeastburger.com at 2.3 s2.3 s
  7. mrbeastburger.com at 2.6 s2.6 s
  8. mrbeastburger.com at 3.0 s3.0 s

Speed

4 to fix81
  • Mobile performance score: 81

    81/100

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

  • Render-blocking requests

    900 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 900 ms.

  • Reduce unused JavaScript

    300 ms · 36 KiB

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

  • Use efficient cache lifetimes

    300 ms · 35 KiB

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

  • Improve image delivery

    150 ms · 28 KiB

    1 image could be 28 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.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Cookiebot), adding 220 KiB and 110 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 71 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    29 KiB

    About 29 KiB of CSS is downloaded but never applied on this page.

  • 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: 0.5 s

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

  • Server response: 24 ms

    24 ms

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

Core Web Vitals

7 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.0 s

    5.0 s

    Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.

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

    +33%

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

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

    +48%

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Time to Interactive: 5.0 s

    5.0 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

7 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 121 ms

    121 ms

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

    1.7 s

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

  • Speed Index: 2.0 s

    2.0 s

    Visually, the page fills in at 2.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.006

    0.006

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

  • Total Blocking Time: 21 ms

    21 ms

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

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.22 g

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

4 checks passed
  • Page weight: 792 KiB in 26 requests

    792 KiB

    Your homepage downloads 792 KiB in 26 requests on a phone: fonts 282 KiB (3), scripts 241 KiB (6) and images 228 KiB (14). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

1 to fixGoogle 10099
  • 14 links without text

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

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

1 to fixGoogle 10093
  • Title is short (14 characters)

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

  • 27 internal links, 12 external

    The homepage links to 27 pages on mrbeastburger.com and 12 external pages.

7 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “MrBeast Burger is a virtual brand run out of kitchens near you, available for delivery and pick up only via food delive…”.

  • One H1 headline

    Your main headline reads: “MrBeast Burger”.

  • Canonical URL set

    The canonical URL is https://www.mrbeastburger.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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://staging.mrbeastburger.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (181 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 5 pages with very little text

    https://www.mrbeastburger.com/menu/product/chocolate-chip-cookie, https://www.mrbeastburger.com/menu/product/chicken-sandwich-combo, https://www.mrbeastburger.com/menu/product/beast-style-fries, https://www.mrbeastburger.com/menu/product/beast-style-burger-combo and https://www.mrbeastburger.com/contact have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 13 internal pages checked

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

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

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

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

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No social proof

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

  • 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 176 words

    The homepage has only about 176 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: “Order Now” and “ORDER NOW”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Order Now”, “Order” and “Order submenu”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and TikTok Pixel.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 2 other companies contacted

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

2 checks passed
  • Consent tool: Cookiebot

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

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 mrbeastburger.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
Vue.js
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

Company

Founded
2020
Headquarters
Greenville

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 16 issues on mrbeastburger.com, including 11 speed issues, 1 SEO issue 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