Website review, no card needed

evolucional.com.br logo

evolucional.com.br website review

Visit site (opens in a new tab)Reviewed 23 October 202648 issues · 90 checks

This review found 48 issues worth fixing on evolucional.com.br, 15 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. 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
2.8 s2.5 sMay 2Oct 172.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.5 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.6 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.8 s
Oct 17, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
210 ms178 msMay 2Oct 17201 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026188 ms
May 9, 2026183 ms
May 16, 2026184 ms
May 23, 2026183 ms
May 30, 2026182 ms
Jun 6, 2026184 ms
Jun 13, 2026183 ms
Jun 20, 2026184 ms
Jun 27, 2026185 ms
Jul 4, 2026190 ms
Jul 11, 2026192 ms
Jul 18, 2026201 ms
Jul 25, 2026205 ms
Aug 1, 2026202 ms
Aug 8, 2026193 ms
Aug 15, 2026187 ms
Aug 22, 2026190 ms
Aug 29, 2026198 ms
Sep 5, 2026202 ms
Sep 12, 2026204 ms
Sep 19, 2026206 ms
Sep 26, 2026202 ms
Oct 3, 2026199 ms
Oct 10, 2026200 ms
Oct 17, 2026201 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 evolucional.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. evolucional.com.br at 0.4 s0.4 s
  2. evolucional.com.br at 0.8 s0.8 s
  3. evolucional.com.br at 1.1 s1.1 s
  4. evolucional.com.br at 1.5 s1.5 s
  5. evolucional.com.br at 1.9 s1.9 s
  6. evolucional.com.br at 2.3 s2.3 s
  7. evolucional.com.br at 2.6 s2.6 s
  8. evolucional.com.br at 3.0 s3.0 s

Speed

14 to fix54
  • Use efficient cache lifetimes

    1.3 s · 2.6 MB

    74 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).

  • Render-blocking requests

    2.5 s

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

  • Google Tag Manager adds 1.3 s

    1.3 s

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

  • Main-thread work: 6.2 s

    A phone's processor spends 6.2 s on main-thread work while loading, 3.5 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, Google CDN and Facebook and others), adding 1.9 MB and 2.9 s of main-thread time.

  • Improve image delivery

    1.6 MB

    29 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    150 ms · 962 KiB

    About 962 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54 (desktop: 69). Pages that score under 90 lose visitors before the first paint.

  • Google CDN adds 793 ms

    793 ms

    Google CDN costs a phone 793 ms of main-thread work and 730 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.

  • Reduce unused CSS

    450 ms · 154 KiB

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

  • Font display

    500 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).

  • Facebook adds 425 ms

    425 ms

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

  • 20 long tasks on the main thread

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

  • Minify CSS

    300 ms · 39 KiB

    39 KiB could be saved by minifying CSS.

  • Document request latency

    46 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify JavaScript

    31 KiB

    31 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

1 checks passed
  • Server response: 72 ms

    72 ms

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

Core Web Vitals

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

  • Time to Interactive: 20.2 s

    20.2 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • Speed Index: 6.1 s

    6.1 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user INP: 203 ms

    203 ms

    Real visitors wait 203 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • Largest Contentful Paint: 3.3 s

    3.3 s

    Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Evolucional - Soluções educacionais”.

  • 28 images without width and height

    28 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 188 ms to 201 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +7%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.7 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

4 to fix43
  • Page weight: 4.7 MB in 118 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 118 requests on a phone: scripts 2.1 MB (28), images 1.8 MB (57) and other files 365 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • 21 images below the first screen load straight away

    21 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 13 images in older formats

    13 images (1.4 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.

  • 8 images far larger than shown

    438 KiB

    8 images are downloaded at several times the size a phone draws them, for example Andrea-Ramos.png at 401 px wide, shown at 100 px. Resized copies would save about 438 KiB.

  • About 1.3 g of CO₂ per visit

    1.33 g

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

Accessibility

8 to fixGoogle 8389
  • 9 text elements with low contrast

    9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 10 form fields without a label

    10 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 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 (h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

2 to fixGoogle 10093
  • 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 X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 17 internal links, 32 external

    The homepage links to 17 pages on evolucional.com.br and 32 external pages.

6 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “A Evolucional gera dados precisos sobre o conhecimento dos alunos e ajuda as instituições de ensino a alavancarem sua q…”.

  • One H1 headline

    Your main headline reads: “Sua escola entre as melhores do país.”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Evolucional: soluções educacionais. Potencialize seus resultados!”.

  • Canonical URL set

    The canonical URL is https://evolucional.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://evolucional.com.br/sitemap.xml.

AI search readiness

1 to fix88
  • 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://evolucional.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 (2,876 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://evolucional.com.br/nossas-solucoes has no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 internal pages checked

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

6 checks passed
  • Linked pages load

    All 7 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 7 pages that loaded have a meta description.

  • 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 7 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CERT_DATE_INVALID”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix56
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 9-field form

    Your longest form asks for 9 fields (6 required). Every extra field lowers completion.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 2,662 words of copy

    The homepage carries about 2,662 words of visible text.

3 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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 evolucional.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2021.

Stack

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 48 issues on evolucional.com.br, including 25 speed issues, 2 SEO issues and 5 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