Website review, no card needed
localwavecoffee.com website review
Visit site (opens in a new tab)Reviewed 12 November 202625 issues · 72 checks
This review found 25 issues worth fixing on localwavecoffee.com, 11 of them high impact, across 72 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
One score from every part of this review. How it works
How it loaded on a phone
0.5 s
0.9 s
1.4 s
1.9 s
2.3 s
2.8 s
3.3 s
3.8 s
Speed
Reduce unused JavaScript
2.0 s · 983 KiBAbout 983 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.
hcaptcha.com adds 1.2 s
1.2 shcaptcha.com costs a phone 1.2 s of main-thread work and 2.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 5.0 s
A phone's processor spends 5.0 s on main-thread work while loading, 2.8 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 (hcaptcha.com, Shopify and Clarity and others), adding 4.0 MB and 1.7 s of main-thread time.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Shopify adds 294 ms
294 msShopify costs a phone 294 ms of main-thread work and 1.5 MB 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.
Improve image delivery
150 ms · 149 KiB11 images could be 149 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 224 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
141 KiB9 files are served with short cache lifetimes, so returning visitors download them again (141 KiB).
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need.
Reduce unused CSS
14 KiBAbout 14 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
7 KiB7 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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 33.2 s
33.2 sThe page becomes fully interactive after 33.2 s. Good is under 3.8 s.
Largest Contentful Paint: 8.9 s
8.9 sYour largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 10.1 s
10.1 sVisually, the page fills in at 10.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 462 ms
462 msScripts block taps and scrolling for 462 ms in total while the page loads. Good is under 200 ms.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0.091
0.091The layout barely moves while loading (CLS 0.091, good is under 0.1).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 5.9 MB in 472 requests
5.9 MBYour homepage downloads 5.9 MB in 472 requests on a phone: scripts 3.0 MB (181), other files 1.2 MB (225) and HTML 1,011 KiB (10). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
50 KiB1 image is downloaded at several times the size a phone draws it, for example LocalWaveCoffeeRoastersLogo_Transparent_Cropped.svg at 1,555 px wide, shown at 120 px. Resized copies would save about 50 KiB.
About 1.7 g of CO₂ per visit
1.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.66 g of CO₂e: 199.2 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
35 text elements with low contrast
35 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
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.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
Headings skip levels
Headings skip levels (h3 → h6, h3 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 19 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. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
One H1 headline
Your <h1> is empty.
61 internal links, 3 external
The homepage links to 61 pages on localwavecoffee.com and 3 external pages.
7 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Locally roasted specialty coffee beans. Shipped the same day they're roasted, farm gate, sustainable packaging, and far…”.
Title: 33 characters
Your title is a healthy 33 characters: “Home - Local Wave Coffee Roasters”.
Canonical URL set
The canonical URL is https://localwavecoffee.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://localwavecoffee.com/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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (567 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://localwavecoffee.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without a meta description
https://localwavecoffee.com/collections/all, https://localwavecoffee.com/policies/shipping-policy, https://localwavecoffee.com/a/loyalty-program, https://localwavecoffee.com/pages/brick-and-mortar and https://localwavecoffee.com/pages/careers have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://localwavecoffee.com/a/loyalty-program and https://localwavecoffee.com/pages/brick-and-mortar 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 24 found) and read each the way a search engine does.
5 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.
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
4 small tap targets
4 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Requests the notification permission on page load
Requests the notification permission on page load.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 403 words of copy
The homepage carries about 403 words of visible text.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “LEARN MORE!” and “Contact Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager 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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 1 of them by other companies (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.
26 other companies contacted
Loading the homepage contacts 26 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 localwavecoffee.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Inbox · Tapita Seo Speed · Sami Wholesale · Avada Seo Suite · Llama Cart Upsells · Upsell Prod · Pushowl · Forms · Appstle Loyalty · Appstle Bundles · revenuehunt.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
- jQuery
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 1 open role
- Job board
- careers page
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on localwavecoffee.com, including 11 speed issues, 1 SEO issue and 3 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.