Website review, no card needed
lacabra.com website review
Visit site (opens in a new tab)Reviewed 7 November 202630 issues · 73 checks
This review found 30 issues worth fixing on lacabra.com, 12 of them high impact, across 73 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
80B- #47,178 of 120,375 reviewed websitesbeats 55%
- #31,335 of 68,150 online storesbeats 48%
- #30,134 of 62,105 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 113 ms |
| May 23, 2026 | 114 ms |
| May 30, 2026 | 114 ms |
| Jun 6, 2026 | 117 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 120 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 123 ms |
| Jul 11, 2026 | 122 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 125 ms |
| Aug 15, 2026 | 129 ms |
| Aug 22, 2026 | 132 ms |
| Aug 29, 2026 | 134 ms |
| Sep 5, 2026 | 131 ms |
| Sep 12, 2026 | 131 ms |
| Sep 19, 2026 | 130 ms |
| Sep 26, 2026 | 130 ms |
| Oct 3, 2026 | 134 ms |
| Oct 10, 2026 | 144 ms |
| Oct 17, 2026 | 149 ms |
| Oct 24, 2026 | 150 ms |
| Oct 31, 2026 | 147 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
5.4 s · 964 KiBAbout 964 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.4 s faster on a phone.
Avoid multiple page redirects
1.4 sThe page goes through 3 redirects before it starts loading, costing about 1.4 s. Link and advertise the final URL directly.
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.4 s
A phone's processor spends 6.4 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,832 HTML elements
The page has 3,832 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
150 ms · 3.7 MB26 images could be 3.7 MB 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.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Clarity and Facebook and others), adding 1.7 MB and 847 ms of main-thread time.
Render-blocking requests
750 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Use efficient cache lifetimes
150 ms · 358 KiB18 files are served with short cache lifetimes, so returning visitors download them again (358 KiB).
Klaviyo adds 202 ms
202 msKlaviyo costs a phone 202 ms of main-thread work and 545 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.
Shopify adds 146 ms
146 msShopify costs a phone 146 ms of main-thread work and 462 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 164 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
8 KiB8 KiB JavaScript is shipped twice across bundles.
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: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 97.7 s
97.7 sYour largest element takes 97.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 27.8 s
27.8 sVisually, the page fills in at 27.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 103.2 s
103.2 sThe page becomes fully interactive after 103.2 s. Good is under 3.8 s.
First Contentful Paint: 4.9 s
4.9 sThe first text or image appears after 4.9 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.281
0.281The layout shifts by 0.281 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 31% slower for real visitors
+31%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 113 ms to 147 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 123 ms
123 msReal visitors wait 123 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 454 ms
454 msReal visitors wait 454 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 186 ms
186 msScripts block the page for only 186 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 34.5 MB in 854 requests
34.5 MBYour homepage downloads 34.5 MB in 854 requests on a phone: images 28.6 MB (148), scripts 3.4 MB (259) and other files 1.5 MB (321). Under 2 MB keeps phones on slow connections fast.
About 9.8 g of CO₂ per visit
9.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 9.77 g of CO₂e: 1172.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
37 text elements with low contrast
37 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
37 tap targets too small
37 tap targets are too small or too close together to hit reliably with a finger.
4 links without text
4 links have no text or label, so screen readers cannot say where they go.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 checks passed
Every image has alt text
All 72 images in the HTML carry an alt attribute.
SEO
Meta description is long (233 characters)
Your meta description is 233 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
252 internal links, 9 external
The homepage links to 252 pages on lacabra.com and 9 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Christmas Calendar”.
Title: 32 characters
Your title is a healthy 32 characters: “Coffee, Bakery & Café – La Cabra”.
Canonical URL set
The canonical URL is https://lacabra.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://lacabra.com/sitemap.xml.
AI search readiness
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.
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.
llms.txt published
The site publishes https://lacabra.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://lacabra.com/collections/coffee has 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 67 found) and read each the way a search engine does.
6 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 11 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 11 pages that loaded have a <title>.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
8 console errors
8 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 400 (Bad Request)”).
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 1,139 words of copy
The homepage carries about 1,139 words of visible text.
3 checks passed
13 calls to action
The homepage has 13 calls to action, for example “Contact”, “Join now” and “Shop”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
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 lacabra.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Selecty · Judge Me Reviews · Stape Remix · Upcart · gorgias.chat · rechargecdn.com · 9gtb.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
Company
- Headquarters
- Ringkobing
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on lacabra.com, including 18 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.