Programmable

Website review, no card needed

vollsolutions.com.br logo

vollsolutions.com.br website review

Visit site (opens in a new tab)Reviewed 25 October 202622 issues · 78 checks

This review found 22 issues worth fixing on vollsolutions.com.br, 2 of them high impact, across 78 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

Site score

84B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
5.1 s2.8 sMay 2Oct 174.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.8 s
May 9, 20264.7 s
May 16, 20264.4 s
May 23, 20264.2 s
May 30, 20264.0 s
Jun 6, 20263.8 s
Jun 13, 20263.5 s
Jun 20, 20263.4 s
Jun 27, 20263.2 s
Jul 4, 20263.1 s
Jul 11, 20263.1 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.2 s
Aug 29, 20263.1 s
Sep 5, 20263.1 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20263.3 s
Oct 3, 20263.5 s
Oct 10, 20263.7 s
Oct 17, 20264.2 s
Real-visitor tap response (INP)75th percentile, phones
266 ms163 msMay 2Oct 17254 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026185 ms
May 9, 2026175 ms
May 16, 2026181 ms
May 23, 2026187 ms
May 30, 2026187 ms
Jun 6, 2026200 ms
Jun 13, 2026203 ms
Jun 20, 2026212 ms
Jun 27, 2026215 ms
Jul 4, 2026220 ms
Jul 11, 2026217 ms
Jul 18, 2026205 ms
Jul 25, 2026213 ms
Aug 1, 2026211 ms
Aug 8, 2026225 ms
Aug 15, 2026216 ms
Aug 22, 2026204 ms
Aug 29, 2026192 ms
Sep 5, 2026197 ms
Sep 12, 2026195 ms
Sep 19, 2026195 ms
Sep 26, 2026211 ms
Oct 3, 2026212 ms
Oct 10, 2026235 ms
Oct 17, 2026254 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

vollsolutions.com.br (opens in a new tab)
Full-page screenshot of vollsolutions.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. vollsolutions.com.br at 0.6 s0.6 s
  2. vollsolutions.com.br at 1.2 s1.2 s
  3. vollsolutions.com.br at 1.8 s1.8 s
  4. vollsolutions.com.br at 2.4 s2.4 s
  5. vollsolutions.com.br at 3.0 s3.0 s
  6. vollsolutions.com.br at 3.6 s3.6 s
  7. vollsolutions.com.br at 4.2 s4.2 s
  8. vollsolutions.com.br at 4.8 s4.8 s

Speed

4 to fix92

  • Render-blocking requests

    1.3 s

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

  • Reduce unused JavaScript

    150 ms · 414 KiB

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

  • Main-thread work: 3.3 s

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

  • 2,346 HTML elements

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

  • Use efficient cache lifetimes

    120 KiB

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

  • 6 long tasks on the main thread

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

  • Reduce unused CSS

    25 KiB

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

  • Improve image delivery

    20 KiB

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

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed

  • Mobile performance score: 92

    92/100

    Your mobile performance score is 92 (desktop: 93). That is in Google's “good” band (90 and up).

  • Server response: 8 ms

    8 ms

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

Core Web Vitals

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

  • Real-user LCP: 3.9 s

    3.9 s

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

  • Real-user INP: 361 ms

    361 ms

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

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

    +36%

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 895 ms

    895 ms

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

  • Largest Contentful Paint: 3.1 s

    3.1 s

    Your largest element takes 3.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 3.4 s

    3.4 s

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

  • Time to Interactive: 3.9 s

    3.9 s

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

  • 3 images without width and height

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

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

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

    -17%

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

  • First Contentful Paint: 1.5 s

    1.5 s

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

  • Total Blocking Time: 106 ms

    106 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

100

  • About 0.4 g of CO₂ per visit

    0.43 g

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

    1.5 MB

    Your homepage downloads 1.5 MB in 57 requests on a phone: media 960 KiB (2), scripts 239 KiB (14) and fonts 171 KiB (3). 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

2 to fixGoogle 9798

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

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

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed

  • Every image has alt text

    All 189 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 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10096

  • Structured data has 4 problems

    Structured data found (Organization, SoftwareApplication, WebPage and WebSite) but with 4 problems, for example “SoftwareApplication: no offers (price) block”.

  • 86 internal links, 7 external

    The homepage links to 86 pages on vollsolutions.com.br and 7 external pages.

7 checks passed

  • Meta description: 146 characters

    Your meta description is 146 characters: “Robôs humanizados, humanos superprodutivos. O Voll 360° reúne WhatsApp, voz, redes sociais e agentes de IA em uma única…”.

  • One H1 headline

    Your main headline reads: “Robôshumanizados,humanossuperprodutivos.”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Plataforma de atendimento omnichannel com IA · Voll Solutions”.

  • Canonical URL set

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

AI search readiness

1 to fix83

  • Parts of the site are closed to 6 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed

  • Organization data: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://vollsolutions.com.br/llms.txt (6 KiB, 36 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95

  • 8 pages without a meta description

    https://vollsolutions.com.br/whatsapp-business-calling-api, https://vollsolutions.com.br/solucoes/voll-360, https://vollsolutions.com.br/solucoes/voll-flows, https://vollsolutions.com.br/integracao-com-activecampaign, https://vollsolutions.com.br/integracao-com-hubspot and https://vollsolutions.com.br/integracao-com-pipedrive and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page slow to respond

    https://vollsolutions.com.br/solucoes/voll-workflows took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

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

  • 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

2 to fixGoogle 10087

  • 3 small tap targets

    3 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 “Failed to load resource: net::ERR_FAILED”.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93

  • 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 opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 875 words of visible text.

6 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Veja uma demo”.

  • 1 call to action

    The homepage has 1 call to action, for example “Veja uma demo”.

  • Social proof on the page

    Social proof on the homepage: 4 testimonial or review blocks and 90 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

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

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.

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

Framework
Next.js
Analytics
Google Analytics | Google Tag Manager
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on vollsolutions.com.br, including 14 speed issues, 1 SEO issue 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