Website review, no card needed
uniitalo.com.br website review
Visit site (opens in a new tab)Reviewed 4 November 202645 issues · 89 checks
This review found 45 issues worth fixing on uniitalo.com.br, 18 of them high impact, across 89 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
61DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 260 ms |
| May 23, 2026 | 271 ms |
| May 30, 2026 | 285 ms |
| Jun 6, 2026 | 300 ms |
| Jun 13, 2026 | 310 ms |
| Jun 20, 2026 | 314 ms |
| Jun 27, 2026 | 314 ms |
| Jul 4, 2026 | 313 ms |
| Jul 11, 2026 | 305 ms |
| Jul 18, 2026 | 298 ms |
| Jul 25, 2026 | 302 ms |
| Aug 1, 2026 | 312 ms |
| Aug 8, 2026 | 338 ms |
| Aug 15, 2026 | 358 ms |
| Aug 22, 2026 | 365 ms |
| Aug 29, 2026 | 365 ms |
| Sep 5, 2026 | 360 ms |
| Sep 12, 2026 | 356 ms |
| Sep 19, 2026 | 354 ms |
| Sep 26, 2026 | 360 ms |
| Oct 3, 2026 | 367 ms |
| Oct 10, 2026 | 377 ms |
| Oct 17, 2026 | 382 ms |
| Oct 24, 2026 | 388 ms |
| Oct 31, 2026 | 382 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
0.6 s
1.3 s
1.9 s
2.5 s
3.2 s
3.8 s
4.5 s
5.1 s
Speed
Improve image delivery
17.6 s · 3.5 MB18 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 17.6 s faster on a phone.
Use efficient cache lifetimes
14.3 s · 2.6 MB91 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).
Reduce unused JavaScript
3.1 s · 642 KiBAbout 642 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.
Render-blocking requests
1.3 s19 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
450 ms · 43 KiBAbout 43 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.
Facebook adds 223 ms
223 msFacebook costs a phone 223 ms of main-thread work and 340 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: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 1.2 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 (Facebook, TikTok and coretava.com and others), adding 660 KiB and 408 ms of main-thread time.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 160 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 7 KiB7 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 3 KiB3 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
27 KiB27 KiB JavaScript is shipped twice across bundles.
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.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 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: 117.3 s
117.3 sYour largest element takes 117.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 118.0 s
118.0 sThe page becomes fully interactive after 118.0 s. Good is under 3.8 s.
Speed Index: 11.6 s
11.6 sVisually, the page fills in at 11.6 s (Speed Index). Good is under 3.4 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.
Real-user INP: 259 ms
259 msReal visitors wait 259 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 45% slower for real visitors
+45%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 260 ms to 382 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 825 ms
825 msReal visitors wait 825 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 590 ms
590 msScripts block taps and scrolling for 590 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.186
0.186The layout shifts by 0.186 while loading, so content jumps under the reader's thumb. Good is under 0.1.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
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.
Images and page weight
Page weight: 23.5 MB in 159 requests
23.5 MBYour homepage downloads 23.5 MB in 159 requests on a phone: images 21.2 MB (45), scripts 1.8 MB (55) and fonts 381 KiB (5). Under 2 MB keeps phones on slow connections fast.
12 images over 500 KB
12 images weigh 17.2 MB together. On a phone connection a single image that size takes seconds.
22 images far larger than shown
8.4 MB22 images are downloaded at several times the size a phone draws them, for example fundo-3.png at 1,600 px wide, shown at 390 px. Resized copies would save about 8.4 MB.
37 images in older formats
37 images (20.9 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.
1 image below the first screen load straight away
1 image further down the page (44 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 6.7 g of CO₂ per visit
6.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.65 g of CO₂e: 798.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
19 images without alt text
19 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (87 characters)
Your title is 87 characters, so Google will cut it off around 60: “UNI ITALO | Graduação, Pós-graduação e Cursos Livres - Presencial, Semipresencial e EAD”.
Meta description is short (9 characters)
Your meta description is only 9 characters: “UNI ITALO”. 70 to 160 characters is enough to sell the click.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
69 internal links, 38 external
The homepage links to 69 pages on uniitalo.com.br and 38 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Sua próxima oportunidade começa aqui. Vagas, estágios e programas de trainee curados para alunos e ex-alunos.”.
Canonical URL set
The canonical URL is https://uniitalo.com.br/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://uniitalo.com.br/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://uniitalo.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 (753 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages share a meta description
https://uniitalo.com.br/category/graduacao, https://uniitalo.com.br/category/pos-graduacao, https://uniitalo.com.br/category/cursos-livres, https://uniitalo.com.br/category/portador-de-diploma, https://uniitalo.com.br/campus and https://uniitalo.com.br/servicos-e-oportunidades and 8 others use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://uniitalo.com.br/campus, https://uniitalo.com.br/servicos-e-oportunidades, https://uniitalo.com.br/reitoria, https://uniitalo.com.br/nucleo-de-estudos-e-pesquisas, https://uniitalo.com.br/revistas and https://uniitalo.com.br/biblioteca have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 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.
Every page has a meta description
All 14 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 14 pages that loaded have a <title>.
Best practices
9 small tap targets
9 of 31 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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_AUTHORITY_INVALID”.
No HTML doctype
The page has no <!DOCTYPE html>, so browsers render it in quirks mode.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 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 302 words of copy
The homepage carries about 302 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, Hotjar, LinkedIn Insight and Cloudflare Web Analytics.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 2 mores (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
24 other companies contacted
Loading the homepage contacts 24 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 uniitalo.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 © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on uniitalo.com.br, including 20 speed issues, 2 SEO issues and 6 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.