Website review, no card needed
verx.com.br website review
Visit site (opens in a new tab)Reviewed 25 October 202635 issues · 80 checks
This review found 35 issues worth fixing on verx.com.br, 8 of them high impact, across 80 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.6 s |
| May 9, 2026 | 3.7 s |
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 3.8 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 4.0 s |
| Jun 20, 2026 | 4.1 s |
| Jun 27, 2026 | 4.0 s |
| Jul 4, 2026 | 4.2 s |
| Jul 11, 2026 | 4.2 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 4.0 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 120 ms |
| May 9, 2026 | 126 ms |
| May 16, 2026 | 105 ms |
| May 23, 2026 | 96 ms |
| May 30, 2026 | 93 ms |
| Jun 6, 2026 | 94 ms |
| Jun 13, 2026 | 99 ms |
| Jun 20, 2026 | 108 ms |
| Jun 27, 2026 | 113 ms |
| Jul 4, 2026 | 114 ms |
| Jul 11, 2026 | 118 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 105 ms |
| Aug 1, 2026 | 111 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 156 ms |
| Aug 29, 2026 | 137 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 118 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 112 ms |
| Oct 3, 2026 | 116 ms |
| Oct 10, 2026 | 126 ms |
| Oct 17, 2026 | 135 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
How it loaded on a phone
0.5 s
1.1 s
1.6 s
2.2 s
2.7 s
3.3 s
3.8 s
4.4 s
Speed
Render-blocking requests
1.4 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 86
86/100Your mobile performance score is 86 (desktop: 96). Pages that score under 90 lose visitors before the first paint.
Google CDN adds 390 ms
390 msGoogle CDN costs a phone 390 ms of main-thread work and 734 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
300 ms · 124 KiBAbout 124 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.
Reduce unused JavaScript
370 KiBAbout 370 KiB of JavaScript is downloaded but never used on this page.
3 third-party services on the page
3 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts), adding 870 KiB and 426 ms of main-thread time.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 156 ms. During a long task the page ignores taps.
Improve image delivery
10 KiB1 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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 756 ms of it running JavaScript. That is comfortably low.
Server response: 141 ms
141 msYour server sent the HTML in 141 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 9.3 s
9.3 sThe page becomes fully interactive after 9.3 s. Good is under 3.8 s.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 3.2 s
3.2 sYour largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Consultoria Especializada em Recrutamento de TI”. Most of its time is element render delay (1.9 s).
Speed Index: 4.2 s
4.2 sVisually, the page fills in at 4.2 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 120 ms to 135 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 29% faster for real visitors
-29%Over the last 25 four-week periods to 2026-10-17, 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).
Total Blocking Time: 114 ms
114 msScripts block the page for only 114 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.5 g of CO₂ per visit
0.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 58.2 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: 1.7 MB in 56 requests
1.7 MBYour homepage downloads 1.7 MB in 56 requests on a phone: scripts 704 KiB (6), other files 348 KiB (1) and images 238 KiB (7). 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
20 text elements with low contrast
20 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA commands must have an accessible name (6 elements)
ARIA commands must have an accessible name: 6 elements on the page fail this check, rated serious by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails 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 banner landmark (1 element)
Document should not have more than one banner 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.
27 links without text
27 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.
Headings skip levels
Headings skip levels (h1 → h5, h3 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 56 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 9 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (29 characters)
Your title is only 29 characters: “RH Especializado em TI - Verx”. Between 30 and 65 characters leaves room to say what you do and for whom.
No robots.txt
There is no robots.txt at verx.com.br/robots.txt, the first file search crawlers ask for.
85 internal links, 14 external
The homepage links to 85 pages on verx.com.br and 14 external pages.
6 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “Empresa de RH Especializado em TI e Consultoria: Contratação, Hunting e Alocação de Profissionais de Tecnologia. Encont…”.
One H1 headline
Your main headline reads: “Oportunidades para Área de TI Desenvolvedores Programação UX Business Analytics”.
Canonical URL set
The canonical URL is https://www.verx.com.br/.
Structured data in place
Structured data found: Article, EmploymentAgency, ImageObject, Organization and Person.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://www.verx.com.br/sitemap.xml.
AI search readiness
2 checks passed
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (604 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.verx.com.br/alocacao-de-profissionais-de-ti and https://www.verx.com.br/alocacao-de-talentos-em-ti all use the title “Alocação de Profissionais de TI - Verx”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://www.verx.com.br/todos-pt, https://www.verx.com.br/saude-e-bem-estar-pt and https://www.verx.com.br/tecnologia-e-inovacao-pt have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.verx.com.br/alocacao-de-profissionais-de-ti and https://www.verx.com.br/alocacao-de-talentos-em-ti use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.verx.com.br/alocacao-de-talentos-em-ti, whose canonical is https://www.verx.com.br/alocacao-de-profissionais-de-ti. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.verx.com.br/sobre 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 21 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.
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
4 small tap targets
4 of 11 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 “Framing 'https://www.google.com/' violates the following report-only Content Security Policy directive: "frame-ancestor…”.
2 low-resolution images
2 images are 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
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 399 words of copy
The homepage carries about 399 words of visible text.
3 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
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.
5 other companies contacted
Loading the homepage contacts 5 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 verx.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 © 2023.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
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 verx.com.br, including 12 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.