Website review, no card needed
springvalleycoffee.com website review
Visit site (opens in a new tab)Reviewed 20 November 202638 issues · 82 checks
This review found 38 issues worth fixing on springvalleycoffee.com, 10 of them high impact, across 82 checks. The most urgent: improve image delivery. 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
82B- #33,812 of 120,386 reviewed websitesbeats 66%
- #22,509 of 68,161 online storesbeats 60%
- #21,752 of 62,115 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.6 s |
| Nov 14, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 123 ms |
| Jun 6, 2026 | 109 ms |
| Jun 13, 2026 | 109 ms |
| Jun 20, 2026 | 102 ms |
| Jun 27, 2026 | 97 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 94 ms |
| Jul 18, 2026 | 93 ms |
| Jul 25, 2026 | 89 ms |
| Aug 1, 2026 | 98 ms |
| Aug 8, 2026 | 103 ms |
| Aug 15, 2026 | 102 ms |
| Aug 22, 2026 | 101 ms |
| Aug 29, 2026 | 99 ms |
| Sep 5, 2026 | 97 ms |
| Sep 12, 2026 | 97 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 96 ms |
| Oct 3, 2026 | 110 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 139 ms |
| Oct 24, 2026 | 146 ms |
| Oct 31, 2026 | 150 ms |
| Nov 7, 2026 | 143 ms |
| Nov 14, 2026 | 151 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.2 s
2.4 s
3.6 s
4.9 s
6.1 s
7.3 s
8.5 s
9.7 s
Speed
Improve image delivery
1.9 s · 1.3 MB23 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Main-thread work: 5.5 s
A phone's processor spends 5.5 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
750 ms · 139 KiBAbout 139 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (Clarity, Shopify and azurefd.net and others), adding 2.5 MB and 411 ms of main-thread time.
Shopify adds 150 ms
150 msShopify costs a phone 150 ms of main-thread work and 2.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.
Render-blocking requests
300 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
1,974 HTML elements
The page has 1,974 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
azurefd.net adds 58 ms
58 msazurefd.net costs a phone 58 ms of main-thread work and 315 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
150 ms · 37 KiBAbout 37 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 81 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
21 KiB7 files are served with short cache lifetimes, so returning visitors download them again (21 KiB).
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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 22.5 s
22.5 sYour largest element takes 22.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “× Stay in touch. Coffee releases & exciting news straight t…”. Most of its time is resource load delay (10.8 s).
Time to Interactive: 22.8 s
22.8 sThe page becomes fully interactive after 22.8 s. Good is under 3.8 s.
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 123 ms to 151 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s 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: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 199 ms
199 msReal visitors wait 199 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 744 ms
744 msReal visitors wait 744 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 35 ms
35 msScripts block the page for only 35 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.3 MB in 462 requests
4.3 MBYour homepage downloads 4.3 MB in 462 requests on a phone: images 2.1 MB (65), other files 1.1 MB (222) and scripts 798 KiB (136). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
359 KiB6 images are downloaded at several times the size a phone draws them, for example Untitled_design_75c6868f-525d-4c5d-97e0-a92a02ae289d_1070x.p at 1,070 px wide, shown at 340 px. Resized copies would save about 359 KiB.
3 images below the first screen load straight away
3 images further down the page (388 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.21 g of CO₂e: 145.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
54 text elements with low contrast
54 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail 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. (4 elements).
2 checks passed
Every image has alt text
All 98 images in the HTML carry an alt attribute.
51 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: 51 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (20 characters)
Your title is only 20 characters: “Spring Valley Coffee”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (63 characters)
Your meta description is only 63 characters: “incredible Kenyan coffee • roasted at origin • established 2009”. 70 to 160 characters is enough to sell the click.
2 H1 headlines
There are 2 <h1> headlines (“” and “Incredible Kenyan coffee,Roasted at origin.”). One clear main headline is easier for people and search engines.
22 links with vague text
22 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
71 internal links, 71 external
The homepage links to 71 pages on springvalleycoffee.com and 71 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.springvalleycoffee.com/.
Structured data in place
Structured data found: Organization and WebSite.
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.springvalleycoffee.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (639 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.springvalleycoffee.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://www.springvalleycoffee.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.springvalleycoffee.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://www.springvalleycoffee.com/collections/all, https://www.springvalleycoffee.com/customer_authentication/redirect and https://www.springvalleycoffee.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.springvalleycoffee.com/customer_authentication/redirect has 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 33 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
32 small tap targets
32 of 140 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a map 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.
Thin social proof
Social proof on the homepage: 12 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 471 words of copy
The homepage carries about 471 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop UK / US ↓” and “Shop Kenya ↗”.
10 calls to action
The homepage has 10 calls to action, for example “Shop”, “Shop UK 🇬🇧 / US 🇺🇸” and “Shop Kenya 🇰🇪”.
10 short forms
10 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
21 other companies contacted
Loading the homepage contacts 21 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 springvalleycoffee.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Nairobi
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on springvalleycoffee.com, including 15 speed issues, 6 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.