Website review, no card needed
brew-company.com website review
Visit site (opens in a new tab)Reviewed 9 November 202649 issues · 99 checks
This review found 49 issues worth fixing on brew-company.com, 19 of them high impact, across 99 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
72C- #96,207 of 124,300 reviewed websitesbeats 19%
- #59,292 of 69,848 online storesbeats 12%
- #55,220 of 63,521 Shopify storesbeats 11%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 2.0 s |
| Nov 7, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 144 ms |
| May 30, 2026 | 150 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 158 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 141 ms |
| Jul 18, 2026 | 139 ms |
| Jul 25, 2026 | 135 ms |
| Aug 1, 2026 | 140 ms |
| Aug 8, 2026 | 141 ms |
| Aug 15, 2026 | 139 ms |
| Aug 22, 2026 | 143 ms |
| Aug 29, 2026 | 144 ms |
| Sep 5, 2026 | 157 ms |
| Sep 12, 2026 | 153 ms |
| Sep 19, 2026 | 150 ms |
| Sep 26, 2026 | 146 ms |
| Oct 3, 2026 | 140 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 133 ms |
| Oct 24, 2026 | 137 ms |
| Oct 31, 2026 | 145 ms |
| Nov 7, 2026 | 148 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
0.9 s
1.7 s
2.6 s
3.4 s
4.3 s
5.1 s
6.0 s
6.8 s
Speed
Reduce unused JavaScript
1.5 s · 1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Render-blocking requests
1.3 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 23
23/100Your mobile performance score is 23. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.9 s
A phone's processor spends 8.9 s on main-thread work while loading, 4.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, YouTube and Facebook and others), adding 3.3 MB and 2.5 s of main-thread time.
Google Tag Manager adds 825 ms
825 msGoogle Tag Manager costs a phone 825 ms of main-thread work and 879 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.
Reduce unused CSS
600 ms · 239 KiBAbout 239 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
YouTube adds 607 ms
607 msYouTube costs a phone 607 ms of main-thread work and 980 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.
Use efficient cache lifetimes
495 KiB24 files are served with short cache lifetimes, so returning visitors download them again (495 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 345 ms. During a long task the page ignores taps.
rebuyengine.com adds 231 ms
231 msrebuyengine.com costs a phone 231 ms of main-thread work and 612 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.
Facebook adds 268 ms
268 msFacebook costs a phone 268 ms of main-thread work and 228 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.
Yotpo adds 252 ms
252 msYotpo costs a phone 252 ms of main-thread work and 390 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.
2,879 HTML elements
The page has 2,879 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 115 KiBPolyfills for old browsers add 115 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Improve image delivery
25 KiB1 image could be 25 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
18 KiB18 KiB could be saved by minifying JavaScript.
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: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 9.7 s
9.7 sYour largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Frame_414”.
Time to Interactive: 32.1 s
32.1 sThe page becomes fully interactive after 32.1 s. Good is under 3.8 s.
Speed Index: 9.4 s
9.4 sVisually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.304
0.304The layout shifts by 0.304 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 144 ms to 148 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
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: 159 ms
159 msReal visitors wait 159 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 582 ms
582 msReal visitors wait 582 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 28% faster for real visitors
-28%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.9 MB in 339 requests
5.9 MBYour homepage downloads 5.9 MB in 339 requests on a phone: scripts 3.6 MB (115), other files 834 KiB (140) and images 790 KiB (45). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Frame_394-_Compressify.io.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).
1 image in older formats
1 image (87 KiB) is 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.
2 images below the first screen load straight away
2 images further down the page (62 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.66 g of CO₂e: 199.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
9 buttons without a name
9 buttons have no accessible name, so screen readers announce just “button”.
13 tap targets too small
13 tap targets are too small or too close together to hit reliably with a finger.
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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Invalid ARIA attributes
4 elements use ARIA attributes their role does not allow, which confuses screen readers.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (86 elements)
All page content should be contained by landmarks: 86 elements on the page fail this check, rated moderate by axe-core.
14 form fields without a label
14 form fields have no label, so screen readers announce an empty box and autofill guesses.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 9 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (16 characters)
Your title is only 16 characters: “The Brew Company”. Between 30 and 65 characters leaves room to say what you do and for whom.
3 H1 headlines
There are 3 <h1> headlines (“YOUR CHRISTMAS GIFTING UPGRADE!”, “The Innovative Coffeebrewer” and “More Coffee, On Us!”). One clear main headline is easier for people and search engines.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
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.
90 internal links, 11 external
The homepage links to 90 pages on brew-company.com and 11 external pages.
6 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “Premium, Organic, Fairtrade and Sustainable Coffee and Tea products of the Highest Quality by The Brew Company. Be Your…”.
Canonical URL set
The canonical URL is https://brew-company.com/.
Structured data in place
Structured data found: CafeOrCoffeeShop, 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://brew-company.com/sitemap.xml.
AI search readiness
4 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (910 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://brew-company.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://brew-company.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://brew-company.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://brew-company.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://brew-company.com/collections/2026-early-bird-christmas-collection and https://brew-company.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 42 found) and read each the way a search engine does.
3 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.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97023454&Ver=2&mid=47bfd188-0a94-4aca-8151-67ab4ed8b18f&bo=1&sid=3b546560dc7a11f183dbb539ca70d0fb&vid=3b549820dc7a11f1870fc7b2baf50090&vids=1&msclkid=N&pi=918639831&lg.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “jQuery is not defined”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
67 of 76 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
About 612 words of copy
The homepage carries about 612 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Buy now!” and “SHOP CHRISTMAS”.
11 calls to action
The homepage has 11 calls to action, for example “Buy now!”, “Contact Us” and “SHOP CHRISTMAS”.
18 short forms
18 short forms (3 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 21 testimonial or review blocks, a star rating, 1 trust badge and “22000+ Reviews”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Opening hours shown
Your opening hours are on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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 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.
30 cookies set on arrival
30Opening the homepage sets 30 cookies, 2 of them by other companies (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.
50 other companies contacted
Loading the homepage contacts 50 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 brew-company.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Gorgias Live Chat Helpdesk · Rebuy Personalization Engine · Yotpo Product Reviews · Ecomposer Builder · Fontify · Klaviyo Email Marketing Sms · Hreflang Manager · Eg Auto Add To Cart · Webrex Ai Seo Optimer · Xapps Geo · 9gtb.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Vue.js
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Middelfart
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on brew-company.com, including 23 speed issues, 4 SEO issues and 2 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.