Website review, no card needed

revelo.com.br logo

revelo.com.br website review

Visit site (opens in a new tab)Reviewed 27 October 202627 issues · 79 checks

This review found 27 issues worth fixing on revelo.com.br, 9 of them high impact, across 79 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
4.0 s1.8 sMay 9Oct 242.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.6 s
May 16, 20263.4 s
May 23, 20263.3 s
May 30, 20263.4 s
Jun 6, 20263.6 s
Jun 13, 20263.7 s
Jun 20, 20263.8 s
Jun 27, 20263.6 s
Jul 4, 20263.4 s
Jul 11, 20263.1 s
Jul 18, 20263.0 s
Jul 25, 20262.9 s
Aug 1, 20262.8 s
Aug 8, 20262.7 s
Aug 15, 20262.6 s
Aug 22, 20262.5 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.2 s
Oct 10, 20262.0 s
Oct 17, 20262.6 s
Oct 24, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
270 ms177 msMay 9Oct 24242 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026207 ms
May 16, 2026227 ms
May 23, 2026259 ms
May 30, 2026253 ms
Jun 6, 2026258 ms
Jun 13, 2026231 ms
Jun 20, 2026225 ms
Jun 27, 2026228 ms
Jul 4, 2026227 ms
Jul 11, 2026228 ms
Jul 18, 2026209 ms
Jul 25, 2026200 ms
Aug 1, 2026198 ms
Aug 8, 2026198 ms
Aug 15, 2026216 ms
Aug 22, 2026212 ms
Aug 29, 2026194 ms
Sep 5, 2026195 ms
Sep 12, 2026188 ms
Sep 19, 2026196 ms
Sep 26, 2026212 ms
Oct 3, 2026229 ms
Oct 10, 2026229 ms
Oct 17, 2026237 ms
Oct 24, 2026242 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 revelo.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

12 to fix43
  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 43

    43/100

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

  • Main-thread work: 4.6 s

    A phone's processor spends 4.6 s on main-thread work while loading, 2.5 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 (Google Tag Manager, Hubspot and Facebook and others), adding 1.5 MB and 1.7 s of main-thread time.

  • Reduce unused JavaScript

    750 ms · 407 KiB

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

  • Google Tag Manager adds 673 ms

    673 ms

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

  • Use efficient cache lifetimes

    150 ms · 465 KiB

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

  • Hubspot adds 372 ms

    372 ms

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

  • Facebook adds 328 ms

    328 ms

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

  • 19 long tasks on the main thread

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

  • 1,607 HTML elements

    The page has 1,607 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • website-files.com adds 120 ms

    120 ms

    website-files.com costs a phone 120 ms of main-thread work and 321 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 CSS

    150 ms · 63 KiB

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

  • Legacy JavaScript

    26 KiB

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

  • Phones get a much slower page than desktops

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

  • Improve image delivery

    10 KiB

    1 image could be 10 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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: 6 ms

    6 ms

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

Core Web Vitals

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

  • Time to Interactive: 18.5 s

    18.5 s

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

  • Largest Contentful Paint: 7.4 s

    7.4 s

    Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Work remotely for U.S. tech and AI companies”.

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Real-user INP: 235 ms

    235 ms

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

  • Real-user TTFB: 802 ms

    802 ms

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

  • Speed Index: 4.8 s

    4.8 s

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

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

    +10%

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

5 checks passed
  • Real-user LCP: 1.5 s

    1.5 s

    Real visitors wait 1.5 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.

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

    -28%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • 1 image below the first screen load straight away

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

  • About 0.5 g of CO₂ per visit

    0.52 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.52 g of CO₂e: 62.3 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.8 MB in 137 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 137 requests on a phone: scripts 1.4 MB (71), fonts 129 KiB (6) and images 117 KiB (29). 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

1 to fixGoogle 9798
  • 26 tap targets too small

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

2 checks passed
  • Every image has alt text

    All 44 images in the HTML carry an alt attribute.

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

SEO

2 to fixGoogle 9294
  • Structured data has 1 problem

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

  • 5 links with vague text

    5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 109 internal links, 28 external

    The homepage links to 109 pages on revelo.com.br and 28 external pages.

7 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Work remotely for U.S. tech and AI companies from Latin America. Full-time roles up to US$95,000 a year, or AI training…”.

  • One H1 headline

    Your main headline reads: “Work remotely for U.S. tech and AI companies”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Remote U.S. tech jobs for Latin American engineers | Revelo”.

  • Canonical URL set

    The canonical URL is https://www.revelo.com/work.

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

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.revelo.com/llms.txt (15 KiB, 91 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 71 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

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

  • Titles are unique

    Every page we checked has its own title.

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 small tap target

    1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • About 1,262 words of copy

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Apply now”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “Learn more”, “Talk to a researcher” and “Apply now”.

  • Social proof on the page

    Social proof on the homepage: 40 customer or partner logos, a star rating, 1 trust badge and “2,500+ companies”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 2 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.

  • 4 cookies set on arrival

    4

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

  • 18 other companies contacted

    Loading the homepage contacts 18 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 revelo.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

CMS
Webflow
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on revelo.com.br, including 20 speed issues, 2 SEO issues and 1 conversion gap. 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