bbot.menu website review

36 files are served with short cache lifetimes, so returning visitors download them again (2.1 MB).

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.

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

7 third-party services load with your homepage (Stripe, Google Maps and Facebook and others), adding 1.5 MB and 742 ms of main-thread time.

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

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

Stripe costs a phone 386 ms of main-thread work and 510 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.

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

Google Maps costs a phone 179 ms of main-thread work and 394 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.

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

46 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

Polyfills for old browsers add 41 KiB JavaScript that modern phones do not need.

31 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

Your largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ORDER FOOD AND DRINK”.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.5 MB in 94 requests on a phone: scripts 2.7 MB (33), fonts 498 KiB (13) and other files 154 KiB (41). Under 2 MB keeps phones on slow connections fast.

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Your meta description is only 43 characters: “Tableside Order & Pay by DoorDash Platform.”. 70 to 160 characters is enough to sell the click.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://app.bbot.menu/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

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

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.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Attribution Reporting is deprecated and will be removed. See https://goo.gle/ps-status for details.”).

1 error was logged to the browser console while the page loaded, for example “The backend did not provide a Stripe API key. Assuming this is not a DD Mx, defaulting to the TOP key”.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

bbot.menu has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

bbot.menu's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

DMARC is set to p=none, so mail pretending to be bbot.menu is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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.

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