Website review, no card needed
antartica.cl website review
Visit site (opens in a new tab)Reviewed 18 November 202651 issues · 94 checks
This review found 51 issues worth fixing on antartica.cl, 23 of them high impact, across 94 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
69D- #108,060 of 126,178 reviewed websitesbeats 12%
- #64,521 of 70,384 online storesbeats 7%
- #476 of 730 Magento storesbeats 30%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.4 s |
| Nov 7, 2026 | 2.4 s |
| Nov 14, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 176 ms |
| Jun 6, 2026 | 178 ms |
| Jun 13, 2026 | 179 ms |
| Jun 20, 2026 | 183 ms |
| Jun 27, 2026 | 184 ms |
| Jul 4, 2026 | 184 ms |
| Jul 11, 2026 | 184 ms |
| Jul 18, 2026 | 181 ms |
| Jul 25, 2026 | 182 ms |
| Aug 1, 2026 | 180 ms |
| Aug 8, 2026 | 180 ms |
| Aug 15, 2026 | 181 ms |
| Aug 22, 2026 | 181 ms |
| Aug 29, 2026 | 183 ms |
| Sep 5, 2026 | 184 ms |
| Sep 12, 2026 | 184 ms |
| Sep 19, 2026 | 184 ms |
| Sep 26, 2026 | 185 ms |
| Oct 3, 2026 | 186 ms |
| Oct 10, 2026 | 188 ms |
| Oct 17, 2026 | 189 ms |
| Oct 24, 2026 | 190 ms |
| Oct 31, 2026 | 193 ms |
| Nov 7, 2026 | 197 ms |
| Nov 14, 2026 | 202 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
How it loaded on a phone
1.2 s
2.4 s
3.6 s
4.9 s
6.1 s
7.3 s
8.5 s
9.7 s
Speed
Improve image delivery
13.0 s · 7.6 MB135 images could be 7.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 13.0 s faster on a phone.
Use efficient cache lifetimes
3.3 s · 709 KiB22 files are served with short cache lifetimes, so returning visitors download them again (709 KiB).
Reduce unused JavaScript
1.8 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
22,863 HTML elements
The page has 22,863 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 11.2 s
A phone's processor spends 11.2 s on main-thread work while loading, 6.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.0 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, fw-cdn.com and Facebook and others), adding 2.5 MB and 2.1 s of main-thread time.
Reduce unused CSS
610 ms · 161 KiBAbout 161 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.
Google Tag Manager adds 430 ms
430 msGoogle Tag Manager costs a phone 430 ms of main-thread work and 491 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.
Freshchat adds 307 ms
307 msFreshchat costs a phone 307 ms of main-thread work and 774 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.
fw-cdn.com adds 341 ms
341 msfw-cdn.com costs a phone 341 ms of main-thread work and 98 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 adds 328 ms
328 msFacebook costs a phone 328 ms of main-thread work and 220 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.
ContentSquare adds 304 ms
304 msContentSquare costs a phone 304 ms of main-thread work and 197 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 on the main thread
20 long tasks block the main thread while loading, the longest for 312 ms. During a long task the page ignores taps.
Legacy JavaScript
200 ms · 21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
1 checks passed
Server response: 43 ms
43 msYour server sent the HTML in 43 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 54.7 s
54.7 sYour largest element takes 54.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 29.2 s
29.2 sVisually, the page fills in at 29.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 80.3 s
80.3 sThe page becomes fully interactive after 80.3 s. Good is under 3.8 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Real-user INP: 382 ms
382 msReal visitors wait 382 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 176 ms to 202 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 681 ms
681 msReal visitors wait 681 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 22.3 MB in 646 requests
22.3 MBYour homepage downloads 22.3 MB in 646 requests on a phone: images 17.9 MB (289), scripts 3.3 MB (279) and other files 422 KiB (51). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
2.1 MB6 images are downloaded at several times the size a phone draws them, for example Mesa_de_trabajo_2_141.png at 1,000 px wide, shown at 175 px. Resized copies would save about 2.1 MB.
6 images below the first screen load straight away
6 images further down the page (2.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.3 g of CO₂ per visit
6.31 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.31 g of CO₂e: 756.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
27 links without text
27 visible links have no text or label, so screen readers cannot say where they go.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
Headings skip levels
Headings skip levels (h3 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
652 internal links, 10 external
The homepage links to 652 pages on antartica.cl and 10 external pages.
4 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Compra en Librería Antártica, las mejores Novelas, Libros Infantiles y Juveniles, Literatura, Libros de Autoayuda, Coci…”.
Title: 36 characters
Your title is a healthy 36 characters: “Librería Online | Librería Antártica”.
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.antartica.cl/media/sitemap.xml.
AI search readiness
robots.txt blocks 4 AI answer engine crawlers
4 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
No Organization structured data
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.
No llms.txt
There is no https://www.antartica.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
Other pages
1 page without a title
https://www.antartica.cl/nuestrastiendas has no <title>, so Google invents the link text in results.
4 pages slow to respond
https://www.antartica.cl/politicas-de-despacho, https://www.antartica.cl/libros.html, https://www.antartica.cl/novedades/preventas.html and https://www.antartica.cl/textos-escolares.html took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 183 found) and read each the way a search engine does.
6 checks passed
Linked pages load
10 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 9 pages that loaded have a meta description.
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.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
9 of 9 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 123 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 70 words
The homepage has only about 70 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
2 checks passed
110 short forms
110 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Hotjar.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
25 other companies contacted
Loading the homepage contacts 25 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 antartica.cl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Magento
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- Cloudflare
Company
- Founded
- 1958
- Headquarters
- Santiago
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on antartica.cl, including 23 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.