ioasys.com.br website review

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

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

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

1 image could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, TikTok and Facebook and others), adding 1.4 MB and 1.5 s of main-thread time.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

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

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

Polyfills for old browsers add 54 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

Google CDN costs a phone 165 ms of main-thread work and 352 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.

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 6.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Your largest element takes 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “technology”. Most of its time is element render delay (8.2 s).

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

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

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

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

37 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-31, real Chrome visitors' tap response (inp) went from 115 ms to 106 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 11.8 MB in 123 requests on a phone: media 5.7 MB (2), images 4.2 MB (52) and scripts 1.8 MB (37). Under 2 MB keeps phones on slow connections fast.

ioasys-inicio-hero-image.gif weighs 4.1 MB. On a phone connection a single image that size takes seconds.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

2 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: 4 elements on the page fail this check, rated moderate by axe-core.

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

Your title is only 6 characters: “ioasys”. 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 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://ioasys.com.br/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at ioasys.com.br/robots.txt, the first file search crawlers ask for.

The homepage links to 35 pages on ioasys.com.br and 10 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://ioasys.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://ioasys.com.br/en and / all use the title “ioasys”. Search engines can't tell which page to show for a search, so each competes with the others.

https://ioasys.com.br/en/insights/divulgacao-de-transparencia-salarial-25-01 and https://ioasys.com.br/en/insights/1154 use the same meta description. A description written for each page earns more clicks.

/, https://ioasys.com.br/en/about-us, https://ioasys.com.br/en/our-solutions, https://ioasys.com.br/en/our-solutions/digital-products, https://ioasys.com.br/en/our-solutions/strategy-acceleration and https://ioasys.com.br/en/our-solutions/data-ai and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://ioasys.com.br/en/cases has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/ and https://ioasys.com.br/en/our-solutions/culture-learning took over 3 s to send their HTML from our server.

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

14 of 22 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_FAILED”.

Social proof on the homepage: 35 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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