qentrega.com.br website review

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

4 images could be 963 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

About 124 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

14 KiB could be saved by minifying JavaScript.

3 third-party services load with your homepage (Google Tag Manager, Google Analytics and Jivochat), adding 181 KiB and 96 ms of main-thread time.

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

Desktop scores 89 but mobile only 64. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Your largest element takes 15.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “IMG_home3 (1)”.

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

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

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

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

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

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

Your homepage downloads 6.1 MB in 114 requests on a phone: media 2.7 MB (1), images 2.1 MB (13) and fonts 689 KiB (6). Under 2 MB keeps phones on slow connections fast.

IMG_2.webp weighs 569 KiB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example IMG_home3-1.webp at 1,400 px wide, shown at 356 px. Resized copies would save about 249 KiB.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

6 visible links have no text or label, so screen readers cannot say where they go.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

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

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 51 pages on qentrega.com.br and 8 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.

https://qentrega.com.br/institucional, https://qentrega.com.br/entregar, https://qentrega.com.br/blog-qe, https://qentrega.com.br/contato, https://qentrega.com.br/trabalhe-conosco and https://qentrega.com.br/entrega-de-produtos-farmaceuticos-com-transporte-refrigerado-seguranca-qualidade-e-eficiencia-para-o-setor and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://qentrega.com.br/institucional, https://qentrega.com.br/entregar, https://qentrega.com.br/blog-qe, https://qentrega.com.br/contato, https://qentrega.com.br/trabalhe-conosco and https://qentrega.com.br/entrega-de-produtos-farmaceuticos-com-transporte-refrigerado-seguranca-qualidade-e-eficiencia-para-o-setor and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://crmeme.com.br/clientes-meme/rsm/wp-content/uploads/2025/04/WhatsApp-Image-2024-07-17-at-11.20.20-1.png.

3 of 8 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”.

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.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 24 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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