Website review, no card needed
caprem.com.br website review
Visit site (opens in a new tab)Reviewed 27 October 202637 issues · 78 checks
This review found 37 issues worth fixing on caprem.com.br, 11 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.4 s |
| May 16, 2026 | 5.2 s |
| May 23, 2026 | 5.4 s |
| May 30, 2026 | 5.6 s |
| Jun 6, 2026 | 5.8 s |
| Jun 13, 2026 | 5.8 s |
| Jun 20, 2026 | 5.8 s |
| Jun 27, 2026 | 5.7 s |
| Jul 4, 2026 | 5.8 s |
| Jul 11, 2026 | 5.7 s |
| Jul 18, 2026 | 5.6 s |
| Jul 25, 2026 | 5.6 s |
| Aug 1, 2026 | 5.5 s |
| Aug 8, 2026 | 5.4 s |
| Aug 15, 2026 | 5.4 s |
| Aug 22, 2026 | 5.2 s |
| Aug 29, 2026 | 5.1 s |
| Sep 5, 2026 | 5.0 s |
| Sep 12, 2026 | 4.6 s |
| Sep 19, 2026 | 4.3 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 3.8 s |
| Oct 10, 2026 | 3.8 s |
| Oct 17, 2026 | 3.8 s |
| Oct 24, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 160 ms |
| May 16, 2026 | 160 ms |
| May 23, 2026 | 159 ms |
| May 30, 2026 | 158 ms |
| Jun 6, 2026 | 149 ms |
| Jun 13, 2026 | 156 ms |
| Jun 20, 2026 | 161 ms |
| Jun 27, 2026 | 156 ms |
| Jul 4, 2026 | 158 ms |
| Jul 11, 2026 | 149 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 153 ms |
| Aug 1, 2026 | 154 ms |
| Aug 8, 2026 | 165 ms |
| Aug 15, 2026 | 173 ms |
| Aug 22, 2026 | 177 ms |
| Aug 29, 2026 | 177 ms |
| Sep 5, 2026 | 175 ms |
| Sep 12, 2026 | 176 ms |
| Sep 19, 2026 | 173 ms |
| Sep 26, 2026 | 195 ms |
| Oct 3, 2026 | 204 ms |
| Oct 10, 2026 | 204 ms |
| Oct 17, 2026 | 204 ms |
| Oct 24, 2026 | 195 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.7 s
1.4 s
2.1 s
2.8 s
3.4 s
4.1 s
4.8 s
5.5 s
Speed
Render-blocking requests
2.6 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Improve image delivery
200 ms · 1.1 MB20 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 952 KiB and 908 ms of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53 (desktop: 66). Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 514 ms
514 msGoogle Tag Manager costs a phone 514 ms of main-thread work and 511 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 · 38 KiBAbout 38 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.
Reduce unused JavaScript
407 KiBAbout 407 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
267 KiB8 files are served with short cache lifetimes, so returning visitors download them again (267 KiB).
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 250 ms. During a long task the page ignores taps.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 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.
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: 3 ms
3 msYour server sent the HTML in 3 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.
Real-user FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 9.0 s
9.0 sYour largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner mobile”.
Time to Interactive: 19.8 s
19.8 sThe page becomes fully interactive after 19.8 s. Good is under 3.8 s.
Speed Index: 8.4 s
8.4 sVisually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 160 ms to 195 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
81 images without width and height
81 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 384 ms
384 msScripts block taps and scrolling for 384 ms in total while the page loads. Good is under 200 ms.
3 checks passed
Real-user INP: 161 ms
161 msReal visitors wait 161 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 30% faster for real visitors
-30%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.4 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 4.0 MB in 131 requests
4.0 MBYour homepage downloads 4.0 MB in 131 requests on a phone: images 2.8 MB (71), scripts 1.1 MB (32) and stylesheets 58 KiB (9). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (37 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.13 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.13 g of CO₂e: 135.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
52 text elements with low contrast
52 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have 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. (2 elements).
2 checks passed
Every image has alt text
All 93 images in the HTML carry an alt attribute.
50 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: 50 passed and 3 failed. 5 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.
Structured data has 2 problems
Structured data found (Organization and WebPage) but with 2 problems, for example “Organization: sameAs is an empty list”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
45 internal links, 20 external
The homepage links to 45 pages on caprem.com.br and 20 external pages.
5 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Compre imóveis com a CAPREM, construtora que desde 2003 fez milhares de clientes felizes e possui ótimas condições de p…”.
Title: 57 characters
Your title is a healthy 57 characters: “Home - CAPREM Construtora - Realizar sonhos é nossa meta!”.
Canonical URL set
The canonical URL is https://www.caprem.com.br/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.caprem.com.br/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, 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://www.caprem.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 (751 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without an H1
https://www.caprem.com.br/sobre-nos has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
43 of 53 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: 8 trust badges. 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 821 words of copy
The homepage carries about 821 words of visible text.
3 checks passed
5 short forms
5 short forms (4 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel 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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
25 other companies contacted
Loading the homepage contacts 25 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 caprem.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on caprem.com.br, including 22 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.