Website review, no card needed
ibccrim.org.br website review
Visit site (opens in a new tab)Reviewed 27 October 202646 issues · 89 checks
This review found 46 issues worth fixing on ibccrim.org.br, 23 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
64DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.1 s |
| May 16, 2026 | 4.2 s |
| May 23, 2026 | 4.4 s |
| May 30, 2026 | 4.2 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 4.0 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.3 s |
| Jul 11, 2026 | 4.5 s |
| Jul 18, 2026 | 4.7 s |
| Jul 25, 2026 | 4.5 s |
| Aug 1, 2026 | 4.6 s |
| Aug 8, 2026 | 4.5 s |
| Aug 15, 2026 | 4.5 s |
| Aug 22, 2026 | 4.4 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 4.3 s |
| Sep 12, 2026 | 4.2 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 4.2 s |
| Oct 10, 2026 | 4.3 s |
| Oct 17, 2026 | 4.6 s |
| Oct 24, 2026 | 4.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 213 ms |
| May 16, 2026 | 206 ms |
| May 23, 2026 | 211 ms |
| May 30, 2026 | 210 ms |
| Jun 6, 2026 | 219 ms |
| Jun 13, 2026 | 222 ms |
| Jun 20, 2026 | 221 ms |
| Jun 27, 2026 | 234 ms |
| Jul 4, 2026 | 231 ms |
| Jul 11, 2026 | 233 ms |
| Jul 18, 2026 | 234 ms |
| Jul 25, 2026 | 225 ms |
| Aug 1, 2026 | 229 ms |
| Aug 8, 2026 | 226 ms |
| Aug 15, 2026 | 222 ms |
| Aug 22, 2026 | 222 ms |
| Aug 29, 2026 | 220 ms |
| Sep 5, 2026 | 230 ms |
| Sep 12, 2026 | 227 ms |
| Sep 19, 2026 | 237 ms |
| Sep 26, 2026 | 243 ms |
| Oct 3, 2026 | 239 ms |
| Oct 10, 2026 | 247 ms |
| Oct 17, 2026 | 265 ms |
| Oct 24, 2026 | 258 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.7 s
3.4 s
5.1 s
6.8 s
8.5 s
10.2 s
11.9 s
13.6 s
Speed
Use efficient cache lifetimes
7.6 s · 1.3 MB64 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).
Reduce unused JavaScript
4.2 s · 796 KiBAbout 796 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.
Render-blocking requests
3.7 s42 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.7 s.
Google Tag Manager adds 1.3 s
1.3 sGoogle Tag Manager costs a phone 1.3 s of main-thread work and 938 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: 33
33/100Your mobile performance score is 33 (desktop: 46). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.3 s
A phone's processor spends 7.3 s on main-thread work while loading, 3.6 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 (Google Tag Manager, TikTok and Facebook and others), adding 1.5 MB and 2.5 s of main-thread time.
Improve image delivery
600 ms · 2.0 MB10 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused CSS
750 ms · 115 KiBAbout 115 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 586 ms. During a long task the page ignores taps.
Facebook adds 350 ms
350 msFacebook costs a phone 350 ms of main-thread work and 225 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.
TikTok adds 354 ms
354 msTikTok costs a phone 354 ms of main-thread work and 160 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.
RD Station adds 285 ms
285 msRD Station costs a phone 285 ms of main-thread work and 135 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.
Legacy JavaScript
100 ms · 21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
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: 172 ms
172 msYour server sent the HTML in 172 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: 5.6 s
5.6 sReal visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.1 s
2.1 sReal visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 33.8 s
33.8 sYour largest element takes 33.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Desde 1992 formando o pensamento crítico em Ciências Crimin…”.
Time to Interactive: 34.7 s
34.7 sThe page becomes fully interactive after 34.7 s. Good is under 3.8 s.
Speed Index: 14.7 s
14.7 sVisually, the page fills in at 14.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Real-user INP: 279 ms
279 msReal visitors wait 279 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 213 ms to 258 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.1 s to 4.6 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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.8 MB in 161 requests
6.8 MBYour homepage downloads 6.8 MB in 161 requests on a phone: images 3.9 MB (25), scripts 2.0 MB (62) and fonts 621 KiB (3). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.
11 images in older formats
11 images (3.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 far larger than shown
23 KiB1 image is downloaded at several times the size a phone draws it, for example logo.png at 390 px wide, shown at 111 px. Resized copies would save about 23 KiB.
1 image below the first screen load straight away
1 image further down the page (36 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.9 g of CO₂ per visit
1.93 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.93 g of CO₂e: 231.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails 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.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 25 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
79 internal links, 8 external
The homepage links to 79 pages on ibccrim.org.br and 8 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Inicio”.
Title: 51 characters
Your title is a healthy 51 characters: “Inicio - Instituto Brasileiro de Ciências Criminais”.
Canonical URL set
The canonical URL is https://ibccrim.org.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://ibccrim.org.br/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://ibccrim.org.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.
3 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (447 words), so crawlers that don't run JavaScript still read it.
Other pages
9 pages without a meta description
https://ibccrim.org.br/seminario, https://ibccrim.org.br/publicacoes, https://ibccrim.org.br/biblioteca, https://ibccrim.org.br/noticias, https://ibccrim.org.br/contatos and https://ibccrim.org.br/associe-se and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://ibccrim.org.br/publicacoes, https://ibccrim.org.br/contatos and https://ibccrim.org.br/associe-se have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://ibccrim.org.br/seminario, https://ibccrim.org.br/publicacoes, https://ibccrim.org.br/biblioteca and https://ibccrim.org.br/noticias took over 3 s to send their HTML from our server.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
10 pages of 12 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 10 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=97045705&tm=gtm002&Ver=2&mid=44f54bc9-e6bb-4a0a-8715-513c22b5bc52&bo=1&sid=c0ed5800d1ae11f1a1dc1d5560d3f7f0&vid=c0ed8530d1ae11f1bed65bce1fa7eb9c&vids=1&msclkid=N>m_t.
3 small tap targets
3 of 8 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 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 271 words of copy
The homepage carries about 271 words of visible text.
3 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, LinkedIn Insight and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 3 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.
17 cookies set on arrival
17Opening the homepage sets 17 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.
30 other companies contacted
Loading the homepage contacts 30 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 ibccrim.org.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 Tag Manager
- Hosting
- Servicos de Internet Ltda
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on ibccrim.org.br, including 24 speed issues, 1 SEO issue and 5 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.