gsctransforma.com.br website review

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

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

10 images could be 5.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

8 third-party services load with your homepage (YouTube, Facebook and RD Station and others), adding 1.2 MB and 630 ms of main-thread time.

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

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

YouTube costs a phone 521 ms of main-thread work and 979 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 158 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

12 KiB could be saved by minifying CSS.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

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

Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Somos especialistas em manutenção de sistemas de climatizaç…”. Most of its time is element render delay (5.5 s).

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 7.4 MB in 78 requests on a phone: images 5.8 MB (19), scripts 1.1 MB (21) and fonts 244 KiB (6). Under 2 MB keeps phones on slow connections fast.

2 images weigh 4.9 MB together. On a phone connection a single image that size takes seconds.

12 images (5.7 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.

2 images are downloaded at several times the size a phone draws them, for example logo-gsc.png at 820 px wide, shown at 160 px. Resized copies would save about 79 KiB.

2 images further down the page (170 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 2.09 g of CO₂e: 251.4 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.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 13 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.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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.

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

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://gsctransforma.com.br/sitemap.xml, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 34 pages on gsctransforma.com.br and 10 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://gsctransforma.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.

Your homepage links to https://gsctransforma.com.br/arquivos/concordar.asp, which answers with an error. Visitors hit a dead end and search engines drop it.

https://gsctransforma.com.br/visitar.asp has no <title>, so Google invents the link text in results.

/, https://gsctransforma.com.br/Politica-de-Privacidade, https://gsctransforma.com.br/botaowhatsapp, https://gsctransforma.com.br/Sobre-Nos, https://gsctransforma.com.br/Manutencao-Digitalizada and https://gsctransforma.com.br/Dispositivos-Inteligentes and 3 others all use the title “GSC Transforma – Manutenção de HVAC e Climatização para Empresas”. Search engines can't tell which page to show for a search, so each competes with the others.

https://gsctransforma.com.br/visitar.asp has no meta description, so Google writes the search snippet from whatever text it finds.

https://gsctransforma.com.br/Politica-de-Privacidade, https://gsctransforma.com.br/botaowhatsapp, https://gsctransforma.com.br/Sobre-Nos, https://gsctransforma.com.br/Manutencao-Digitalizada, https://gsctransforma.com.br/Dispositivos-Inteligentes and https://gsctransforma.com.br/Manutencao-Prescritiva and 2 others use the same meta description. A description written for each page earns more clicks.

https://gsctransforma.com.br/visitar.asp, https://gsctransforma.com.br/Sobre-Nos, https://gsctransforma.com.br/Manutencao-Digitalizada, https://gsctransforma.com.br/Dispositivos-Inteligentes, https://gsctransforma.com.br/Manutencao-Prescritiva and https://gsctransforma.com.br/Projetos-Obras-e-Instalacoes and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://gsctransforma.com.br/botaowhatsapp and https://gsctransforma.com.br/Contato 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://gsctransforma.com.br/Contato and https://gsctransforma.com.br/dispositivos-inteligentes took over 3 s to send their HTML from our server.

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

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

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

1 error was logged to the browser console while the page loaded, for example “Bad element for masonry: null”.

2 images are displayed at the wrong aspect ratio, so they look 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.

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

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

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

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

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