supermalhas.com.br website review

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

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

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

7 third-party services load with your homepage (awsli.com.br, Google Tag Manager and Google/Doubleclick Ads and others), adding 1.6 MB and 674 ms of main-thread time.

awsli.com.br costs a phone 362 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.

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

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

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

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

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

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.

4 KiB could be saved by minifying CSS.

Your largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Full banner 2 @Mobile”.

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

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

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

Scripts block taps and scrolling for 481 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.

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.

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

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

Images must have alternative text: 5 elements on the page fail this check, rated critical by axe-core.

Some list items are not inside a list.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

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

ARIA role should be appropriate for the element: 10 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 10 elements on the page fail this check, rated minor by axe-core.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 12 characters: “Super Malhas”. 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.

27 links have no real href, so search engines can't follow them.

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

Your <h1> is empty.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 105 pages on supermalhas.com.br and 9 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://supermalhasloja.lojaintegrada.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.

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

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

2 images are 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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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