Website review, no card needed
abcdaconstrucao.com.br website review
Visit site (opens in a new tab)Reviewed 2 November 202645 issues · 85 checks
This review found 45 issues worth fixing on abcdaconstrucao.com.br, 18 of them high impact, across 85 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 266 ms |
| May 23, 2026 | 258 ms |
| May 30, 2026 | 255 ms |
| Jun 6, 2026 | 255 ms |
| Jun 13, 2026 | 258 ms |
| Jun 20, 2026 | 264 ms |
| Jun 27, 2026 | 267 ms |
| Jul 4, 2026 | 270 ms |
| Jul 11, 2026 | 276 ms |
| Jul 18, 2026 | 278 ms |
| Jul 25, 2026 | 282 ms |
| Aug 1, 2026 | 281 ms |
| Aug 8, 2026 | 284 ms |
| Aug 15, 2026 | 290 ms |
| Aug 22, 2026 | 295 ms |
| Aug 29, 2026 | 298 ms |
| Sep 5, 2026 | 299 ms |
| Sep 12, 2026 | 296 ms |
| Sep 19, 2026 | 297 ms |
| Sep 26, 2026 | 299 ms |
| Oct 3, 2026 | 300 ms |
| Oct 10, 2026 | 298 ms |
| Oct 17, 2026 | 296 ms |
| Oct 24, 2026 | 300 ms |
| Oct 31, 2026 | 302 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
How it loaded on a phone
0.9 s
1.7 s
2.6 s
3.4 s
4.3 s
5.1 s
6.0 s
6.8 s
Speed
Improve image delivery
10.2 s · 4.2 MB30 images could be 4.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.2 s faster on a phone.
Reduce unused JavaScript
2.1 s · 479 KiBAbout 479 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Mobile performance score: 28
28/100Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
9,745 HTML elements
The page has 9,745 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 7.5 s
A phone's processor spends 7.5 s on main-thread work while loading, 4.2 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 Tag Manager, fbitsstatic.net and Facebook and others), adding 8.8 MB and 2.0 s of main-thread time.
fbitsstatic.net adds 429 ms
429 msfbitsstatic.net costs a phone 429 ms of main-thread work and 7.3 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.
Use efficient cache lifetimes
600 ms · 490 KiB9 files are served with short cache lifetimes, so returning visitors download them again (490 KiB).
Google Tag Manager adds 979 ms
979 msGoogle Tag Manager costs a phone 979 ms of main-thread work and 714 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.
Render-blocking requests
750 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused CSS
460 ms · 79 KiBAbout 79 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.
Legacy JavaScript
300 ms · 58 KiBPolyfills for old browsers add 58 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 356 ms. During a long task the page ignores taps.
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: 101 ms
101 msYour server sent the HTML in 101 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 28.1 s
28.1 sYour largest element takes 28.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Fabricante Deca”.
Time to Interactive: 31.4 s
31.4 sThe page becomes fully interactive after 31.4 s. Good is under 3.8 s.
Speed Index: 12.3 s
12.3 sVisually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Real-user INP: 476 ms
476 msReal visitors wait 476 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Cumulative Layout Shift: 0.182
0.182The layout shifts by 0.182 while loading, so content jumps under the reader's thumb. Good is under 0.1.
29 images without width and height
29 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 266 ms to 302 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 679 ms
679 msReal visitors wait 679 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 9.1 MB in 212 requests
9.1 MBYour homepage downloads 9.1 MB in 212 requests on a phone: images 6.9 MB (147), scripts 1.6 MB (25) and HTML 185 KiB (1). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 3.0 MB together. On a phone connection a single image that size takes seconds.
13 images in older formats
13 images (4.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.
An image on the first screen is lazy-loaded
0881796f-1492-48e1-9ce6-43b3db339fc8.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 far larger than shown
266 KiB1 image is downloaded at several times the size a phone draws it, for example chance-unica-home.png at 627 px wide, shown at 31 px. Resized copies would save about 266 KiB.
4 images below the first screen load straight away
4 images further down the page (374 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.6 g of CO₂ per visit
2.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.58 g of CO₂e: 309.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
26 text elements with low contrast
26 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.
12 form fields without a label
12 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (8 elements)
Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 100 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
2,380 internal links, 13 external
The homepage links to 2,380 pages on abcdaconstrucao.com.br and 13 external pages.
5 checks passed
Meta description: 88 characters
Your meta description is 88 characters: “Encontre acabamentos com os melhores preços na ABC da Construção. Acesse e compre agora!”.
Title: 55 characters
Your title is a healthy 55 characters: “ABC da Construção - A Maior Especialista em Acabamentos”.
Canonical URL set
The canonical URL is https://www.abcdaconstrucao.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.abcdaconstrucao.com.br/sitemap.xml.
AI search readiness
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.abcdaconstrucao.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 (6,429 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.abcdaconstrucao.com.br/abc-outlet is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.abcdaconstrucao.com.br/abc-outlet has no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.abcdaconstrucao.com.br/cupom-abc-da-construcao, https://www.abcdaconstrucao.com.br/abc-outlet, https://www.abcdaconstrucao.com.br/semana-do-cliente, https://www.abcdaconstrucao.com.br/saldao-abc, https://www.abcdaconstrucao.com.br/black-friday and https://www.abcdaconstrucao.com.br/diretorio-de-lojas and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
11 pages slow to respond
https://www.abcdaconstrucao.com.br/semana-do-cliente, https://www.abcdaconstrucao.com.br/saldao-abc, https://www.abcdaconstrucao.com.br/black-friday, https://www.abcdaconstrucao.com.br/diretorio-de-lojas, https://www.abcdaconstrucao.com.br/materiais-hidraulicos and https://www.abcdaconstrucao.com.br/materiais-hidraulicos/acessorios and 5 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 199 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “The source list for the Content Security Policy directive 'default-src' contains an invalid source: '*.*hotjar.com'. It…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
159 of 168 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 1,361 words of copy
The homepage carries about 1,361 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 trackers load before any consent
6Before 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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
21 other companies contacted
Loading the homepage contacts 21 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 abcdaconstrucao.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 45 issues on abcdaconstrucao.com.br, including 22 speed issues, 2 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.