Website review, no card needed
coffeebeans.io website review
Visit site (opens in a new tab)Reviewed 26 October 202645 issues · 80 checks
This review found 45 issues worth fixing on coffeebeans.io, 15 of them high impact, across 80 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.3 s |
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 151 ms |
| May 16, 2026 | 149 ms |
| May 23, 2026 | 150 ms |
| May 30, 2026 | 149 ms |
| Jun 6, 2026 | 150 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 155 ms |
| Jun 27, 2026 | 157 ms |
| Jul 4, 2026 | 152 ms |
| Jul 11, 2026 | 154 ms |
| Jul 18, 2026 | 165 ms |
| Jul 25, 2026 | 170 ms |
| Aug 1, 2026 | 194 ms |
| Aug 8, 2026 | 178 ms |
| Aug 15, 2026 | 158 ms |
| Aug 22, 2026 | 155 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 174 ms |
| Sep 19, 2026 | 185 ms |
| Sep 26, 2026 | 188 ms |
| Oct 3, 2026 | 205 ms |
| Oct 10, 2026 | 202 ms |
| Oct 17, 2026 | 196 ms |
| Oct 24, 2026 | 185 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
Speed
Reduce unused JavaScript
3.0 s · 449 KiBAbout 449 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Mobile performance score: 39
39/100Your mobile performance score is 39 (desktop: 56). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
6.6 MB1 image could be 6.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google Analytics and LinkedIn Ads and others), adding 934 KiB and 726 ms of main-thread time.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 793 ms. During a long task the page ignores taps.
Google Tag Manager adds 653 ms
653 msGoogle Tag Manager costs a phone 653 ms of main-thread work and 776 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.
Font display
600 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).
Reduce unused CSS
450 ms · 34 KiBAbout 34 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
300 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 30 KiB6 files are served with short cache lifetimes, so returning visitors download them again (30 KiB).
Render-blocking requests
150 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
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.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 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.
Real-user CLS: 0.26
0.26For real visitors the layout shifts by 0.26 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 81.6 s
81.6 sYour largest element takes 81.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 15.5 s
15.5 sVisually, the page fills in at 15.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 83.3 s
83.3 sThe page becomes fully interactive after 83.3 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.274
0.274The layout shifts by 0.274 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 151 ms to 185 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 430 ms
430 msScripts block taps and scrolling for 430 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 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.
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user INP: 196 ms
196 msReal visitors wait 196 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Images and page weight
Page weight: 18.0 MB in 51 requests
18.0 MBYour homepage downloads 18.0 MB in 51 requests on a phone: images 16.2 MB (7), scripts 1.6 MB (21) and fonts 99 KiB (2). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 16.2 MB together. On a phone connection a single image that size takes seconds.
1 image far larger than shown
6.3 MB1 image is downloaded at several times the size a phone draws it, for example image at 4,096 px wide, shown at 287 px. Resized copies would save about 6.3 MB.
3 images below the first screen load straight away
3 images further down the page (9.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (6.6 MB) 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 5.1 g of CO₂ per visit
5.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.09 g of CO₂e: 611.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (3 elements)
Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 127 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 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 long (71 characters)
Your title is 71 characters, so Google will cut it off around 60: “CoffeeBeans | Tech, Product & Process Consulting Services | India & USA”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
9 H1 headlines
There are 9 <h1> headlines (“Home”, “Expertise” and “Case Studies”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (169 characters)
Your meta description is 169 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
63 internal links, 3 external
The homepage links to 63 pages on coffeebeans.io and 3 external pages.
2 checks passed
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.coffeebeans.io/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://coffeebeans.io/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
Text is in the HTML
Your server sends the page's text in the HTML (888 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages without a title
https://coffeebeans.io/consulting/cloud, https://coffeebeans.io/consulting/data, https://coffeebeans.io/consulting/machine-learning-ops, https://coffeebeans.io/consulting/ai, https://coffeebeans.io/services/infrastructure-services and https://coffeebeans.io/services/application-modernization and 2 others have no <title>, so Google invents the link text in results.
2 pages share a title
https://coffeebeans.io/primary-services and https://coffeebeans.io/additional-services all use the title “Business meets technology | About CoffeeBeans and their services”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://coffeebeans.io/consulting/cloud, https://coffeebeans.io/consulting/data, https://coffeebeans.io/consulting/machine-learning-ops, https://coffeebeans.io/consulting/ai, https://coffeebeans.io/services/infrastructure-services and https://coffeebeans.io/services/application-modernization and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://coffeebeans.io/primary-services, https://coffeebeans.io/additional-services and https://coffeebeans.io/about use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.
4 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 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.
Best practices
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
5 of 5 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 823 words of copy
The homepage carries about 823 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact Us” and “Talk to us”.
Social proof on the page
Social proof on the homepage: 39 testimonial or review blocks and 64 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight (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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
15 other companies contacted
Loading the homepage contacts 15 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 coffeebeans.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on coffeebeans.io, including 23 speed issues, 7 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.