Website review, no card needed

kovi.com.br logo

kovi.com.br website review

Visit site (opens in a new tab)Reviewed 18 November 202648 issues · 89 checks

This review found 48 issues worth fixing on kovi.com.br, 16 of them high impact, across 89 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.7 s1.7 sMay 30Nov 142.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.3 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.1 s
Jul 18, 20262.0 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20262.0 s
Oct 17, 20262.4 s
Oct 24, 20262.6 s
Oct 31, 20262.6 s
Nov 7, 20262.6 s
Nov 14, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
324 ms240 msMay 30Nov 14308 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026250 ms
Jun 6, 2026251 ms
Jun 13, 2026252 ms
Jun 20, 2026254 ms
Jun 27, 2026255 ms
Jul 4, 2026258 ms
Jul 11, 2026260 ms
Jul 18, 2026260 ms
Jul 25, 2026261 ms
Aug 1, 2026263 ms
Aug 8, 2026272 ms
Aug 15, 2026277 ms
Aug 22, 2026280 ms
Aug 29, 2026280 ms
Sep 5, 2026277 ms
Sep 12, 2026276 ms
Sep 19, 2026276 ms
Sep 26, 2026280 ms
Oct 3, 2026285 ms
Oct 10, 2026293 ms
Oct 17, 2026305 ms
Oct 24, 2026311 ms
Oct 31, 2026313 ms
Nov 7, 2026314 ms
Nov 14, 2026308 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 kovi.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix43
  • Use efficient cache lifetimes

    3.5 s · 752 KiB

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

  • Reduce unused JavaScript

    3.1 s · 506 KiB

    About 506 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

  • Mobile performance score: 43

    43/100

    Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Hubspot and others), adding 1.4 MB and 1.4 s of main-thread time.

  • Render-blocking requests

    950 ms

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

  • Google Tag Manager adds 700 ms

    700 ms

    Google Tag Manager costs a phone 700 ms of main-thread work and 661 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.

  • Improve image delivery

    300 ms · 102 KiB

    6 images could be 102 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Facebook adds 357 ms

    357 ms

    Facebook costs a phone 357 ms of main-thread work and 302 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.

  • 12 long tasks on the main thread

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

  • Main-thread work: 2.8 s

    A phone's processor spends 2.8 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Hubspot adds 190 ms

    190 ms

    Hubspot costs a phone 190 ms of main-thread work and 342 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.

  • Legacy JavaScript

    150 ms · 25 KiB

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

  • Reduce unused CSS

    110 ms · 26 KiB

    About 26 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 110 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.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 15 ms

    15 ms

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

Core Web Vitals

12 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: 17.6 s

    17.6 s

    Your largest element takes 17.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner home mobile atualização”.

  • Time to Interactive: 18.2 s

    18.2 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Total Blocking Time: 822 ms

    822 ms

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

  • Speed Index: 6.1 s

    6.1 s

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 246 ms

    246 ms

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

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

    +24%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 1 image without width and height

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

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

    +10%

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

2 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 2.2 MB in 111 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 111 requests on a phone: scripts 1.4 MB (35), images 476 KiB (31) and fonts 207 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Banner home mobile-Aug-11-2026-07-32-19-8861-PM.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.6 g of CO₂ per visit

    0.64 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.64 g of CO₂e: 76.5 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

9 to fixGoogle 8388
  • 20 buttons without a name

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

  • 26 tap targets too small

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

  • 5 text elements with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 48 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 8 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10093
  • Structured data has 1 problem

    Structured data found (FAQPage, Organization, Product and WebSite) but with 1 problem, for example “Product: no offers (price) block”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 36 internal links, 14 external

    The homepage links to 36 pages on kovi.com.br and 14 external pages.

6 checks passed
  • Meta description: 116 characters

    Your meta description is 116 characters: “Carro por assinatura sem análise de crédito, com preço justo e KM ilimitado. Conheça a Kovi e dirija sem burocracia.”.

  • One H1 headline

    Your main headline reads: “Aluguel de carros para motoristas de aplicativo”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Kovi: Aluguel de Carros sem Aprovação de Crédito e Burocracias”.

  • Canonical URL set

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

AI search readiness

100
  • No llms.txt

    There is no https://www.kovi.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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

5 to fix58
  • 1 page without a title

    https://www.kovi.com.br/cnh-digital has no <title>, so Google invents the link text in results.

  • 1 page points its canonical at the homepage

    https://www.kovi.com.br/escola-kovi 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.

  • 2 pages share a title

    / and https://www.kovi.com.br/escola-kovi all use the title “Kovi: Aluguel de Carros sem Aprovação de Crédito e Burocracias”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.kovi.com.br/cnh-digital and https://www.kovi.com.br/direcao-segura have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.kovi.com.br/cnh-digital has no <h1> headline, so visitors and search engines get no clear main topic.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

2 checks passed
  • Linked pages load

    All 12 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 7785
  • 8 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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 map 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: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 995 words of visible text.

4 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, HubSpot and Segment.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and HubSpot and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 cookies, 8 of them by other companies (measured from a US location before any click).

  • 38 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 kovi.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 48 issues on kovi.com.br, including 23 speed issues, 2 SEO issues 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