uysa.com.pe website review

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

The HTML itself could arrive about 8.2 s sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 8.2 s on a phone.

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

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

Your server takes 8.3 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Google CDN and others), adding 10.2 MB and 1.9 s of main-thread time.

vtexassets.com costs a phone 980 ms of main-thread work and 7.3 MB 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.

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

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

Google CDN costs a phone 264 ms of main-thread work and 2.0 MB 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.

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

The page has 2,806 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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.

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

Real visitors wait 633 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Your largest element takes 119.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “mobile-banner-0”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 24.7 MB in 201 requests on a phone: media 20.0 MB (3), images 2.0 MB (67) and scripts 1.9 MB (64). Under 2 MB keeps phones on slow connections fast.

13 images are downloaded at several times the size a phone draws them, for example 9c022f7f-e9ed-49b7-9a4e-e14b6b43e95e___edf658762c82c7498560e at 1,708 px wide, shown at 370 px. Resized copies would save about 1.6 MB.

16 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (69 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.

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

10 buttons have no accessible name, so screen readers announce just “button”.

15 visible links have no text or label, so screen readers cannot say where they go.

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

8 tap targets are too small or too close together to hit reliably with a finger.

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

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

Elements with visible text labels do not have matching accessible names. (6 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 14 characters: “Unión Ychicawa”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 86 pages on uysa.com.pe and 16 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.uysa.com.pe/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.uysa.com.pe/847, https://www.uysa.com.pe/924 and https://www.uysa.com.pe/las-previas-en-casa are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/, https://www.uysa.com.pe/tiendas, https://www.uysa.com.pe/showroom, https://www.uysa.com.pe/contactanos, https://www.uysa.com.pe/terminos-y-condiciones and https://www.uysa.com.pe/promociones all use the title “Unión Ychicawa”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.uysa.com.pe/847, https://www.uysa.com.pe/showroom, https://www.uysa.com.pe/924 and https://www.uysa.com.pe/las-previas-en-casa use the same meta description. A description written for each page earns more clicks.

https://www.uysa.com.pe/productos-nuevos, https://www.uysa.com.pe/tiendas, https://www.uysa.com.pe/847, https://www.uysa.com.pe/contactanos, https://www.uysa.com.pe/924 and https://www.uysa.com.pe/terminos-y-condiciones and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.uysa.com.pe/contactanos 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.

https://www.uysa.com.pe/buffet took over 3 s to send its HTML from our server.

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

12 of 51 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 “Cannot read properties of undefined (reading 'register')”.

6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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: 1 trust badge. 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 513 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, 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.

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