Website review, no card needed

r2.com.vc logo

r2.com.vc website review

Visit site (opens in a new tab)Reviewed 20 October 202635 issues · 71 checks

This review found 35 issues worth fixing on r2.com.vc, 11 of them high impact, across 71 checks. The most urgent: render-blocking requests. 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.5 s2.9 sMay 2Sep 53.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.9 s
May 9, 20263.0 s
May 16, 20263.3 s
May 23, 20263.4 s
May 30, 20263.4 s
Jun 6, 20263.4 s
Jun 13, 20263.4 s
Jun 20, 20263.5 s
Jun 27, 20263.4 s
Jul 4, 20263.3 s
Jul 11, 20263.2 s
Jul 18, 20263.2 s
Jul 25, 20263.2 s
Aug 1, 20263.2 s
Aug 8, 20263.2 s
Aug 15, 20263.1 s
Aug 22, 20263.1 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
275 ms208 msMay 2Sep 5267 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026230 ms
May 9, 2026231 ms
May 16, 2026254 ms
May 23, 2026262 ms
May 30, 2026259 ms
Jun 6, 2026263 ms
Jun 13, 2026247 ms
Jun 20, 2026243 ms
Jun 27, 2026235 ms
Jul 4, 2026225 ms
Jul 11, 2026220 ms
Jul 18, 2026216 ms
Jul 25, 2026220 ms
Aug 1, 2026226 ms
Aug 8, 2026238 ms
Aug 15, 2026249 ms
Aug 22, 2026256 ms
Aug 29, 2026267 ms
Sep 5, 2026267 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 r2.com.vc (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix68
  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 68

    68/100

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

  • Reduce unused CSS

    610 ms · 77 KiB

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

  • Reduce unused JavaScript

    310 ms · 59 KiB

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

  • Use efficient cache lifetimes

    150 ms · 3 KiB

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

  • 6 long tasks on the main thread

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google CDN, Cloudflare CDN and openfpcdn.io and others), adding 230 KiB and 38 ms of main-thread time.

  • Minify CSS

    11 KiB

    11 KiB could be saved by minifying CSS.

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

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

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 16 ms

    16 ms

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

Core Web Vitals

4 to fix72
  • Largest Contentful Paint: 5.6 s

    5.6 s

    Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A API não respondeu (Failed to fetch). Verifique se o servi…”. Most of its time is element render delay (2.3 s).

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • Speed Index: 5.2 s

    5.2 s

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

  • Time to Interactive: 5.7 s

    5.7 s

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

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

    +16%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 87 ms

    87 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.1 g of CO₂ per visit

    0.14 g

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

4 checks passed
  • Page weight: 509 KiB in 38 requests

    509 KiB

    Your homepage downloads 509 KiB in 38 requests on a phone: scripts 232 KiB (13), fonts 96 KiB (6) and stylesheets 80 KiB (8). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

4 to fixGoogle 9493
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 7 images without alt text

    7 images have no alt text, which hurts accessibility and image search.

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

  • 15 form fields without a label

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

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

11 to fixGoogle 4533
  • Page is set to noindex

    The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

  • No meta description

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

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (9 characters)

    Your title is only 9 characters: “r2.com.vc”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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 (“{{ form.foreigner == 1 ? "One moment" : "Um minut…”, “{{ form.foreigner == 1 ? "Welcome" : "Bem-vindo"}…” and “{{ form.foreigner == 1 ? "One moment" : "Um minut…”). One clear main headline is easier for people and search engines.

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

  • No XML sitemap

    No XML sitemap at https://r2.com.vc/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at r2.com.vc/robots.txt, the first file search crawlers ask for.

  • 4 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 22 internal links, 12 external

    The homepage links to 22 pages on r2.com.vc and 12 external pages.

AI search readiness

1 to fix83
  • 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://r2.com.vc/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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

2 to fix90
  • 1 page without a meta description

    https://r2.com.vc/corporativos has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://r2.com.vc/corporativos has no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 internal pages checked

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

5 checks passed
  • Linked pages load

    All 8 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 1 page that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 4 broken images

    4 images failed to load on a phone, for example https://media.r2.com.vc/uploads/2022/05/logotipo-2.svg.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://media.r2.com.vc/ultra/site/home.json?_=1792477829064' from origin 'https://r2.com.vc' has b…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • A 13-field form

    Your longest form asks for 13 fields (0 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.

  • Only about 79 words

    The homepage has only about 79 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Privacy and tracking

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

  • 7 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
Vue.js
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on r2.com.vc, including 8 speed issues, 11 SEO issues and 7 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