Website review, no card needed
kimacoffee.com website review
Visit site (opens in a new tab)Reviewed 8 November 202634 issues · 78 checks
This review found 34 issues worth fixing on kimacoffee.com, 13 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. 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
74C- #71,884 of 102,069 reviewed websitesbeats 26%
- #44,329 of 56,611 online storesbeats 18%
- #41,645 of 51,485 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 936 ms |
| May 23, 2026 | 956 ms |
| May 30, 2026 | 945 ms |
| Jun 6, 2026 | 900 ms |
| Jun 13, 2026 | 949 ms |
| Jun 20, 2026 | 953 ms |
| Jun 27, 2026 | 976 ms |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 1.0 s |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 998 ms |
| Sep 19, 2026 | 966 ms |
| Sep 26, 2026 | 898 ms |
| Oct 3, 2026 | 874 ms |
| Oct 10, 2026 | 898 ms |
| Oct 17, 2026 | 933 ms |
| Oct 24, 2026 | 966 ms |
| Oct 31, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 73 ms |
| May 23, 2026 | 72 ms |
| May 30, 2026 | 71 ms |
| Jun 6, 2026 | 73 ms |
| Jun 13, 2026 | 75 ms |
| Jun 20, 2026 | 75 ms |
| Jun 27, 2026 | 76 ms |
| Jul 4, 2026 | 78 ms |
| Jul 11, 2026 | 77 ms |
| Jul 18, 2026 | 78 ms |
| Jul 25, 2026 | 78 ms |
| Aug 1, 2026 | 77 ms |
| Aug 8, 2026 | 80 ms |
| Aug 15, 2026 | 80 ms |
| Aug 22, 2026 | 81 ms |
| Aug 29, 2026 | 81 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 78 ms |
| Sep 19, 2026 | 77 ms |
| Sep 26, 2026 | 74 ms |
| Oct 3, 2026 | 72 ms |
| Oct 10, 2026 | 73 ms |
| Oct 17, 2026 | 74 ms |
| Oct 24, 2026 | 77 ms |
| Oct 31, 2026 | 79 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.5 s
2.9 s
4.4 s
5.8 s
7.3 s
8.7 s
10.2 s
11.6 s
Speed
Use efficient cache lifetimes
1.2 s · 185 KiB7 files are served with short cache lifetimes, so returning visitors download them again (185 KiB).
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
750 ms · 363 KiB6 images could be 363 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
Reduce unused JavaScript
680 ms · 173 KiBAbout 173 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 680 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.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 124 ms
124 msShopify costs a phone 124 ms of main-thread work and 327 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, one.store and Hexton and others), adding 550 KiB and 199 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 66 ms. During a long task the page ignores taps.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 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.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.9 s
10.9 sYour largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Buscamos la perfección”.
Speed Index: 12.2 s
12.2 sVisually, the page fills in at 12.2 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.495
0.495The layout shifts by 0.495 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 11.0 s
11.0 sThe page becomes fully interactive after 11.0 s. Good is under 3.8 s.
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.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 73 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 79 ms
79 msReal visitors wait 79 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 381 ms
381 msReal visitors wait 381 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 17 ms
17 msScripts block the page for only 17 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.8 MB in 301 requests
2.8 MBYour homepage downloads 2.8 MB in 301 requests on a phone: other files 1.1 MB (211), images 725 KiB (18) and scripts 707 KiB (59). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (138 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.8 g of CO₂ per visit
0.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.79 g of CO₂e: 94.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
ARIA attributes must conform to valid values (6 elements)
ARIA attributes must conform to valid values: 6 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 34 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 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (11 characters)
Your title is only 11 characters: “Kima Coffee”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“” and “Molino Manual de café Comandante MK4”). One clear main headline is easier for people and search engines.
Meta description is long (219 characters)
Your meta description is 219 characters; Google truncates after about 160, so the end of your pitch is cut.
86 internal links, 7 external
The homepage links to 86 pages on kimacoffee.com and 7 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://kimacoffee.com/es-us.
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://kimacoffee.com/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.
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 (490 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://kimacoffee.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://kimacoffee.com/es-us/collections/accesorios-1, https://kimacoffee.com/es-us/blogs/nuestros-cafes, https://kimacoffee.com/es-us/policies/terms-of-service and https://kimacoffee.com/es-us/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages slow to respond
https://kimacoffee.com/es-us/collections/nuestros-cafes-de-especialidad-frescos-y-tostados-en-malaga, https://kimacoffee.com/es-us/collections/accesorios-1, https://kimacoffee.com/es-us/pages/wholesales-venta-de-cafe-a-cafeterias-y-tiendas-de-cafe-tostadores-en-malaga, https://kimacoffee.com/es-us/collections/formacion-cafe-malaga-espana-barista-brewing-tueste and https://kimacoffee.com/es-us/blogs/nuestros-cafes took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.
6 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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.
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 14 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 360 words of copy
The homepage carries about 360 words of visible text.
1 checks passed
5 short forms
5 short forms (4 fields at most) are right on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager 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.
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 kimacoffee.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on kimacoffee.com, including 13 speed issues, 4 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.