Website review, no card needed

atika.cl logo

atika.cl website review

Visit site (opens in a new tab)Reviewed 28 October 202648 issues · 88 checks

This review found 48 issues worth fixing on atika.cl, 17 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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
4.1 s3.7 sMay 9Oct 244.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.0 s
May 16, 20264.0 s
May 23, 20264.0 s
May 30, 20263.9 s
Jun 6, 20263.9 s
Jun 13, 20263.9 s
Jun 20, 20263.9 s
Jun 27, 20264.0 s
Jul 4, 20264.0 s
Jul 11, 20264.1 s
Jul 18, 20264.1 s
Jul 25, 20264.0 s
Aug 1, 20263.8 s
Aug 8, 20263.8 s
Aug 15, 20263.8 s
Aug 22, 20263.8 s
Aug 29, 20263.8 s
Sep 5, 20263.9 s
Sep 12, 20263.9 s
Sep 19, 20263.8 s
Sep 26, 20263.9 s
Oct 3, 20263.9 s
Oct 10, 20263.9 s
Oct 17, 20264.0 s
Oct 24, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
225 ms191 msMay 9Oct 24221 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026205 ms
May 16, 2026203 ms
May 23, 2026200 ms
May 30, 2026204 ms
Jun 6, 2026205 ms
Jun 13, 2026208 ms
Jun 20, 2026211 ms
Jun 27, 2026205 ms
Jul 4, 2026199 ms
Jul 11, 2026196 ms
Jul 18, 2026195 ms
Jul 25, 2026196 ms
Aug 1, 2026203 ms
Aug 8, 2026203 ms
Aug 15, 2026204 ms
Aug 22, 2026205 ms
Aug 29, 2026207 ms
Sep 5, 2026213 ms
Sep 12, 2026212 ms
Sep 19, 2026212 ms
Sep 26, 2026211 ms
Oct 3, 2026216 ms
Oct 10, 2026217 ms
Oct 17, 2026221 ms
Oct 24, 2026221 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 atika.cl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix35
  • Reduce unused JavaScript

    5.0 s · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.

  • Use efficient cache lifetimes

    1.3 s · 328 KiB

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

  • Mobile performance score: 35

    35/100

    Your mobile performance score is 35 (desktop: 13). 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, vtexassets.com and Google CDN and others), adding 3.0 MB and 2.1 s of main-thread time.

  • Improve image delivery

    650 ms · 114 KiB

    1 image could be 114 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

  • Google Tag Manager adds 662 ms

    662 ms

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

  • Reduce unused CSS

    600 ms · 104 KiB

    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.

  • vtexassets.com adds 561 ms

    561 ms

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

  • Google CDN adds 452 ms

    452 ms

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

  • Main-thread work: 4.0 s

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

  • Legacy JavaScript

    300 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 300 ms faster on a phone.

  • 14 long tasks on the main thread

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

  • Font display

    200 ms

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

  • Render-blocking requests

    150 ms

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

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 31 ms

    31 ms

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

Core Web Vitals

11 to fix33
  • 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 CLS: 0.84

    0.84

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

  • First Contentful Paint: 11.1 s

    11.1 s

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

  • Largest Contentful Paint: 18.3 s

    18.3 s

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

  • Time to Interactive: 25.3 s

    25.3 s

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

  • Speed Index: 11.1 s

    11.1 s

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

  • Total Blocking Time: 878 ms

    878 ms

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

  • Real-user INP: 210 ms

    210 ms

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

  • Real-user FCP: 2.3 s

    2.3 s

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

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

2 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix70
  • Page weight: 4.2 MB in 150 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 150 requests on a phone: scripts 2.6 MB (60), fonts 762 KiB (6) and other files 375 KiB (47). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.18 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

9 to fixGoogle 8288
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • Hidden but focusable

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

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

    All page content should be contained by landmarks: 4 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.

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

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails 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.

  • 3 links without text

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

  • 2 form fields without a label

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

  • 2 tap targets too small

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

2 checks passed
  • Every image has alt text

    All 3 images in the HTML carry an alt attribute.

  • 34 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: 34 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 10072
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “ATIKA | Calidad y diseños de tendencia con el precio justo para ti”.

  • Structured data has 1 problem

    Structured data found (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.

  • No XML sitemap

    No XML sitemap at https://www.MiTienda.com.br/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 12 internal links, 0 external

    The homepage links to 12 pages on atika.cl and 0 external pages.

3 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Crea ambientes y espacios únicos, junto a una exclusiva selección de Porcelanatos, Cerámicos, Griferías, Sanitarios y P…”.

  • Canonical URL set

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

  • robots.txt in place

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

AI search readiness

1 to fix83
  • 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.atika.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.

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

Other pages

3 to fix86
  • 2 pages share a title

    / and https://www.atika.cl/tiendas-atika all use the title “ATIKA | Calidad y diseños de tendencia con el precio justo para ti”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 9 pages share a meta description

    https://www.atika.cl/outdoor-season-sale-piscinas, https://www.atika.cl/nuestras-marcas, https://www.atika.cl/quienes-somos, https://www.atika.cl/tiendas-atika, https://www.atika.cl/seguimiento-de-pedido and https://www.atika.cl/last-chance and 3 others use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://www.atika.cl/nuestras-marcas, https://www.atika.cl/quienes-somos and https://www.atika.cl/seguimiento-de-pedido have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.atika.cl/tiendas-atika and https://www.atika.cl/seguimiento-de-pedido have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 1 page slow to respond

    https://www.atika.cl/last-chance took over 3 s to send its HTML from our server.

  • 10 internal pages checked

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

5 checks passed
  • Linked pages load

    All 10 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 10 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

2 checks passed
  • Tap targets are thumb-sized

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

  • 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 40 words

    The homepage has only about 40 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.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and Hotjar.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (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.

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 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.

  • 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 atika.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
React
Analytics
Google Tag Manager | Hotjar
Hosting
Chile Internet S.A.

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 atika.cl, including 22 speed issues, 5 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