telmec.com.br website review

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

30 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

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

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

6 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 978 KiB and 505 ms of main-thread time.

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

Google CDN costs a phone 347 ms of main-thread work and 736 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.

About 83 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

3 KiB could be saved by minifying JavaScript.

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 19.4 s. Good is under 3.8 s.

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

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

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

Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

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

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

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

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

Your homepage downloads 5.5 MB in 102 requests on a phone: images 3.3 MB (21), scripts 1.1 MB (43) and fonts 553 KiB (4). Under 2 MB keeps phones on slow connections fast.

DJI_20250217144224_0013_D.jpg weighs 586 KiB. On a phone connection a single image that size takes seconds.

10 images (1.6 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.

5 images further down the page (512 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 1.57 g of CO₂e: 188.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.

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: 28 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

Elements with visible text labels do not have matching accessible names. (3 elements).

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

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

The homepage links to 42 pages on telmec.com.br and 15 external pages.

There is no https://telmec.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://telmec.com.br/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://telmec.com.br/home all use the title “Home - Telmec | Somos apaixonados por Engenharia”. Search engines can't tell which page to show for a search, so each competes with the others.

https://telmec.com.br/en/home-english and https://telmec.com.br/home have no <h1> headline, so visitors and search engines get no clear main topic.

https://telmec.com.br/obras and https://telmec.com.br/home took over 3 s to send their HTML from our server.

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

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: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 4 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.