Website review, no card needed
iel.org.br website review
Visit site (opens in a new tab)Reviewed 23 October 202659 issues · 92 checks
This review found 59 issues worth fixing on iel.org.br, 29 of them high impact, across 92 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
57FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.2 s |
| May 9, 2026 | 5.2 s |
| May 16, 2026 | 5.0 s |
| May 23, 2026 | 5.1 s |
| May 30, 2026 | 5.1 s |
| Jun 6, 2026 | 5.0 s |
| Jun 13, 2026 | 5.1 s |
| Jun 20, 2026 | 5.2 s |
| Jun 27, 2026 | 5.1 s |
| Jul 4, 2026 | 5.1 s |
| Jul 11, 2026 | 5.1 s |
| Jul 18, 2026 | 5.0 s |
| Jul 25, 2026 | 5.1 s |
| Aug 1, 2026 | 5.0 s |
| Aug 8, 2026 | 5.0 s |
| Aug 15, 2026 | 5.0 s |
| Aug 22, 2026 | 4.9 s |
| Aug 29, 2026 | 4.9 s |
| Sep 5, 2026 | 4.9 s |
| Sep 12, 2026 | 5.2 s |
| Sep 19, 2026 | 5.8 s |
| Sep 26, 2026 | 6.2 s |
| Oct 3, 2026 | 6.4 s |
| Oct 10, 2026 | 6.6 s |
| Oct 17, 2026 | 6.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 573 ms |
| May 9, 2026 | 574 ms |
| May 16, 2026 | 533 ms |
| May 23, 2026 | 523 ms |
| May 30, 2026 | 470 ms |
| Jun 6, 2026 | 452 ms |
| Jun 13, 2026 | 470 ms |
| Jun 20, 2026 | 478 ms |
| Jun 27, 2026 | 502 ms |
| Jul 4, 2026 | 491 ms |
| Jul 11, 2026 | 498 ms |
| Jul 18, 2026 | 491 ms |
| Jul 25, 2026 | 481 ms |
| Aug 1, 2026 | 496 ms |
| Aug 8, 2026 | 503 ms |
| Aug 15, 2026 | 510 ms |
| Aug 22, 2026 | 502 ms |
| Aug 29, 2026 | 446 ms |
| Sep 5, 2026 | 427 ms |
| Sep 12, 2026 | 414 ms |
| Sep 19, 2026 | 422 ms |
| Sep 26, 2026 | 424 ms |
| Oct 3, 2026 | 397 ms |
| Oct 10, 2026 | 367 ms |
| Oct 17, 2026 | 355 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.4 s
2.7 s
4.1 s
5.4 s
6.8 s
8.2 s
9.5 s
10.9 s
Speed
Render-blocking requests
11.1 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 11.1 s.
Reduce unused CSS
8.3 s · 2.5 MBAbout 2.5 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 8.3 s faster on a phone.
Improve image delivery
1.9 s · 5.6 MB14 images could be 5.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Reduce unused JavaScript
3.2 s · 837 KiBAbout 837 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.2 s faster on a phone.
Mobile performance score: 31
31/100Your mobile performance score is 31 (desktop: 40). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.4 s
A phone's processor spends 7.4 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6,625 HTML elements
The page has 6,625 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Document request latency
850 ms · 946 KiBThe HTML itself could arrive about 850 ms sooner: redirects, a slow server response or missing compression delay everything after it.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, handtalk.me and Clarity and others), adding 5.8 MB and 1.1 s of main-thread time.
Minify CSS
780 ms · 185 KiB185 KiB could be saved by minifying CSS.
Reduce initial server response time
869 msReduce initial server response time. Google estimates savings of 869 ms on a phone.
Google Tag Manager adds 721 ms
721 msGoogle Tag Manager costs a phone 721 ms of main-thread work and 531 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 636 ms. During a long task the page ignores taps.
sistemaindustria.com.br adds 16 ms
16 mssistemaindustria.com.br costs a phone 16 ms of main-thread work and 4.7 MB 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
300 ms · 28 KiB5 files are served with short cache lifetimes, so returning visitors download them again (28 KiB).
handtalk.me adds 136 ms
136 mshandtalk.me costs a phone 136 ms of main-thread work and 417 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.
Server response: 969 ms
969 msYour server takes 969 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Duplicated JavaScript
150 ms · 7 KiB7 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
43 KiB43 KiB could be saved by minifying JavaScript.
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.
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: 8.5 s
8.5 sReal visitors wait 8.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.6 s
5.6 sReal visitors see the first content after 5.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.6 s
2.6 sReal visitors wait 2.6 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 19.9 s
19.9 sThe first text or image appears after 19.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 62.5 s
62.5 sYour largest element takes 62.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Academia de Líderes IEL”.
Speed Index: 19.9 s
19.9 sVisually, the page fills in at 19.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 99.1 s
99.1 sThe page becomes fully interactive after 99.1 s. Good is under 3.8 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: 407 ms
407 msReal visitors wait 407 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.2 s to 6.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Tap response (INP) got 37% faster for real visitors
-37%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 573 ms to 355 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 26.0 MB in 170 requests
26.0 MBYour homepage downloads 26.0 MB in 170 requests on a phone: other files 13.8 MB (53), images 6.9 MB (36) and scripts 2.0 MB (66). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 4.7 MB together. On a phone connection a single image that size takes seconds.
14 images far larger than shown
3.2 MB14 images are downloaded at several times the size a phone draws them, for example 71eb8d24-9984-0145-5bd2-2557e3b4e81c at 1,920 px wide, shown at 390 px. Resized copies would save about 3.2 MB.
18 images in older formats
18 images (5.8 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.
14 images below the first screen load straight away
14 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 7.4 g of CO₂ per visit
7.37 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.37 g of CO₂e: 884.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must be contained by particular parents (5 elements)
Certain ARIA roles must be contained by particular parents: 5 elements on the page fail this check, rated critical by axe-core.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
52 text elements with low contrast
52 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
<svg> elements with an img or image role must have alternative text (1 element)
<svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 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.
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.
1 checks passed
41 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: 41 passed and 8 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “Soluções do IEL para Você: Estágios, Liderança e Inovação - IEL - Sistema Indústria”.
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, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at http://iel.org.br:80/sitemap.xml, so Google discovers your pages only by following links.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
One H1 headline
Your <h1> is empty.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
20 internal links, 16 external
The homepage links to 20 pages on iel.org.br and 16 external pages.
3 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Descubra as oportunidades do IEL para o seu desenvolvimento. Acesse vagas de estágio, bolsas de inovação e trilhas de e…”.
Canonical URL set
The canonical URL is https://iel.portaldaindustria.com.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://iel.portaldaindustria.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 (1,193 words), so crawlers that don't run JavaScript still read it.
Other pages
9 pages without a meta description
https://iel.portaldaindustria.com.br/w/educacao-executiva-global-edicao-mit-2027, https://iel.portaldaindustria.com.br/w/para-voce/formacao-para-novos-lideres, https://iel.portaldaindustria.com.br/w/para-voce/academia-de-lideres-iel/lideran%C3%A7a-feminina, https://iel.portaldaindustria.com.br/w/para-voce/academia-de-lideres-iel/geracao-z-nova-lideranca, https://iel.portaldaindustria.com.br/w/para-voce/academia-de-lideres-iel/gente-gest%C3%A3o and https://iel.portaldaindustria.com.br/w/para-voce/academia-de-lideres-iel/lideran%C3%A7a-futuro-industria and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://iel.portaldaindustria.com.br/para-voce/academia-de-lideres-iel has no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://iel.portaldaindustria.com.br/w/para-voce/academia-de-lideres-iel/educacao-executiva-global-china, https://iel.portaldaindustria.com.br/w/programa-lidera-recebe-thirza-reis, https://iel.portaldaindustria.com.br/w/para-voce/academia-de-lideres-iel/gente-gest%C3%A3o, https://iel.portaldaindustria.com.br/w/para-voce/academia-de-lideres-iel/lideran%C3%A7a-futuro-industria and https://iel.portaldaindustria.com.br/institucional/premio-iel took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.
5 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.
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://iel.portaldaindustria.com.br/para-voce.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Unsafe attempt to load URL https://liferay.sistemaindustria.com.br/documents/20121/2248354/spritemap.svg from frame wit…”.
2 checks passed
Tap targets are thumb-sized
23 of 26 tappable elements near the top are at least 24 px.
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 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,279 words of copy
The homepage carries about 1,279 words of visible text.
2 checks passed
2 short forms
2 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 1 more (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.
11 cookies set on arrival
11Opening the homepage sets 11 cookies, 1 of them by other companies (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 iel.org.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 59 issues on iel.org.br, including 28 speed issues, 6 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.