preunic.cl website review

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

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 986 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.

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

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

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

29 images could be 711 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.

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

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

Facebook costs a phone 250 ms of main-thread work and 257 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,093 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 20 KiB of CSS is downloaded but never applied on this page.

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.

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

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

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

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

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

Your largest element takes 31.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “landing-generioc-ba”. Most of its time is resource load delay (14.7 s).

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

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

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

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

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

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

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

Your homepage downloads 5.8 MB in 330 requests on a phone: scripts 3.8 MB (161), images 1.7 MB (97) and fonts 153 KiB (8). Under 2 MB keeps phones on slow connections fast.

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Your page has no <title>, so Google has to invent the blue link in search results.

No meta description, so Google writes its own snippet from whatever text it finds.

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

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

There is no robots.txt at preunic.cl/robots.txt, the first file search crawlers ask for.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

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://preunic.cl/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.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Hydration failed because the server rendered HTML didn't match the client. As a result this tree will be regenerated on…”.

Chrome logged issues while loading the page (“Cookie”).

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.

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

The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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

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