vetoreditora.com.br website review

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

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

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

61 images could be 6.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, fbitsstatic.net and Google CDN and others), adding 9.0 MB and 3.2 s of main-thread time.

fbitsstatic.net costs a phone 818 ms of main-thread work and 2.2 MB 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.

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

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

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

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

ContentSquare costs a phone 405 ms of main-thread work and 187 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 321 ms of main-thread work and 224 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.

The page has 2,870 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

About 57 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

Polyfills for old browsers add 40 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “banner”.

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

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

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

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

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

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

18 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-10, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.8 MB in 287 requests on a phone: images 6.9 MB (104), scripts 2.3 MB (57) and other files 512 KiB (111). Under 2 MB keeps phones on slow connections fast.

894253a8-809b-4ed9-bde9-b2a1e0996a39.jpg 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 257651-1.jpg at 600 px wide, shown at 181 px. Resized copies would save about 9 KiB.

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

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 441 pages on vetoreditora.com.br and 49 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://www.vetoreditora.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://www.vetoreditora.com.br/distribuidores and https://www.vetoreditora.com.br/busca have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.vetoreditora.com.br/vetor-servicos/projetos-e-servicos, https://www.vetoreditora.com.br/vetor-servicos/projetos-e-servicos/aplicacao-de-teste-e-avaliacao-psicologica, https://www.vetoreditora.com.br/vetor-servicos/projetos-e-servicos/avaliacao-psicossocial, https://www.vetoreditora.com.br/vetor-servicos/projetos-e-servicos/cursos-e-treinamentos-personalizados-e-supervisao-de-teste, https://www.vetoreditora.com.br/vetor-servicos/projetos-e-servicos/rh-e-projetos-organizacionais and https://www.vetoreditora.com.br/vetor-servicos/projetos-e-servicos/palestras-workshops-oficinas-ou-roda-de-conversa and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.vetoreditora.com.br/vetor-servicos/projetos-e-servicos/rh-e-projetos-organizacionais, https://www.vetoreditora.com.br/vetor-servicos/projetos-e-servicos/palestras-workshops-oficinas-ou-roda-de-conversa, https://www.vetoreditora.com.br/vetor-servicos/projetos-e-servicos/projetos-escolares, https://www.vetoreditora.com.br/produto/nr-01-pade-fp-preco-sob-consulta-72167, https://www.vetoreditora.com.br/testes and https://www.vetoreditora.com.br/testes/colecao-de-testes and 2 others took over 3 s to send their HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “The source list for the Content Security Policy directive 'default-src' contains an invalid source: '.contentsquare.net…”.

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

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

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.

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

Opening the homepage sets 8 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.