Website review, no card needed
kaapimachines.com website review
Visit site (opens in a new tab)Reviewed 24 October 202633 issues · 81 checks
This review found 33 issues worth fixing on kaapimachines.com, 6 of them high impact, across 81 checks. The most urgent: fails Core Web Vitals for real visitors. 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
83B- #27,005 of 117,615 reviewed websitesbeats 72%
- #17,851 of 66,923 online storesbeats 67%
- #306 of 2,700 WooCommerce storesbeats 85%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.5 s |
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 5.1 s |
| Sep 5, 2026 | 4.3 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 175 ms |
| May 9, 2026 | 171 ms |
| May 16, 2026 | 161 ms |
| May 23, 2026 | 151 ms |
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 147 ms |
| Jun 13, 2026 | 150 ms |
| Jun 20, 2026 | 149 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 144 ms |
| Jul 11, 2026 | 140 ms |
| Jul 18, 2026 | 143 ms |
| Jul 25, 2026 | 148 ms |
| Aug 1, 2026 | 150 ms |
| Aug 8, 2026 | 155 ms |
| Aug 15, 2026 | 159 ms |
| Aug 22, 2026 | 161 ms |
| Aug 29, 2026 | 164 ms |
| Sep 5, 2026 | 167 ms |
| Sep 12, 2026 | 165 ms |
| Sep 19, 2026 | 159 ms |
| Sep 26, 2026 | 155 ms |
| Oct 3, 2026 | 156 ms |
| Oct 10, 2026 | 160 ms |
| Oct 17, 2026 | 166 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.6 s
1.2 s
1.8 s
2.3 s
2.9 s
3.5 s
4.1 s
4.7 s
Speed
5,424 HTML elements
The page has 5,424 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 89
89/100Your mobile performance score is 89 (desktop: 97). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.
Document request latency
700 msThe HTML itself could arrive about 700 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
700 msReduce initial server response time. Google estimates savings of 700 ms on a phone.
Reduce unused CSS
300 ms · 95 KiBAbout 95 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Server response: 800 ms
800 msYour server takes 800 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Use efficient cache lifetimes
150 ms · 36 KiB8 files are served with short cache lifetimes, so returning visitors download them again (36 KiB).
1 long task on the main thread
1 long task block the main thread while loading, the longest for 64 ms. During a long task the page ignores taps.
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
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 61 ms of it running JavaScript. That is comfortably low.
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.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
Real-user INP: 205 ms
205 msReal visitors wait 205 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 2.6 s
2.6 sYour largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (2.9 s).
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 175 ms to 166 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Time to Interactive: 2.7 s
2.7 sThe page is fully interactive after 2.7 s.
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
About 0.2 g of CO₂ per visit
0.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.20 g of CO₂e: 23.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 716 KiB in 15 requests
716 KiBYour homepage downloads 716 KiB in 15 requests on a phone: images 267 KiB (8), fonts 205 KiB (4) and stylesheets 122 KiB (1). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).
106 tap targets too small
106 tap targets are too small or too close together to hit reliably with a finger.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
21 text elements with low contrast
21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h3 → h5), 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. (3 elements).
1 checks passed
13 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 18 WCAG 2.2 A/AA and best-practice rules on the phone render: 13 passed and 5 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 (172 characters)
Your meta description is 172 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 8 problems
Structured data found (CollectionPage, ImageObject, Organization and Person) but with 8 problems, for example “VideoObject: thumbnailUrl is not an absolute URL ("banner.png")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
517 internal links, 10 external
The homepage links to 517 pages on kaapimachines.com and 10 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Partners for Your Coffee Business”.
Title: 59 characters
Your title is a healthy 59 characters: “Kaapi Machines | Explore Premium Commercial Coffee Machines”.
Canonical URL set
The canonical URL is https://kaapimachines.com/.
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://kaapimachines.com/sitemap_index.xml.
AI search readiness
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
llms.txt published
The site publishes https://kaapimachines.com/llms.txt (17 KiB, 44 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 171 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 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
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.
Thin social proof
Social proof on the homepage: 119 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
A 8-field form
Your longest form asks for 8 fields (4 required). Every extra field lowers completion.
Only about 7 words
The homepage has only about 7 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
5 checks passed
22 calls to action
The homepage has 22 calls to action, for example “Shop & Retail Grinders”, “Contact Us” and “Get In Touch”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 11 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
5 other companies contacted
Loading the homepage contacts 5 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 kaapimachines.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on kaapimachines.com, including 14 speed issues, 3 SEO issues and 5 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.