Website review, no card needed
dutchbros.com website review
Visit site (opens in a new tab)Reviewed 22 November 202619 issues · 79 checks
This review found 19 issues worth fixing on dutchbros.com, 4 of them high impact, across 79 checks. The most urgent: 2 tap targets too small. 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
89BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Score over time |
|---|---|
| Oct 11, 2026 | 84 |
| Nov 22, 2026 | 89 |
Since Oct 11, 2026: Speed +20 · SEO +5
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 622 ms |
| Jun 6, 2026 | 623 ms |
| Jun 13, 2026 | 624 ms |
| Jun 20, 2026 | 619 ms |
| Jun 27, 2026 | 624 ms |
| Jul 4, 2026 | 623 ms |
| Jul 11, 2026 | 625 ms |
| Jul 18, 2026 | 633 ms |
| Jul 25, 2026 | 629 ms |
| Aug 1, 2026 | 620 ms |
| Aug 8, 2026 | 611 ms |
| Aug 15, 2026 | 601 ms |
| Aug 22, 2026 | 615 ms |
| Aug 29, 2026 | 661 ms |
| Sep 5, 2026 | 704 ms |
| Sep 12, 2026 | 755 ms |
| Sep 19, 2026 | 774 ms |
| Sep 26, 2026 | 772 ms |
| Oct 3, 2026 | 769 ms |
| Oct 10, 2026 | 766 ms |
| Oct 17, 2026 | 772 ms |
| Oct 24, 2026 | 769 ms |
| Oct 31, 2026 | 785 ms |
| Nov 7, 2026 | 776 ms |
| Nov 14, 2026 | 766 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 73 ms |
| Jun 6, 2026 | 74 ms |
| Jun 13, 2026 | 74 ms |
| Jun 20, 2026 | 74 ms |
| Jun 27, 2026 | 75 ms |
| Jul 4, 2026 | 75 ms |
| Jul 11, 2026 | 75 ms |
| Jul 18, 2026 | 76 ms |
| Jul 25, 2026 | 76 ms |
| Aug 1, 2026 | 77 ms |
| Aug 8, 2026 | 77 ms |
| Aug 15, 2026 | 77 ms |
| Aug 22, 2026 | 77 ms |
| Aug 29, 2026 | 76 ms |
| Sep 5, 2026 | 75 ms |
| Sep 12, 2026 | 73 ms |
| Sep 19, 2026 | 73 ms |
| Sep 26, 2026 | 73 ms |
| Oct 3, 2026 | 73 ms |
| Oct 10, 2026 | 74 ms |
| Oct 17, 2026 | 74 ms |
| Oct 24, 2026 | 74 ms |
| Oct 31, 2026 | 74 ms |
| Nov 7, 2026 | 73 ms |
| Nov 14, 2026 | 72 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 86
86/100Your mobile performance score is 86. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
300 ms · 304 KiB10 images could be 304 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.
ctfassets.net adds 0 ms
0 msctfassets.net costs a phone 0 ms of main-thread work and 301 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 JavaScript
150 ms · 61 KiBAbout 61 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Cloudflare, Adobe TypeKit and ctfassets.net and others), adding 493 KiB and 11 ms of main-thread time.
Use efficient cache lifetimes
51 KiB14 files are served with short cache lifetimes, so returning visitors download them again (51 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
2 checks passed
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 175 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.3 s
4.3 sYour largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Tell your friends! Our creamy holiday nog is back w/ NEW ho…”.
Largest content (LCP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.6 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 4.3 s
4.3 sThe page becomes fully interactive after 4.3 s. Good is under 3.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 73 ms to 72 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 72 ms
72 msReal visitors wait 72 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 412 ms
412 msReal visitors wait 412 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Speed Index: 0.9 s
0.9 sVisually, the page fills in at 0.9 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
1 image far larger than shown
148 KiB1 image is downloaded at several times the size a phone draws it, for example Dutch_Bros_Coffee_wordmark.svg.png at 3,840 px wide, shown at 124 px. Resized copies would save about 148 KiB.
1 image in older formats
1 image (150 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.
4 images below the first screen load straight away
4 images further down the page (177 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.3 g of CO₂ per visit
0.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.29 g of CO₂e: 35.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.0 MB in 70 requests
1.0 MBYour homepage downloads 1.0 MB in 70 requests on a phone: images 580 KiB (21), scripts 204 KiB (20) and fonts 176 KiB (4). That is a lean page.
Accessibility
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (8 elements).
2 checks passed
Every image has alt text
All 9 images in the HTML carry an alt attribute.
45 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: 45 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (24 characters)
Your title is only 24 characters: “Home | Dutch Bros Coffee”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
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.
34 internal links, 23 external
The homepage links to 34 pages on dutchbros.com and 23 external pages.
6 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “Dutch Bros® Coffee is your go-to drive thru for coffee, energy drinks, and more. Order ahead on the app and stop by a s…”.
One H1 headline
Your main headline reads: “Dutch Bros Coffee”.
Canonical URL set
The canonical URL is https://www.dutchbros.com/.
Structured data in place
Structured data found: CafeOrCoffeeShop, MobileApplication, Offer, Organization and Product.
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.dutchbros.com/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
58%The HTML your server sends has 267 of the 457 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
llms.txt published
The site publishes https://www.dutchbros.com/llms.txt (1 KiB, 10 links), a plain-text guide to the site for AI tools.
Other pages
1 page with very little text
https://www.dutchbros.com/locations has 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 18 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Hydration completed but contains mismatches.”.
2 checks passed
Tap targets are thumb-sized
34 of 37 tappable elements near the top are at least 24 px.
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.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 457 words of copy
The homepage carries about 457 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “ORDER NOW”.
6 calls to action
The homepage has 6 calls to action, for example “ORDER NOW”, “SHOP NOW” and “JOIN REWARDS”.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
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
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: Ketch
A consent management tool (Ketch) loads with the page.
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 dutchbros.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Hiring
- Hiring
- 3 open roles
- Job board
- careers page
- Careers page
- careers.dutchbros.com/us/en (opens in a new tab)
Company
- Employees
- 23,000
- Founded
- 1992
- Headquarters
- Grants Pass
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 19 issues on dutchbros.com, including 7 speed issues, 3 SEO issues and 3 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.