tecnocomp.com.br website review

framerusercontent.com costs a phone 1.6 s of main-thread work and 1.9 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.

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

The page has 4,383 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (framerusercontent.com, Google Tag Manager and Facebook and others), adding 3.4 MB and 2.7 s of main-thread time.

Your mobile performance score is 58 (desktop: 62). Pages that score under 90 lose visitors before the first paint.

Google Tag Manager costs a phone 789 ms of main-thread work and 1.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.

About 854 KiB of JavaScript is downloaded but never used on this page.

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

34 images could be 347 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

12 files are served with short cache lifetimes, so returning visitors download them again (307 KiB).

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.

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

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

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

Real visitors wait 246 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

Your homepage downloads 3.5 MB in 196 requests on a phone: scripts 2.1 MB (73), images 788 KiB (70) and fonts 372 KiB (11). Under 2 MB keeps phones on slow connections fast.

2 images further down the page (54 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 button has no accessible name, so screen readers announce just “button”.

18 tap targets are too small or too close together to hit reliably with a finger.

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

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

11 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is only 16 characters: “Tecnocomp - Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 4 <h1> headlines (“Impulsionamos negócios por meio da inovação e tec…”, “Impulsionamos e transformamosnegócios por meio da…” and “Impulsionamos negócios por meio da inovação e tec…”). One clear main headline is easier for people and search engines.

Your meta description is 215 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 295 pages on tecnocomp.com.br and 24 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.

There is no https://www.tecnocomp.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.tecnocomp.com.br/segmentos/industria, https://www.tecnocomp.com.br/segmentos/varejo, https://www.tecnocomp.com.br/segmentos/governo, https://www.tecnocomp.com.br/segmentos/educacao, https://www.tecnocomp.com.br/segmentos/logistica and https://www.tecnocomp.com.br/segmentos/agro and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Assertion Error: nextVariant should be defined B (https://framerusercontent.com/sites/4TbKu6VbxwwUdIF7Eo1rnw/framer.Bk_…”.

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

1 image is served at too low a resolution for sharp phone screens.

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your longest form asks for 20 fields (7 required). Every extra field lowers completion.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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 8 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 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.