Website review, no card needed

koin.com.br logo

koin.com.br website review

Visit site (opens in a new tab)Reviewed 4 November 202634 issues · 79 checks

This review found 34 issues worth fixing on koin.com.br, 8 of them high impact, across 79 checks. The most urgent: framer CDN adds 1.4 s. 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
3.1 s1.8 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.8 s
Aug 15, 20262.5 s
Aug 22, 20262.2 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
172 ms136 msMay 16Oct 31144 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026168 ms
May 23, 2026168 ms
May 30, 2026165 ms
Jun 6, 2026164 ms
Jun 13, 2026165 ms
Jun 20, 2026162 ms
Jun 27, 2026162 ms
Jul 4, 2026160 ms
Jul 11, 2026160 ms
Jul 18, 2026160 ms
Jul 25, 2026162 ms
Aug 1, 2026164 ms
Aug 8, 2026163 ms
Aug 15, 2026161 ms
Aug 22, 2026154 ms
Aug 29, 2026147 ms
Sep 5, 2026144 ms
Sep 12, 2026145 ms
Sep 19, 2026142 ms
Sep 26, 2026143 ms
Oct 3, 2026141 ms
Oct 10, 2026141 ms
Oct 17, 2026143 ms
Oct 24, 2026140 ms
Oct 31, 2026144 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 koin.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. koin.com.br at 0.6 s0.6 s
  2. koin.com.br at 1.1 s1.1 s
  3. koin.com.br at 1.7 s1.7 s
  4. koin.com.br at 2.2 s2.2 s
  5. koin.com.br at 2.8 s2.8 s
  6. koin.com.br at 3.3 s3.3 s
  7. koin.com.br at 3.9 s3.9 s
  8. koin.com.br at 4.5 s4.5 s

Speed

8 to fix84
  • Framer CDN adds 1.4 s

    1.4 s

    Framer CDN costs a phone 1.4 s of main-thread work and 2.1 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.

  • Main-thread work: 5.1 s

    A phone's processor spends 5.1 s on main-thread work while loading, 2.9 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 (Framer CDN, atendimen.to and Google Tag Manager and others), adding 3.5 MB and 2.2 s of main-thread time.

  • Mobile performance score: 84

    84/100

    Your mobile performance score is 84. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    995 KiB

    5 images could be 995 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • atendimen.to adds 370 ms

    370 ms

    atendimen.to costs a phone 370 ms of main-thread work and 789 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 JavaScript

    358 KiB

    About 358 KiB of JavaScript is downloaded but never used on this page.

  • handtalk.me adds 194 ms

    194 ms

    handtalk.me costs a phone 194 ms of main-thread work and 412 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.

  • 14 long tasks on the main thread

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

  • Reduce unused CSS

    35 KiB

    About 35 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    22 KiB

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

  • Legacy JavaScript

    14 KiB

    Polyfills for old browsers add 14 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.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 49 ms

    49 ms

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

Core Web Vitals

6 to fix100
  • 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.

  • Time to Interactive: 18.6 s

    18.6 s

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

  • Speed Index: 6.9 s

    6.9 s

    Visually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 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.

  • Real-user TTFB: 990 ms

    990 ms

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

  • Total Blocking Time: 369 ms

    369 ms

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

8 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 INP: 146 ms

    146 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Tap response (INP) got 15% faster for real visitors

    -15%

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

  • Largest content (LCP) got 27% faster for real visitors

    -27%

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0.022

    0.022

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

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Conectamos empresas e clientes com Soluções de Prevenção à …”.

Images and page weight

1 to fix85
  • Page weight: 3.5 MB in 115 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 115 requests on a phone: images 1.7 MB (14), scripts 1.2 MB (62) and fonts 524 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (280 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.99 g

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

6 to fixGoogle 9192
  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

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

  • 6 links without text

    6 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 21 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

2 to fixGoogle 10091
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 4 H1 headlines

    There are 4 <h1> headlines (“Conectamosempresas e clientescom Soluções de Prev…”, “Conectamosempresas e clientescom Soluções de Prev…” and “Conectamos empresase clientes com Soluçõesde Prev…”). One clear main headline is easier for people and search engines.

  • 50 internal links, 26 external

    The homepage links to 50 pages on koin.com.br and 26 external pages.

6 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “Koin é uma instituição de pagamento que desenvolve soluções para melhorar a vida das pessoas, democratizando o acesso a…”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “Koin | Antifraude e Pix Parcelado”.

  • Canonical URL set

    The canonical URL is https://www.koin.com.br/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

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

AI search readiness

1 to fix88
  • 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 https://www.koin.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 (1,023 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 12 pages share a title

    /, https://www.koin.com.br/antifraude, https://www.koin.com.br/pix-parcelado, https://www.koin.com.br/pix-app, https://www.koin.com.br/onde-comprar and https://www.koin.com.br/2via-boleto and 6 others all use the title “Koin | Antifraude e Pix Parcelado”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages share a meta description

    https://www.koin.com.br/antifraude, https://www.koin.com.br/pix-parcelado, https://www.koin.com.br/pix-app, https://www.koin.com.br/onde-comprar, https://www.koin.com.br/2via-boleto and https://www.koin.com.br/conteudos and 5 others use the same meta description. A description written for each page earns more clicks.

  • 11 internal pages checked

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

6 checks passed
  • Linked pages load

    All 11 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 11 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 5 small tap targets

    5 of 10 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 “Uncaught TypeError: Target [NeoassistCentral] element not found...”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 9-field form

    Your longest form asks for 9 fields (6 required). Every extra field lowers completion.

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

    The homepage carries about 491 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 koin.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
Framer
Analytics
Google Analytics
Hosting
Framer

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on koin.com.br, including 14 speed issues, 2 SEO issues and 5 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