psa.com.ar website review

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

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

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

YouTube costs a phone 1.5 s of main-thread work and 2.8 MB 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.

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

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

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

8 third-party services load with your homepage (YouTube, Google CDN and Google Tag Manager and others), adding 5.6 MB and 3.6 s of main-thread time.

Google CDN costs a phone 662 ms of main-thread work and 1.1 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 570 ms of main-thread work and 542 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.

Facebook costs a phone 312 ms of main-thread work and 299 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.

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

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

About 153 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.

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

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

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.

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

Your largest element takes 62.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Tienda PSA”.

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

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

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

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

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

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

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

The first text or image appears after 2.6 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.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.6 MB in 170 requests on a phone: images 6.3 MB (46), scripts 5.3 MB (55) and other files 365 KiB (34). Under 2 MB keeps phones on slow connections fast.

PSA_AR_BAnneranim_mobile_0.gif weighs 5.1 MB. On a phone connection a single image that size takes seconds.

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

PSA_AR_BAnneranim_mobile_0.gif 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).

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

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

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

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

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

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

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

No Open Graph image (also missing: og:title, og:description), 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 169 pages on psa.com.ar and 23 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.psa.com.ar/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.psa.com.ar/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.psa.com.ar/home all use the title “Purificadores de Agua | Garantía Oficial | PSA Argentina”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.psa.com.ar/productos/dispenser and https://www.psa.com.ar/productos/mate-termo-psa have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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