Website review, no card needed
incapto.com website review
Visit site (opens in a new tab)Reviewed 19 October 202644 issues · 92 checks
This review found 44 issues worth fixing on incapto.com, 13 of them high impact, across 92 checks. The most urgent: page weight: 9.2 MB in 299 requests. 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
76C- #68,873 of 112,162 reviewed websitesbeats 34%
- #44,740 of 64,315 online storesbeats 26%
- #42,500 of 58,774 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.3 s |
| May 9, 2026 | 5.4 s |
| May 16, 2026 | 5.4 s |
| May 23, 2026 | 5.3 s |
| May 30, 2026 | 5.2 s |
| Jun 6, 2026 | 4.9 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 163 ms |
| May 9, 2026 | 163 ms |
| May 16, 2026 | 163 ms |
| May 23, 2026 | 165 ms |
| May 30, 2026 | 165 ms |
| Jun 6, 2026 | 171 ms |
| Jun 13, 2026 | 192 ms |
| Jun 20, 2026 | 212 ms |
| Jun 27, 2026 | 235 ms |
| Jul 4, 2026 | 253 ms |
| Jul 11, 2026 | 259 ms |
| Jul 18, 2026 | 258 ms |
| Jul 25, 2026 | 252 ms |
| Aug 1, 2026 | 246 ms |
| Aug 8, 2026 | 244 ms |
| Aug 15, 2026 | 246 ms |
| Aug 22, 2026 | 255 ms |
| Aug 29, 2026 | 256 ms |
| Sep 5, 2026 | 256 ms |
| Sep 12, 2026 | 255 ms |
| Sep 19, 2026 | 254 ms |
| Sep 26, 2026 | 258 ms |
| Oct 3, 2026 | 268 ms |
| Oct 10, 2026 | 272 ms |
| Oct 17, 2026 | 276 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
Main-thread work: 8.4 s
A phone's processor spends 8.4 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,154 HTML elements
The page has 4,154 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 (Shopify, Clarity and Google Tag Manager and others), adding 1.7 MB and 1.3 s of main-thread time.
Mobile performance score: 51
51/100Your mobile performance score is 51 (desktop: 56). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
695 KiBAbout 695 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
150 ms · 536 KiB20 files are served with short cache lifetimes, so returning visitors download them again (536 KiB).
Render-blocking requests
500 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Reduce unused CSS
450 ms · 50 KiBAbout 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Shopify adds 343 ms
343 msShopify costs a phone 343 ms of main-thread work and 527 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 267 ms. During a long task the page ignores taps.
Google Tag Manager adds 214 ms
214 msGoogle Tag Manager costs a phone 214 ms of main-thread work and 369 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.
loloyal.com adds 156 ms
156 msloloyal.com costs a phone 156 ms of main-thread work and 389 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.
Duplicated JavaScript
150 ms · 76 KiB76 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
198 KiB8 images could be 198 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
Minify JavaScript
9 KiB9 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.
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: 27 ms
27 msYour server sent the HTML in 27 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: 8.6 s
8.6 sYour largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 23.9 s
23.9 sThe page becomes fully interactive after 23.9 s. Good is under 3.8 s.
Speed Index: 10.9 s
10.9 sVisually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.
Real-user INP: 220 ms
220 msReal visitors wait 220 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 68% slower for real visitors
+68%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 163 ms to 276 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 422 ms
422 msScripts block taps and scrolling for 422 ms in total while the page loads. Good is under 200 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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: 789 ms
789 msReal visitors wait 789 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 55% faster for real visitors
-55%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.3 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 9.2 MB in 299 requests
9.2 MBYour homepage downloads 9.2 MB in 299 requests on a phone: media 4.1 MB (3), scripts 2.0 MB (103) and images 1.6 MB (53). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
slider-lanzamiento-aura-duo-mobile.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).
5 images below the first screen load straight away
5 images further down the page (162 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.6 g of CO₂ per visit
2.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.60 g of CO₂e: 312.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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail 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.
10 form fields without a label
10 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (170 characters)
Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
355 internal links, 14 external
The homepage links to 355 pages on incapto.com and 14 external pages.
6 checks passed
Title: 48 characters
Your title is a healthy 48 characters: “Incapto | Freshly roasted specialty coffee beans”.
Canonical URL set
The canonical URL is https://incapto.com/en.
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://incapto.com/sitemap.xml.
AI search readiness
Parts of the site are closed to 6 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
3 checks passed
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 (774 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://incapto.com/llms.txt (7 KiB, 3 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://incapto.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://incapto.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://incapto.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://incapto.com/en/products/incapto-aura-duo-coffee-maker, https://incapto.com/en/products/worldwide-coffee-beans-tasting-pack, https://incapto.com/en/pages/coffee-bean-subscriptions, https://incapto.com/en/pages/contact, https://incapto.com/customer_authentication/redirect and https://incapto.com/en/collections/coffee-beans and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
14 pages with very little text
https://incapto.com/en/products/incapto-aura-duo-coffee-maker, https://incapto.com/en/products/worldwide-coffee-beans-tasting-pack, https://incapto.com/en/pages/coffee-bean-subscriptions, https://incapto.com/en/pages/contact, https://incapto.com/en/collections/coffee-beans and https://incapto.com/en/products/pack-initiation-coffee-beans and 8 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 101 found) and read each the way a search engine does.
3 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.
Best practices
1 broken image
1 image failed to load on a phone, for example https://incapto.com/en#.
5 small tap targets
5 of 24 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
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 859 words of copy
The homepage carries about 859 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Try coffees”.
39 calls to action
The homepage has 39 calls to action, for example “Try coffees”, “Subscribe and save” and “Shop coffee packs”.
6 short forms
6 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 11 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and TikTok Pixel.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel 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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
27 other companies contacted
Loading the homepage contacts 27 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 incapto.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on incapto.com, including 22 speed issues, 3 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.