saetowers.com website review

2 third-party services load with your homepage (Wix and Sentry), adding 9.0 MB and 656 ms of main-thread time.

Wix costs a phone 635 ms of main-thread work and 9.0 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.

Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.

About 147 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.

A phone's processor spends 2.3 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

29 KiB JavaScript is shipped twice across bundles.

About 14 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The page becomes fully interactive after 8.9 s. Good is under 3.8 s.

Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

Visually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 1.8 s on a phone. Good is under 1.8 s.

5 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 99 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 13.9 MB in 237 requests on a phone: media 10.8 MB (1), other files 1.0 MB (93) and scripts 978 KiB (101). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 3.93 g of CO₂e: 471.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

6 buttons have no accessible name, so screen readers announce just “button”.

13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

4 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

Your title is 78 characters, so Google will cut it off around 60: “SAE Towers - DO PROJETO À EXECUÇÃO, MUITO MAIS QUE ENERGIA, TRANSMITINDO VIDA.”.

There are 6 <h1> headlines (“Torres de Energia”, “Pórticos e suportes para equipamentos” and “Torres de telecomunicações”). One clear main headline is easier for people and search engines.

Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 79 pages on saetowers.com and 7 external pages.

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.

https://www.saetowers.com/beneficios is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.saetowers.com/quem-somos, https://www.saetowers.com/hello-happiness, https://www.saetowers.com/sustentabilidade-e-social, https://www.saetowers.com/politicas, https://www.saetowers.com/pessoas-e-talentos and https://www.saetowers.com/dia-a-dia and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.saetowers.com/quem-somos, https://www.saetowers.com/hello-happiness, https://www.saetowers.com/sustentabilidade-e-social, https://www.saetowers.com/politicas, https://www.saetowers.com/pessoas-e-talentos and https://www.saetowers.com/dia-a-dia and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.saetowers.com/sustentabilidade-e-social, https://www.saetowers.com/dia-a-dia, https://www.saetowers.com/fale-conosco and https://www.saetowers.com/midia 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.

We fetched 9 pages linked from your homepage and read each the way a search engine does.

6 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “globalThis.defineStrictProperty is not a function”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 450 words of visible text.

Opening the homepage sets 6 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.