Website review, no card needed
damasio.com.br website review
Visit site (opens in a new tab)Reviewed 4 November 202636 issues · 85 checks
This review found 36 issues worth fixing on damasio.com.br, 16 of them high impact, across 85 checks. The most urgent: improve image delivery. 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
76C- #71,889 of 117,584 reviewed websitesbeats 34%
- #46,460 of 66,923 online storesbeats 26%
- #1,150 of 2,700 WooCommerce storesbeats 52%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 3.8 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.6 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.7 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.7 s |
| Oct 24, 2026 | 3.8 s |
| Oct 31, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 320 ms |
| May 23, 2026 | 320 ms |
| May 30, 2026 | 324 ms |
| Jun 6, 2026 | 327 ms |
| Jun 13, 2026 | 329 ms |
| Jun 20, 2026 | 328 ms |
| Jun 27, 2026 | 328 ms |
| Jul 4, 2026 | 336 ms |
| Jul 11, 2026 | 348 ms |
| Jul 18, 2026 | 356 ms |
| Jul 25, 2026 | 361 ms |
| Aug 1, 2026 | 364 ms |
| Aug 8, 2026 | 369 ms |
| Aug 15, 2026 | 380 ms |
| Aug 22, 2026 | 385 ms |
| Aug 29, 2026 | 390 ms |
| Sep 5, 2026 | 393 ms |
| Sep 12, 2026 | 395 ms |
| Sep 19, 2026 | 404 ms |
| Sep 26, 2026 | 413 ms |
| Oct 3, 2026 | 419 ms |
| Oct 10, 2026 | 429 ms |
| Oct 17, 2026 | 433 ms |
| Oct 24, 2026 | 441 ms |
| Oct 31, 2026 | 426 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
Improve image delivery
2.2 s · 1.2 MB11 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.2 s faster on a phone.
Use efficient cache lifetimes
2.1 s · 477 KiB13 files are served with short cache lifetimes, so returning visitors download them again (477 KiB).
Reduce unused JavaScript
1.9 s · 656 KiBAbout 656 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Render-blocking requests
1.9 s44 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
3,457 HTML elements
The page has 3,457 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Hubspot and Amplitude Mobile Analytics and others), adding 1.2 MB and 1.1 s of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 414 ms
414 msGoogle Tag Manager costs a phone 414 ms of main-thread work and 520 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.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Hubspot adds 326 ms
326 msHubspot costs a phone 326 ms of main-thread work and 346 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 · 51 KiBPolyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 176 ms. During a long task the page ignores taps.
Reduce unused CSS
12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page.
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: 7 ms
7 msYour server sent the HTML in 7 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.
Largest Contentful Paint: 20.4 s
20.4 sYour largest element takes 20.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner de black freeze damásio: pós-graduação com o menor p…”.
Time to Interactive: 21.8 s
21.8 sThe page becomes fully interactive after 21.8 s. Good is under 3.8 s.
Speed Index: 11.7 s
11.7 sVisually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 s.
Real-user INP: 294 ms
294 msReal visitors wait 294 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 35% slower for real visitors
+35%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 320 ms to 426 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 394 ms
394 msScripts block taps and scrolling for 394 ms in total while the page loads. Good is under 200 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.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.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: 775 ms
775 msReal visitors wait 775 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.8 MB in 194 requests
5.8 MBYour homepage downloads 5.8 MB in 194 requests on a phone: images 3.2 MB (41), scripts 1.6 MB (76) and fonts 800 KiB (7). Under 2 MB keeps phones on slow connections fast.
17 images in older formats
17 images (2.1 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.
3 images far larger than shown
243 KiB3 images are downloaded at several times the size a phone draws them, for example POS-BF_Banner-site_mobile.webp at 1,440 px wide, shown at 390 px. Resized copies would save about 243 KiB.
About 1.6 g of CO₂ per visit
1.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.63 g of CO₂e: 195.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
[role="img"] and [role="image"] elements must have alternative text (5 elements)
[role="img"] and [role="image"] elements must have alternative text: 5 elements on the page fail this check, rated serious by axe-core.
177 form fields without a label
177 form fields have no label, so screen readers announce an empty box and autofill guesses.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 32 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 8 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
278 internal links, 75 external
The homepage links to 278 pages on damasio.com.br and 75 external pages.
8 checks passed
Meta description: 134 characters
Your meta description is 134 characters: “Há mais de 50 anos formando os melhores profissionais do Direito. Pós-graduação, OAB e concursos jurídicos com quem apr…”.
One H1 headline
Your main headline reads: “Estude no Damásio Educacional, a maior comunidade jurídica do Brasil”.
Title: 56 characters
Your title is a healthy 56 characters: “Damásio | Pós, OAB e Concursos Jurídicos com Excelência.”.
Canonical URL set
The canonical URL is https://damasio.com.br/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://damasio.com.br/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,372 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://damasio.com.br/llms.txt (2 KiB, 16 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://damasio.com.br/c/pos-graduacao/mais-vendidas, https://damasio.com.br/c/pos-graduacao/novos-cursos-pos, https://damasio.com.br/c/pos-graduacao/civil and https://damasio.com.br/c/pos-graduacao/constitucional have no meta description, so Google writes the search snippet from whatever text it finds.
1 page slow to respond
https://damasio.com.br/c/pos-graduacao/mais-vendidas took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 87 found) and read each the way a search engine does.
6 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.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=211046632&tm=gtm002&Ver=2&mid=e847ab71-df81-4e1d-a402-09fcaefb70c4&bo=1&sid=f1a144a0d86711f186b18bee6d698c1a&vid=f1a162c0d86711f1b227c5ab9c69a8dd&vids=1&msclkid=N&pi=9.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
16 of 18 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: 35 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 1,264 words of copy
The homepage carries about 1,264 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, Microsoft Clarity, HubSpot, Amplitude and Cloudflare Web Analytics.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and HubSpot and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
28 cookies set on arrival
28Opening the homepage sets 28 cookies (measured from a US location before any click).
45 other companies contacted
Loading the homepage contacts 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) 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 damasio.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
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager | Amplitude | Microsoft Clarity
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on damasio.com.br, including 19 speed 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.