Website review, no card needed

klatchcoffee.com logo

klatchcoffee.com website review

Visit site (opens in a new tab)Reviewed 25 October 202632 issues · 80 checks

This review found 32 issues worth fixing on klatchcoffee.com, 11 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. 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

Real-visitor load time (LCP)75th percentile, phones
1.2 s1.0 sMay 2Oct 171.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.1 s
May 9, 20261.1 s
May 16, 20261.2 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.0 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
158 ms116 msMay 2Oct 17146 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026121 ms
May 9, 2026121 ms
May 16, 2026122 ms
May 23, 2026124 ms
May 30, 2026126 ms
Jun 6, 2026127 ms
Jun 13, 2026129 ms
Jun 20, 2026129 ms
Jun 27, 2026129 ms
Jul 4, 2026128 ms
Jul 11, 2026124 ms
Jul 18, 2026125 ms
Jul 25, 2026127 ms
Aug 1, 2026129 ms
Aug 8, 2026129 ms
Aug 15, 2026129 ms
Aug 22, 2026136 ms
Aug 29, 2026140 ms
Sep 5, 2026145 ms
Sep 12, 2026149 ms
Sep 19, 2026152 ms
Sep 26, 2026153 ms
Oct 3, 2026152 ms
Oct 10, 2026150 ms
Oct 17, 2026146 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

Full-page screenshot of klatchcoffee.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. klatchcoffee.com at 0.4 s0.4 s
  2. klatchcoffee.com at 0.8 s0.8 s
  3. klatchcoffee.com at 1.1 s1.1 s
  4. klatchcoffee.com at 1.5 s1.5 s
  5. klatchcoffee.com at 1.9 s1.9 s
  6. klatchcoffee.com at 2.3 s2.3 s
  7. klatchcoffee.com at 2.6 s2.6 s
  8. klatchcoffee.com at 3.0 s3.0 s

Speed

10 to fix57
  • Use efficient cache lifetimes

    2.5 s · 393 KiB

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

  • Improve image delivery

    1.4 s · 1.2 MB

    12 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Reduce unused JavaScript

    1.6 s · 395 KiB

    About 395 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    950 ms

    10 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Clarity, Yotpo and Shopify and others), adding 1.7 MB and 592 ms of main-thread time.

  • Reduce unused CSS

    300 ms · 47 KiB

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

  • Main-thread work: 2.2 s

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

  • 2,038 HTML elements

    The page has 2,038 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Shopify adds 75 ms

    75 ms

    Shopify costs a phone 75 ms of main-thread work and 901 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 · 18 KiB

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

  • 2 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 87 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 20.1 s

    20.1 s

    Your largest element takes 20.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • First Contentful Paint: 6.5 s

    6.5 s

    The first text or image appears after 6.5 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 20.6 s

    20.6 s

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

  • Speed Index: 8.2 s

    8.2 s

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

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

    +22%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 121 ms to 146 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-17, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 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.3 s

    1.3 s

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

  • Real-user INP: 145 ms

    145 ms

    Real visitors wait 145 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.1 s

    1.1 s

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

  • Real-user TTFB: 440 ms

    440 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 16 ms

    16 ms

    Scripts block the page for only 16 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 4.6 MB in 271 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 271 requests on a phone: images 2.3 MB (17), scripts 1,015 KiB (85) and other files 900 KiB (128). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.31 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.31 g of CO₂e: 157.1 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

3 to fixGoogle 9296
  • 18 text elements with low contrast

    18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

  • 17 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 145 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10090
  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “Limited-Edition Holiday Velvet Bags Are Here!” and “Where Coffee is the Conversation”). One clear main headline is easier for people and search engines.

  • Meta description is long (313 characters)

    Your meta description is 313 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 171 internal links, 8 external

    The homepage links to 171 pages on klatchcoffee.com and 8 external pages.

6 checks passed
  • Title: 48 characters

    Your title is a healthy 48 characters: “Klatch Coffee | Where Coffee Is The Conversation”.

  • Canonical URL set

    The canonical URL is https://www.klatchcoffee.com/.

  • 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://www.klatchcoffee.com/sitemap.xml.

AI search readiness

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

  • llms.txt published

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

Other pages

5 to fix57
  • 3 linked pages are broken

    Your homepage links to https://www.klatchcoffee.com/products/original-christmas-2, https://www.klatchcoffee.com/products/dancing-reindeer-blend-2 and https://www.klatchcoffee.com/products/fireside-blend-2, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages share a title

    https://www.klatchcoffee.com/collections/pearl-reserve and https://www.klatchcoffee.com/products/el-salvador-jasal-orange-geisha-anaerobic-natural all use the title “Pearl Reserve Coffee Collection – Klatch Coffee”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.klatchcoffee.com/policies/shipping-policy has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.klatchcoffee.com/collections/pearl-reserve and https://www.klatchcoffee.com/products/el-salvador-jasal-orange-geisha-anaerobic-natural use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.klatchcoffee.com/products/el-salvador-jasal-orange-geisha-anaerobic-natural, whose canonical is https://www.klatchcoffee.com/collections/pearl-reserve. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 105 found) and read each the way a search engine does.

3 checks passed
  • 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 12 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7776
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56324253&Ver=2&mid=6abc3d65-3dfc-4141-80b9-0fff01ffac7a&bo=1&sid=14d31d90d04411f19a935b3100afbf74&vid=14d339a0d04411f18c6703ee7e0836c2&vids=0&msclkid=N&pi=918639831&lg.

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

2 checks passed
  • Tap targets are thumb-sized

    28 of 33 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 688 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 26 calls to action

    The homepage has 26 calls to action, for example “Shop”, “Toggle Shop submenu” and “Shop Coffee”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity and LinkedIn Insight.

Privacy and tracking

1 to fix
  • 11 trackers load before any consent

    11

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 6 mores (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.

  • 24 cookies set on arrival

    24

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

  • 44 other companies contacted

    Loading the homepage contacts 44 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 klatchcoffee.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on klatchcoffee.com, including 15 speed issues, 2 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