ferosor.cl website review

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

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

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

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

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

39 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

8 third-party services load with your homepage (Facebook, Google Tag Manager and Google CDN and others), adding 1.1 MB and 820 ms of main-thread time.

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

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

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

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

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

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

Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need. 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 50 ms).

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.

3 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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

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

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

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

40 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 177 ms to 207 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.3 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.1 MB in 141 requests on a phone: images 8.4 MB (76), scripts 1.3 MB (34) and fonts 162 KiB (7). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.8 MB together. On a phone connection a single image that size takes seconds.

26 images (5.0 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.

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

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

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

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

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

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

32 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is only 23 characters: “Ferosor - Tienda Online”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 35 <h1> headlines (“Chaqueta Rugged BETACRAFT Hombre”, “Chaqueta Rugged BETACRAFT Mujer” and “Chaqueta Mamaku BETACRAFT Color Café”). One clear main headline is easier for people and search engines.

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.

No XML sitemap at https://ferosor.cl/sitemap.xml, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 588 pages on ferosor.cl and 22 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.

Your homepage links to /contacto-6, which answers with an error. Visitors hit a dead end and search engines drop it.

/module/askforaquote/QuotesCart and /carrito are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/module/askforaquote/QuotesCart, /carrito, /103-ferreteria-agricola, /204-semillas, /171-automotriz and /118-combustible and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

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

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

2 links from your homepage to your own site are broken, for example https://ferosor.cl/contacto-6 (404).

3 links to other sites are dead, for example https://cl.linkedin.com/company/ferosordeos (404).

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

ferosor.cl has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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