carnivorebar.com website review

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

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

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

8 third-party services load with your homepage (Intercom, Clarity and Klaviyo and others), adding 924 KiB and 533 ms of main-thread time.

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

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

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

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

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 16.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Carnivore Bar in the field”.

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

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

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

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

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

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

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

Your homepage downloads 3.0 MB in 324 requests on a phone: scripts 1.1 MB (169), other files 948 KiB (128) and images 563 KiB (8). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example cb-home-hero-bordeau-30-v1.webp at 1,600 px wide, shown at 390 px. Resized copies would save about 163 KiB.

2 images (405 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.

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

8 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: 2 elements on the page fail this check, rated moderate by axe-core.

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

There are 2 <h1> headlines (“The Carnivore Bar” and “The Original Meat Bar”). One clear main headline is easier for people and search engines.

There is no robots.txt at carnivorebar.com/robots.txt, the first file search crawlers ask for.

The homepage links to 43 pages on carnivorebar.com and 4 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://carnivorebar.com/pages/merch-collections-page is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://carnivorebar.com/collections/all, https://carnivorebar.com/pages/faqs-1, https://carnivorebar.com/pages/merch-collections-page, https://carnivorebar.com/pages/related-research, https://carnivorebar.com/policies/refund-policy and https://carnivorebar.com/policies/privacy-policy and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://carnivorebar.com/pages/faqs-1, https://carnivorebar.com/pages/merch-collections-page, https://carnivorebar.com/pages/related-research and https://carnivorebar.com/policies/refund-policy took over 3 s to send their HTML from our server.

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

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

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

The homepage carries about 746 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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 32 cookies, 2 of them by other companies (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 47 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.