Website review, no card needed
costaatacadao.com.br website review
Visit site (opens in a new tab)Reviewed 18 November 202654 issues · 82 checks
This review found 54 issues worth fixing on costaatacadao.com.br, 32 of them high impact, across 82 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
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 5.0 s |
| Jun 6, 2026 | 5.3 s |
| Jun 13, 2026 | 5.6 s |
| Jun 20, 2026 | 5.6 s |
| Jun 27, 2026 | 5.7 s |
| Jul 4, 2026 | 5.8 s |
| Jul 11, 2026 | 5.6 s |
| Jul 18, 2026 | 5.5 s |
| Jul 25, 2026 | 5.3 s |
| Aug 1, 2026 | 5.6 s |
| Aug 8, 2026 | 5.9 s |
| Aug 15, 2026 | 6.2 s |
| Aug 22, 2026 | 6.3 s |
| Aug 29, 2026 | 6.4 s |
| Sep 5, 2026 | 6.5 s |
| Sep 12, 2026 | 6.2 s |
| Sep 19, 2026 | 6.3 s |
| Sep 26, 2026 | 6.3 s |
| Oct 3, 2026 | 6.3 s |
| Oct 10, 2026 | 6.6 s |
| Oct 17, 2026 | 6.6 s |
| Oct 24, 2026 | 6.6 s |
| Oct 31, 2026 | 6.6 s |
| Nov 7, 2026 | 6.8 s |
| Nov 14, 2026 | 7.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 318 ms |
| Jun 6, 2026 | 292 ms |
| Jun 13, 2026 | 272 ms |
| Jun 20, 2026 | 263 ms |
| Jun 27, 2026 | 273 ms |
| Jul 4, 2026 | 281 ms |
| Jul 11, 2026 | 280 ms |
| Jul 18, 2026 | 263 ms |
| Jul 25, 2026 | 239 ms |
| Aug 1, 2026 | 230 ms |
| Aug 8, 2026 | 226 ms |
| Aug 15, 2026 | 231 ms |
| Aug 22, 2026 | 241 ms |
| Aug 29, 2026 | 242 ms |
| Sep 5, 2026 | 244 ms |
| Sep 12, 2026 | 236 ms |
| Sep 19, 2026 | 235 ms |
| Sep 26, 2026 | 236 ms |
| Oct 3, 2026 | 240 ms |
| Oct 10, 2026 | 249 ms |
| Oct 17, 2026 | 258 ms |
| Oct 24, 2026 | 263 ms |
| Oct 31, 2026 | 260 ms |
| Nov 7, 2026 | 257 ms |
| Nov 14, 2026 | 255 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
1.8 s
3.5 s
5.3 s
7.0 s
8.8 s
10.6 s
12.3 s
14.1 s
Speed
Use efficient cache lifetimes
40.6 s · 93.8 MB151 files are served with short cache lifetimes, so returning visitors download them again (93.8 MB).
Improve image delivery
40.5 s · 24.4 MB16 images could be 24.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 40.5 s faster on a phone.
Render-blocking requests
7.0 s39 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.0 s.
Reduce initial server response time
5.4 sReduce initial server response time. Google estimates savings of 5.4 s on a phone.
Document request latency
5.3 sThe HTML itself could arrive about 5.3 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce unused CSS
2.4 s · 492 KiBAbout 492 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Reduce unused JavaScript
1.5 s · 933 KiBAbout 933 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Font display
1.7 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.7 s).
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Server response: 5.5 s
5.5 sYour server takes 5.5 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, soswebsites.com and Google Analytics and others), adding 653 KiB and 644 ms of main-thread time.
Google Tag Manager adds 593 ms
593 msGoogle Tag Manager costs a phone 593 ms of main-thread work and 602 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.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,533 HTML elements
The page has 2,533 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 242 ms. During a long task the page ignores taps.
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
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
4 KiB4 KiB could be saved by minifying CSS.
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: 7.2 s
7.2 sReal visitors wait 7.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.7 s
4.7 sReal visitors see the first content after 4.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 4.0 s
4.0 sReal visitors wait 4.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 80.9 s
80.9 sYour largest element takes 80.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “banner sorteio luziania nov 2027 mobile”.
Speed Index: 47.7 s
47.7 sVisually, the page fills in at 47.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 266.0 s
266.0 sThe page becomes fully interactive after 266.0 s. Good is under 3.8 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Real-user INP: 239 ms
239 msReal visitors wait 239 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 33% slower for real visitors
+33%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 5.0 s to 7.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
67 images without width and height
67 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 411 ms
411 msScripts block taps and scrolling for 411 ms in total while the page loads. Good is under 200 ms.
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 318 ms to 255 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 106.0 MB in 164 requests
106.0 MBYour homepage downloads 106.0 MB in 164 requests on a phone: images 82.3 MB (51), media 20.9 MB (1) and scripts 1.8 MB (39). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
tabloide-food-go-01-2-scaled.png weighs 4.0 MB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
3.3 MB1 image is downloaded at several times the size a phone draws it, for example tabloide-food-go-01-2-scaled.png at 2,048 px wide, shown at 290 px. Resized copies would save about 3.3 MB.
1 image in older formats
1 image (4.0 MB) is 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.
1 image below the first screen load straight away
1 image further down the page (4.0 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 30.0 g of CO₂ per visit
30.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 30.04 g of CO₂e: 3604.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Unlabelled dropdowns
2 dropdowns have no label.
12 tap targets too small
12 tap targets are too small or too close together to hit reliably with a finger.
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA commands must have an accessible name (4 elements)
ARIA commands must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (3 elements)
Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).
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.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 98 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (14 characters)
Your title is only 14 characters: “Costa Atacadão”. Between 30 and 65 characters leaves room to say what you do and for whom.
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 (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://costaatacadao.com.br/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
132 internal links, 28 external
The homepage links to 132 pages on costaatacadao.com.br and 28 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://costaatacadao.com.br/.
robots.txt in place
robots.txt is in place.
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.
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,292 words), so crawlers that don't run JavaScript still read it.
Other pages
Your server turned our page checks away
7 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.
Best practices
4 small tap targets
4 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
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 285 words of copy
The homepage carries about 285 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Matomo.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
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.
2 other companies contacted
Loading the homepage contacts 2 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 costaatacadao.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
- Analytics
- Google Analytics | Google Tag Manager | Matomo
- Hosting
- As28299 Lwsa S/A
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 54 issues on costaatacadao.com.br, including 26 speed issues, 6 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.