Website review, no card needed

templecoffee.com logo

templecoffee.com website review

Visit site (opens in a new tab)Reviewed 10 November 202624 issues · 78 checks

This review found 24 issues worth fixing on templecoffee.com, 8 of them high impact, across 78 checks. The most urgent: page weight: 11.5 MB in 215 requests. 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
2.6 s1.0 sMay 23Nov 71.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.4 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.0 s
Jun 20, 20261.7 s
Jun 27, 20261.4 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Oct 31, 20261.3 s
Nov 7, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
103 ms85 msMay 23Nov 793 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202687 ms
May 30, 202687 ms
Jun 6, 202687 ms
Jun 13, 202690 ms
Jun 20, 202695 ms
Jun 27, 202697 ms
Jul 4, 2026101 ms
Jul 11, 2026100 ms
Jul 18, 202698 ms
Jul 25, 202697 ms
Aug 1, 202695 ms
Aug 8, 202693 ms
Aug 15, 202695 ms
Aug 22, 202694 ms
Aug 29, 202694 ms
Sep 5, 202695 ms
Sep 12, 202695 ms
Sep 19, 202695 ms
Sep 26, 202696 ms
Oct 3, 202694 ms
Oct 10, 202694 ms
Oct 17, 202692 ms
Oct 24, 202693 ms
Oct 31, 202693 ms
Nov 7, 202693 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 templecoffee.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix71
  • Render-blocking requests

    1.1 s

    13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Improve image delivery

    2.6 MB

    10 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 71

    71/100

    Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.

  • Main-thread work: 2.7 s

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

  • 2,471 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, rechargecdn.com and pxucdn.com and others), adding 473 KiB and 393 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Reduce unused JavaScript

    184 KiB

    About 184 KiB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    130 ms · 18 KiB

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

  • Use efficient cache lifetimes

    5 KiB

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

  • 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: 9 ms

    9 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 13.6 s

    13.6 s

    Your largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Close up footage of dripping, water pouring, a glass is fil…”.

  • Time to Interactive: 15.0 s

    15.0 s

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

  • Speed Index: 3.7 s

    3.7 s

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

  • Tap response (INP) held steady for real visitors

    +7%

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

10 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.2 s

    1.2 s

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

  • Real-user INP: 96 ms

    96 ms

    Real visitors wait 96 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.0 s

    1.0 s

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

  • Real-user TTFB: 347 ms

    347 ms

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

  • Largest content (LCP) got 47% faster for real visitors

    -47%

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

  • Total Blocking Time: 175 ms

    175 ms

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

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix35
  • Page weight: 11.5 MB in 215 requests

    11.5 MB

    Your homepage downloads 11.5 MB in 215 requests on a phone: media 6.5 MB (1), images 3.5 MB (36) and other files 718 KiB (92). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 2.0 MB together. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    2.4 MB

    8 images are downloaded at several times the size a phone draws them, for example Temple_K_Street.jpg at 2,694 px wide, shown at 390 px. Resized copies would save about 2.4 MB.

  • About 3.3 g of CO₂ per visit

    3.26 g

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

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

Accessibility

5 to fixGoogle 9194
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 9 text elements with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 258 images in the HTML carry an alt attribute.

  • 50 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: 50 passed and 5 failed. 4 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
  • Meta description is long (202 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 145 internal links, 3 external

    The homepage links to 145 pages on templecoffee.com and 3 external pages.

6 checks passed
  • Title: 38 characters

    Your title is a healthy 38 characters: “Temple Coffee – Temple Coffee Roasters”.

  • Canonical URL set

    The canonical URL is https://templecoffee.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://templecoffee.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,129 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix93
  • 9 pages share a meta description

    https://templecoffee.com/collections/all, https://templecoffee.com/policies/shipping-policy, https://templecoffee.com/collections/coffee-club, https://templecoffee.com/collections/coffee, https://templecoffee.com/collections/new-coffees and https://templecoffee.com/collections/single-origin and 3 others use the same meta description. A description written for each page earns more clicks.

  • 6 pages without an H1

    https://templecoffee.com/collections/coffee, https://templecoffee.com/collections/new-coffees, https://templecoffee.com/collections/single-origin, https://templecoffee.com/collections/blends, https://templecoffee.com/collections/espresso and https://templecoffee.com/collections/decaf have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    33 of 41 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: 3 trust badges. 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 257 words of copy

    The homepage carries about 257 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: “Join the Coffee Club”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Apply”, “Join the Coffee Club” and “Contact”.

  • 6 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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.

  • 7 cookies set on arrival

    7

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

  • 13 other companies contacted

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

Apps on your store

Your storefront loads 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

rechargecdn.com · pxucdn.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

Hiring

Hiring
1 open role
Job board
careers page

Company

Headquarters
Sacramento

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on templecoffee.com, including 8 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