Website review, no card needed
joolca.com website review
Visit site (opens in a new tab)Reviewed 19 November 202631 issues · 79 checks
This review found 31 issues worth fixing on joolca.com, 10 of them high impact, across 79 checks. The most urgent: improve image delivery. 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
88B- #5,755 of 121,674 reviewed websitesbeats 93%
- #3,152 of 68,840 online storesbeats 93%
- #3,052 of 62,729 Shopify storesbeats 93%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
| Nov 7, 2026 | 1.8 s |
| Nov 14, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 144 ms |
| Jun 13, 2026 | 145 ms |
| Jun 20, 2026 | 152 ms |
| Jun 27, 2026 | 144 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 105 ms |
| Jul 25, 2026 | 103 ms |
| Aug 1, 2026 | 98 ms |
| Aug 8, 2026 | 98 ms |
| Aug 15, 2026 | 101 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 108 ms |
| Sep 5, 2026 | 113 ms |
| Sep 12, 2026 | 117 ms |
| Sep 19, 2026 | 117 ms |
| Sep 26, 2026 | 120 ms |
| Oct 3, 2026 | 116 ms |
| Oct 10, 2026 | 119 ms |
| Oct 17, 2026 | 120 ms |
| Oct 24, 2026 | 119 ms |
| Oct 31, 2026 | 117 ms |
| Nov 7, 2026 | 112 ms |
| Nov 14, 2026 | 105 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
Improve image delivery
1.9 s · 1.9 MB25 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Reduce unused JavaScript
1.5 s · 370 KiBAbout 370 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Main-thread work: 6.7 s
A phone's processor spends 6.7 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, Google Tag Manager and Klaviyo and others), adding 1.3 MB and 842 ms of main-thread time.
Clarity adds 351 ms
351 msClarity costs a phone 351 ms of main-thread work and 30 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.
Google Tag Manager adds 249 ms
249 msGoogle Tag Manager costs a phone 249 ms of main-thread work and 489 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.
2,368 HTML elements
The page has 2,368 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 116 ms
116 msKlaviyo costs a phone 116 ms of main-thread work and 314 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 38 ms
38 msShopify costs a phone 38 ms of main-thread work and 379 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 142 ms. During a long task the page ignores taps.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
18 KiB5 files are served with short cache lifetimes, so returning visitors download them again (18 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: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 18.0 s
18.0 sYour largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BFCM Website Homescreen Video - 9x16 Vertical”.
Time to Interactive: 18.0 s
18.0 sThe page becomes fully interactive after 18.0 s. Good is under 3.8 s.
Speed Index: 10.0 s
10.0 sVisually, the page fills in at 10.0 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
7 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 95 ms
95 msReal visitors wait 95 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 TTFB: 779 ms
779 msReal visitors wait 779 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 146 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 164 ms
164 msScripts block the page for only 164 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 28.0 MB in 414 requests
28.0 MBYour homepage downloads 28.0 MB in 414 requests on a phone: media 21.5 MB (2), images 3.4 MB (54) and other files 1.4 MB (257). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
emre_customer_support.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image far larger than shown
37 KiB1 image is downloaded at several times the size a phone draws it, for example hottap_go_close_up_temp_display.jpg at 390 px wide, shown at 70 px. Resized copies would save about 37 KiB.
About 7.9 g of CO₂ per visit
7.93 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.93 g of CO₂e: 951.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
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.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 122 images in the HTML carry an alt attribute.
49 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: 49 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (302 characters)
Your meta description is 302 characters; Google truncates after about 160, so the end of your pitch is cut.
147 internal links, 20 external
The homepage links to 147 pages on joolca.com and 20 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Joolca United States”.
Title: 43 characters
Your title is a healthy 43 characters: “Joolca | Welcome to the Great(er) Outdoors.”.
Canonical URL set
The canonical URL is https://www.joolca.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.joolca.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (1,317 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.joolca.com/llms.txt (16 KiB, 103 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.
7 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.
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 15 pages that loaded have a <title>.
Best practices
9 small tap targets
9 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
About 708 words of copy
The homepage carries about 708 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop the sale.” and “Shop”.
22 calls to action
The homepage has 22 calls to action, for example “Shop the sale.”, “Shop” and “Contact us”.
11 short forms
11 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 111 testimonial or review blocks, 3 customer or partner logos and “100,000+ Customers”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads 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.
26 cookies set on arrival
26Opening the homepage sets 26 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.
28 other companies contacted
Loading the homepage contacts 28 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 joolca.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Microsoft Clarity · Judge Me Reviews · Klaviyo Email Marketing Sms · Aimerce First Party Pixel · Simprosys Google Shopping Feed · Aftersell
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
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Campbellfield
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on joolca.com, including 17 speed issues, 1 SEO issue and 1 conversion gap. 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.