Website review, no card needed
ibmec.br website review
Visit site (opens in a new tab)Reviewed 31 October 202641 issues · 88 checks
This review found 41 issues worth fixing on ibmec.br, 22 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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
52FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.7 s |
| May 16, 2026 | 5.5 s |
| May 23, 2026 | 5.0 s |
| May 30, 2026 | 4.2 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 416 ms |
| May 16, 2026 | 419 ms |
| May 23, 2026 | 430 ms |
| May 30, 2026 | 442 ms |
| Jun 6, 2026 | 462 ms |
| Jun 13, 2026 | 466 ms |
| Jun 20, 2026 | 461 ms |
| Jun 27, 2026 | 451 ms |
| Jul 4, 2026 | 437 ms |
| Jul 11, 2026 | 428 ms |
| Jul 18, 2026 | 421 ms |
| Jul 25, 2026 | 417 ms |
| Aug 1, 2026 | 418 ms |
| Aug 8, 2026 | 421 ms |
| Aug 15, 2026 | 421 ms |
| Aug 22, 2026 | 420 ms |
| Aug 29, 2026 | 412 ms |
| Sep 5, 2026 | 399 ms |
| Sep 12, 2026 | 393 ms |
| Sep 19, 2026 | 388 ms |
| Sep 26, 2026 | 392 ms |
| Oct 3, 2026 | 397 ms |
| Oct 10, 2026 | 406 ms |
| Oct 17, 2026 | 411 ms |
| Oct 24, 2026 | 420 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
Reduce unused JavaScript
1.3 s · 1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Mobile performance score: 19
19/100Your mobile performance score is 19. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.3 s
A phone's processor spends 6.3 s on main-thread work while loading, 4.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
500 ms · 10.6 MB48 files are served with short cache lifetimes, so returning visitors download them again (10.6 MB).
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Facebook and TikTok and others), adding 1.9 MB and 1.2 s of main-thread time.
YouTube adds 422 ms
422 msYouTube costs a phone 422 ms of main-thread work and 1,007 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.
1,559 HTML elements
The page has 1,559 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
150 ms · 211 KiB10 images could be 211 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 236 ms. During a long task the page ignores taps.
Reduce unused CSS
169 KiBAbout 169 KiB of CSS is downloaded but never applied on this page.
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
43 KiBPolyfills for old browsers add 43 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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 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.
Real-user LCP: 4.4 s
4.4 sReal visitors wait 4.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.92
0.92For real visitors the layout shifts by 0.92 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 9.7 s
9.7 sYour largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 34.6 s
34.6 sThe page becomes fully interactive after 34.6 s. Good is under 3.8 s.
Cumulative Layout Shift: 1.119
1.119The layout shifts by 1.119 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Real-user INP: 483 ms
483 msReal visitors wait 483 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 416 ms to 420 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Largest content (LCP) got 46% faster for real visitors
-46%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.7 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 15.0 MB in 209 requests
15.0 MBYour homepage downloads 15.0 MB in 209 requests on a phone: media 9.6 MB (1), scripts 4.3 MB (89) and images 501 KiB (36). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
banner_hackton_ibmec_mobile_a3114ed96c.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image in older formats
1 image (101 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 4.2 g of CO₂ per visit
4.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.25 g of CO₂e: 509.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
14 buttons without a name
14 buttons have no accessible name, so screen readers announce just “button”.
Images must have alternative text (9 elements)
Images must have alternative text: 9 elements on the page fail this check, rated critical by axe-core.
Orphan list items
Some list items are not inside a list.
Elements must only use permitted ARIA attributes (2 elements)
Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
5 links without text
5 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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 1 problem
Structured data found (Organization, SoftwareApplication and VideoObject) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
108 internal links, 26 external
The homepage links to 108 pages on ibmec.br and 26 external pages.
6 checks passed
Meta description: 119 characters
Your meta description is 119 characters: “Ingresse no Ibmec com sua nota do ENEM. Graduação e pós-graduação de excelência em um ensino premium e focado no aluno.”.
Title: 38 characters
Your title is a healthy 38 characters: “Graduação com sua nota do ENEM | Ibmec”.
Canonical URL set
The canonical URL is https://www.ibmec.br/.
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://www.ibmec.br/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
44%The HTML your server sends has 338 of the 771 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.ibmec.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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Other pages
1 page without an H1
https://www.ibmec.br/estude-no-ibmec/tech has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.ibmec.br/estude-no-ibmec/nosso-mestrado took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 46 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 15 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 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=259001389&Ver=2&mid=8ece4acf-1741-47ee-9452-e477d652b2df&bo=1&sid=37c5f060d52611f18aa10b8f6edbb523&vid=37c615d0d52611f198819f08abdd7ff9&vids=1&msclkid=N&pi=918639831&l.
10 small tap targets
10 of 42 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 third-party cookies
6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 771 words of copy
The homepage carries about 771 words of visible text.
1 checks passed
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 6 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
26 cookies set on arrival
26Opening the homepage sets 26 cookies, 2 of them by other companies (measured from a US location before any click).
54 other companies contacted
Loading the homepage contacts 54 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 ibmec.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Hosting
- CloudFront
Company
- Founded
- 1970
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 ibmec.br, including 19 speed issues, 2 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.