bevzilla.co website review

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

34 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

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

8 third-party services load with your homepage (Cloudflare CDN, Shopify and JSDelivr CDN and others), adding 1.4 MB and 3 ms of main-thread time.

Shopify costs a phone 0 ms of main-thread work and 1.1 MB 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.

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

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

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.

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

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.

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

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

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

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

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

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

Your homepage downloads 4.4 MB in 112 requests on a phone: images 3.5 MB (60), scripts 467 KiB (33) and HTML 192 KiB (1). Under 2 MB keeps phones on slow connections fast.

25 images are downloaded at several times the size a phone draws them, for example OUR_PLANET.jpg at 1,080 px wide, shown at 100 px. Resized copies would save about 1.8 MB.

15 images (1.3 MB) 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.

Vibrant_BYOB_Coffee_Sale_Poster.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

1 tap target is too small or too close together to hit reliably with a finger.

27 images have no alt text, which hurts accessibility and image search.

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

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

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

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“Bevzilla” and “2 million+ Happy Customers”). One clear main headline is easier for people and search engines.

Your meta description is 180 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 107 pages on bevzilla.co and 8 external pages.

Your Organization JSON-LD is missing logo, 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.

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.

Your homepage links to /products/50g-x-3-coffee-jars-electric-frother, /products/assorted-coffee-powder-box-96-sachets and /products/build-your-own-box, which answer with an error. Visitors hit a dead end and search engines drop them.

/collections/coffee-sachets, /collections/shaker-pack and /collections/matcha have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/coffee-sachets, /collections/instant-iced-tea, /collections/instant-coffee-cubes, /collections/instant-coffee-powder, /collections/shaker-pack and /collections/matcha have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “window is not defined”.

6 links from your homepage to your own site are broken, for example https://www.bevzilla.co/collections/coffee-sachets (network).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 36 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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 614 words of visible text.

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

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

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 redirect=_spf.mailhostbox.com”.

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.

Opening the homepage sets 5 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.