Website review, no card needed
drinkbrez.com website review
Visit site (opens in a new tab)Reviewed 8 November 202644 issues · 94 checks
This review found 44 issues worth fixing on drinkbrez.com, 12 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
77C- #67,469 of 121,058 reviewed websitesbeats 39%
- #43,858 of 68,509 online storesbeats 31%
- #41,748 of 62,430 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 138 ms |
| May 23, 2026 | 144 ms |
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 148 ms |
| Jun 13, 2026 | 149 ms |
| Jun 20, 2026 | 147 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 147 ms |
| Jul 25, 2026 | 152 ms |
| Aug 1, 2026 | 152 ms |
| Aug 8, 2026 | 153 ms |
| Aug 15, 2026 | 153 ms |
| Aug 22, 2026 | 153 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 153 ms |
| Oct 3, 2026 | 147 ms |
| Oct 10, 2026 | 146 ms |
| Oct 17, 2026 | 145 ms |
| Oct 24, 2026 | 146 ms |
| Oct 31, 2026 | 146 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
How it loaded on a phone
1.6 s
3.2 s
4.8 s
6.3 s
7.9 s
9.5 s
11.1 s
12.7 s
Speed
Reduce unused JavaScript
3.2 s · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.2 s faster on a phone.
Main-thread work: 11.2 s
A phone's processor spends 11.2 s on main-thread work while loading, 5.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,085 HTML elements
The page has 4,085 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (JSDelivr CDN, Google Tag Manager and Shopify and others), adding 3.1 MB and 2.0 s of main-thread time.
Use efficient cache lifetimes
900 ms · 612 KiB45 files are served with short cache lifetimes, so returning visitors download them again (612 KiB).
Improve image delivery
300 ms · 388 KiB16 images could be 388 KiB 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.
Legacy JavaScript
500 ms · 104 KiBPolyfills for old browsers add 104 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.
Render-blocking requests
550 ms15 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Reduce unused CSS
470 ms · 46 KiBAbout 46 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 470 ms faster on a phone.
Shopify adds 363 ms
363 msShopify costs a phone 363 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.
JSDelivr CDN adds 432 ms
432 msJSDelivr CDN costs a phone 432 ms of main-thread work and 126 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.
Google Tag Manager adds 363 ms
363 msGoogle Tag Manager costs a phone 363 ms of main-thread work and 502 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 380 ms. During a long task the page ignores taps.
Minify JavaScript
320 ms · 54 KiB54 KiB could be saved by minifying JavaScript.
rebuyengine.com adds 180 ms
180 msrebuyengine.com costs a phone 180 ms of main-thread work and 624 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.
cdn-spurit.com adds 185 ms
185 mscdn-spurit.com costs a phone 185 ms of main-thread work and 308 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.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Duplicated JavaScript
17 KiB17 KiB JavaScript is shipped twice across bundles.
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: 132 ms
132 msYour server sent the HTML in 132 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 22.8 s
22.8 sYour largest element takes 22.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 17.1 s
17.1 sVisually, the page fills in at 17.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 38.2 s
38.2 sThe page becomes fully interactive after 38.2 s. Good is under 3.8 s.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 138 ms to 146 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.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 153 ms
153 msReal visitors wait 153 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 490 ms
490 msReal visitors wait 490 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.5 MB in 613 requests
9.5 MBYour homepage downloads 9.5 MB in 613 requests on a phone: scripts 3.6 MB (206), media 2.2 MB (2) and other files 1.2 MB (267). Under 2 MB keeps phones on slow connections fast.
5 images below the first screen load straight away
5 images further down the page (343 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.7 g of CO₂ per visit
2.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.69 g of CO₂e: 323.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 78 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (178 characters)
Your meta description is 178 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
89 internal links, 10 external
The homepage links to 89 pages on drinkbrez.com and 10 external pages.
6 checks passed
Title: 50 characters
Your title is a healthy 50 characters: “THC Drinks - Cannabis Infused Drinks - BREZ – BRĒZ”.
Canonical URL set
The canonical URL is https://www.drinkbrez.com/.
Structured data in place
Structured data found: Organization 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://www.drinkbrez.com/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
53%The HTML your server sends has 954 of the 1,785 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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.
llms.txt published
The site publishes https://www.drinkbrez.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages without a meta description
https://www.drinkbrez.com/collections/all, https://www.drinkbrez.com/policies/terms-of-service, https://www.drinkbrez.com/policies/privacy-policy, https://www.drinkbrez.com/policies/shipping-policy, https://www.drinkbrez.com/collections/shop-all and https://www.drinkbrez.com/pages/mocktail-recipes and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://www.drinkbrez.com/collections/all, https://www.drinkbrez.com/products/og-extra-strength, https://www.drinkbrez.com/collections/shop-all, https://www.drinkbrez.com/pages/build-your-own-bundle, https://www.drinkbrez.com/products/brez-gift-card and https://www.drinkbrez.com/pages/mocktail-recipes and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://www.drinkbrez.com/products/og-extra-strength, https://www.drinkbrez.com/collections/shop-all, https://www.drinkbrez.com/products/brez-gift-card, https://www.drinkbrez.com/products/black-cherry-lemonade-10mg, https://www.drinkbrez.com/products/amplify and https://www.drinkbrez.com/products/flow 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
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
5 small tap targets
5 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 third-party cookies
4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“`<source src>` with a `<picture>` parent is invalid and therefore ignored. Please use `<source srcs…”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,785 words of copy
The homepage carries about 1,785 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More”.
10 calls to action
The homepage has 10 calls to action, for example “Shop All”, “Subscribe and Save” and “Contact”.
3 short forms
3 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads 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.
28 cookies set on arrival
28Opening the homepage sets 28 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.
66 other companies contacted
Loading the homepage contacts 66 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 drinkbrez.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on drinkbrez.com, including 23 speed issues, 3 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.