senaimt.ind.br website review

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

6 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 19.4 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and RD Station and others), adding 1.7 MB and 1.0 s of main-thread time.

103 KiB could be saved by minifying JavaScript.

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

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

48 KiB could be saved by minifying CSS.

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

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

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.

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

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

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

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

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

12 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-24, real Chrome visitors' tap response (inp) went from 171 ms to 182 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.5 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.3 MB in 105 requests on a phone: images 4.4 MB (21), scripts 2.4 MB (35) and stylesheets 265 KiB (24). Under 2 MB keeps phones on slow connections fast.

3 images weigh 4.2 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example aluno-senai.png at 1,358 px wide, shown at 390 px. Resized copies would save about 1.1 MB.

4 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.

1 image further down the page (50 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

7 images have no alt text, which hurts accessibility and image search.

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

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

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

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

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://senaimt.ind.br/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 44 pages on senaimt.ind.br and 34 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://senaimt.ind.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://senaimt.ind.br/para-industria/inspiraragro and https://senaimt.ind.br/para-industria/capacitacao have no meta description, so Google writes the search snippet from whatever text it finds.

https://senaimt.ind.br/para-voce/cursos, https://senaimt.ind.br/para-voce/2693/validar-documento-certificado-e-diploma, https://senaimt.ind.br/para-voce/43/ensino-medio-integrado-sesi-senai, https://senaimt.ind.br/para-industria/unidades-moveis, https://senaimt.ind.br/para-industria/131/centro-de-eventos-senai-cuiaba and https://senaimt.ind.br/unidades and 5 others use the same meta description. A description written for each page earns more clicks.

https://senaimt.ind.br/para-voce, https://senaimt.ind.br/para-industria, https://senaimt.ind.br/para-voce/cursos, https://senaimt.ind.br/para-voce/2693/validar-documento-certificado-e-diploma, https://senaimt.ind.br/para-voce/43/ensino-medio-integrado-sesi-senai and https://senaimt.ind.br/para-industria/inspiraragro and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://senaimt.ind.br/para-industria/inspiraragro and https://senaimt.ind.br/para-industria/capacitacao 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.

https://senaimt.ind.br/para-voce and https://senaimt.ind.br/para-industria 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.

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.fiemt.ind.br/style/css/geral.css' from origin 'https://senaimt.ind.br' has bee…”.

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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 264 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 10 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.