Website review, no card needed

nossalavoura.com.br logo

nossalavoura.com.br website review

Visit site (opens in a new tab)Reviewed 26 October 202635 issues · 75 checks

This review found 35 issues worth fixing on nossalavoura.com.br, 15 of them high impact, across 75 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of nossalavoura.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nossalavoura.com.br at 0.6 s0.6 s
  2. nossalavoura.com.br at 1.3 s1.3 s
  3. nossalavoura.com.br at 1.9 s1.9 s
  4. nossalavoura.com.br at 2.5 s2.5 s
  5. nossalavoura.com.br at 3.1 s3.1 s
  6. nossalavoura.com.br at 3.8 s3.8 s
  7. nossalavoura.com.br at 4.4 s4.4 s
  8. nossalavoura.com.br at 5.0 s5.0 s

Speed

6 to fix36
  • Render-blocking requests

    2.4 s

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

  • Reduce unused JavaScript

    1.2 s · 253 KiB

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

  • Font display

    1.1 s

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

  • Mobile performance score: 36

    36/100

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

  • Google Tag Manager adds 272 ms

    272 ms

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

  • Main-thread work: 2.0 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, xlabs.com.br and Google/Doubleclick Ads and others), adding 870 KiB and 455 ms of main-thread time.

  • 7 long tasks on the main thread

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

  • Use efficient cache lifetimes

    175 KiB

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

  • Reduce unused CSS

    150 ms · 14 KiB

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

  • Improve image delivery

    46 KiB

    2 images could be 46 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Phones get a much slower page than desktops

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 458 ms

    458 ms

    Your server sent the HTML in 458 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix32
  • Largest Contentful Paint: 9.6 s

    9.6 s

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

  • Time to Interactive: 13.5 s

    13.5 s

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

  • Cumulative Layout Shift: 0.473

    0.473

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

  • Speed Index: 8.0 s

    8.0 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Total Blocking Time: 294 ms

    294 ms

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

2 to fix81
  • Page weight: 2.2 MB in 96 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 96 requests on a phone: images 900 KiB (20), scripts 694 KiB (32) and fonts 379 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    WhatsApp-Image-2026-05-12-at-16.44.24-768x960.jpeg 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 in older formats

    1 image (140 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.

  • About 0.6 g of CO₂ per visit

    0.64 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9193
  • 12 text elements with low contrast

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

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

  • Page should contain a level-one heading (1 element)

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

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

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 9262
  • No meta description

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

  • No H1 headline

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

  • Title is short (13 characters)

    Your title is only 13 characters: “Nossa Lavoura”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

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

  • No robots.txt

    There is no robots.txt at nossalavoura.com.br/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

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

  • 29 internal links, 26 external

    The homepage links to 29 pages on nossalavoura.com.br and 26 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://nossalavoura.com.br/.

  • XML sitemap found

    Your XML sitemap is reachable at https://nossalavoura.com.br/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://nossalavoura.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.

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (573 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://nossalavoura.com.br/produtos and https://nossalavoura.com.br/politica-de-privacidade have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://nossalavoura.com.br/produtos and https://nossalavoura.com.br/politica-de-privacidade have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 internal pages checked

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

5 checks passed
  • Linked pages load

    All 2 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 2 pages that loaded have a <title>.

Best practices

3 to fixGoogle 8885
  • 7 small tap targets

    7 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • No call to action on the first screen

    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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

  • No risk reducer

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

  • About 541 words of copy

    The homepage carries about 541 words of visible text.

3 checks passed
  • 3 short forms

    3 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 11 other companies contacted

    Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at nossalavoura.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on nossalavoura.com.br, including 12 speed issues, 6 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25