Website review, no card needed
unicentro.br website review
Visit site (opens in a new tab)Reviewed 26 October 202643 issues · 75 checks
This review found 43 issues worth fixing on unicentro.br, 19 of them high impact, across 75 checks. The most urgent: render-blocking requests. 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 | 2.0 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 157 ms |
| May 16, 2026 | 161 ms |
| May 23, 2026 | 167 ms |
| May 30, 2026 | 180 ms |
| Jun 6, 2026 | 191 ms |
| Jun 13, 2026 | 199 ms |
| Jun 20, 2026 | 199 ms |
| Jun 27, 2026 | 194 ms |
| Jul 4, 2026 | 189 ms |
| Jul 11, 2026 | 184 ms |
| Jul 18, 2026 | 185 ms |
| Jul 25, 2026 | 185 ms |
| Aug 1, 2026 | 184 ms |
| Aug 8, 2026 | 184 ms |
| Aug 15, 2026 | 183 ms |
| Aug 22, 2026 | 179 ms |
| Aug 29, 2026 | 185 ms |
| Sep 5, 2026 | 194 ms |
| Sep 12, 2026 | 194 ms |
| Sep 19, 2026 | 206 ms |
| Sep 26, 2026 | 214 ms |
| Oct 3, 2026 | 210 ms |
| Oct 10, 2026 | 212 ms |
| Oct 17, 2026 | 218 ms |
| Oct 24, 2026 | 209 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.3 s
2.5 s
3.8 s
5.1 s
6.3 s
7.6 s
8.9 s
10.1 s
Speed
Render-blocking requests
9.1 s59 files block the first paint until they finish downloading. Deferring or inlining them could save about 9.1 s.
Improve image delivery
4.1 s · 819 KiB7 images could be 819 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.1 s faster on a phone.
Reduce unused JavaScript
2.7 s · 504 KiBAbout 504 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Font display
2.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.1 s).
Use efficient cache lifetimes
1.6 s · 183 KiB5 files are served with short cache lifetimes, so returning visitors download them again (183 KiB).
Reduce unused CSS
1.1 s · 157 KiBAbout 157 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 43
43/100Your mobile performance score is 43 (desktop: 37). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.3 s
A phone's processor spends 5.3 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Clarity and vlibras.gov.br and others), adding 934 KiB and 847 ms of main-thread time.
Google Tag Manager adds 718 ms
718 msGoogle Tag Manager costs a phone 718 ms of main-thread work and 797 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.
Minify JavaScript
450 ms · 69 KiB69 KiB could be saved by minifying JavaScript.
2,568 HTML elements
The page has 2,568 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 214 ms. During a long task the page ignores taps.
Legacy JavaScript
37 KiBPolyfills for old browsers add 37 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 CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 183 ms
183 msYour server sent the HTML in 183 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: 32.7 s
32.7 sYour largest element takes 32.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Submissão da propostas no Programa Institucional de Apoio à…”.
Speed Index: 16.7 s
16.7 sVisually, the page fills in at 16.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 33.4 s
33.4 sThe page becomes fully interactive after 33.4 s. Good is under 3.8 s.
First Contentful Paint: 5.8 s
5.8 sThe first text or image appears after 5.8 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 34% slower for real visitors
+34%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 157 ms to 209 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 867 ms
867 msReal visitors wait 867 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 470 ms
470 msScripts block taps and scrolling for 470 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 136 ms
136 msReal visitors wait 136 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.044
0.044The layout barely moves while loading (CLS 0.044, good is under 0.1).
Images and page weight
Page weight: 7.1 MB in 195 requests
7.1 MBYour homepage downloads 7.1 MB in 195 requests on a phone: images 4.8 MB (70), scripts 1.3 MB (47) and fonts 627 KiB (13). Under 2 MB keeps phones on slow connections fast.
About 2.0 g of CO₂ per visit
2.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.01 g of CO₂e: 241.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
19 text elements with low contrast
19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
19 links without text
19 links have no text or label, so screen readers cannot say where they go.
11 tap targets too small
11 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
7 elements hidden from screen readers can still receive keyboard focus.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (9 characters)
Your title is only 9 characters: “Unicentro”. 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.
4 H1 headlines
There are 4 <h1> headlines (“Estude na Unicentro”, “Acesso rápido” and “Câmpus Universitários”). One clear main headline is easier for people and search engines.
No XML sitemap
No XML sitemap at https://www3.unicentro.br/mapa/, so Google discovers your pages only by following links.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
343 internal links, 57 external
The homepage links to 343 pages on unicentro.br and 57 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://www3.unicentro.br/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
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.
No llms.txt
There is no https://www3.unicentro.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
15 pages without a meta description
https://www3.unicentro.br/sobre/historia, https://www3.unicentro.br/sobre/missao-visao-e-valores, https://www3.unicentro.br/visitantes, https://www3.unicentro.br/cpa, https://www3.unicentro.br/cipa and https://www3.unicentro.br/anuario and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www3.unicentro.br/eri, whose canonical is https://www3.unicentro.br/coori/en/home. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
9 pages without an H1
https://www3.unicentro.br/visitantes, https://www3.unicentro.br/cipa, https://www3.unicentro.br/anuario, https://www3.unicentro.br/pdi, https://www3.unicentro.br/noticias and https://www3.unicentro.br/vestibular and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://www3.unicentro.br/cipa, https://www3.unicentro.br/anuario, https://www3.unicentro.br/pdi and https://www3.unicentro.br/eri have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
1 page slow to respond
https://www3.unicentro.br/noticias took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 147 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 15 pages that loaded have a <title>.
Best practices
5 console errors
5 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 404 (Not Found)”).
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
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.
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 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,729 words of copy
The homepage carries about 1,729 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, Google Analytics and Microsoft Clarity.
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 unicentro.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 | Microsoft Clarity
- Hosting
- Universidade Estadual De Ponta Grossa
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on unicentro.br, including 22 speed issues, 5 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.