kroton.com.pe website review

The page goes through 1 redirect before it starts loading, costing about 24.6 s. Link and advertise the final URL directly.

About 683 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.8 s faster on a phone.

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

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

12 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 54 (desktop: 65). Pages that score under 90 lose visitors before the first paint.

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

6 third-party services load with your homepage (Google Maps, Facebook and Google Tag Manager and others), adding 808 KiB and 525 ms of main-thread time.

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

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

Google Maps costs a phone 226 ms of main-thread work and 383 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 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

13 KiB could be saved by minifying CSS.

6 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.

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 5.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 4.5 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 25.9 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

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

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

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

Your homepage downloads 7.7 MB in 268 requests on a phone: images 5.3 MB (81), scripts 1.7 MB (107) and fonts 375 KiB (10). Under 2 MB keeps phones on slow connections fast.

5 images (245 KiB) 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.

6 images further down the page (274 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

22 images have no alt text, which hurts accessibility and image search.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

13 form fields have no label, so screen readers announce an empty box and autofill guesses.

There are 3 <h1> headlines (“Conoce a nuestros aliados estratégicos”, “DSS Profesional V8” and “Certificados por la Sunat como Operador Económico…”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

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

No XML sitemap at https://www.kroton.com.pe/chicken-and-wrsrlux/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 131 pages on kroton.com.pe and 3 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), 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.

There is no /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.

/tienda, /contactenos, /servicio-tecnico, /nosotros, /capacitaciones and /blog 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 61 found) and read each the way a search engine does.

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

2 links from your homepage to your own site are broken, for example https://www.kroton.com.pe/cart/ (410).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

kroton.com.pe has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

DMARC is set to p=none, so mail pretending to be kroton.com.pe is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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 7 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.