viamia.com.br website review

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

The page goes through 1 redirect before it starts loading, costing about 2.1 s. Link and advertise the final URL directly.

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

About 48 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.

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

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

5 third-party services load with your homepage (vteximg.com.br, vtex.com.br and vtex.com and others), adding 100 KiB and 3 ms of main-thread time.

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

For real visitors the layout shifts by 0.99 (75th percentile). Good is under 0.1.

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

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

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

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

Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 237 ms to 222 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 2.1 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 15.9 MB in 506 requests on a phone: images 13.1 MB (232), scripts 2.0 MB (110) and other files 455 KiB (147). Under 2 MB keeps phones on slow connections fast.

4 images weigh 6.8 MB together. On a phone connection a single image that size takes seconds.

17 images are downloaded at several times the size a phone draws them, for example banner-mobile-sapatilhas.jpg at 1,536 px wide, shown at 390 px. Resized copies would save about 1.5 MB.

19 images (1.9 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.

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

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

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 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.

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

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

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

Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

Your title is only 28 characters: “Via Mia - Calçados Femininos”. 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.

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

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

The homepage links to 190 pages on viamia.com.br and 8 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://www.viamia.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://www.viamia.com.br/vantagens and https://www.viamia.com.br/institucional/lojas use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.viamia.com.br/institucional/lojas, whose canonical is https://www.viamia.com.br/institucional. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.viamia.com.br/bolsas took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=134613936&Ver=2&mid=a1e4d027-f00f-4f42-abb4-9d1b5809794d&bo=1&sid=a40d6040d28411f1b94f77570ed8e1b6&vid=a40d92c0d28411f1abfc9f2d7e83c514&vids=1&msclkid=N&pi=918639831&l.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Event name is not defined”.

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

Social proof on the homepage: 1 testimonial or review block. 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 865 words of visible text.

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