primaveras.com.br website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and RD Station and others), adding 847 KiB and 693 ms of main-thread time.

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

Google Tag Manager costs a phone 403 ms of main-thread work and 359 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 366 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

8 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' tap response (inp) went from 125 ms to 128 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 19.5 MB in 171 requests on a phone: images 13.8 MB (62), media 3.9 MB (1) and scripts 1.0 MB (40). Under 2 MB keeps phones on slow connections fast.

home-50anos-768x267.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 (278 KiB) is 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 5.53 g of CO₂e: 664.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

1 button has no accessible name, so screen readers announce just “button”.

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

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

[role="img"] and [role="image"] elements must have alternative text: 22 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (4 elements).

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

Your title is only 10 characters: “Primaveras”. 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 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 79 pages on primaveras.com.br and 33 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.primaveras.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.primaveras.com.br/onde, https://www.primaveras.com.br/fale-conosco, https://www.primaveras.com.br/perdi-alguem, https://www.primaveras.com.br/apoio-ao-luto, https://www.primaveras.com.br/grupo-de-apoio and https://www.primaveras.com.br/estrutura and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.primaveras.com.br/onde, https://www.primaveras.com.br/fale-conosco, https://www.primaveras.com.br/estrutura and https://www.primaveras.com.br/funeraria-primaveras have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.primaveras.com.br/perdi-alguem, https://www.primaveras.com.br/velorio, https://www.primaveras.com.br/repatriacao and https://www.primaveras.com.br/floricultura-primaveras took over 3 s to send their HTML from our server.

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

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

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 2,096 words of visible text.

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