ka-la.cc website review

A phone's processor spends 4.5 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

About 71 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

5 third-party services load with your homepage (Klaviyo, Shopify and facturama.mx and others), adding 185 KiB and 219 ms of main-thread time.

10 long tasks block the main thread while loading, the longest for 235 ms. During a long task the page ignores taps.

About 37 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

1 image could be 65 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 files are served with short cache lifetimes, so returning visitors download them again (40 KiB).

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

11 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (2.5 s).

Visually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 488 ms in total while the page loads. Good is under 200 ms.

The page becomes fully interactive after 6.4 s. Good is under 3.8 s.

The layout shifts by 0.123 while loading, so content jumps under the reader's thumb. Good is under 0.1.

The first text or image appears after 1.9 s on a phone. Good is under 1.8 s.

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.

1 image (81 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 0.42 g of CO₂e: 50.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element hidden from screen readers can still receive keyboard focus.

1 tap target is too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 13 characters: “Ka la – Ka lā”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 18 characters: “¡Bienvenid@ Ka la!”. 70 to 160 characters is enough to sell the click.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 104 pages on ka-la.cc and 3 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.ka-la.cc/collections/men and https://www.ka-la.cc/collections/tops-1 all use the title “Hombres – Ka lā”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ka-la.cc/collections/men, https://www.ka-la.cc/collections/tops-1, https://www.ka-la.cc/collections/jerseys, https://www.ka-la.cc/collections/long-sleeve-jerseys, https://www.ka-la.cc/collections/men-jackets and https://www.ka-la.cc/collections/gilets and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.

17 of 42 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://app.facturama.mx/Public/css/storeFrontStyles.css' from origin 'https://www.ka-la.c…”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 21 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 536 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Klaviyo (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.

Opening the homepage sets 10 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.