Website review, no card needed

americanas.com logo

americanas.com website review

Visit site (opens in a new tab)Reviewed 19 October 202649 issues · 97 checks

This review found 49 issues worth fixing on americanas.com, 22 of them high impact, across 97 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
3.4 s2.9 sMay 2Oct 173.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.3 s
May 9, 20263.3 s
May 16, 20263.4 s
May 23, 20263.4 s
May 30, 20263.4 s
Jun 6, 20263.4 s
Jun 13, 20263.4 s
Jun 20, 20263.3 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.1 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.0 s
Aug 29, 20263.1 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.3 s
Oct 10, 20263.3 s
Oct 17, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
406 ms273 msMay 2Oct 17391 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026288 ms
May 9, 2026301 ms
May 16, 2026309 ms
May 23, 2026316 ms
May 30, 2026322 ms
Jun 6, 2026329 ms
Jun 13, 2026335 ms
Jun 20, 2026341 ms
Jun 27, 2026345 ms
Jul 4, 2026347 ms
Jul 11, 2026349 ms
Jul 18, 2026350 ms
Jul 25, 2026354 ms
Aug 1, 2026357 ms
Aug 8, 2026365 ms
Aug 15, 2026373 ms
Aug 22, 2026378 ms
Aug 29, 2026379 ms
Sep 5, 2026377 ms
Sep 12, 2026377 ms
Sep 19, 2026377 ms
Sep 26, 2026379 ms
Oct 3, 2026382 ms
Oct 10, 2026387 ms
Oct 17, 2026391 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 americanas.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. americanas.com at 0.9 s0.9 s
  2. americanas.com at 1.8 s1.8 s
  3. americanas.com at 2.7 s2.7 s
  4. americanas.com at 3.6 s3.6 s
  5. americanas.com at 4.5 s4.5 s
  6. americanas.com at 5.3 s5.3 s
  7. americanas.com at 6.2 s6.2 s
  8. americanas.com at 7.1 s7.1 s

Speed

11 to fix12
  • Render-blocking requests

    2.4 s

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

  • Insider adds 1.3 s

    1.3 s

    Insider costs a phone 1.3 s of main-thread work and 536 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 12

    12/100

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

  • Main-thread work: 8.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Insider, Google Tag Manager and Facebook and others), adding 1.8 MB and 2.9 s of main-thread time.

  • Reduce unused JavaScript

    600 ms · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 1.0 MB

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

  • Improve image delivery

    300 ms · 789 KiB

    35 images could be 789 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.

  • Google Tag Manager adds 868 ms

    868 ms

    Google Tag Manager costs a phone 868 ms of main-thread work and 680 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 480 ms. During a long task the page ignores taps.

  • 2,567 HTML elements

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

  • Legacy JavaScript

    150 ms · 34 KiB

    Polyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    164 KiB

    About 164 KiB of CSS is downloaded but never applied on this page.

  • Phones get a much slower page than desktops

    Desktop scores 50 but mobile only 12. 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.

1 checks passed
  • Server response: 5 ms

    5 ms

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

Core Web Vitals

12 to fix0
  • 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.61

    0.61

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

  • 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 “Imagem especial beleza com até 40% de desconto”.

  • Time to Interactive: 26.7 s

    26.7 s

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

  • Total Blocking Time: 2.0 s

    2.0 s

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

  • Cumulative Layout Shift: 0.52

    0.52

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

  • Speed Index: 8.0 s

    8.0 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Real-user INP: 407 ms

    407 ms

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

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

    +32%

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

  • 14 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

2 checks passed
  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 528 ms

    528 ms

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

Images and page weight

3 to fix40
  • Page weight: 6.8 MB in 378 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 378 requests on a phone: images 3.7 MB (148), scripts 2.0 MB (42) and other files 591 KiB (170). Under 2 MB keeps phones on slow connections fast.

  • 18 images far larger than shown

    1.6 MB

    18 images are downloaded at several times the size a phone draws them, for example 7622210674050_1.jpg at 1,500 px wide, shown at 128 px. Resized copies would save about 1.6 MB.

  • 4 images in older formats

    4 images (757 KiB) 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.

  • 2 images below the first screen load straight away

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

  • About 1.9 g of CO₂ per visit

    1.94 g

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

Accessibility

6 to fixGoogle 8992
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA dialog and alertdialog nodes should have an accessible name (2 elements)

    ARIA dialog and alertdialog nodes should have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • 2 text elements with low contrast

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

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

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

2 checks passed
  • Every image has alt text

    All 53 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

4 to fixGoogle 9289
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 1 link crawlers can't follow

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

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

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

  • 50 internal links, 4 external

    The homepage links to 50 pages on americanas.com and 4 external pages.

6 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Precisando de iPhone, creatina ou daquela barra de chocolate no meio da tarde? Passou na Americanas, colocou na cestinh…”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “Americanas - Tudo que você ama”.

  • Canonical URL set

    The canonical URL is https://www.americanas.com.br/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.americanas.com.br/sitemap.xml.

AI search readiness

1 to fix75
  • Most text only appears after JavaScript runs

    6%

    A phone browser shows 2,215 words, but the HTML your server sends has only 141. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • Opted out of AI training for 3 crawlers

    robots.txt blocks GPTBot, Google-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, which the crawlers above handle.

3 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: 5 of 6 facts

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

  • llms.txt published

    The site publishes https://www.americanas.com.br/llms.txt (11 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 15 pages without an H1

    https://www.americanas.com.br/especial/beleza, https://www.americanas.com.br/nossas-lojas, https://www.americanas.com.br/especial/app, https://www.americanas.com.br/especial/cliente-a/cartao-de-credito, https://www.americanas.com.br/especial/cliente-a and https://www.americanas.com.br/hotsite/mais-vendidos and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages with very little text

    https://www.americanas.com.br/especial/beleza, https://www.americanas.com.br/nossas-lojas, https://www.americanas.com.br/especial/app, https://www.americanas.com.br/especial/cliente-a/cartao-de-credito, https://www.americanas.com.br/especial/cliente-a and https://www.americanas.com.br/hotsite/mais-vendidos and 9 others 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 30 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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

4 to fixGoogle 4679
  • 1 broken image

    1 image failed to load on a phone, for example https://dbpbyh.americanas.com.br/g/uids?pld=kFkdtPv2yfl-AouJIWdG1_qmiGdq21Ups2DVXjgUnwbzTdaE0M-dnXokcdatz2KAk71cGsu2vf1MxOACdlyKs-9bCjShGM3K_BRHZ2cQQ8MgyrCq-ifhavBhzQ7CZReVr2c4iMGSXIbrV7c0hqjCB8OdxL0A.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Attribution Reporting is deprecated and will be removed. See https://goo.gle/ps-status for details.”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 distorted images

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

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix44
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 2,215 words of visible text.

2 checks passed
  • 4 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 23 cookies set on arrival

    23

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

  • 42 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on americanas.com, including 23 speed issues, 4 SEO issues and 6 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
americanas.com website review: scores and fixes