megavig.com.br website review

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

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

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

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

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

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

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

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

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

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

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

7 KiB could be saved by minifying CSS.

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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

Your largest element takes 24.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

Real visitors wait 336 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Scripts block taps and scrolling for 211 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 205 ms to 236 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.0 MB in 154 requests on a phone: images 9.1 MB (43), scripts 1.6 MB (56) and stylesheets 127 KiB (31). Under 2 MB keeps phones on slow connections fast.

8 images weigh 5.2 MB together. On a phone connection a single image that size takes seconds.

9 images are downloaded at several times the size a phone draws them, for example shopping_segmentos_site_megavig_ly01-1.jpeg at 1,000 px wide, shown at 175 px. Resized copies would save about 4.0 MB.

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

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

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

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

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

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

Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “Organization: missing name”.

The homepage links to 43 pages on megavig.com.br and 18 external pages.

Your Organization JSON-LD is missing name, logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://megavig.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://megavig.com.br/sobre-nos, https://megavig.com.br/condominios, https://megavig.com.br/trabalhe-conosco, https://megavig.com.br/contato, https://megavig.com.br/solicitar-proposta and https://megavig.com.br/codigo-de-etica-e-conduta and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://megavig.com.br/seguranca-para-industrias, https://megavig.com.br/seguranca-patrimonial, https://megavig.com.br/facilities, https://megavig.com.br/tecnologia-ia, https://megavig.com.br/megavision and https://megavig.com.br/trabalhe-conosco and 3 others took over 3 s to send their HTML from our server.

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

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

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

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