verde.ag website review

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

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

Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

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

1 long task block the main thread while loading, the longest for 60 ms. During a long task the page ignores taps.

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.

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

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

Your largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Produza como jamais imaginou”.

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

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

Real visitors wait 281 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-31, real Chrome visitors' tap response (inp) went from 128 ms to 288 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

Mina.jpg weighs 513 KiB. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example Mina.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 790 KiB.

Your homepage downloads 2.0 MB in 31 requests on a phone: images 1.8 MB (15), fonts 126 KiB (8) and HTML 36 KiB (1). Under 2 MB keeps phones on slow connections fast.

5 images (1.7 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.

2 images further down the page (367 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

3 elements hidden from screen readers can still receive keyboard focus.

2 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: 21 elements on the page fail this check, rated moderate by axe-core.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

Your title is only 21 characters: “Home - Verde Agritech”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 5 <h1> headlines (“Produza como jamais imaginou”, “O Brasil retomando o controle do seu futuro” and “Lançamento KAAPY®”). One clear main headline is easier for people and search engines.

Your meta description is 189 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 23 pages on verde.ag and 32 external pages.

Your Organization JSON-LD is missing 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 https://verde.ag/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://verde.ag/produtos, https://verde.ag/sobrenos, https://verde.ag/fale-conosco, https://verde.ag/trabalhe-conosco, https://verde.ag/produtos/kaapy and https://verde.ag/seja-representante and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://verde.ag/pre-cadastro-de-fornecedor has no <h1> headline, so visitors and search engines get no clear main topic.

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

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.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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.