Website review, no card needed
comgas.com.br website review
Visit site (opens in a new tab)Reviewed 31 October 202649 issues · 89 checks
This review found 49 issues worth fixing on comgas.com.br, 20 of them high impact, across 89 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
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.1 s |
| May 16, 2026 | 5.1 s |
| May 23, 2026 | 5.0 s |
| May 30, 2026 | 5.0 s |
| Jun 6, 2026 | 4.9 s |
| Jun 13, 2026 | 4.9 s |
| Jun 20, 2026 | 4.8 s |
| Jun 27, 2026 | 4.7 s |
| Jul 4, 2026 | 4.6 s |
| Jul 11, 2026 | 4.6 s |
| Jul 18, 2026 | 4.7 s |
| Jul 25, 2026 | 4.7 s |
| Aug 1, 2026 | 4.7 s |
| Aug 8, 2026 | 4.8 s |
| Aug 15, 2026 | 4.9 s |
| Aug 22, 2026 | 5.0 s |
| Aug 29, 2026 | 5.0 s |
| Sep 5, 2026 | 4.9 s |
| Sep 12, 2026 | 4.9 s |
| Sep 19, 2026 | 4.9 s |
| Sep 26, 2026 | 4.8 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.8 s |
| Oct 17, 2026 | 4.8 s |
| Oct 24, 2026 | 4.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 235 ms |
| May 16, 2026 | 232 ms |
| May 23, 2026 | 230 ms |
| May 30, 2026 | 229 ms |
| Jun 6, 2026 | 228 ms |
| Jun 13, 2026 | 228 ms |
| Jun 20, 2026 | 227 ms |
| Jun 27, 2026 | 226 ms |
| Jul 4, 2026 | 225 ms |
| Jul 11, 2026 | 232 ms |
| Jul 18, 2026 | 239 ms |
| Jul 25, 2026 | 246 ms |
| Aug 1, 2026 | 255 ms |
| Aug 8, 2026 | 264 ms |
| Aug 15, 2026 | 272 ms |
| Aug 22, 2026 | 278 ms |
| Aug 29, 2026 | 282 ms |
| Sep 5, 2026 | 281 ms |
| Sep 12, 2026 | 278 ms |
| Sep 19, 2026 | 278 ms |
| Sep 26, 2026 | 278 ms |
| Oct 3, 2026 | 277 ms |
| Oct 10, 2026 | 281 ms |
| Oct 17, 2026 | 280 ms |
| Oct 24, 2026 | 282 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.8 s
1.6 s
2.3 s
3.1 s
3.9 s
4.6 s
5.4 s
6.2 s
Speed
Use efficient cache lifetimes
5.5 s · 3.0 MB77 files are served with short cache lifetimes, so returning visitors download them again (3.0 MB).
Reduce unused JavaScript
4.6 s · 718 KiBAbout 718 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.6 s faster on a phone.
Improve image delivery
1.8 s · 1.7 MB12 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
2.2 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Reduce unused CSS
1.1 s · 149 KiBAbout 149 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 25
25/100Your mobile performance score is 25. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and smooch.io and others), adding 1.8 MB and 1.7 s of main-thread time.
Google Tag Manager adds 933 ms
933 msGoogle Tag Manager costs a phone 933 ms of main-thread work and 863 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.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 258 ms. During a long task the page ignores taps.
smooch.io adds 121 ms
121 mssmooch.io costs a phone 121 ms of main-thread work and 354 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.
Legacy JavaScript
150 ms · 46 KiBPolyfills for old browsers add 46 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 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: 6.0 s
6.0 sReal visitors wait 6.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.26
0.26For real visitors the layout shifts by 0.26 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 23.6 s
23.6 sYour largest element takes 23.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 23.7 s
23.7 sThe page becomes fully interactive after 23.7 s. Good is under 3.8 s.
Speed Index: 11.9 s
11.9 sVisually, the page fills in at 11.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.284
0.284The layout shifts by 0.284 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 297 ms
297 msReal visitors wait 297 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 235 ms to 282 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
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.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.1 s to 4.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.1 MB in 142 requests
5.1 MBYour homepage downloads 5.1 MB in 142 requests on a phone: images 2.8 MB (48), scripts 1.9 MB (41) and stylesheets 181 KiB (9). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (1.3 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
An image on the first screen is lazy-loaded
comgas-consumo-consciente-2025-bannerdesktop_v1-1.png 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).
1 image far larger than shown
35 KiB1 image is downloaded at several times the size a phone draws it, for example geracao_distribuida.webp at 500 px wide, shown at 98 px. Resized copies would save about 35 KiB.
8 images below the first screen load straight away
8 images further down the page (279 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.5 g of CO₂ per visit
1.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.45 g of CO₂e: 174.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
17 text elements with low contrast
17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
18 images without alt text
18 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (62 elements)
All page content should be contained by landmarks: 62 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (71 characters)
Your title is 71 characters, so Google will cut it off around 60: “Comgás: a maior distribuidora de gás natural encanado da América Latina”.
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.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
148 internal links, 55 external
The homepage links to 148 pages on comgas.com.br and 55 external pages.
5 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “Conheça a líder Comgás: soluções energéticas inovadoras e sustentáveis com gás natural para vida e negócios. Transforme…”.
One H1 headline
Your main headline reads: “Comgás”.
Canonical URL set
The canonical URL is https://www.comgas.com.br/.
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.comgas.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://www.comgas.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
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,008 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 34 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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Loading the image 'https://www.googleadservices.com/ccm/conversion/16595995046/?random=1793449571545&cv=11&fst=17934495…”.
6 distorted images
6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
28 of 34 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.
Thin social proof
Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 671 words of copy
The homepage carries about 671 words of visible text.
3 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and Hotjar.
Direct contact links
Visitors can reach you directly: 8 phone links and 0 email links.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 2 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
14 cookies set on arrival
14Opening the homepage sets 14 cookies (measured from a US location before any click).
37 other companies contacted
Loading the homepage contacts 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 comgas.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
- jQuery
- Analytics
- Google Tag Manager | Hotjar | Microsoft Clarity
- Hosting
- Akamai
Company
- Founded
- 1872
- Headquarters
- São Paulo
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 comgas.com.br, including 25 speed issues, 5 SEO issues and 3 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.