Website review, no card needed

eletronicasantana.com.br logo

eletronicasantana.com.br website review

Visit site (opens in a new tab)Reviewed 3 November 202656 issues · 97 checks

This review found 56 issues worth fixing on eletronicasantana.com.br, 26 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.8 s2.5 sMay 16Oct 313.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.2 s
May 23, 20263.3 s
May 30, 20263.2 s
Jun 6, 20263.1 s
Jun 13, 20262.9 s
Jun 20, 20262.7 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.9 s
Aug 1, 20263.2 s
Aug 8, 20263.3 s
Aug 15, 20263.5 s
Aug 22, 20263.6 s
Aug 29, 20263.7 s
Sep 5, 20263.7 s
Sep 12, 20263.5 s
Sep 19, 20263.3 s
Sep 26, 20263.1 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20263.1 s
Oct 24, 20263.0 s
Oct 31, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
216 ms146 msMay 16Oct 31205 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026154 ms
May 23, 2026156 ms
May 30, 2026157 ms
Jun 6, 2026157 ms
Jun 13, 2026155 ms
Jun 20, 2026154 ms
Jun 27, 2026155 ms
Jul 4, 2026157 ms
Jul 11, 2026156 ms
Jul 18, 2026165 ms
Jul 25, 2026171 ms
Aug 1, 2026179 ms
Aug 8, 2026184 ms
Aug 15, 2026194 ms
Aug 22, 2026201 ms
Aug 29, 2026205 ms
Sep 5, 2026208 ms
Sep 12, 2026195 ms
Sep 19, 2026183 ms
Sep 26, 2026171 ms
Oct 3, 2026166 ms
Oct 10, 2026170 ms
Oct 17, 2026180 ms
Oct 24, 2026190 ms
Oct 31, 2026205 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 eletronicasantana.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eletronicasantana.com.br at 1.1 s1.1 s
  2. eletronicasantana.com.br at 2.1 s2.1 s
  3. eletronicasantana.com.br at 3.2 s3.2 s
  4. eletronicasantana.com.br at 4.3 s4.3 s
  5. eletronicasantana.com.br at 5.3 s5.3 s
  6. eletronicasantana.com.br at 6.4 s6.4 s
  7. eletronicasantana.com.br at 7.5 s7.5 s
  8. eletronicasantana.com.br at 8.5 s8.5 s

Speed

12 to fix32
  • Render-blocking requests

    3.5 s

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

  • Use efficient cache lifetimes

    1.6 s · 855 KiB

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

  • Reduce unused JavaScript

    1.2 s · 476 KiB

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

  • vtex.com.br adds 1.1 s

    1.1 s

    vtex.com.br costs a phone 1.1 s of main-thread work and 68 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: 32

    32/100

    Your mobile performance score is 32. 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.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 4,356 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (vtex.com.br, Google Tag Manager and konfidency.com.br and others), adding 1.4 MB and 2.9 s of main-thread time.

  • Google Tag Manager adds 681 ms

    681 ms

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

  • konfidency.com.br adds 404 ms

    404 ms

    konfidency.com.br costs a phone 404 ms of main-thread work and 228 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.

  • Improve image delivery

    422 KiB

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 36 KiB

    Polyfills for old browsers add 36 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

    160 ms · 17 KiB

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

  • Minify CSS

    150 ms · 5 KiB

    5 KiB could be saved by minifying CSS.

  • Minify JavaScript

    11 KiB

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

  • 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: 11 ms

    11 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 12.5 s

    12.5 s

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

  • Time to Interactive: 21.1 s

    21.1 s

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

  • Speed Index: 11.0 s

    11.0 s

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

  • Total Blocking Time: 1.8 s

    1.8 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Real-user INP: 261 ms

    261 ms

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

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

    +27%

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

  • Real-user FCP: 2.1 s

    2.1 s

    Real visitors see the first content after 2.1 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.

  • 11 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

2 checks passed
  • Real-user CLS: 0.05

    0.05

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

2 to fix81
  • Page weight: 3.3 MB in 381 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 381 requests on a phone: scripts 1.7 MB (94), images 1,019 KiB (76) and fonts 210 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    mobile 1.png 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).

  • 1 image in older formats

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

    0.92 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 110.8 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

15 to fixGoogle 6681
  • 3 buttons without a name

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

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

  • Interactive controls must not be nested (5 elements)

    Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.

  • ARIA input fields must have an accessible name (3 elements)

    ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

  • [aria-*] attributes do not have valid values

    [aria-*] attributes do not have valid values (4 elements).

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 4 form fields without a label

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

  • 4 links without text

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

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 10084
  • Title is long (136 characters)

    Your title is 136 characters, so Google will cut it off around 60: “Eletrônica Santana - Informática, Eletrônicos, Telefonia, Headsets, Áudio e Vídeo Conferê…”.

  • No structured data

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

  • Meta description is long (250 characters)

    Your meta description is 250 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 303 internal links, 10 external

    The homepage links to 303 pages on eletronicasantana.com.br and 10 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Eletrônica Santana – Loja de Eletrônicos e Itens para Casa”.

  • Canonical URL set

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

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.eletronicasantana.com.br/sitemap.xml.

AI search readiness

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

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,281 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix76
  • 1 page points its canonical at the homepage

    https://www.eletronicasantana.com.br/busca declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.eletronicasantana.com.br/busca all use the title “Eletrônica Santana - Informática, Eletrônicos, Telefonia, Headsets, Á…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages share a meta description

    https://www.eletronicasantana.com.br/entrega-flash, https://www.eletronicasantana.com.br/busca, https://www.eletronicasantana.com.br/desconto-30, https://www.eletronicasantana.com.br/desconto-25, https://www.eletronicasantana.com.br/desconto-20 and https://www.eletronicasantana.com.br/desconto-15 and 4 others use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.eletronicasantana.com.br/entrega-flash, https://www.eletronicasantana.com.br/busca, https://www.eletronicasantana.com.br/desconto-30, https://www.eletronicasantana.com.br/desconto-25, https://www.eletronicasantana.com.br/desconto-20 and https://www.eletronicasantana.com.br/desconto-15 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://www.eletronicasantana.com.br/busca, https://www.eletronicasantana.com.br/desconto-30, https://www.eletronicasantana.com.br/desconto-25, https://www.eletronicasantana.com.br/desconto-20, https://www.eletronicasantana.com.br/destaque-de-vendas and https://www.eletronicasantana.com.br/escritorio-e-home-office/apresentacao/microfones took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 8885
  • 24 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Event name is not defined”.

  • 4 distorted images

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

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 677 words of visible text.

3 checks passed
  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 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, Meta Pixel and Microsoft Clarity 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.

  • 34 cookies set on arrival

    34

    Opening the homepage sets 34 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 eletronicasantana.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
jQuery
Analytics
Google Tag Manager | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 56 issues on eletronicasantana.com.br, including 24 speed issues, 3 SEO issues and 3 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