Website review, no card needed
atualcargas.com.br website review
Visit site (opens in a new tab)Reviewed 19 November 202629 issues · 78 checks
This review found 29 issues worth fixing on atualcargas.com.br, 13 of them high impact, across 78 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.0 s |
| Nov 7, 2026 | 1.9 s |
| Nov 14, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 259 ms |
| Jun 6, 2026 | 262 ms |
| Jun 13, 2026 | 257 ms |
| Jun 20, 2026 | 261 ms |
| Jun 27, 2026 | 259 ms |
| Jul 4, 2026 | 257 ms |
| Jul 11, 2026 | 255 ms |
| Jul 18, 2026 | 260 ms |
| Jul 25, 2026 | 261 ms |
| Aug 1, 2026 | 262 ms |
| Aug 8, 2026 | 270 ms |
| Aug 15, 2026 | 270 ms |
| Aug 22, 2026 | 267 ms |
| Aug 29, 2026 | 264 ms |
| Sep 5, 2026 | 262 ms |
| Sep 12, 2026 | 262 ms |
| Sep 19, 2026 | 270 ms |
| Sep 26, 2026 | 272 ms |
| Oct 3, 2026 | 278 ms |
| Oct 10, 2026 | 278 ms |
| Oct 17, 2026 | 278 ms |
| Oct 24, 2026 | 278 ms |
| Oct 31, 2026 | 248 ms |
| Nov 7, 2026 | 203 ms |
| Nov 14, 2026 | 139 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.9 s
1.7 s
2.6 s
3.4 s
4.3 s
5.1 s
6.0 s
6.8 s
Speed
Use efficient cache lifetimes
3.1 s · 1.3 MB77 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).
Render-blocking requests
2.3 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Improve image delivery
1.1 s · 525 KiB11 images could be 525 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Reduce unused CSS
900 ms · 147 KiBAbout 147 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 400 KiBAbout 400 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 803 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Clarity and Cloudflare and others), adding 277 KiB and 287 ms of main-thread time.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 126 ms. During a long task the page ignores taps.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 154 ms
154 msYour server sent the HTML in 154 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner Site LIA”.
Time to Interactive: 12.4 s
12.4 sThe page becomes fully interactive after 12.4 s. Good is under 3.8 s.
Speed Index: 8.1 s
8.1 sVisually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.
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.
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 120 ms
120 msReal visitors wait 120 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.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 514 ms
514 msReal visitors wait 514 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 34% faster for real visitors
-34%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 259 ms to 139 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 34% faster for real visitors
-34%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 164 ms
164 msScripts block the page for only 164 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 2.2 MB in 95 requests
2.2 MBYour homepage downloads 2.2 MB in 95 requests on a phone: images 1.1 MB (14), scripts 876 KiB (40) and stylesheets 222 KiB (26). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (751 KiB) 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.
5 images below the first screen load straight away
5 images further down the page (355 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
15 KiB2 images are downloaded at several times the size a phone draws them, for example Banner_Americana_e_Osasco-1250x700.webp at 1,250 px wide, shown at 385 px. Resized copies would save about 15 KiB.
About 0.6 g of CO₂ per visit
0.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.64 g of CO₂e: 76.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
36 text elements with low contrast
36 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
16 tap targets too small
16 tap targets are too small or too close together to hit reliably with a finger.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
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.
Headings skip levels
Headings skip levels (h2 → h6, h2 → h5 and h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 14 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 6 failed. 1 more 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.
Title is short (21 characters)
Your title is only 21 characters: “Início - Atual Cargas”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
25 internal links, 52 external
The homepage links to 25 pages on atualcargas.com.br and 52 external pages.
5 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Transportadora com atuação em todo o Brasil: transporte rodoviário, armazenagem e logística B2B/B2C. Cotação online, ra…”.
Canonical URL set
The canonical URL is https://www.atualcargas.com.br/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and WebPage.
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.atualcargas.com.br/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.atualcargas.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.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (360 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.atualcargas.com.br/historia, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page with very little text
https://www.atualcargas.com.br/nossos-clientes has 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.
10 internal pages checked
We fetched 10 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 9 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 9 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 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 312 words of copy
The homepage carries about 312 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Analytics, Microsoft Clarity and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, 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.
4 cookies set on arrival
4Opening 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.
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 atualcargas.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on atualcargas.com.br, including 11 speed issues, 3 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.