Website review, no card needed

centraldascertidoes.com.br logo

centraldascertidoes.com.br website review

Visit site (opens in a new tab)Reviewed 23 October 202631 issues · 81 checks

This review found 31 issues worth fixing on centraldascertidoes.com.br, 11 of them high impact, across 81 checks. The most urgent: improve image delivery. 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
1.4 s1.2 sMay 2Oct 171.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.3 s
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
304 ms244 msMay 2Oct 17294 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026262 ms
May 9, 2026263 ms
May 16, 2026263 ms
May 23, 2026261 ms
May 30, 2026261 ms
Jun 6, 2026260 ms
Jun 13, 2026260 ms
Jun 20, 2026261 ms
Jun 27, 2026261 ms
Jul 4, 2026260 ms
Jul 11, 2026259 ms
Jul 18, 2026256 ms
Jul 25, 2026252 ms
Aug 1, 2026251 ms
Aug 8, 2026252 ms
Aug 15, 2026255 ms
Aug 22, 2026261 ms
Aug 29, 2026264 ms
Sep 5, 2026270 ms
Sep 12, 2026284 ms
Sep 19, 2026291 ms
Sep 26, 2026295 ms
Oct 3, 2026297 ms
Oct 10, 2026295 ms
Oct 17, 2026294 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 centraldascertidoes.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. centraldascertidoes.com.br at 0.4 s0.4 s
  2. centraldascertidoes.com.br at 0.8 s0.8 s
  3. centraldascertidoes.com.br at 1.1 s1.1 s
  4. centraldascertidoes.com.br at 1.5 s1.5 s
  5. centraldascertidoes.com.br at 1.9 s1.9 s
  6. centraldascertidoes.com.br at 2.3 s2.3 s
  7. centraldascertidoes.com.br at 2.6 s2.6 s
  8. centraldascertidoes.com.br at 3.0 s3.0 s

Speed

6 to fix70
  • Improve image delivery

    2.2 s · 549 KiB

    3 images could be 549 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.2 s faster on a phone.

  • Mobile performance score: 70

    70/100

    Your mobile performance score is 70 (desktop: 96). Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    300 ms · 261 KiB

    5 files are served with short cache lifetimes, so returning visitors download them again (261 KiB).

  • Reduce unused JavaScript

    300 ms · 117 KiB

    About 117 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Render-blocking requests

    350 ms

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.

  • Reduce unused CSS

    300 ms · 18 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Facebook, RD Station and JSDelivr CDN and others), adding 327 KiB and 243 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

    Desktop scores 96 but mobile only 70. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 383 ms of it running JavaScript. That is comfortably low.

  • Server response: 201 ms

    201 ms

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

Core Web Vitals

7 to fix67
  • 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: 7.8 s

    7.8 s

    Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Peça seu documento de onde estiver. Solicite certidões em c…”.

  • Time to Interactive: 7.9 s

    7.9 s

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

  • Real-user INP: 249 ms

    249 ms

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

  • Real-user TTFB: 820 ms

    820 ms

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

  • Speed Index: 4.7 s

    4.7 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

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

    +12%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

5 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Total Blocking Time: 112 ms

    112 ms

    Scripts block the page for only 112 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.023

    0.023

    The layout barely moves while loading (CLS 0.023, good is under 0.1).

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    img-certidao.webp 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).

  • About 0.5 g of CO₂ per visit

    0.49 g

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

3 checks passed
  • Page weight: 1.7 MB in 49 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 49 requests on a phone: images 1,016 KiB (9), scripts 466 KiB (22) and fonts 185 KiB (8). That is a lean page.

  • 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

5 to fixGoogle 8792
  • 8 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 2 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 47 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: 47 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10097
  • 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.

  • No X (Twitter) card tag

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

  • 64 internal links, 11 external

    The homepage links to 64 pages on centraldascertidoes.com.br and 11 external pages.

7 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Peça online sua certidão de nascimento, casamento, óbito, imóvel e outras certidões de todos os cartórios do Brasil. Re…”.

  • One H1 headline

    Your main headline reads: “Peça seu documento de onde estiver.”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Peça sua certidão no Brasil ou no exterior sem sair de casa.”.

  • Canonical URL set

    The canonical URL is https://centraldascertidoes.com.br/.

  • Structured data in place

    Structured data found: Organization.

  • 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://centraldascertidoes.com.br/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://centraldascertidoes.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.

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (846 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix70
  • 1 page without a title

    https://centraldascertidoes.com.br/carrinho has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://centraldascertidoes.com.br/carrinho has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://centraldascertidoes.com.br/carrinho, whose canonical is https://centraldascertidoes.com.br/fluxoCompra/carrinho/index. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://centraldascertidoes.com.br/carrinho 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 26 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

2 to fixGoogle 9687
  • 7 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Identifier 'open' has already been declared”.

  • 1 low-resolution image

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix67
  • 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.

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

  • Thin social proof

    Social proof on the homepage: 14 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 1,250 words of copy

    The homepage carries about 1,250 words of visible text.

5 checks passed
  • 1 short form

    A short form (2 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Meta 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.

  • 5 cookies set on arrival

    5

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

  • 8 other companies contacted

    Loading the homepage contacts 8 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 centraldascertidoes.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

Framework
jQuery
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 31 issues on centraldascertidoes.com.br, including 13 speed issues, 1 SEO issue 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

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