vmtec.com.br website review

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

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

16 images could be 348 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

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

About 59 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

35 KiB could be saved by minifying JavaScript.

1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.

10 KiB could be saved by minifying CSS.

1 third-party service load with your homepage (Google Fonts), adding 93 KiB and 0 ms of main-thread time.

Polyfills for old browsers add 7 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.

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

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

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

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

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

1 image (286 KiB) is 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 0.52 g of CO₂e: 62.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

All page content should be contained by landmarks: 16 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 visible links have no text or label, so screen readers cannot say where they go.

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

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

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

No meta description, so Google writes its own snippet from whatever text it finds.

Google's crawler is blocked from indexing this page.

Your title is only 5 characters: “VMTec”. 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 XML sitemap at https://vmtec.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 incomplete here.

The homepage links to 18 pages on vmtec.com.br and 17 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 /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.

/empresa, /fabricantes, /produtos-e-servicos, /produtos, /categoria-produto/hardwares and /contato and 2 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/empresa, /fabricantes, /produtos-e-servicos, /produtos, /categoria-produto/hardwares and /contato and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

/produtos-e-servicos has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “$ is not a function”.

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

1 resource load over plain http on your https page (for example http://vmtec.com.br/wp-content/uploads/2018/07/LOGO-01-PNG-.png); browsers block or warn about them.

http://vmtec.com.br does not redirect to https, so some visitors land on the insecure version.

2 links to other sites are dead, for example https://www.linkedin.com/in/vmtec-projetos-corp-vmtec-projetos-corporativos-439130143/ (999).

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.

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.

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.

vmtec.com.br is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

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

vmtec.com.br's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

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

DMARC is set to p=none, so mail pretending to be vmtec.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.

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