Website review, no card needed
keat.mx website review
Visit site (opens in a new tab)Reviewed 4 November 202639 issues · 84 checks
This review found 39 issues worth fixing on keat.mx, 14 of them high impact, across 84 checks. The most urgent: render-blocking 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
70C- #96,723 of 115,529 reviewed websitesbeats 14%
- #59,842 of 66,525 online storesbeats 8%
- #55,579 of 60,790 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.8 s |
| Oct 17, 2026 | 3.7 s |
| Oct 24, 2026 | 3.7 s |
| Oct 31, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 179 ms |
| May 30, 2026 | 162 ms |
| Jun 6, 2026 | 186 ms |
| Jun 13, 2026 | 234 ms |
| Jun 20, 2026 | 262 ms |
| Jul 4, 2026 | 305 ms |
| Jul 18, 2026 | 294 ms |
| Jul 25, 2026 | 303 ms |
| Aug 1, 2026 | 299 ms |
| Aug 8, 2026 | 299 ms |
| Aug 15, 2026 | 297 ms |
| Aug 22, 2026 | 306 ms |
| Aug 29, 2026 | 306 ms |
| Sep 5, 2026 | 306 ms |
| Sep 12, 2026 | 305 ms |
| Sep 19, 2026 | 303 ms |
| Sep 26, 2026 | 308 ms |
| Oct 3, 2026 | 313 ms |
| Oct 10, 2026 | 318 ms |
| Oct 17, 2026 | 321 ms |
| Oct 24, 2026 | 320 ms |
| Oct 31, 2026 | 318 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
Render-blocking requests
1.2 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Main-thread work: 6.3 s
A phone's processor spends 6.3 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,125 HTML elements
The page has 3,125 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, Shopify and Facebook and others), adding 1.6 MB and 1.5 s of main-thread time.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 518 ms
518 msGoogle Tag Manager costs a phone 518 ms of main-thread work and 371 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.
Use efficient cache lifetimes
482 KiB27 files are served with short cache lifetimes, so returning visitors download them again (482 KiB).
Reduce unused JavaScript
455 KiBAbout 455 KiB of JavaScript is downloaded but never used on this page.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 389 ms. During a long task the page ignores taps.
Shopify adds 284 ms
284 msShopify costs a phone 284 ms of main-thread work and 484 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.
Minify JavaScript
43 KiB43 KiB could be saved by minifying JavaScript.
Reduce unused CSS
32 KiBAbout 32 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
10 KiB10 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
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.
Real-user FCP: 3.4 s
3.4 sReal visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 22.6 s
22.6 sThe page becomes fully interactive after 22.6 s. Good is under 3.8 s.
Largest Contentful Paint: 5.7 s
5.7 sYour largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Tu primer paso hacia una alimentación funcional.”.
Total Blocking Time: 900 ms
900 msScripts block taps and scrolling for 900 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.6 s
3.6 sReal visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 318 ms
318 msReal visitors wait 318 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 87% slower for real visitors
+87%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 179 ms to 318 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 86% slower for real visitors
+86%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 870 ms
870 msReal visitors wait 870 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.2 MB in 377 requests
4.2 MBYour homepage downloads 4.2 MB in 377 requests on a phone: scripts 1.7 MB (110), other files 1.1 MB (153) and images 902 KiB (57). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.18 g of CO₂e: 142.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
31 text elements with low contrast
31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
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.
60 form fields without a label
60 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
50 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: 50 passed and 4 failed. 2 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 (228 characters)
Your meta description is 228 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
One H1 headline
Your <h1> is empty.
101 internal links, 10 external
The homepage links to 101 pages on keat.mx and 10 external pages.
6 checks passed
Title: 45 characters
Your title is a healthy 45 characters: “k.eat | Nutrición Funcional y Caldo de Huesos”.
Canonical URL set
The canonical URL is https://keat.mx/.
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://keat.mx/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: 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 (2,401 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://keat.mx/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://keat.mx/collections/caldos-indivuales, https://keat.mx/collections/programas-con-caldos, https://keat.mx/collections/programas-grupales-con-caldos and https://keat.mx/collections/remedios-naturales have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://keat.mx/collections/all has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://keat.mx/collections/all has 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.
3 pages slow to respond
https://keat.mx/collections/all, https://keat.mx/collections/caldos-indivuales and https://keat.mx/products/caldo-de-huesos-paquete took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 45 found) and read each the way a search engine does.
5 checks passed
Linked pages load
8 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.
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 8 pages that loaded have a <title>.
Best practices
4 broken images
4 images failed to load on a phone, for example https://public-images.judge.me/judgeme/medals-v2-2025-rebranding/tran/platinum.svg?auto=format.
12 small tap targets
12 of 37 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_SOCKET_NOT_CONNECTED”.
1 checks passed
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
About 1,574 words of copy
The homepage carries about 1,574 words of visible text.
5 checks passed
19 short forms
19 short forms (5 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 61 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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, HubSpot and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
18 cookies set on arrival
18Opening the homepage sets 18 cookies (measured from a US location before any click).
47 other companies contacted
Loading the homepage contacts 47 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 keat.mx, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- AVADA Commerce;Shopify;Shopify Plus
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on keat.mx, including 23 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.