Website review, no card needed
fiepe.org.br website review
Visit site (opens in a new tab)Reviewed 19 October 202647 issues · 85 checks
This review found 47 issues worth fixing on fiepe.org.br, 23 of them high impact, across 85 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.3 s |
| May 9, 2026 | 5.2 s |
| May 16, 2026 | 5.1 s |
| May 23, 2026 | 5.0 s |
| May 30, 2026 | 5.0 s |
| Jun 6, 2026 | 5.1 s |
| Jun 13, 2026 | 5.1 s |
| Jun 20, 2026 | 5.1 s |
| Jun 27, 2026 | 5.0 s |
| Jul 4, 2026 | 5.0 s |
| Jul 11, 2026 | 5.1 s |
| Jul 18, 2026 | 5.2 s |
| Jul 25, 2026 | 5.2 s |
| Aug 1, 2026 | 5.2 s |
| Aug 8, 2026 | 5.0 s |
| Aug 15, 2026 | 5.1 s |
| Aug 22, 2026 | 5.5 s |
| Aug 29, 2026 | 5.6 s |
| Sep 5, 2026 | 5.7 s |
| Sep 12, 2026 | 5.9 s |
| Sep 19, 2026 | 5.7 s |
| Sep 26, 2026 | 5.8 s |
| Oct 3, 2026 | 5.9 s |
| Oct 10, 2026 | 6.1 s |
| Oct 17, 2026 | 6.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 84 ms |
| May 9, 2026 | 83 ms |
| May 16, 2026 | 85 ms |
| May 23, 2026 | 88 ms |
| May 30, 2026 | 88 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 84 ms |
| Jun 27, 2026 | 85 ms |
| Jul 4, 2026 | 87 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 89 ms |
| Jul 25, 2026 | 88 ms |
| Aug 1, 2026 | 88 ms |
| Aug 8, 2026 | 87 ms |
| Aug 15, 2026 | 87 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 87 ms |
| Sep 5, 2026 | 88 ms |
| Sep 12, 2026 | 91 ms |
| Sep 19, 2026 | 89 ms |
| Sep 26, 2026 | 89 ms |
| Oct 3, 2026 | 95 ms |
| Oct 10, 2026 | 100 ms |
| Oct 17, 2026 | 104 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
Improve image delivery
3.6 s · 3.6 MB12 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.6 s faster on a phone.
Render-blocking requests
3.1 s37 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
Mobile performance score: 36
36/100Your mobile performance score is 36 (desktop: 52). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1,024 KiB and 860 ms of main-thread time.
Reduce unused JavaScript
300 ms · 488 KiBAbout 488 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 470 ms
470 msGoogle Tag Manager costs a phone 470 ms of main-thread work and 639 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.
Reduce unused CSS
450 ms · 67 KiBAbout 67 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.
Use efficient cache lifetimes
287 KiB9 files are served with short cache lifetimes, so returning visitors download them again (287 KiB).
Facebook adds 261 ms
261 msFacebook costs a phone 261 ms of main-thread work and 245 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.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 969 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 174 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 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.
1 checks passed
Server response: 11 ms
11 msYour server sent the HTML in 11 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: 6.6 s
6.6 sReal visitors wait 6.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.7 s
5.7 sReal visitors see the first content after 5.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 4.7 s
4.7 sReal visitors wait 4.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 9.5 s
9.5 sYour largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ACESSE”.
Time to Interactive: 12.3 s
12.3 sThe page becomes fully interactive after 12.3 s. Good is under 3.8 s.
Speed Index: 7.5 s
7.5 sVisually, the page fills in at 7.5 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.301
0.301The layout shifts by 0.301 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 84 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 432 ms
432 msScripts block taps and scrolling for 432 ms in total while the page loads. Good is under 200 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.3 s to 6.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 106 ms
106 msReal visitors wait 106 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 11.0 MB in 104 requests
11.0 MBYour homepage downloads 11.0 MB in 104 requests on a phone: images 9.6 MB (32), scripts 1.1 MB (34) and fonts 138 KiB (2). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
49 KiB1 image is downloaded at several times the size a phone draws it, for example Marcas Sistema FIEPE -_branca.png at 3,334 px wide, shown at 230 px. Resized copies would save about 49 KiB.
2 images in older formats
2 images (120 KiB) 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.
About 3.1 g of CO₂ per visit
3.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.11 g of CO₂e: 373.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
29 buttons without a name
29 buttons have no accessible name, so screen readers announce just “button”.
22 tap targets too small
22 tap targets are too small or too close together to hit reliably with a finger.
Orphan list items
Some list items are not inside a list.
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
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.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 9 failed. 5 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.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (4 characters)
Your title is only 4 characters: “Home”. 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.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
82 internal links, 49 external
The homepage links to 82 pages on fiepe.org.br and 49 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://fiepe.org.br/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://fiepe.org.br/sitemap.xml.
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://fiepe.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.
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 (759 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://fiepe.org.br/para-sindicato, https://fiepe.org.br/para-sindicato/defesa-da-industria, https://fiepe.org.br/para-sindicato/sindicatos-associados-e-convencao-coletiva, https://fiepe.org.br/para-sindicato/manual-dos-sindicatos, https://fiepe.org.br/para-sindicato/relacao-de-feriados and https://fiepe.org.br/para-sindicato/contribuicao-sindical 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://fiepe.org.br/para-sindicato/manual-dos-sindicatos, whose canonical is https://fiepe.org.br/para-sindicato/conselhos-tematicos-comites. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
14 pages without an H1
https://fiepe.org.br/para-sindicato, https://fiepe.org.br/para-sindicato/defesa-da-industria, https://fiepe.org.br/para-sindicato/sindicatos-associados-e-convencao-coletiva, https://fiepe.org.br/para-sindicato/manual-dos-sindicatos, https://fiepe.org.br/para-sindicato/relacao-de-feriados and https://fiepe.org.br/para-sindicato/contribuicao-sindical and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://fiepe.org.br/para-sindicato, https://fiepe.org.br/para-sindicato/defesa-da-industria, https://fiepe.org.br/para-sindicato/sindicatos-associados-e-convencao-coletiva and https://fiepe.org.br/para-sindicato/manual-dos-sindicatos took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 32 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
12 small tap targets
12 of 43 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.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
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 436 words of copy
The homepage carries about 436 words of visible text.
3 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics, Meta Pixel and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 9 phone links and 9 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
15 other companies contacted
Loading the homepage contacts 15 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 fiepe.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 Analytics | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on fiepe.org.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.