Website review, no card needed

carvalhohosken.com.br logo

carvalhohosken.com.br website review

Visit site (opens in a new tab)Reviewed 1 November 202640 issues · 87 checks

This review found 40 issues worth fixing on carvalhohosken.com.br, 20 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
2.4 s2.0 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.0 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.1 s
Aug 1, 20262.0 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.0 s
Oct 3, 20262.1 s
Oct 10, 20262.2 s
Oct 17, 20262.3 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
232 ms154 msMay 9Oct 24220 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026186 ms
May 16, 2026194 ms
May 23, 2026187 ms
May 30, 2026192 ms
Jun 6, 2026198 ms
Jun 13, 2026198 ms
Jun 20, 2026223 ms
Jun 27, 2026197 ms
Jul 4, 2026184 ms
Jul 11, 2026175 ms
Jul 18, 2026163 ms
Jul 25, 2026188 ms
Aug 1, 2026191 ms
Aug 8, 2026181 ms
Aug 15, 2026175 ms
Aug 22, 2026178 ms
Aug 29, 2026178 ms
Sep 5, 2026178 ms
Sep 12, 2026185 ms
Sep 19, 2026187 ms
Sep 26, 2026191 ms
Oct 3, 2026203 ms
Oct 10, 2026219 ms
Oct 17, 2026211 ms
Oct 24, 2026220 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 carvalhohosken.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. carvalhohosken.com.br at 1.3 s1.3 s
  2. carvalhohosken.com.br at 2.6 s2.6 s
  3. carvalhohosken.com.br at 4.0 s4.0 s
  4. carvalhohosken.com.br at 5.3 s5.3 s
  5. carvalhohosken.com.br at 6.6 s6.6 s
  6. carvalhohosken.com.br at 7.9 s7.9 s
  7. carvalhohosken.com.br at 9.3 s9.3 s
  8. carvalhohosken.com.br at 10.6 s10.6 s

Speed

10 to fix14
  • Use efficient cache lifetimes

    41.4 s · 47.5 MB

    63 files are served with short cache lifetimes, so returning visitors download them again (47.5 MB).

  • Improve image delivery

    56.5 s · 11.3 MB

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

  • Reduce unused JavaScript

    2.1 s · 1.8 MB

    About 1.8 MB 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.

  • Google CDN adds 1.1 s

    1.1 s

    Google CDN costs a phone 1.1 s of main-thread work and 1.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 998 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 14

    14/100

    Your mobile performance score is 14. 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.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, Google CDN and Facebook and others), adding 3.4 MB and 2.9 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • Reduce unused CSS

    150 ms · 27 KiB

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

  • Legacy JavaScript

    150 ms · 23 KiB

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

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

    2 ms

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

Core Web Vitals

10 to fix33
  • 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: 65.8 s

    65.8 s

    Your largest element takes 65.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Carvalho Hosken HÁ 75 ANOS DESENVOLVENDO TODAS AS DIMENSÕES…”.

  • Time to Interactive: 79.5 s

    79.5 s

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

  • Speed Index: 14.8 s

    14.8 s

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

  • Cumulative Layout Shift: 0.947

    0.947

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Real-user INP: 203 ms

    203 ms

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

  • Real-user CLS: 0.15

    0.15

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 21 images without width and height

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

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

    +13%

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

  • Largest content (LCP) got 14% slower for real visitors

    +14%

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

3 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix70
  • Page weight: 76.0 MB in 134 requests

    76.0 MB

    Your homepage downloads 76.0 MB in 134 requests on a phone: media 59.2 MB (13), images 12.4 MB (45) and scripts 3.4 MB (34). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (62 KiB) 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.

  • About 21.5 g of CO₂ per visit

    21.55 g

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

2 checks passed
  • 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

8 to fixGoogle 8890
  • 14 buttons without a name

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

  • 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 (54 elements)

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

  • 12 form fields without a label

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

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

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

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

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

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

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 47 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

4 to fixGoogle 8581
  • No H1 headline

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

  • Structured data has 1 problem

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links crawlers can't follow

    4 links have no real href, so search engines can't follow them.

  • 35 internal links, 11 external

    The homepage links to 35 pages on carvalhohosken.com.br and 11 external pages.

5 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “Imóveis à venda na Barra da Tijuca. Encontre os melhores apartamentos e coberturas nos bairros planejados da Carvalho H…”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Carvalho Hosken S/A: imóveis na Barra da Tijuca - RJ”.

  • Canonical URL set

    The canonical URL is https://www.carvalhohosken.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://carvalhohosken.com.br/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing name, 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.carvalhohosken.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 (523 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://www.carvalhohosken.com.br/blog and https://www.carvalhohosken.com.br/parcerias-e-negocios have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://www.carvalhohosken.com.br/bairros-planejados/peninsula, https://www.carvalhohosken.com.br/bairros-planejados/ilha-pura, https://www.carvalhohosken.com.br/bairros-planejados/rio-2, https://www.carvalhohosken.com.br/bairros-planejados/cidade-jardim, https://www.carvalhohosken.com.br/bairros-planejados/centro-metropolitano and https://www.carvalhohosken.com.br/blog and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.carvalhohosken.com.br/sobre-nos and https://www.carvalhohosken.com.br/politica-de-privacidade took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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 to fixGoogle 8893
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    67 of 83 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 650 words of copy

    The homepage carries about 650 words of visible text.

3 checks passed
  • 3 short forms

    3 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • 4 other companies contacted

    Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 carvalhohosken.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 Analytics | Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on carvalhohosken.com.br, including 20 speed issues, 4 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

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