uxgroup.com.br website review

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

15 images could be 4.4 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, secureprivacy.ai and Hotjar and others), adding 684 KiB and 1.0 s of main-thread time.

Your mobile performance score is 70 (desktop: 81). Pages that score under 90 lose visitors before the first paint.

Google Tag Manager costs a phone 636 ms of main-thread work and 514 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 281 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

Polyfills for old browsers add 17 KiB JavaScript that modern phones do not need.

About 10 KiB of CSS is downloaded but never applied on this page.

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.

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

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Descrição da imagem”.

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

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

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.

Your homepage downloads 7.5 MB in 123 requests on a phone: images 6.6 MB (50), scripts 895 KiB (38) and other files 48 KiB (24). Under 2 MB keeps phones on slow connections fast.

vendasBanner.d37f7265.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example porqueUx.a02264d9.png at 2,148 px wide, shown at 351 px. Resized copies would save about 238 KiB.

2 images (374 KiB) 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 2.14 g of CO₂e: 256.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 dropdowns have no label.

Interactive controls must not be nested: 21 elements on the page fail this check, rated serious by axe-core.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

Your title is only 8 characters: “UX Group”. 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.

Your meta description is only 40 characters: “Tecnologia, Logística e Sustentabilidade”. 70 to 160 characters is enough to sell the click.

There are 14 <h1> headlines (“Transformamos a experiência do cliente através da…”, “Por quê UX?” and “UX (user experience), para nós, também significa …”). One clear main headline is easier for people and search engines.

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.

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

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

The homepage links to 20 pages on uxgroup.com.br and 20 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://uxgroup.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://uxgroup.com.br/fusion, https://uxgroup.com.br/fulfillment, https://uxgroup.com.br/torre, https://uxgroup.com.br/pudos and https://uxgroup.com.br/connect and 3 others all use the title “UX Group”. Search engines can't tell which page to show for a search, so each competes with the others.

https://uxgroup.com.br/fusion, https://uxgroup.com.br/fulfillment, https://uxgroup.com.br/torre, https://uxgroup.com.br/pudos, https://uxgroup.com.br/connect and https://uxgroup.com.br/ondetah and 2 others use the same meta description. A description written for each page earns more clicks.

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

3 images failed to load on a phone, for example https://uxgroup.com.br/.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

Your longest form asks for 13 fields (7 required). Every extra field lowers completion.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 1,223 words of visible text.

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