Website review, no card needed
inbetweencoffee.com website review
Visit site (opens in a new tab)Reviewed 11 November 202621 issues · 68 checks
This review found 21 issues worth fixing on inbetweencoffee.com, 3 of them high impact, across 68 checks. The most urgent: 17 text elements with low contrast. 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
84B- #19,850 of 109,350 reviewed websitesbeats 77%
- #12,897 of 61,859 online storesbeats 73%
- #12,521 of 56,401 Shopify storesbeats 71%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.0 s
1.5 s
2.0 s
2.4 s
2.9 s
3.4 s
3.9 s
Speed
Mobile performance score: 76
76/100Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 189 KiBAbout 189 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Render-blocking requests
500 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Improve image delivery
300 ms · 118 KiB4 images could be 118 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.
Shopify adds 33 ms
33 msShopify costs a phone 33 ms of main-thread work and 417 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.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, superfiliate-cdn.com and adoric-om.com and others), adding 730 KiB and 135 ms of main-thread time.
Use efficient cache lifetimes
157 KiB8 files are served with short cache lifetimes, so returning visitors download them again (157 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
26 KiBAbout 26 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 424 ms of it running JavaScript. That is comfortably low.
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 5.9 s
5.9 sThe page becomes fully interactive after 5.9 s. Good is under 3.8 s.
Speed Index: 4.0 s
4.0 sVisually, the page fills in at 4.0 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 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: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
1 image in older formats
1 image (62 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.
About 0.6 g of CO₂ per visit
0.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.55 g of CO₂e: 66.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.9 MB in 226 requests
1.9 MBYour homepage downloads 1.9 MB in 226 requests on a phone: other files 918 KiB (96), scripts 616 KiB (83) and images 199 KiB (4). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
17 text elements with low contrast
17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 4 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (173 characters)
Your meta description is 173 characters; Google truncates after about 160, so the end of your pitch is cut.
28 internal links, 7 external
The homepage links to 28 pages on inbetweencoffee.com and 7 external pages.
7 checks passed
One H1 headline
Your main headline reads: “In Between Coffee”.
Title: 50 characters
Your title is a healthy 50 characters: “In Between Coffee - Half the Caffeine, All the Joy”.
Canonical URL set
The canonical URL is https://inbetweencoffee.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://inbetweencoffee.com/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
31%The HTML your server sends has 190 of the 605 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
2 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.
llms.txt published
The site publishes https://inbetweencoffee.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages point its canonical at the homepage
https://inbetweencoffee.com/products/half-caff-coffee and https://inbetweencoffee.com/products/wholesale-in-between-bags declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
3 pages share a title
/, https://inbetweencoffee.com/products/half-caff-coffee and https://inbetweencoffee.com/products/wholesale-in-between-bags all use the title “In Between Coffee - Half the Caffeine, All the Joy”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://inbetweencoffee.com/pages/about, https://inbetweencoffee.com/pages/contact, https://inbetweencoffee.com/policies/privacy-policy, https://inbetweencoffee.com/policies/refund-policy, https://inbetweencoffee.com/policies/terms-of-service and https://inbetweencoffee.com/policies/contact-information and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://inbetweencoffee.com/products/half-caff-coffee and https://inbetweencoffee.com/products/wholesale-in-between-bags use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://inbetweencoffee.com/pages/about and https://inbetweencoffee.com/pages/contact have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://inbetweencoffee.com/pages/contact, https://inbetweencoffee.com/policies/contact-information and https://inbetweencoffee.com/policies/shipping-policy 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.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
11 pages of 12 loaded without an error (the rest turned automated requests away).
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Unexpected token ';'”.
2 checks passed
Tap targets are thumb-sized
11 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 605 words of copy
The homepage carries about 605 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 OUR HALF CAFF COFFEE”.
10 calls to action
The homepage has 10 calls to action, for example “Shop”, “Contact” and “SHOP OUR HALF CAFF COFFEE”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 7 testimonial or review blocks and a star rating.
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 Pinterest Tag (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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
24 other companies contacted
Loading the homepage contacts 24 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 inbetweencoffee.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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Sami Wholesale · Judge Me Reviews · adoric-om.com · superfiliate-cdn.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
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 21 issues on inbetweencoffee.com, including 8 speed issues, 1 SEO issue 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.