Website review, no card needed

cilantro.cafe logo

cilantro.cafe website review

Visit site (opens in a new tab)Reviewed 3 November 202644 issues · 93 checks

This review found 44 issues worth fixing on cilantro.cafe, 17 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of cilantro.cafe (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cilantro.cafe at 0.5 s0.5 s
  2. cilantro.cafe at 0.9 s0.9 s
  3. cilantro.cafe at 1.4 s1.4 s
  4. cilantro.cafe at 1.8 s1.8 s
  5. cilantro.cafe at 2.3 s2.3 s
  6. cilantro.cafe at 2.7 s2.7 s
  7. cilantro.cafe at 3.2 s3.2 s
  8. cilantro.cafe at 3.6 s3.6 s

Speed

8 to fix47
  • Reduce unused JavaScript

    3.0 s · 710 KiB

    About 710 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.

  • Use efficient cache lifetimes

    2.0 s · 500 KiB

    24 files are served with short cache lifetimes, so returning visitors download them again (500 KiB).

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 5.8 s

    A phone's processor spends 5.8 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Bold Commerce, Clarity and OptiMonk and others), adding 1.2 MB and 1.0 s of main-thread time.

  • Reduce unused CSS

    360 ms · 80 KiB

    About 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 360 ms faster on a phone.

  • 17 long tasks on the main thread

    17 long tasks block the main thread while loading, the longest for 395 ms. During a long task the page ignores taps.

  • Bold Commerce adds 330 ms

    330 ms

    Bold Commerce costs a phone 330 ms of main-thread work and 485 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.

  • Legacy JavaScript

    150 ms · 89 KiB

    Polyfills for old browsers add 89 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Improve image delivery

    100 ms · 35 KiB

    1 image could be 35 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

  • Duplicated JavaScript

    17 KiB

    17 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    15 KiB

    15 KiB could be saved by minifying JavaScript.

  • 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
  • Server response: 10 ms

    10 ms

    Your server sent the HTML in 10 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix67
  • 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: 10.9 s

    10.9 s

    Your 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 element shown below.

  • Time to Interactive: 16.6 s

    16.6 s

    The page becomes fully interactive after 16.6 s. Good is under 3.8 s.

  • Total Blocking Time: 1.1 s

    1.1 s

    Scripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 3.8 s

    3.8 s

    Real visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Speed Index: 5.6 s

    5.6 s

    Visually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.

  • 4 images without width and height

    4 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 18% slower for real visitors

    +18%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 152 ms to 180 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user INP: 182 ms

    182 ms

    Real visitors wait 182 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

    Real visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 748 ms

    748 ms

    Real visitors wait 748 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix85
  • Page weight: 3.0 MB in 220 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 220 requests on a phone: scripts 1.7 MB (106), other files 782 KiB (86) and images 309 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.85 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.85 g of CO₂e: 102.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • 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

14 to fixGoogle 6880
  • Invalid ARIA attributes

    5 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (5 elements)

    Certain ARIA roles must contain particular children: 5 elements on the page fail this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (5 elements)

    ARIA attributes must conform to valid values: 5 elements on the page fail this check, rated critical by axe-core.

  • Hidden but focusable

    22 elements hidden from screen readers can still receive keyboard focus.

  • ARIA input fields must have an accessible name (9 elements)

    ARIA input fields must have an accessible name: 9 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (4 elements)

    Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • ARIA toggle fields must have an accessible name (3 elements)

    ARIA toggle fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (11 elements)

    All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.

  • 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.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Elements marked as presentational should be consistently ignored (5 elements)

    Elements marked as presentational should be consistently ignored: 5 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 52 images in the HTML carry an alt attribute.

  • 41 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: 41 passed and 13 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9274
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (8 characters)

    Your title is only 8 characters: “Cilantro”. 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.

  • One H1 headline

    Your <h1> is empty.

  • 106 internal links, 12 external

    The homepage links to 106 pages on cilantro.cafe and 12 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://cilantro.cafe/.

  • 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://cilantro.cafe/sitemap.xml.

AI search readiness

1 to fix88
  • 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 (378 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://cilantro.cafe/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix76
  • 2 pages share a title

    https://cilantro.cafe/collections/buy-2-get-1/products/cilantro-frappe-powder-500g and https://cilantro.cafe/collections/frappe-range/products/cilantro-frappe-powder-500g all use the title “Frappe Powder – Cilantro”. 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://cilantro.cafe/collections/products-on-site, https://cilantro.cafe/collections/buy-2-get-1, https://cilantro.cafe/collections/frappe-range, https://cilantro.cafe/collections/coffee, https://cilantro.cafe/collections/turkish-coffee-kit and https://cilantro.cafe/collections/our-special-kits and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://cilantro.cafe/collections/buy-2-get-1/products/cilantro-frappe-powder-500g and https://cilantro.cafe/collections/frappe-range/products/cilantro-frappe-powder-500g use the same meta description. A description written for each page earns more clicks.

  • 7 links to non-canonical URLs

    Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://cilantro.cafe/collections/buy-2-get-1/products/cilantro-frappe-powder-500g, whose canonical is https://cilantro.cafe/products/cilantro-frappe-powder-500g. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://cilantro.cafe/collections/products-on-site has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://cilantro.cafe/collections/products-on-site has 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 39 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.

  • 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

1 to fixGoogle 9693
  • 6 small tap targets

    6 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

2 to fix88
  • 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: 78 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 291 words of copy

    The homepage carries about 291 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Shop”, “Shop Now” and “Shop now”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity and 1 more (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.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 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.

  • 42 other companies contacted

    Loading the homepage contacts 42 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 cilantro.cafe, 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 44 issues on cilantro.cafe, including 15 speed issues, 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25