constance.com.br website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user CLS: 0.71

  0.71

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

• Real-user LCP: 3.2 s

  3.2 s

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

• Real-user INP: 270 ms

  270 ms

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

• Real-user FCP: 2.2 s

  2.2 s

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

• Real-user TTFB: 1.5 s

  1.5 s

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

• Tap response (INP) held steady for real visitors

  0%

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

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

  +12%

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

• Page weight: 5.3 MB

  5.3 MB

  Your homepage downloads 5.3 MB on a phone, 1.8 MB of it images (34%). Under 2 MB keeps phones on slow connections fast.

• About 1.5 g of CO₂ per visit

  1.51 g

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

• 2 buttons without a name

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

  Elements (2)

• 21 tap targets too small

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

  Elements (3)

• 10 text elements with low contrast

  10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (3)

• Hidden but focusable

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

  Elements (2)

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

  All page content should be contained by landmarks: 28 elements on the page fail this check, rated moderate by axe-core.

  Elements (3)

• Heading levels should only increase by one (1 element)

  Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• No main landmark

  The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  Elements (1)

• 8 links without text

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

  Elements (3)

• 4 form fields without a label

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

• No page title

  Your page has no <title>, so Google has to invent the blue link in search results.

• No meta description

  No meta description, so Google writes its own snippet from whatever text it finds.

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

• No canonical URL

  No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

• Only 0 internal links

  The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

• No favicon declared

  No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

• No X (Twitter) card tag

  No twitter:card tag. X falls back to Open Graph, which is incomplete here.

• Most text only appears after JavaScript runs

  0%

  A phone browser shows 255 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

• Opted out of AI training for 5 crawlers

  robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

• 1 broken image

  1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97027203&tm=gtm002&Ver=2&mid=3d9162e9-5ffc-4c17-b780-e601d8c672b4&bo=1&sid=55cd6190d3be11f1a7630d66d62ee253&vid=55cdb4c0d3be11f182d5eb956bf3dede&vids=1&msclkid=N&pi=91.

• 85 small tap targets

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

• 6 JavaScript errors while loading

  6 errors were logged to the browser console while the page loaded, for example “account_id is not defined”.

• No HSTS header

  No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

• No Content-Security-Policy

  No Content-Security-Policy header, the main browser-side defence against injected scripts.

• No X-Content-Type-Options

  X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• No CAA record

  constance.com.br has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• DNSSEC is off

  constance.com.br's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• 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 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 form on the homepage

  There is no form on the homepage, so every lead has to click through to another page first.

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

  The homepage carries about 255 words of visible text.

• Email authentication score: 85/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 8 trackers load before any consent

  8

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

• 36 cookies set on arrival

  36

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

• 44 other companies contacted

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