Website review, no card needed
estaf.com.br website review
Visit site (opens in a new tab)Reviewed 1 November 202644 issues · 88 checks
This review found 44 issues worth fixing on estaf.com.br, 21 of them high impact, across 88 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
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 162 ms |
| May 16, 2026 | 144 ms |
| May 23, 2026 | 108 ms |
| May 30, 2026 | 124 ms |
| Jun 6, 2026 | 134 ms |
| Jun 13, 2026 | 157 ms |
| Jun 20, 2026 | 180 ms |
| Jun 27, 2026 | 177 ms |
| Jul 4, 2026 | 180 ms |
| Jul 11, 2026 | 157 ms |
| Jul 18, 2026 | 161 ms |
| Jul 25, 2026 | 157 ms |
| Aug 1, 2026 | 125 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 152 ms |
| Aug 29, 2026 | 178 ms |
| Sep 5, 2026 | 202 ms |
| Sep 12, 2026 | 197 ms |
| Sep 19, 2026 | 146 ms |
| Sep 26, 2026 | 136 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 119 ms |
| Oct 17, 2026 | 119 ms |
| Oct 24, 2026 | 115 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
12.9 s · 3.8 MB5 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 12.9 s faster on a phone.
Reduce unused JavaScript
7.2 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.2 s faster on a phone.
Use efficient cache lifetimes
2.7 s · 841 KiB75 files are served with short cache lifetimes, so returning visitors download them again (841 KiB).
Render-blocking requests
2.6 s53 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Mobile performance score: 27
27/100Your mobile performance score is 27. 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, Google CDN and RD Station and others), adding 2.1 MB and 989 ms of main-thread time.
Reduce unused CSS
450 ms · 101 KiBAbout 101 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.
Font display
500 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).
Google Tag Manager adds 411 ms
411 msGoogle Tag Manager costs a phone 411 ms of main-thread work and 589 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: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 265 ms
265 msGoogle CDN costs a phone 265 ms of main-thread work and 742 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,782 HTML elements
The page has 1,782 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Cloudflare CDN adds 46 ms
46 msCloudflare CDN costs a phone 46 ms of main-thread work and 330 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.
Minify JavaScript
150 ms · 25 KiB25 KiB could be saved by minifying JavaScript.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 131 ms. During a long task the page ignores taps.
Legacy JavaScript
36 KiBPolyfills for old browsers add 36 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: 336 ms
336 msYour server sent the HTML in 336 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 CLS: 0.65
0.65For real visitors the layout shifts by 0.65 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 36.4 s
36.4 sYour largest element takes 36.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Há 50 anos elevando grandes projetos As plataformas aéreas …”.
Time to Interactive: 38.3 s
38.3 sThe page becomes fully interactive after 38.3 s. Good is under 3.8 s.
Speed Index: 11.2 s
11.2 sVisually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.513
0.513The layout shifts by 0.513 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 361 ms
361 msScripts block taps and scrolling for 361 ms in total while the page loads. Good is under 200 ms.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 144 ms
144 msReal visitors wait 144 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 162 ms to 115 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 7.9 MB in 135 requests
7.9 MBYour homepage downloads 7.9 MB in 135 requests on a phone: images 4.7 MB (21), scripts 2.0 MB (54) and fonts 593 KiB (11). Under 2 MB keeps phones on slow connections fast.
About 2.2 g of CO₂ per visit
2.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.25 g of CO₂e: 269.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
14 form fields without a label
14 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
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
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is short (46 characters)
Your meta description is only 46 characters: “Eleve a qualidade na entrega dos seus projetos”. 70 to 160 characters is enough to sell the click.
70 internal links, 8 external
The homepage links to 70 pages on estaf.com.br and 8 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Há 50 anos elevando grandes projetos”.
Title: 55 characters
Your title is a healthy 55 characters: “Estaf Equipamentos | Aluguel de Plataformas Elevatórias”.
Canonical URL set
The canonical URL is https://estaf.com.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://estaf.com.br/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://estaf.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.
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 (1,154 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages share a title
/, https://estaf.com.br/plataformas-elevatorias, https://estaf.com.br/mapa-de-atuacao, https://estaf.com.br/produtos, https://estaf.com.br/a-estaf and https://estaf.com.br/responsabilidade-social and 6 others all use the title “Estaf Equipamentos | Aluguel de Plataformas Elevatórias”. Search engines can't tell which page to show for a search, so each competes with the others.
11 pages share a meta description
https://estaf.com.br/plataformas-elevatorias, https://estaf.com.br/mapa-de-atuacao, https://estaf.com.br/produtos, https://estaf.com.br/a-estaf, https://estaf.com.br/responsabilidade-social and https://estaf.com.br/treinamento and 5 others use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://estaf.com.br/mapa-de-atuacao, https://estaf.com.br/produtos, https://estaf.com.br/a-estaf, https://estaf.com.br/responsabilidade-social, https://estaf.com.br/protecao-equipamento and https://estaf.com.br/orcamento 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 26 found) and read each the way a search engine does.
5 checks passed
Linked pages load
11 pages of 15 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.
Every page has a meta description
All 11 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
7 of 8 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.
A 8-field form
Your longest form asks for 8 fields (4 required). Every extra field lowers completion.
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 702 words of copy
The homepage carries about 702 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
17 other companies contacted
Loading the homepage contacts 17 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 estaf.com.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
- Hosting
- Hostinger
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on estaf.com.br, including 25 speed issues, 1 SEO issue 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.