Website review, no card needed
artcaffe.co.ke website review
Visit site (opens in a new tab)Reviewed 1 November 202631 issues · 78 checks
This review found 31 issues worth fixing on artcaffe.co.ke, 9 of them high impact, across 78 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
88B- #5,859 of 124,051 reviewed websitesbeats 93%
- #3,181 of 69,761 online storesbeats 93%
- #3,081 of 63,450 Shopify storesbeats 93%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 174 ms |
| May 16, 2026 | 167 ms |
| May 23, 2026 | 167 ms |
| May 30, 2026 | 168 ms |
| Jun 6, 2026 | 172 ms |
| Jun 13, 2026 | 175 ms |
| Jun 20, 2026 | 175 ms |
| Jun 27, 2026 | 172 ms |
| Jul 4, 2026 | 169 ms |
| Jul 11, 2026 | 169 ms |
| Jul 18, 2026 | 163 ms |
| Jul 25, 2026 | 161 ms |
| Aug 1, 2026 | 161 ms |
| Aug 8, 2026 | 159 ms |
| Aug 15, 2026 | 163 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 177 ms |
| Sep 5, 2026 | 178 ms |
| Sep 12, 2026 | 185 ms |
| Sep 19, 2026 | 193 ms |
| Sep 26, 2026 | 200 ms |
| Oct 3, 2026 | 205 ms |
| Oct 10, 2026 | 206 ms |
| Oct 17, 2026 | 205 ms |
| Oct 24, 2026 | 204 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
2.1 s · 438 KiBAbout 438 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Improve image delivery
250 ms · 4.1 MB13 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Minify JavaScript
750 ms · 148 KiB148 KiB could be saved by minifying JavaScript.
Heroku adds 17 ms
17 msHeroku costs a phone 17 ms of main-thread work and 413 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.
Use efficient cache lifetimes
200 ms · 80 KiB3 files are served with short cache lifetimes, so returning visitors download them again (80 KiB).
7 third-party services on the page
7 third-party services load with your homepage (Clarity, cloudfront.net and Shopify and others), adding 667 KiB and 172 ms of main-thread time.
Legacy JavaScript
200 ms · 10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused CSS
140 ms · 12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.
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.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 462 ms of it running JavaScript. That is comfortably low.
Server response: 8 ms
8 msYour server sent the HTML in 8 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.
Largest Contentful Paint: 20.6 s
20.6 sYour largest element takes 20.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: 21.8 s
21.8 sThe page becomes fully interactive after 21.8 s. Good is under 3.8 s.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 174 ms to 204 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
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.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
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
Page weight: 6.3 MB in 162 requests
6.3 MBYour homepage downloads 6.3 MB in 162 requests on a phone: images 4.5 MB (23), scripts 730 KiB (43) and other files 691 KiB (65). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
inside-artcaffes-root-to-stem-philosophy-8289190.jpg weighs 505 KiB. On a phone connection a single image that size takes seconds.
9 images far larger than shown
656 KiB9 images are downloaded at several times the size a phone draws them, for example inside-artcaffes-root-to-stem-philosophy-8289190.jpg at 2,801 px wide, shown at 360 px. Resized copies would save about 656 KiB.
9 images in older formats
9 images (1.3 MB) 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.8 g of CO₂ per visit
1.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.78 g of CO₂e: 213.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h6), 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
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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
Meta description is long (205 characters)
Your meta description is 205 characters; Google truncates after about 160, so the end of your pitch is cut.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
One H1 headline
Your <h1> is empty.
47 internal links, 11 external
The homepage links to 47 pages on artcaffe.co.ke and 11 external pages.
6 checks passed
Title: 46 characters
Your title is a healthy 46 characters: “Artcaffe Coffee & Bakery – Artcaffé Restaurant”.
Canonical URL set
The canonical URL is https://artcaffe.co.ke/.
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://artcaffe.co.ke/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (736 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://artcaffe.co.ke/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://artcaffe.co.ke/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://artcaffe.co.ke/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
8 pages without a meta description
https://artcaffe.co.ke/pages/dine-in, https://artcaffe.co.ke/pages/locations, https://artcaffe.co.ke/collections/food, https://artcaffe.co.ke/pages/gastro-bar, https://artcaffe.co.ke/blogs/our-blog and https://artcaffe.co.ke/pages/vouchers and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://artcaffe.co.ke/pages/dine-in, https://artcaffe.co.ke/pages/locations, https://artcaffe.co.ke/collections/food, https://artcaffe.co.ke/pages/gastro-bar, https://artcaffe.co.ke/pages/vouchers and https://artcaffe.co.ke/customer_authentication/redirect and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://artcaffe.co.ke/pages/locations and https://artcaffe.co.ke/pages/vouchers 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.
3 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.
Titles are unique
Every page we checked has its own title.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “$ is not defined”.
8 distorted images
8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
9 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 556 words of copy
The homepage carries about 556 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “For Orders Contact Our Call Center” and “BOOK A TABLE”.
14 calls to action
The homepage has 14 calls to action, for example “For Orders Contact Our Call Center”, “Book a table” and “Order food online”.
3 short forms
3 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
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 Microsoft Clarity (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
18 other companies contacted
Loading the homepage contacts 18 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 artcaffe.co.ke, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on artcaffe.co.ke, including 14 speed issues, 3 SEO issues and 1 conversion gap. 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.