apsis.com.br website review

5 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.4 s faster on a phone.

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

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

18 files are served with short cache lifetimes, so returning visitors download them again (358 KiB).

YouTube costs a phone 1.1 s of main-thread work and 1.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

Google Tag Manager costs a phone 561 ms of main-thread work and 515 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 208 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

poli.digital costs a phone 144 ms of main-thread work and 375 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.

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

13 KiB could be saved by minifying JavaScript.

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

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

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

Real visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 21.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A Apsis é líder por dois anos consecutivos em Valuation pel…”.

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

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

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

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

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

13 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 3.5 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.1 MB in 219 requests on a phone: images 5.1 MB (34), scripts 3.2 MB (77) and stylesheets 349 KiB (48). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.

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

1 image is downloaded at several times the size a phone draws it, for example webchat.png at 4,501 px wide, shown at 25 px. Resized copies would save about 56 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 2.58 g of CO₂e: 309.3 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.

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

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

Document should not have more than one banner landmark: 1 element on the page fails 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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

The skip-link target should exist and be focusable: 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.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 81 pages on apsis.com.br and 10 external pages.

Your Organization JSON-LD is missing url, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

/cases is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and /en all use the title “Home - Apsis Consultoria Empresarial”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/ativo-fixo and /ativo-fixo-3 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /ativo-fixo-3, whose canonical is /ativo-fixo. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/en has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

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.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your longest form asks for 8 fields (0 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.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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