Website review, no card needed

nacional.cl logo

nacional.cl website review

Visit site (opens in a new tab)Reviewed 10 November 202638 issues · 86 checks

This review found 38 issues worth fixing on nacional.cl, 14 of them high impact, across 86 checks. The most urgent: fails Core Web Vitals for real visitors. 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.7 s1.4 sMay 23Nov 71.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.6 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.6 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.5 s
Oct 17, 20261.6 s
Oct 24, 20261.5 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
331 ms126 msMay 23Nov 7298 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026150 ms
May 30, 2026156 ms
Jun 6, 2026163 ms
Jun 13, 2026167 ms
Jun 20, 2026168 ms
Jun 27, 2026170 ms
Jul 4, 2026169 ms
Jul 11, 2026170 ms
Jul 18, 2026179 ms
Jul 25, 2026187 ms
Aug 1, 2026205 ms
Aug 8, 2026210 ms
Aug 15, 2026218 ms
Aug 22, 2026221 ms
Aug 29, 2026216 ms
Sep 5, 2026213 ms
Sep 12, 2026199 ms
Sep 19, 2026194 ms
Sep 26, 2026182 ms
Oct 3, 2026194 ms
Oct 10, 2026245 ms
Oct 17, 2026259 ms
Oct 24, 2026269 ms
Oct 31, 2026307 ms
Nov 7, 2026298 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 nacional.cl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nacional.cl at 0.9 s0.9 s
  2. nacional.cl at 1.7 s1.7 s
  3. nacional.cl at 2.6 s2.6 s
  4. nacional.cl at 3.4 s3.4 s
  5. nacional.cl at 4.3 s4.3 s
  6. nacional.cl at 5.1 s5.1 s
  7. nacional.cl at 6.0 s6.0 s
  8. nacional.cl at 6.8 s6.8 s

Speed

8 to fix58
  • 7,011 HTML elements

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

  • Main-thread work: 5.6 s

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

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Clarity and pinflag.cl and others), adding 1.4 MB and 558 ms of main-thread time.

  • Improve image delivery

    696 KiB

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

  • Shopify adds 312 ms

    312 ms

    Shopify costs a phone 312 ms of main-thread work and 1.0 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 CSS

    300 ms · 92 KiB

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

  • Render-blocking requests

    300 ms

    15 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • 9 long tasks on the main thread

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

  • Reduce unused JavaScript

    179 KiB

    About 179 KiB of JavaScript is downloaded but never used on this page.

  • Font display

    150 ms

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

  • Use efficient cache lifetimes

    31 KiB

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

  • Legacy JavaScript

    19 KiB

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

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

  • Duplicated JavaScript

    4 KiB

    4 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 22 ms

    22 ms

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

Core Web Vitals

10 to fix67
  • 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: 10.1 s

    10.1 s

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

  • Time to Interactive: 20.4 s

    20.4 s

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

  • Speed Index: 6.7 s

    6.7 s

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

  • Real-user INP: 438 ms

    438 ms

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

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

    +98%

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

  • 46 images without width and height

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

  • Total Blocking Time: 279 ms

    279 ms

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

  • Cumulative Layout Shift: 0.118

    0.118

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

4 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 678 ms

    678 ms

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

Images and page weight

3 to fix62
  • Page weight: 5.5 MB in 483 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 483 requests on a phone: images 2.8 MB (90), other files 1.2 MB (165) and scripts 1.0 MB (147). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Banners_W43_Banner_MOB_Libretas_2027.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).

  • 10 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (37 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 1.6 g of CO₂ per visit

    1.56 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

7 to fixGoogle 8591
  • 88 text elements with low contrast

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

  • 3 tap targets too small

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 13 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

  • 4 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3), 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. (9 elements).

1 checks passed
  • 52 automated accessibility rules passed

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

SEO

1 to fixGoogle 9295
  • 4 H1 headlines

    There are 4 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.

  • 606 internal links, 31 external

    The homepage links to 606 pages on nacional.cl and 31 external pages.

7 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Descubre productos de arte, pintura, papelería y oficina. Inspira tu creatividad y compra online en Nacional Librería c…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Nacional Librería | Tienda Online | Despachos a todo Chile”.

  • Canonical URL set

    The canonical URL is https://nacional.cl/.

  • Structured data in place

    Structured data found: Organization, SocialMediaPosting 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://nacional.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 (4,353 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://nacional.cl/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 2 linked pages hidden from search

    https://nacional.cl/customer_authentication/redirect and https://nacional.cl/collections/oferta-imperdible are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 6 pages without a meta description

    https://nacional.cl/collections/all, https://nacional.cl/customer_authentication/redirect, https://nacional.cl/policies/shipping-policy, https://nacional.cl/pages/compra-y-retira-en-tienda, https://nacional.cl/pages/servicio-al-cliente and https://nacional.cl/pages/nuestras-tiendas have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://nacional.cl/customer_authentication/redirect, https://nacional.cl/pages/servicio-al-cliente and https://nacional.cl/pages/nuestras-tiendas have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 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.

Best practices

2 to fixGoogle 9291
  • 2 JavaScript errors while loading

    2 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 ()”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    96 of 101 tappable elements near the top are at least 24 px.

  • 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,516 words of copy

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

4 checks passed
  • 54 short forms

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

  • Social proof on the page

    Social proof on the homepage: 12 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies, 3 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.

  • 33 other companies contacted

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

Apps on your store

Your storefront loads 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Mercado Pago Antifraud Plus · Instafeed · Fether Frequently Bought · Pagefly Ai Page Builder · Judge Me Reviews · Klaviyo Email Marketing Sms · Microsoft Clarity · Mercadopago Pf App · Xb Wishlist

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Company

Employees
350
Headquarters
Las Condes

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on nacional.cl, including 18 speed issues, 1 SEO issue 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