tecnisa.com.br website review

About 4.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.9 s faster on a phone.

68 files are served with short cache lifetimes, so returning visitors download them again (9.5 MB).

YouTube costs a phone 2.3 s of main-thread work and 7.7 MB 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.

About 295 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.

Your mobile performance score is 14. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 9.3 MB and 3.2 s of main-thread time.

13 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 900 ms).

Google Tag Manager costs a phone 417 ms of main-thread work and 518 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 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.

handtalk.me costs a phone 70 ms of main-thread work and 412 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.

20 long tasks block the main thread while loading, the longest for 240 ms. During a long task the page ignores taps.

Polyfills for old browsers add 13 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.

For real visitors the layout shifts by 0.49 (75th percentile). Good is under 0.1.

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

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

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

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

The layout shifts by 0.485 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Scripts block taps and scrolling for 874 ms in total while the page loads. Good is under 200 ms.

24 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 127 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 19.3 MB in 266 requests on a phone: images 8.9 MB (51), scripts 8.6 MB (84) and stylesheets 697 KiB (32). Under 2 MB keeps phones on slow connections fast.

5 images weigh 6.9 MB together. On a phone connection a single image that size takes seconds.

16 images (8.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.

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

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

1 element hidden from screen readers can still receive keyboard focus.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 14 characters: “Home | TECNISA”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 23 characters: “Mais construtora por m²”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

10 links have no real href, so search engines can't follow them.

The homepage links to 73 pages on tecnisa.com.br and 24 external pages.

There is no https://www.tecnisa.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.

https://www.tecnisa.com.br/imoveis/null/apartamento, https://www.tecnisa.com.br/imoveis/null/studio, https://www.tecnisa.com.br/imoveis/null/laje-corporativa,loja and https://www.tecnisa.com.br/imoveis all use the title “Imóveis | TECNISA”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tecnisa.com.br/imoveis/null/apartamento, https://www.tecnisa.com.br/imoveis/null/studio, https://www.tecnisa.com.br/imoveis/null/laje-corporativa,loja and https://www.tecnisa.com.br/imoveis use the same meta description. A description written for each page earns more clicks.

https://www.tecnisa.com.br/portfolio-de-entregues, https://www.tecnisa.com.br/sobre, https://www.tecnisa.com.br/causas-e-compromissos and https://www.tecnisa.com.br/campanhas-e-promocoes have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.tecnisa.com.br/imoveis/null/apartamento, https://www.tecnisa.com.br/imoveis/null/studio and https://www.tecnisa.com.br/imoveis took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 37 found) and read each the way a search engine does.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

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.

Social proof on the homepage: 49 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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 558 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, 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.

Opening the homepage sets 12 cookies, 1 of them by other companies (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 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.