kemsa.com.py website review

27 images could be 19.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 30.9 s faster on a phone.

7 files are served with short cache lifetimes, so returning visitors download them again (12.6 MB).

About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.6 s faster on a phone.

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.4 s).

About 186 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

tagembed.com costs a phone 1.2 s of main-thread work and 378 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 11. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (tagembed.com, Google Tag Manager and Facebook and others), adding 1.7 MB and 2.1 s of main-thread time.

14 long tasks block the main thread while loading, the longest for 1.5 s. During a long task the page ignores taps.

Google Tag Manager costs a phone 450 ms of main-thread work and 660 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.

Polyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

Google Maps costs a phone 193 ms of main-thread work and 393 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.

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.

3 KiB could be saved by minifying JavaScript.

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 visitors wait 610 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.86 (75th percentile). Good is under 0.1.

Your largest element takes 101.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PUMA”.

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

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

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

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

Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 128 ms to 303 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 861 ms for your server to start answering (75th percentile). Good is under 800 ms.

17 images have no width and height attributes, so the layout jumps as each one loads.

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 26.5 MB in 203 requests on a phone: images 22.9 MB (55), scripts 2.6 MB (81) and fonts 566 KiB (7). Under 2 MB keeps phones on slow connections fast.

banner-mobi299-1-1690463710.png weighs 553 KiB. On a phone connection a single image that size takes seconds.

5 images (1.9 MB) are 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.

banner-mobi299-1-1690463710.png 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 is downloaded at several times the size a phone draws it, for example nosotros-2.webp at 1,365 px wide, shown at 330 px. Resized copies would save about 44 KiB.

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

Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 frame has no title, so screen-reader users cannot tell what it contains.

ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 6 elements on the page fail this check, rated minor by axe-core.

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

SVG elements with an img role do not have an accessible text alternative (3 elements).

Your title is only 5 characters: “KEMSA”. 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.

There are 2 <h1> headlines (“Sobre Nosotros” and “Sobre Nosotros”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 242 characters; Google truncates after about 160, so the end of your pitch is cut.

No XML sitemap at https://www.kemsa.com.py/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at kemsa.com.py/robots.txt, the first file search crawlers ask for.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 171 pages on kemsa.com.py and 6 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.

There is no https://www.kemsa.com.py/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.kemsa.com.py/sporthouse, https://www.kemsa.com.py/sporthouse/buscador, https://www.kemsa.com.py/sporthouse/producto/148907/cn26-home-shirt, https://www.kemsa.com.py/sporthouse/producto/149143/ccp-26-away-shirt and https://www.kemsa.com.py/sporthouse/producto/128291/libertad-home-shirt all use the title “Sport House”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.kemsa.com.py/sporthouse, https://www.kemsa.com.py/americanlook, https://www.kemsa.com.py/sporthouse/buscador, https://www.kemsa.com.py/sporthouse/producto/148907/cn26-home-shirt, https://www.kemsa.com.py/sporthouse/producto/149143/ccp-26-away-shirt and https://www.kemsa.com.py/sporthouse/producto/128291/libertad-home-shirt and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kemsa.com.py/nosotros, https://www.kemsa.com.py/tiendas, https://www.kemsa.com.py/mayoristas, https://www.kemsa.com.py/fabrica, https://www.kemsa.com.py/rrhh and https://www.kemsa.com.py/contacto use the same meta description. A description written for each page earns more clicks.

https://www.kemsa.com.py/shoes4less and https://www.kemsa.com.py/tiendas have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.kemsa.com.py/sporthouse, https://www.kemsa.com.py/americanlook, https://www.kemsa.com.py/shoes4less, https://www.kemsa.com.py/sporthouse/buscador, https://www.kemsa.com.py/sporthouse/producto/148907/cn26-home-shirt and https://www.kemsa.com.py/sporthouse/producto/149143/ccp-26-away-shirt and 2 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.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 image is served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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 367 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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, 1 of them by other companies (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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.