Website review, no card needed
rockcreekcoffee.com website review
Visit site (opens in a new tab)Reviewed 7 November 202629 issues · 82 checks
This review found 29 issues worth fixing on rockcreekcoffee.com, 7 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
88B- #6,028 of 126,379 reviewed websitesbeats 93%
- #3,202 of 70,450 online storesbeats 93%
- #3,100 of 63,950 Shopify storesbeats 93%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.3 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 113 ms |
| Jun 6, 2026 | 102 ms |
| Jun 13, 2026 | 106 ms |
| Aug 22, 2026 | 120 ms |
| Aug 29, 2026 | 121 ms |
| Sep 5, 2026 | 124 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 155 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 164 ms |
| Oct 10, 2026 | 168 ms |
| Oct 17, 2026 | 171 ms |
| Oct 24, 2026 | 178 ms |
| Oct 31, 2026 | 178 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.8 s
1.5 s
2.3 s
3.1 s
3.8 s
4.6 s
5.4 s
6.2 s
Speed
Improve image delivery
1.8 s · 1.2 MB17 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 70
70/100Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
800 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Shopify and rechargecdn.com and others), adding 1.2 MB and 443 ms of main-thread time.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 924 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
289 KiBAbout 289 KiB of JavaScript is downloaded but never used on this page.
1,933 HTML elements
The page has 1,933 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 159 ms
159 msKlaviyo costs a phone 159 ms of main-thread work and 316 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.
Shopify adds 147 ms
147 msShopify costs a phone 147 ms of main-thread work and 432 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.
rechargecdn.com adds 99 ms
99 msrechargecdn.com costs a phone 99 ms of main-thread work and 296 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 · 52 KiBAbout 52 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 95 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
61 KiB12 files are served with short cache lifetimes, so returning visitors download them again (61 KiB).
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.6 s
8.6 sYour largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 16.9 s
16.9 sThe page becomes fully interactive after 16.9 s. Good is under 3.8 s.
Tap response (INP) got 66% slower for real visitors
+66%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 113 ms to 178 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
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: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 168 ms
168 msReal visitors wait 168 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.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: 563 ms
563 msReal visitors wait 563 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 26% faster for real visitors
-26%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 49 ms
49 msScripts block the page for only 49 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.1 MB in 334 requests
4.1 MBYour homepage downloads 4.1 MB in 334 requests on a phone: images 1.7 MB (23), scripts 1.2 MB (186) and other files 820 KiB (107). Under 2 MB keeps phones on slow connections fast.
11 images below the first screen load straight away
11 images further down the page (914 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images in older formats
4 images (603 KiB) 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.
About 1.2 g of CO₂ per visit
1.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.15 g of CO₂e: 138.1 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
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.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
93 internal links, 5 external
The homepage links to 93 pages on rockcreekcoffee.com and 5 external pages.
7 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Freshly roasted in small batches, ethically sourced coffee crafted for everyday moments. Discover rich flavor and quali…”.
One H1 headline
Your main headline reads: “Rock Creek Coffee Roasters”.
Title: 61 characters
Your title is a healthy 61 characters: “Small-Batch Fresh Roasted Coffee | Rock Creek Coffee Roasters”.
Canonical URL set
The canonical URL is https://rockcreekcoffee.com/.
Structured data in place
Structured data found: Organization.
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://rockcreekcoffee.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), 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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,069 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://rockcreekcoffee.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
21 of 21 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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 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 302 words of copy
The homepage carries about 302 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP COSTA RICA SANTA ELENA →”.
6 calls to action
The homepage has 6 calls to action, for example “Start a Coffee Subscription”, “Contact Us” and “Shop Costa Rica Santa Elena →”.
9 short forms
9 short forms (1 field at most) are right on the homepage.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
25 other companies contacted
Loading the homepage contacts 25 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 rockcreekcoffee.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Instafeed · Klaviyo Email Marketing Sms · Selleasy · Swym Wishlist Plus · omnisrc.com · smile.io · nfcube.com · rechargecdn.com · goaffpro.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
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Billings
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on rockcreekcoffee.com, including 15 speed issues, 1 SEO issue 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.