viainox.com website review

The page goes through 4 redirects before it starts loading, costing about 2.0 s. Link and advertise the final URL directly.

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

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

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

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

34 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

1 file is served with short cache lifetimes, so returning visitors download them again (3 KiB).

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.

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

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

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

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

The layout shifts by 0.404 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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.

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

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

Your homepage downloads 16.6 MB in 163 requests on a phone: images 14.5 MB (74), scripts 1.6 MB (45) and fonts 287 KiB (6). Under 2 MB keeps phones on slow connections fast.

6 images weigh 11.1 MB together. On a phone connection a single image that size takes seconds.

22 images are downloaded at several times the size a phone draws them, for example c202753157dcecebfa63c44da21ba458.gif at 1,182 px wide, shown at 370 px. Resized copies would save about 4.5 MB.

6 images (9.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.

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

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

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

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

13 elements hidden from screen readers can still receive keyboard focus.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 22 elements on the page fail this check, rated minor by axe-core.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

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://www.viainox.com/xml/produtos.xml, so Google discovers your pages only by following links.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

A phone browser shows 880 words, but the HTML your server sends has only 12. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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://viainox.com/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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

No viewport meta tag, so phones render the desktop layout zoomed out.

4 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=97160418&tm=gtm002&Ver=2&mid=06841a8c-aa76-42ff-88fe-ae91aee0d1e0&bo=1&sid=a92c5790cdf211f1a7eafde1075407b4&vid=a92c8bd0cdf211f1a613678cf24dc6ec&vids=1&msclkid=N&gtm_t.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CERT_AUTHORITY_INVALID”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

No character set is declared, so some characters can render as gibberish.

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

Large scripts ship without source maps.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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

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