Website review, no card needed

abrasce.com.br logo

abrasce.com.br website review

Visit site (opens in a new tab)Reviewed 19 October 202656 issues · 94 checks

This review found 56 issues worth fixing on abrasce.com.br, 24 of them high impact, across 94 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
3.3 s2.7 sMay 2Oct 172.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.3 s
May 9, 20263.2 s
May 16, 20263.2 s
May 23, 20263.2 s
May 30, 20263.2 s
Jun 6, 20263.1 s
Jun 13, 20263.1 s
Jun 20, 20262.9 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.7 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
96 ms85 msMay 2Oct 1794 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202693 ms
May 9, 202690 ms
May 16, 202688 ms
May 23, 202687 ms
May 30, 202686 ms
Jun 6, 202687 ms
Jun 13, 202689 ms
Jun 20, 202690 ms
Jun 27, 202692 ms
Jul 4, 202693 ms
Jul 11, 202689 ms
Jul 18, 202689 ms
Jul 25, 202690 ms
Aug 1, 202689 ms
Aug 8, 202694 ms
Aug 15, 202693 ms
Aug 22, 202691 ms
Aug 29, 202691 ms
Sep 5, 202690 ms
Sep 12, 202694 ms
Sep 19, 202695 ms
Sep 26, 202693 ms
Oct 3, 202692 ms
Oct 10, 202691 ms
Oct 17, 202694 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 abrasce.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

15 to fix18
  • Improve image delivery

    5.5 s · 13.0 MB

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

  • Render-blocking requests

    2.9 s

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

  • Reduce unused JavaScript

    1.1 s · 1.4 MB

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

  • Mobile performance score: 18

    18/100

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

  • Main-thread work: 7.1 s

    A phone's processor spends 7.1 s on main-thread work while loading, 4.0 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 (Google Maps, Google CDN and spotifycdn.com and others), adding 3.4 MB and 2.6 s of main-thread time.

  • Google Maps adds 704 ms

    704 ms

    Google Maps costs a phone 704 ms of main-thread work and 945 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.

  • Use efficient cache lifetimes

    150 ms · 635 KiB

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

  • Google CDN adds 543 ms

    543 ms

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

  • spotifycdn.com adds 532 ms

    532 ms

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

    450 ms · 137 KiB

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

  • Google Tag Manager adds 495 ms

    495 ms

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

  • 2,067 HTML elements

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

  • Cloudflare CDN adds 158 ms

    158 ms

    Cloudflare CDN costs a phone 158 ms of main-thread work and 407 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.

  • Legacy JavaScript

    250 ms · 20 KiB

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

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

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

    128 ms

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

Core Web Vitals

11 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: 30.8 s

    30.8 s

    Your largest element takes 30.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “GUIAS Você encontra tudo: Guia de Shopping, Guia de Fornece…”.

  • Speed Index: 19.7 s

    19.7 s

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

  • Time to Interactive: 53.4 s

    53.4 s

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

  • Cumulative Layout Shift: 0.394

    0.394

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

  • Total Blocking Time: 1,000 ms

    1,000 ms

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 941 ms

    941 ms

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

  • 40 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

3 checks passed
  • Real-user INP: 165 ms

    165 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 12% faster for real visitors

    -12%

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

Images and page weight

5 to fix18
  • Page weight: 27.4 MB in 241 requests

    27.4 MB

    Your homepage downloads 27.4 MB in 241 requests on a phone: images 23.2 MB (86), scripts 3.4 MB (89) and other files 377 KiB (28). Under 2 MB keeps phones on slow connections fast.

  • 11 images over 500 KB

    11 images weigh 10.8 MB together. On a phone connection a single image that size takes seconds.

  • 17 images far larger than shown

    5.8 MB

    17 images are downloaded at several times the size a phone draws them, for example unnamed-10-1.jpg at 1,024 px wide, shown at 119 px. Resized copies would save about 5.8 MB.

  • 40 images in older formats

    40 images (18.5 MB) 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.

  • 20 images below the first screen load straight away

    20 images further down the page (7.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 7.8 g of CO₂ per visit

    7.76 g

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

Accessibility

14 to fixGoogle 7383
  • 5 buttons without a name

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

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

  • 17 tap targets too small

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

  • Hidden but focusable

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

  • Frames without titles

    3 frames have no title, so screen-reader users cannot tell what they contain.

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

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • 23 links without text

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

  • 18 form fields without a label

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

  • ARIA role should be appropriate for the element (4 elements)

    ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (4 elements)

    Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 75 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 10092
  • 3 H1 headlines

    There are 3 <h1> headlines (“PROCURA?”, “LOGIN” and “CADASTRO”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, 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.

  • 152 internal links, 45 external

    The homepage links to 152 pages on abrasce.com.br and 45 external pages.

6 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Associação Brasileira de Shopping Centers (Abrasce) atua para o fortalecimento e desenvolvimento do setor e na defesa d…”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Abrasce - Associação Brasileira de Shopping Centers”.

  • Canonical URL set

    The canonical URL is https://abrasce.com.br/.

  • Structured data in place

    Structured data found: BreadcrumbList, CollectionPage, 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://abrasce.com.br/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://abrasce.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 (2,342 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 60 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 8891
  • 14 small tap targets

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

  • 1 distorted image

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

  • 2 low-resolution images

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

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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.

  • Local business without LocalBusiness data

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 11-field form

    Your longest form asks for 11 fields (8 required). Every extra field lowers completion.

  • No opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 846 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 10 cookies set on arrival

    10

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

  • 17 other companies contacted

    Loading the homepage contacts 17 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 abrasce.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

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
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 56 issues on abrasce.com.br, including 26 speed issues, 2 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