Website review, no card needed

andra.com.br logo

andra.com.br website review

Visit site (opens in a new tab)Reviewed 18 November 202658 issues · 92 checks

This review found 58 issues worth fixing on andra.com.br, 25 of them high impact, across 92 checks. The most urgent: improve image delivery. 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.3 sMay 30Nov 143.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.0 s
Jun 6, 20264.0 s
Jun 13, 20263.9 s
Jun 20, 20263.8 s
Jun 27, 20263.8 s
Jul 4, 20263.8 s
Jul 11, 20263.7 s
Jul 18, 20263.8 s
Jul 25, 20263.8 s
Aug 1, 20263.8 s
Aug 8, 20263.7 s
Aug 15, 20263.6 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.6 s
Sep 19, 20263.6 s
Sep 26, 20263.6 s
Oct 3, 20263.7 s
Oct 10, 20263.9 s
Oct 17, 20263.9 s
Oct 24, 20263.9 s
Oct 31, 20263.7 s
Nov 7, 20263.5 s
Nov 14, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
452 ms200 msMay 30Nov 14364 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026241 ms
Jun 6, 2026237 ms
Jun 13, 2026236 ms
Jun 20, 2026236 ms
Jun 27, 2026231 ms
Jul 4, 2026230 ms
Jul 11, 2026233 ms
Jul 18, 2026229 ms
Jul 25, 2026233 ms
Aug 1, 2026231 ms
Aug 8, 2026231 ms
Aug 15, 2026233 ms
Aug 22, 2026240 ms
Aug 29, 2026246 ms
Sep 5, 2026254 ms
Sep 12, 2026276 ms
Sep 19, 2026295 ms
Sep 26, 2026332 ms
Oct 3, 2026369 ms
Oct 10, 2026395 ms
Oct 17, 2026418 ms
Oct 24, 2026423 ms
Oct 31, 2026410 ms
Nov 7, 2026385 ms
Nov 14, 2026364 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 andra.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. andra.com.br at 0.9 s0.9 s
  2. andra.com.br at 1.8 s1.8 s
  3. andra.com.br at 2.7 s2.7 s
  4. andra.com.br at 3.6 s3.6 s
  5. andra.com.br at 4.6 s4.6 s
  6. andra.com.br at 5.5 s5.5 s
  7. andra.com.br at 6.4 s6.4 s
  8. andra.com.br at 7.3 s7.3 s

Speed

12 to fix44
  • Improve image delivery

    3.3 s · 1.3 MB

    18 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.

  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 44

    44/100

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

  • Main-thread work: 4.1 s

    A phone's processor spends 4.1 s on main-thread work while loading, 2.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 (vtexassets.com, Google Tag Manager and Google CDN and others), adding 5.5 MB and 1.8 s of main-thread time.

  • vtexassets.com adds 698 ms

    698 ms

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

    735 KiB

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

  • Use efficient cache lifetimes

    434 KiB

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

  • Google Tag Manager adds 372 ms

    372 ms

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

  • Google CDN adds 245 ms

    245 ms

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

  • 15 long tasks on the main thread

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

  • 1,912 HTML elements

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    43 KiB

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

  • Minify JavaScript

    18 KiB

    18 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    11 KiB

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

1 checks passed
  • Server response: 57 ms

    57 ms

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

Core Web Vitals

13 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.27

    0.27

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

  • Largest Contentful Paint: 11.3 s

    11.3 s

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

  • Time to Interactive: 24.4 s

    24.4 s

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

  • Speed Index: 8.6 s

    8.6 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Total Blocking Time: 677 ms

    677 ms

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user INP: 374 ms

    374 ms

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

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

    +57%

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 28 images without width and height

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

2 checks passed
  • Largest content (LCP) got 14% faster for real visitors

    -14%

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

  • Cumulative Layout Shift: 0.024

    0.024

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

Images and page weight

4 to fix28
  • Page weight: 5.7 MB in 232 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 232 requests on a phone: scripts 2.4 MB (62), images 2.3 MB (49) and other files 438 KiB (77). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    d2102711-ae31-4960-b8c2-e2d27e37d34b___7f80be5b6449ba93f594f weighs 555 KiB. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    1.0 MB

    6 images are downloaded at several times the size a phone draws them, for example d2102711-ae31-4960-b8c2-e2d27e37d34b___7f80be5b6449ba93f594f at 2,752 px wide, shown at 390 px. Resized copies would save about 1.0 MB.

  • 10 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (31 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.61 g

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

Accessibility

12 to fixGoogle 7583
  • 9 buttons without a name

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

  • 48 tap targets too small

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

  • 7 text elements with low contrast

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

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

  • Hidden but focusable

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

  • 5 images without alt text

    5 images have 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.

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 20 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (13 elements).

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

5 to fixGoogle 8566
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (25 characters)

    Your title is only 25 characters: “Andra Materiais Elétricos”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image (also missing: 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.

  • 65 internal links, 16 external

    The homepage links to 65 pages on andra.com.br and 16 external pages.

3 checks passed
  • Canonical URL set

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

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

  • No llms.txt

    There is no https://www.andra.com.br/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.

2 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 (559 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix55
  • 1 page without a title

    https://www.andra.com.br/tomadas has no <title>, so Google invents the link text in results.

  • 2 linked pages hidden from search

    https://www.andra.com.br/disjuntor and https://www.andra.com.br/orion are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages share a title

    /, https://www.andra.com.br/nossas-lojas, https://www.andra.com.br/conheca-ayla and https://www.andra.com.br/servicos all use the title “Andra Materiais Elétricos”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://www.andra.com.br/nossas-lojas, https://www.andra.com.br/disjuntor, https://www.andra.com.br/tomadas, https://www.andra.com.br/conheca-ayla, https://www.andra.com.br/servicos and https://www.andra.com.br/linha-smarteck and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.andra.com.br/Infraestrutura/Quadros-e-Caixas-Eletricas, whose canonical is https://www.andra.com.br/infraestrutura/quadros-e-caixas-eletricas. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.andra.com.br/tomadas and https://www.andra.com.br/conheca-ayla have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://www.andra.com.br/iluminacao/iluminacao-decorativa/lustres-e-pendentes, https://www.andra.com.br/tomadas, https://www.andra.com.br/fios-e-cabos, https://www.andra.com.br/servicos, https://www.andra.com.br/linha-smarteck and https://www.andra.com.br/fortlev and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 9687
  • 17 small tap targets

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

  • 2 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • 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 378 words of copy

    The homepage carries about 378 words of visible text.

4 checks passed
  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: 20 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

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 LinkedIn Insight 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.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 1 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.

  • 41 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 58 issues on andra.com.br, including 25 speed issues, 5 SEO issues 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