Website review, no card needed
abiatar.com website review
Visit site (opens in a new tab)Reviewed 23 October 202637 issues · 83 checks
This review found 37 issues worth fixing on abiatar.com, 11 of them high impact, across 83 checks. The most urgent: fails Core Web Vitals for real visitors. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.7 s |
| May 9, 2026 | 1.7 s |
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 197 ms |
| May 9, 2026 | 186 ms |
| May 16, 2026 | 189 ms |
| May 23, 2026 | 192 ms |
| May 30, 2026 | 186 ms |
| Jun 6, 2026 | 188 ms |
| Jun 13, 2026 | 186 ms |
| Jun 20, 2026 | 177 ms |
| Jun 27, 2026 | 177 ms |
| Jul 4, 2026 | 177 ms |
| Jul 11, 2026 | 175 ms |
| Jul 18, 2026 | 179 ms |
| Jul 25, 2026 | 185 ms |
| Aug 1, 2026 | 187 ms |
| Aug 8, 2026 | 191 ms |
| Aug 15, 2026 | 185 ms |
| Aug 22, 2026 | 180 ms |
| Aug 29, 2026 | 183 ms |
| Sep 5, 2026 | 184 ms |
| Sep 12, 2026 | 183 ms |
| Sep 19, 2026 | 183 ms |
| Sep 26, 2026 | 180 ms |
| Oct 3, 2026 | 175 ms |
| Oct 10, 2026 | 178 ms |
| Oct 17, 2026 | 179 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
Speed
Mobile performance score: 79
79/100Your mobile performance score is 79 (desktop: 98). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 75 KiBAbout 75 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
450 ms · 53 KiBAbout 53 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.
Render-blocking requests
500 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 500 ms.
2,222 HTML elements
The page has 2,222 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
114 KiB4 images could be 114 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1 third-party service on the page
1 third-party service load with your homepage (Google Tag Manager), adding 114 KiB and 62 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 69 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.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 50 ms of it running JavaScript. That is comfortably low.
Server response: 402 ms
402 msYour server sent the HTML in 402 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: 5.1 s
5.1 sYour largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Seu Imóvel Aqui! Pronto para conhecer o seu futuro lar? Pal…”.
Largest content (LCP) got 39% slower for real visitors
+39%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.7 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 817 ms
817 msReal visitors wait 817 ms for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 5.1 s
5.1 sThe page becomes fully interactive after 5.1 s. Good is under 3.8 s.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 197 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 155 ms
155 msReal visitors wait 155 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Total Blocking Time: 19 ms
19 msScripts block the page for only 19 ms while loading. Good is under 200 ms.
Images and page weight
About 0.3 g of CO₂ per visit
0.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.33 g of CO₂e: 39.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.2 MB in 41 requests
1.2 MBYour homepage downloads 1.2 MB in 41 requests on a phone: images 878 KiB (36), scripts 114 KiB (1) and HTML 109 KiB (1). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
31 text elements with low contrast
31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (4 elements)
Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (124 elements)
All page content should be contained by landmarks: 124 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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
45 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: 45 passed and 8 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.
36 internal links, 24 external
The homepage links to 36 pages on abiatar.com and 24 external pages.
7 checks passed
Meta description: 100 characters
Your meta description is 100 characters: “Há mais de 15 anos entregando empreendimentos com a qualidade e o conforto que a sua família merece!”.
Title: 37 characters
Your title is a healthy 37 characters: “Abiatar | Construtora e Incorporadora”.
Canonical URL set
The canonical URL is https://abiatar.com/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and WebPage.
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://abiatar.com/sitemap_index.xml.
AI search readiness
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://abiatar.com/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 (1,088 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://abiatar.com/blog, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page points its canonical at the homepage
https://abiatar.com/inicio 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.
5 pages share 2 titles
/ and https://abiatar.com/inicio all use the title “Abiatar | Construtora e Incorporadora”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://abiatar.com/empreendimentos/vista-parque-guaiba-residencial, https://abiatar.com/empreendimentos/moove-campo-limpo, https://abiatar.com/empreendimentos/abiatar-conecta, https://abiatar.com/empreendimentos/vista-plaza-residencial, https://abiatar.com/empreendimentos/innovare-portal-do-morumbi and https://abiatar.com/empreendimentos/abiatar-residence-tower have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://abiatar.com/lorem-ipsum-dolor-sit-amet-consectetur-adipiscing-elit-7, https://abiatar.com/lorem-ipsum-dolor-sit-amet-consectetur-adipiscing-elit-6 and https://abiatar.com/lorem-ipsum-dolor-sit-amet-consectetur-adipiscing-elit-5 use the same meta description. A description written for each page earns more clicks.
14 pages without an H1
https://abiatar.com/inicio, https://abiatar.com/empreendimentos, https://abiatar.com/sobre-nos, https://abiatar.com/area-do-cliente, https://abiatar.com/area-do-corretor and https://abiatar.com/empreendimentos/vista-parque-guaiba-residencial and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages slow to respond
https://abiatar.com/empreendimentos, https://abiatar.com/area-do-cliente, https://abiatar.com/area-do-corretor, https://abiatar.com/empreendimentos/vista-parque-guaiba-residencial, https://abiatar.com/empreendimentos/abiatar-conecta and https://abiatar.com/empreendimentos/vista-plaza-residencial and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
2 checks passed
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
2 small tap targets
2 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://api.reclameaqui.com.br/embed-raverified/hash/MTA0MjExOmFiaWF0YXItaW1vdmVpcw==' fro…”.
1 checks passed
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.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 922 words of copy
The homepage carries about 922 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Hotjar and TikTok Pixel.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and TikTok Pixel (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
19 other companies contacted
Loading the homepage contacts 19 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 abiatar.com, 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
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on abiatar.com, including 12 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.