Website review, no card needed

apro.cl logo

apro.cl website review

Visit site (opens in a new tab)Reviewed 26 October 202627 issues · 77 checks

This review found 27 issues worth fixing on apro.cl, 13 of them high impact, across 77 checks. The most urgent: render-blocking requests. 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
1.6 s1.3 sMay 9Oct 241.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.4 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
151 ms93 msMay 9Oct 24144 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026100 ms
May 16, 2026104 ms
May 23, 2026106 ms
May 30, 2026110 ms
Jun 6, 2026113 ms
Jun 13, 2026114 ms
Jun 20, 2026114 ms
Jun 27, 2026115 ms
Jul 4, 2026113 ms
Jul 11, 2026112 ms
Jul 18, 2026112 ms
Jul 25, 2026114 ms
Aug 1, 2026115 ms
Aug 8, 2026118 ms
Aug 15, 2026119 ms
Aug 22, 2026118 ms
Aug 29, 2026118 ms
Sep 5, 2026118 ms
Sep 12, 2026121 ms
Sep 19, 2026126 ms
Sep 26, 2026134 ms
Oct 3, 2026140 ms
Oct 10, 2026143 ms
Oct 17, 2026143 ms
Oct 24, 2026144 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 apro.cl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. apro.cl at 0.4 s0.4 s
  2. apro.cl at 0.8 s0.8 s
  3. apro.cl at 1.1 s1.1 s
  4. apro.cl at 1.5 s1.5 s
  5. apro.cl at 1.9 s1.9 s
  6. apro.cl at 2.3 s2.3 s
  7. apro.cl at 2.6 s2.6 s
  8. apro.cl at 3.0 s3.0 s

Speed

5 to fix61
  • Render-blocking requests

    1.1 s

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

  • Main-thread work: 5.0 s

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

  • 3,397 HTML elements

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

  • Mobile performance score: 61

    61/100

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

  • Improve image delivery

    300 ms · 405 KiB

    20 images could be 405 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Clarity, loox.io and Shopify and others), adding 206 KiB and 297 ms of main-thread time.

  • Reduce unused JavaScript

    180 ms · 45 KiB

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

  • Use efficient cache lifetimes

    150 ms · 25 KiB

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

  • 3 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 92 but mobile only 61. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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 CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

7 to fix100
  • 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.

  • Largest Contentful Paint: 12.2 s

    12.2 s

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

  • Time to Interactive: 12.4 s

    12.4 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Speed Index: 6.9 s

    6.9 s

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

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

    +41%

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

6 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 175 ms

    175 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Total Blocking Time: 79 ms

    79 ms

    Scripts block the page for only 79 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix83
  • Page weight: 2.8 MB in 206 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 206 requests on a phone: images 1.5 MB (56), other files 682 KiB (77) and scripts 352 KiB (46). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Banner_Octubre_-_HOME_safety_2026_CALZADO_-_MOBILE.jpg 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).

  • 2 images below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.79 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 8593
  • 8 tap targets too small

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

  • 6 text elements with low contrast

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

  • 62 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 15 links without text

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

1 checks passed
  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 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

3 to fixGoogle 9283
  • Title is long (77 characters)

    Your title is 77 characters, so Google will cut it off around 60: “Venta de Articulos de Seguridad Industrial | APRO – Apro Seguridad Industrial”.

  • Meta description is long (229 characters)

    Your meta description is 229 characters; Google truncates after about 160, so the end of your pitch is cut.

  • One H1 headline

    Your <h1> is empty.

  • 487 internal links, 13 external

    The homepage links to 487 pages on apro.cl and 13 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.apro.cl/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.apro.cl/sitemap.xml.

AI search readiness

100
4 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: 4 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,547 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.apro.cl/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 15 pages without a meta description

    https://www.apro.cl/collections/zapatos-y-zapatillas-new, https://www.apro.cl/collections/botines-new, https://www.apro.cl/collections/botas-new, https://www.apro.cl/collections/botas-industriales-new, https://www.apro.cl/collections/accesorios-calzados-new and https://www.apro.cl/collections/calzados-de-seguridad-new and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 24 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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 risk reducer

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

  • About 1,187 words of copy

    The homepage carries about 1,187 words of visible text.

4 checks passed
  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 61 customer or partner logos, a star rating and 3 trust badges.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies (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.

  • 21 other companies contacted

    Loading the homepage contacts 21 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 apro.cl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on apro.cl, including 12 speed issues, 3 SEO issues and 2 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