arcom.com.br website review

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

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

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

16 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (clearsale.com.br, Facebook and Hotjar and others), adding 530 KiB and 655 ms of main-thread time.

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

About 323 KiB of JavaScript is downloaded but never used on this page.

clearsale.com.br costs a phone 291 ms of main-thread work and 98 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.

Facebook costs a phone 273 ms of main-thread work and 259 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 36 KiB of CSS is downloaded but never applied on this page.

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.

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.

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

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

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

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

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

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

The first text or image appears after 2.5 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.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 304 ms to 311 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.3 MB in 170 requests on a phone: images 6.8 MB (112), scripts 1.3 MB (35) and fonts 115 KiB (6). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 2.34 g of CO₂e: 281.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

[aria-*] attributes do not have valid values (1 element).

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails 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 9 characters: “Arcom S/A”. 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 XML sitemap at https://www.arcom.com.br/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of 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 /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.

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.

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

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.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

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.

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

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.

The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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.

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