Website review, no card needed

academiawave.com.br logo

academiawave.com.br website review

Visit site (opens in a new tab)Reviewed 18 October 202641 issues · 83 checks

This review found 41 issues worth fixing on academiawave.com.br, 19 of them high impact, across 83 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.1 s1.7 sApr 25Oct 103.8 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.0 s
May 2, 20262.0 s
May 9, 20262.0 s
May 16, 20262.1 s
May 23, 20262.0 s
May 30, 20262.1 s
Jun 6, 20262.2 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.4 s
Jul 18, 20262.5 s
Jul 25, 20262.4 s
Aug 1, 20262.5 s
Aug 8, 20263.1 s
Aug 15, 20263.2 s
Aug 22, 20263.4 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.5 s
Sep 19, 20263.6 s
Sep 26, 20263.6 s
Oct 3, 20263.8 s
Oct 10, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
257 ms154 msApr 25Oct 10245 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026176 ms
May 2, 2026185 ms
May 9, 2026176 ms
May 16, 2026173 ms
May 23, 2026183 ms
May 30, 2026166 ms
Jun 6, 2026181 ms
Jun 13, 2026205 ms
Jun 20, 2026195 ms
Jun 27, 2026207 ms
Jul 4, 2026204 ms
Jul 11, 2026175 ms
Jul 18, 2026175 ms
Jul 25, 2026180 ms
Aug 1, 2026190 ms
Aug 8, 2026204 ms
Aug 15, 2026213 ms
Aug 22, 2026220 ms
Aug 29, 2026224 ms
Sep 5, 2026216 ms
Sep 12, 2026216 ms
Sep 19, 2026223 ms
Sep 26, 2026225 ms
Oct 3, 2026244 ms
Oct 10, 2026245 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

Full-page screenshot of academiawave.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. academiawave.com.br at 1.3 s1.3 s
  2. academiawave.com.br at 2.6 s2.6 s
  3. academiawave.com.br at 3.9 s3.9 s
  4. academiawave.com.br at 5.2 s5.2 s
  5. academiawave.com.br at 6.5 s6.5 s
  6. academiawave.com.br at 7.8 s7.8 s
  7. academiawave.com.br at 9.1 s9.1 s
  8. academiawave.com.br at 10.4 s10.4 s

Speed

12 to fix27
  • Improve image delivery

    4.0 s · 1.2 MB

    4 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 4.0 s faster on a phone.

  • Google Tag Manager adds 1.9 s

    1.9 s

    Google Tag Manager costs a phone 1.9 s of main-thread work and 1.1 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.

  • Reduce unused JavaScript

    1.1 s · 828 KiB

    About 828 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Render-blocking requests

    1.6 s

    18 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

  • Mobile performance score: 27

    27/100

    Your mobile performance score is 27 (desktop: 37). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 9.7 s

    A phone's processor spends 9.7 s on main-thread work while loading, 3.7 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 (Google Tag Manager, Facebook and RD Station and others), adding 3.0 MB and 2.6 s of main-thread time.

  • Reduce unused CSS

    910 ms · 160 KiB

    About 160 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 910 ms faster on a phone.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 994 ms. During a long task the page ignores taps.

  • Facebook adds 533 ms

    533 ms

    Facebook costs a phone 533 ms of main-thread work and 223 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.

  • Use efficient cache lifetimes

    270 KiB

    6 files are served with short cache lifetimes, so returning visitors download them again (270 KiB).

  • WordPress adds 12 ms

    12 ms

    WordPress costs a phone 12 ms of main-thread work and 1.5 MB 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.

  • Minify JavaScript

    150 ms · 30 KiB

    30 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    150 ms · 28 KiB

    Polyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 41 ms

    41 ms

    Your server sent the HTML in 41 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix33
  • 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 FCP: 3.2 s

    3.2 s

    Real visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 2.4 s

    2.4 s

    Real visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 14.5 s

    14.5 s

    Your largest element takes 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Aviso de privacidade Utilizamos cookies em nosso website pa…”.

  • Speed Index: 15.2 s

    15.2 s

    Visually, the page fills in at 15.2 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 21.4 s

    21.4 s

    The page becomes fully interactive after 21.4 s. Good is under 3.8 s.

  • Total Blocking Time: 2.9 s

    2.9 s

    Scripts block taps and scrolling for 2.9 s in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 4.6 s

    4.6 s

    The first text or image appears after 4.6 s on a phone. Good is under 1.8 s.

  • Real-user LCP: 3.8 s

    3.8 s

    Real visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 236 ms

    236 ms

    Real visitors wait 236 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-10, real Chrome visitors' tap response (inp) went from 176 ms to 245 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 91% slower for real visitors

    +91%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.0 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix48
  • Page weight: 19.3 MB in 106 requests

    19.3 MB

    Your homepage downloads 19.3 MB in 106 requests on a phone: images 16.9 MB (16), scripts 1.9 MB (41) and fonts 237 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1,003 KiB together. On a phone connection a single image that size takes seconds.

  • 1 image below the first screen load straight away

    1 image further down the page (492 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (74 KiB) 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.

  • About 5.5 g of CO₂ per visit

    5.47 g

    By the Sustainable Web Design model, a visit to your homepage emits about 5.47 g of CO₂e: 656.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9497
  • All page content should be contained by landmarks (11 elements)

    All page content should be contained by landmarks: 11 elements on the page fail 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 should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10097
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 15 internal links, 10 external

    The homepage links to 15 pages on academiawave.com.br and 10 external pages.

7 checks passed
  • Meta description: 129 characters

    Your meta description is 129 characters: “Saia da Rotina! Nossa Academia vai melhorar sua Saúde! Na Wave tem Musculação, Boxe, Ioga, Natação e mais! Conheça noss…”.

  • One H1 headline

    Your main headline reads: “Experimente”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Academias Wave | Conheça nossos Planos e Mude a sua Saúde!”.

  • Canonical URL set

    The canonical URL is https://academiawave.com.br/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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://academiawave.com.br/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://academiawave.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 (608 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://academiawave.com.br/regulamento-indique-um-amigo has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://academiawave.com.br/sou-aluno has no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 internal pages checked

    We fetched 5 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    4 pages of 5 loaded without an error (the rest turned automated requests away).

  • 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 4 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 2 broken images

    2 images failed to load on a phone, for example https://luizacademiawave.wpcomstaging.com/wp-content/uploads/2020/06/Logotipo_Academia_Wave.png.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://luizacademiawave.wpcomstaging.com/wp-content/plugins/revslider/public/assets/svg/n…”.

2 checks passed
  • Tap targets are thumb-sized

    7 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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: 6 trust badges. 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 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 311 words of copy

    The homepage carries about 311 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 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.

  • 22 other companies contacted

    Loading the homepage contacts 22 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 academiawave.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
Analytics
Google Analytics | Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on academiawave.com.br, including 24 speed issues, 1 SEO issue 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25