Website review, no card needed

prestigio.com.ar logo

prestigio.com.ar website review

Visit site (opens in a new tab)Reviewed 19 November 202648 issues · 85 checks

This review found 48 issues worth fixing on prestigio.com.ar, 18 of them high impact, across 85 checks. The most urgent: threatMetrix adds 3.5 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
6.6 s5.5 sMay 30Nov 146.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20266.0 s
Jun 6, 20265.9 s
Jun 13, 20265.9 s
Jun 20, 20265.8 s
Jun 27, 20266.0 s
Jul 4, 20266.1 s
Jul 11, 20266.3 s
Jul 18, 20266.3 s
Jul 25, 20266.2 s
Aug 1, 20266.0 s
Aug 8, 20265.8 s
Aug 15, 20265.6 s
Aug 22, 20265.6 s
Aug 29, 20265.7 s
Sep 5, 20265.8 s
Sep 12, 20266.1 s
Sep 19, 20266.2 s
Sep 26, 20266.1 s
Oct 3, 20266.1 s
Oct 10, 20266.0 s
Oct 17, 20265.8 s
Oct 24, 20266.0 s
Oct 31, 20266.4 s
Nov 7, 20266.4 s
Nov 14, 20266.4 s
Real-visitor tap response (INP)75th percentile, phones
302 ms163 msMay 30Nov 14228 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026198 ms
Jun 6, 2026198 ms
Jun 13, 2026195 ms
Jun 20, 2026192 ms
Jun 27, 2026195 ms
Jul 4, 2026197 ms
Jul 11, 2026202 ms
Jul 18, 2026204 ms
Jul 25, 2026205 ms
Aug 1, 2026201 ms
Aug 8, 2026193 ms
Aug 15, 2026188 ms
Aug 22, 2026182 ms
Aug 29, 2026180 ms
Sep 5, 2026188 ms
Sep 12, 2026255 ms
Sep 19, 2026284 ms
Sep 26, 2026282 ms
Oct 3, 2026286 ms
Oct 10, 2026248 ms
Oct 17, 2026179 ms
Oct 24, 2026189 ms
Oct 31, 2026204 ms
Nov 7, 2026227 ms
Nov 14, 2026228 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of prestigio.com.ar (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. prestigio.com.ar at 1.4 s1.4 s
  2. prestigio.com.ar at 2.8 s2.8 s
  3. prestigio.com.ar at 4.2 s4.2 s
  4. prestigio.com.ar at 5.6 s5.6 s
  5. prestigio.com.ar at 7.0 s7.0 s
  6. prestigio.com.ar at 8.4 s8.4 s
  7. prestigio.com.ar at 9.8 s9.8 s
  8. prestigio.com.ar at 11.2 s11.2 s

Speed

12 to fix42
  • ThreatMetrix adds 3.5 s

    3.5 s

    ThreatMetrix costs a phone 3.5 s of main-thread work and 290 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.

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 42

    42/100

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

  • Main-thread work: 9.2 s

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

  • 8 third-party services on the page

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

  • 20 long tasks on the main thread

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

  • vtexassets.com adds 983 ms

    983 ms

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

  • Reduce unused JavaScript

    300 ms · 517 KiB

    About 517 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 741 ms

    741 ms

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

  • Use efficient cache lifetimes

    350 ms · 383 KiB

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

  • Font display

    450 ms

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

  • Improve image delivery

    380 KiB

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

  • Legacy JavaScript

    150 ms · 47 KiB

    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.

  • Reduce unused CSS

    135 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 45 ms

    45 ms

    Your server sent the HTML in 45 ms, well inside Google's 600 ms guideline.

Core Web Vitals

13 to fix0
  • Fails Core Web Vitals for real visitors

    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-user LCP: 5.4 s

    5.4 s

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

  • Real-user CLS: 1.02

    1.02

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

  • Real-user FCP: 3.7 s

    3.7 s

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

  • Time to Interactive: 21.1 s

    21.1 s

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

  • Total Blocking Time: 3.4 s

    3.4 s

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

  • Speed Index: 7.2 s

    7.2 s

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

  • Largest Contentful Paint: 4.2 s

    4.2 s

    Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Pintura para piletas, maderas y pisos atérmicos”.

  • Real-user INP: 299 ms

    299 ms

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Cumulative Layout Shift: 0.126

    0.126

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

  • 6 images without width and height

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

  • Tap response (INP) got 15% slower for real visitors

    +15%

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

Images and page weight

3 to fix60
  • 1 image over 500 KB

    17d95561-06f6-4c4f-b506-9a8b35b43c26___90e2b2ca3aab58c472357 weighs 540 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.3 MB in 143 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 143 requests on a phone: scripts 1.8 MB (63), images 697 KiB (18) and fonts 461 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (540 KiB) is 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.

  • About 0.9 g of CO₂ per visit

    0.92 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8692
  • 3 text elements with low contrast

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

  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • All page content should be contained by landmarks (3 elements)

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

  • No main landmark

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9290
  • Structured data has 1 problem

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

  • No social preview image

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

  • Only 4 internal links

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

  • No favicon declared

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

  • No X (Twitter) card tag

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

6 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Encontrá pinturas látex, impermeabilizantes, aires acondicionados, zócalos, wall panels, pádel y complementos para el h…”.

  • One H1 headline

    Your main headline reads: “Prestigio”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Prestigio - Descubrí Pinturas, Wall panels y Decoración”.

  • Canonical URL set

    The canonical URL is https://www.prestigio.com.ar/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.prestigio.com.ar/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.prestigio.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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

Other pages

3 to fix86
  • 3 linked pages hidden from search

    https://www.prestigio.com.ar/4258, https://www.prestigio.com.ar/4153 and https://www.prestigio.com.ar/4158 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages share a meta description

    https://www.prestigio.com.ar/4258, https://www.prestigio.com.ar/4153 and https://www.prestigio.com.ar/4158 use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://www.prestigio.com.ar/4258, https://www.prestigio.com.ar/4153 and https://www.prestigio.com.ar/4158 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 internal pages checked

    We fetched 3 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 3 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 3 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 3 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 2 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “The Content-Security-Policy directive name 'script-src='nonce-{SERVER-GENERATED-NONCE}'' contains one or more invalid c…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • No call to action on the first screen

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

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

  • No direct contact details

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

  • Only about 15 words

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

  • No form on the homepage

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

  • No risk reducer

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies, 2 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 36 other companies contacted

    Loading the homepage contacts 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at prestigio.com.ar, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager
Hosting
AWS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on prestigio.com.ar, including 25 speed issues, 4 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25