Website review, no card needed
supportautomacao.com.br website review
Visit site (opens in a new tab)Reviewed 25 October 202642 issues · 82 checks
This review found 42 issues worth fixing on supportautomacao.com.br, 16 of them high impact, across 82 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
71CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
0.9 s
1.4 s
1.8 s
2.3 s
2.7 s
3.2 s
3.6 s
Speed
Use efficient cache lifetimes
20.9 s · 9.0 MB79 files are served with short cache lifetimes, so returning visitors download them again (9.0 MB).
Improve image delivery
8.2 s · 4.5 MB9 images could be 4.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.2 s faster on a phone.
Reduce unused JavaScript
3.0 s · 535 KiBAbout 535 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 49). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 172 KiBAbout 172 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.
Render-blocking requests
900 ms16 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
7 third-party services on the page
7 third-party services load with your homepage (YouTube, Salesforce.com and Other Google APIs/SDKs and others), adding 1.1 MB and 389 ms of main-thread time.
YouTube adds 337 ms
337 msYouTube costs a phone 337 ms of main-thread work and 971 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.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 121 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 597 ms of it running JavaScript. That is comfortably low.
Server response: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 34.9 s
34.9 sYour largest element takes 34.9 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.9 s
34.9 sThe page becomes fully interactive after 34.9 s. Good is under 3.8 s.
First Contentful Paint: 7.3 s
7.3 sThe first text or image appears after 7.3 s on a phone. Good is under 1.8 s.
Speed Index: 11.8 s
11.8 sVisually, the page fills in at 11.8 s (Speed Index). Good is under 3.4 s.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 114 ms
114 msScripts block the page for only 114 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 12.4 MB in 105 requests
12.4 MBYour homepage downloads 12.4 MB in 105 requests on a phone: images 11.1 MB (47), scripts 1,023 KiB (33) and stylesheets 153 KiB (13). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 9.3 MB together. On a phone connection a single image that size takes seconds.
4 images far larger than shown
1.1 MB4 images are downloaded at several times the size a phone draws them, for example nova-thumb-24-07-video.png at 1,167 px wide, shown at 312 px. Resized copies would save about 1.1 MB.
6 images in older formats
6 images (4.3 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.
8 images below the first screen load straight away
8 images further down the page (3.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.5 g of CO₂ per visit
3.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.51 g of CO₂e: 421.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
21 text elements with low contrast
21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
32 images without alt text
32 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (31 elements)
All page content should be contained by landmarks: 31 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
3 links without text
3 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.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
31 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 7 failed. 1 more 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.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
40 internal links, 13 external
The homepage links to 40 pages on supportautomacao.com.br and 13 external pages.
6 checks passed
Meta description: 102 characters
Your meta description is 102 characters: “A Support Automação Industrial é referência em soluções com alta maturidade tecnológica para empresas.”.
Title: 30 characters
Your title is a healthy 30 characters: “Support - Automação Industrial”.
Canonical URL set
The canonical URL is https://supportautomacao.com.br/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://supportautomacao.com.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://supportautomacao.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 (538 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages without a meta description
https://supportautomacao.com.br/industria-4-0/analiticos, https://supportautomacao.com.br/produtos/acionamento-de-motores, https://supportautomacao.com.br/servicos/clean-service, https://supportautomacao.com.br/rok-technology-movimenta-goiania-com-inovacao-industrial, https://supportautomacao.com.br/support-e-sonepar-um-novo-capitulo-comeca-agora and https://supportautomacao.com.br/uma-nova-marca-para-um-novo-momento and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://supportautomacao.com.br/a-support, https://supportautomacao.com.br/industria-4-0/analiticos, https://supportautomacao.com.br/produtos/acionamento-de-motores, https://supportautomacao.com.br/servicos/clean-service, https://supportautomacao.com.br/cases and https://supportautomacao.com.br/blog and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://supportautomacao.com.br/blog and https://supportautomacao.com.br/contato have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage 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
3 broken images
3 images failed to load on a phone, for example https://supportautomacao.com.br/wp-content/uploads/logo-case-1-min.webp.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 small tap targets
2 of 6 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
No HTML doctype
The page has no <!DOCTYPE html>, so browsers render it in quirks mode.
6 distorted images
6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 380 words of copy
The homepage carries about 380 words of visible text.
2 checks passed
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Ads (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.
1 cookie set on arrival
1Opening the homepage sets 1 cookie, 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.
12 other companies contacted
Loading the homepage contacts 12 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 supportautomacao.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on supportautomacao.com.br, including 13 speed issues, 2 SEO issues 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.