Website review, no card needed

venhapranuvem.com.br logo

venhapranuvem.com.br website review

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

This review found 31 issues worth fixing on venhapranuvem.com.br, 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

Full-page screenshot of venhapranuvem.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. venhapranuvem.com.br at 0.8 s0.8 s
  2. venhapranuvem.com.br at 1.6 s1.6 s
  3. venhapranuvem.com.br at 2.3 s2.3 s
  4. venhapranuvem.com.br at 3.1 s3.1 s
  5. venhapranuvem.com.br at 3.9 s3.9 s
  6. venhapranuvem.com.br at 4.7 s4.7 s
  7. venhapranuvem.com.br at 5.5 s5.5 s
  8. venhapranuvem.com.br at 6.3 s6.3 s

Speed

7 to fix54
  • Render-blocking requests

    5.8 s

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

  • Mobile performance score: 54

    54/100

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

  • Reduce unused JavaScript

    600 ms · 138 KiB

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

  • Reduce unused CSS

    350 ms · 106 KiB

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

  • Use efficient cache lifetimes

    343 KiB

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

  • Main-thread work: 2.1 s

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

  • 1,679 HTML elements

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (goadopt.io, JSDelivr CDN and RD Station and others), adding 452 KiB and 253 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • 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

    3 KiB

    3 KiB could be saved by minifying CSS.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 259 ms

    259 ms

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

Core Web Vitals

5 to fix64
  • Largest Contentful Paint: 9.6 s

    9.6 s

    Your largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sua transformação digital na nuvem começa agora Fale com no…”.

  • First Contentful Paint: 7.2 s

    7.2 s

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

  • Speed Index: 9.2 s

    9.2 s

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

  • Time to Interactive: 9.6 s

    9.6 s

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

  • 8 images without width and height

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

  • 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
  • Cumulative Layout Shift: 0.088

    0.088

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.35 g

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

    1.2 MB

    Your homepage downloads 1.2 MB in 115 requests on a phone: scripts 648 KiB (44), images 337 KiB (20) and stylesheets 147 KiB (36). 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 9194
  • 33 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

    All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 44 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

6 to fixGoogle 9272
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (27 characters)

    Your title is only 27 characters: “Home - venhapranuvem.com.br”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (388 characters)

    Your meta description is 388 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 6 links crawlers can't follow

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 146 internal links, 4 external

    The homepage links to 146 pages on venhapranuvem.com.br and 4 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://venhapranuvem.com.br/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

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

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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,829 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 3 pages without a meta description

    https://venhapranuvem.com.br/cases/a-concremat-ocupa-o-primeiro-lugar-no-ranking-das-maiores-companhias-de-engenharia-consultiva-do-brasil, https://venhapranuvem.com.br/cases/aliansce-centraliza-identidades-e-beneficios-com-azure-active-directory-b2c and https://venhapranuvem.com.br/cases/ganhos-de-performance-e-produtividade-com-o-google-cloud-e-o-google-workspace have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://venhapranuvem.com.br/blog, https://venhapranuvem.com.br/cases, https://venhapranuvem.com.br/ia, https://venhapranuvem.com.br/solucoes-dados, https://venhapranuvem.com.br/solucoes-cloud and https://venhapranuvem.com.br/solucoes-ciberseguranca and 8 others have 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 28 found) and read each the way a search engine does.

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

  • 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 9687
  • 8 small tap targets

    8 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix13
  • 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.

  • No analytics detected

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 837 words of visible text.

Privacy and tracking

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

  • 11 other companies contacted

    Loading the homepage contacts 11 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 venhapranuvem.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
WordPress
Framework
jQuery

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on venhapranuvem.com.br, including 12 speed issues, 6 SEO issues and 4 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