alumetal.com.br website review

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

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

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

About 641 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.

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

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

Your mobile performance score is 47 (desktop: 63). 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 Other Google APIs/SDKs and others), adding 1.2 MB and 918 ms of main-thread time.

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

17 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 41 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

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

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

Your largest element takes 23.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Damper / Janela Corta-Fogo Sob Medida”.

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

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

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

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

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

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

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

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.3 MB in 122 requests on a phone: images 4.9 MB (75), scripts 1.4 MB (16) and stylesheets 649 KiB (16). Under 2 MB keeps phones on slow connections fast.

21 images are downloaded at several times the size a phone draws them, for example ferregista-20cm-300dpi-slide-1140x380.png at 1,140 px wide, shown at 332 px. Resized copies would save about 919 KiB.

34 images (4.5 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.

16 images further down the page (725 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.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.

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

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

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

1 link inside paragraphs relies on colour alone to stand out.

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

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

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

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

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

Structured data found (BreadcrumbList, Organization, Store and WebSite) but with 6 problems, for example “WebSite: url is not an absolute URL ("www.alumetal.com.br")”.

The homepage links to 206 pages on alumetal.com.br and 5 external pages.

There is no /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.

/sobre-nos.html, /localizacao.html, /corte-a-laser.html and /contato.html use the same meta description. A description written for each page earns more clicks.

/corte-a-laser.html has no <h1> headline, so visitors and search engines get no clear main topic.

/comprar/etiquetas-de-moveis.html, /comprar/etiquetas-de-extintor.html and /comprar/reguas-para-brindes.html took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://alumetal.com.br/' was loaded over HTTPS, but requested an insecure stylesheet 'http…”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 images are served at too low a resolution for sharp phone screens.

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

1 link from your homepage to your own site is broken, for example https://alumetal.com.br/comprar/escorredor-de-pratos.html (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example http://www.facebook.com/AlumetalOficial.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

alumetal.com.br has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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: 2 trust badges. 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 597 words of visible text.

DMARC is set to p=none, so mail pretending to be alumetal.com.br is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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