Website review, no card needed
eneva.com.br website review
Visit site (opens in a new tab)Reviewed 3 November 202649 issues · 87 checks
This review found 49 issues worth fixing on eneva.com.br, 26 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 4.0 s |
| May 30, 2026 | 4.1 s |
| Jun 6, 2026 | 4.1 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.3 s |
| Jul 11, 2026 | 4.3 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.4 s |
| Aug 1, 2026 | 4.4 s |
| Aug 8, 2026 | 4.4 s |
| Aug 15, 2026 | 4.6 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.6 s |
| Sep 5, 2026 | 4.7 s |
| Sep 12, 2026 | 4.7 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 4.4 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.3 s |
| Oct 17, 2026 | 4.3 s |
| Oct 24, 2026 | 4.3 s |
| Oct 31, 2026 | 4.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 120 ms |
| May 23, 2026 | 126 ms |
| May 30, 2026 | 130 ms |
| Jun 6, 2026 | 125 ms |
| Jun 13, 2026 | 122 ms |
| Jun 20, 2026 | 117 ms |
| Jun 27, 2026 | 116 ms |
| Jul 4, 2026 | 117 ms |
| Jul 11, 2026 | 117 ms |
| Jul 18, 2026 | 117 ms |
| Jul 25, 2026 | 114 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 115 ms |
| Aug 15, 2026 | 120 ms |
| Aug 22, 2026 | 120 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 124 ms |
| Sep 12, 2026 | 133 ms |
| Sep 19, 2026 | 136 ms |
| Sep 26, 2026 | 125 ms |
| Oct 3, 2026 | 122 ms |
| Oct 10, 2026 | 122 ms |
| Oct 17, 2026 | 122 ms |
| Oct 24, 2026 | 124 ms |
| Oct 31, 2026 | 133 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
Speed
Use efficient cache lifetimes
5.0 s · 13.2 MB36 files are served with short cache lifetimes, so returning visitors download them again (13.2 MB).
Reduce unused JavaScript
14.9 s · 2.7 MBAbout 2.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 14.9 s faster on a phone.
Improve image delivery
4.1 s · 3.1 MB9 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.1 s faster on a phone.
Reduce unused CSS
2.3 s · 475 KiBAbout 475 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.3 s faster on a phone.
YouTube adds 1.8 s
1.8 sYouTube costs a phone 1.8 s of main-thread work and 3.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 15
15/100Your mobile performance score is 15. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.1 s
A phone's processor spends 6.1 s on main-thread work while loading, 3.0 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 (YouTube, Google Tag Manager and Clarity and others), adding 5.0 MB and 2.3 s of main-thread time.
Render-blocking requests
550 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 550 ms.
Google Tag Manager adds 176 ms
176 msGoogle Tag Manager costs a phone 176 ms of main-thread work and 311 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.
handtalk.me adds 104 ms
104 mshandtalk.me costs a phone 104 ms of main-thread work and 412 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.
Google CDN adds 108 ms
108 msGoogle CDN costs a phone 108 ms of main-thread work and 353 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 241 ms. During a long task the page ignores taps.
Document request latency
47 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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.
1 checks passed
Server response: 44 ms
44 msYour server sent the HTML in 44 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.
Real-user LCP: 5.6 s
5.6 sReal visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.3 s
4.3 sReal visitors see the first content after 4.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.8 s
2.8 sReal visitors wait 2.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 38.5 s
38.5 sYour largest element takes 38.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DA SEGURANÇA ENERGÉTICA ÀS OPORTUNIDADES”.
Speed Index: 24.5 s
24.5 sVisually, the page fills in at 24.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 46.6 s
46.6 sThe page becomes fully interactive after 46.6 s. Good is under 3.8 s.
Cumulative Layout Shift: 1
1The layout shifts by 1 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 804 ms
804 msScripts block taps and scrolling for 804 ms in total while the page loads. Good is under 200 ms.
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
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 120 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.0 s to 4.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 115 ms
115 msReal visitors wait 115 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 19.2 MB in 132 requests
19.2 MBYour homepage downloads 19.2 MB in 132 requests on a phone: media 9.5 MB (3), scripts 4.7 MB (37) and images 3.7 MB (37). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 3.2 MB together. On a phone connection a single image that size takes seconds.
4 images far larger than shown
2.0 MB4 images are downloaded at several times the size a phone draws them, for example _L5A2198_2.2e16d0ba.fill-1920x955.webp at 1,920 px wide, shown at 390 px. Resized copies would save about 2.0 MB.
An image on the first screen is lazy-loaded
_L5A2198_2.2e16d0ba.fill-1920x955.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
4 images below the first screen load straight away
4 images further down the page (180 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.4 g of CO₂ per visit
5.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.44 g of CO₂e: 653.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
4 frames have no title, so screen-reader users cannot tell what they contain.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 37 images in the HTML carry an alt attribute.
37 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: 37 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No robots.txt
There is no robots.txt at eneva.com.br/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
80 internal links, 9 external
The homepage links to 80 pages on eneva.com.br and 9 external pages.
4 checks passed
Meta description: 91 characters
Your meta description is 91 characters: “Conheça a Eneva, a maior operadora privada de gás natural e geração termelétrica do Brasil.”.
Title: 50 characters
Your title is a healthy 50 characters: “Eneva - Segurança Energética Gerando Oportunidades”.
Canonical URL set
The canonical URL is https://www.eneva.com.br/.
XML sitemap found
Your XML sitemap is reachable at https://eneva.com.br/sitemap.xml.
AI search readiness
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://eneva.com.br/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (542 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://eneva.com.br/a-eneva and https://eneva.com.br/a-eneva/quem-somos all use the title “Quem Somos”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://eneva.com.br/en has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://eneva.com.br/a-eneva and https://eneva.com.br/a-eneva/quem-somos 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://eneva.com.br/a-eneva, whose canonical is https://eneva.com.br/a-eneva/quem-somos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
13 pages without an H1
https://eneva.com.br/en, https://eneva.com.br/a-eneva, https://eneva.com.br/a-eneva/quem-somos, https://eneva.com.br/a-eneva/seguranca-energetica, https://eneva.com.br/a-eneva/governanca and https://eneva.com.br/a-eneva/compliance and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://eneva.com.br/a-eneva and https://eneva.com.br/a-eneva/quem-somos have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
11 pages slow to respond
https://eneva.com.br/en, https://eneva.com.br/a-eneva, https://eneva.com.br/a-eneva/governanca, https://eneva.com.br/a-eneva/compliance, https://eneva.com.br/nossa-atuacao/exploracao-e-producao and https://eneva.com.br/nossa-atuacao/geracao-de-energia and 5 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.
3 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://analytics.google.com/g/collect?v=2&tid=G-02721PSMW7>m=45je6au1v9100441568za20ozb9262479102zd92…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
12 of 13 tappable elements near the top are at least 24 px.
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.
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 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 349 words of copy
The homepage carries about 349 words of visible text.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Microsoft Clarity (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.
6 cookies set on arrival
6Opening the homepage sets 6 cookies, 1 of them by other companies (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.
20 other companies contacted
Loading the homepage contacts 20 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 eneva.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
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Azure
Company
- Founded
- 2007
- Headquarters
- Rio de Janeiro
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on eneva.com.br, including 23 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.