Website review, no card needed
pensi.com.br website review
Visit site (opens in a new tab)Reviewed 31 October 202632 issues · 66 checks
This review found 32 issues worth fixing on pensi.com.br, 13 of them high impact, across 66 checks. The most urgent: avoid multiple page redirects. 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
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.8 s |
| May 16, 2026 | 4.8 s |
| May 23, 2026 | 4.7 s |
| May 30, 2026 | 4.7 s |
| Jun 6, 2026 | 4.7 s |
| Jun 13, 2026 | 4.8 s |
| Jun 20, 2026 | 4.8 s |
| Jun 27, 2026 | 4.8 s |
| Jul 4, 2026 | 4.7 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 4.7 s |
| Jul 25, 2026 | 4.8 s |
| Aug 1, 2026 | 4.8 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.6 s |
| Aug 22, 2026 | 4.3 s |
| Aug 29, 2026 | 4.0 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 208 ms |
| May 16, 2026 | 217 ms |
| May 23, 2026 | 217 ms |
| May 30, 2026 | 218 ms |
| Jun 6, 2026 | 216 ms |
| Jun 13, 2026 | 207 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 202 ms |
| Jul 4, 2026 | 210 ms |
| Jul 11, 2026 | 216 ms |
| Jul 18, 2026 | 224 ms |
| Jul 25, 2026 | 223 ms |
| Aug 1, 2026 | 222 ms |
| Aug 8, 2026 | 218 ms |
| Aug 15, 2026 | 217 ms |
| Aug 22, 2026 | 214 ms |
| Aug 29, 2026 | 209 ms |
| Sep 5, 2026 | 213 ms |
| Sep 12, 2026 | 227 ms |
| Sep 19, 2026 | 237 ms |
| Sep 26, 2026 | 252 ms |
| Oct 3, 2026 | 261 ms |
| Oct 10, 2026 | 266 ms |
| Oct 17, 2026 | 272 ms |
| Oct 24, 2026 | 281 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
Avoid multiple page redirects
10.1 sThe page goes through 1 redirect before it starts loading, costing about 10.1 s. Link and advertise the final URL directly.
gruposaltaedu.com adds 1.9 s
1.9 sgruposaltaedu.com costs a phone 1.9 s of main-thread work and 7 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.
Mobile performance score: 22
22/100Your mobile performance score is 22. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 3.4 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 (gruposaltaedu.com, Google Tag Manager and Facebook and others), adding 1.3 MB and 3.0 s of main-thread time.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 2.3 s. During a long task the page ignores taps.
Google Tag Manager adds 727 ms
727 msGoogle Tag Manager costs a phone 727 ms of main-thread work and 741 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
414 KiB20 files are served with short cache lifetimes, so returning visitors download them again (414 KiB).
Reduce unused JavaScript
392 KiBAbout 392 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
31 KiBAbout 31 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 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: 1 ms
1 msYour server sent the HTML in 1 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.
Time to Interactive: 26.6 s
26.6 sThe page becomes fully interactive after 26.6 s. Good is under 3.8 s.
Total Blocking Time: 2.7 s
2.7 sScripts block taps and scrolling for 2.7 s in total while the page loads. Good is under 200 ms.
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.
Cumulative Layout Shift: 0.462
0.462The layout shifts by 0.462 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 4.5 s
4.5 sYour largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PROVA DE BOLSA”. Most of its time is element render delay (2.1 s).
Real-user INP: 316 ms
316 msReal visitors wait 316 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 208 ms to 281 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 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.
Largest content (LCP) got 36% faster for real visitors
-36%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.8 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.5 MB in 174 requests
5.5 MBYour homepage downloads 5.5 MB in 174 requests on a phone: images 3.0 MB (43), scripts 1.6 MB (52) and fonts 614 KiB (12). Under 2 MB keeps phones on slow connections fast.
About 1.5 g of CO₂ per visit
1.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.55 g of CO₂e: 185.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
15 links without text
15 links have no text or label, so screen readers cannot say where they go.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Colégio Pensi - Educação de excelência do infantil ao pré-vestibular”.
87 internal links, 24 external
The homepage links to 87 pages on pensi.com.br and 24 external pages.
7 checks passed
Meta description: 130 characters
Your meta description is 130 characters: “Referência em resultados no ENEM, vestibulares e olimpíadas. Ensino Fundamental e Médio com método, foco e educação de …”.
One H1 headline
Your main headline reads: “Home”.
Canonical URL set
The canonical URL is https://pensi.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://pensi.com.br/page-sitemap.xml.
AI search readiness
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://pensi.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.
1 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.
Other pages
1 page without a meta description
https://pensi.com.br/segmentos/ensino-medio/preparatorio has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.
6 checks passed
Linked pages load
14 pages of 15 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.
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 14 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 44 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 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 1,602 words of copy
The homepage carries about 1,602 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and HubSpot.
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 pensi.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
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on pensi.com.br, including 21 speed issues, 1 SEO issue 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.