Website review, no card needed

zanotti.com.br logo

zanotti.com.br website review

Visit site (opens in a new tab)Reviewed 28 October 202641 issues · 85 checks

This review found 41 issues worth fixing on zanotti.com.br, 19 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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

Real-visitor load time (LCP)75th percentile, phones
2.6 s1.6 sMay 9Oct 242.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.8 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.3 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
115 ms100 msMay 9Oct 24109 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026111 ms
May 16, 2026110 ms
May 23, 2026111 ms
May 30, 2026113 ms
Jun 6, 2026110 ms
Jun 13, 2026111 ms
Jun 20, 2026107 ms
Jun 27, 2026106 ms
Jul 4, 2026105 ms
Jul 11, 2026102 ms
Jul 18, 2026105 ms
Jul 25, 2026106 ms
Aug 1, 2026107 ms
Aug 8, 2026106 ms
Aug 15, 2026106 ms
Aug 22, 2026105 ms
Aug 29, 2026106 ms
Sep 5, 2026111 ms
Sep 12, 2026111 ms
Sep 19, 2026108 ms
Sep 26, 2026105 ms
Oct 3, 2026104 ms
Oct 10, 2026103 ms
Oct 17, 2026106 ms
Oct 24, 2026109 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

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

How it loaded on a phone

  1. zanotti.com.br at 0.8 s0.8 s
  2. zanotti.com.br at 1.6 s1.6 s
  3. zanotti.com.br at 2.5 s2.5 s
  4. zanotti.com.br at 3.3 s3.3 s
  5. zanotti.com.br at 4.1 s4.1 s
  6. zanotti.com.br at 4.9 s4.9 s
  7. zanotti.com.br at 5.7 s5.7 s
  8. zanotti.com.br at 6.5 s6.5 s

Speed

10 to fix40
  • Use efficient cache lifetimes

    8.6 s · 13.5 MB

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

  • Improve image delivery

    5.3 s · 11.2 MB

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

  • Reduce unused JavaScript

    5.2 s · 600 KiB

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

  • Render-blocking requests

    2.9 s

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

  • Mobile performance score: 40

    40/100

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

  • Reduce unused CSS

    900 ms · 155 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and goadopt.io and others), adding 1.5 MB and 538 ms of main-thread time.

  • Google CDN adds 267 ms

    267 ms

    Google CDN costs a phone 267 ms of main-thread work and 734 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.1 s

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

  • Google Tag Manager adds 127 ms

    127 ms

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

  • 8 long tasks on the main thread

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

  • Document request latency

    44 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 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 CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 429 ms

    429 ms

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

Core Web Vitals

12 to fix33
  • Fails Core Web Vitals for real visitors

    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-user CLS: 0.37

    0.37

    For real visitors the layout shifts by 0.37 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 28.9 s

    28.9 s

    Your largest element takes 28.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Catálogo de Produtos 2026”.

  • Time to Interactive: 35.1 s

    35.1 s

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

  • Speed Index: 14.2 s

    14.2 s

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

  • Cumulative Layout Shift: 0.425

    0.425

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Largest content (LCP) got 42% slower for real visitors

    +42%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 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.

  • 20 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

2 checks passed
  • Real-user INP: 129 ms

    129 ms

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

  • Total Blocking Time: 101 ms

    101 ms

    Scripts block the page for only 101 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix38
  • Page weight: 15.3 MB in 87 requests

    15.3 MB

    Your homepage downloads 15.3 MB in 87 requests on a phone: images 13.0 MB (45), scripts 1.6 MB (21) and other files 359 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    banner-mobile-book.png weighs 795 KiB. On a phone connection a single image that size takes seconds.

  • 17 images in older formats

    17 images (6.0 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.

  • An image on the first screen is lazy-loaded

    banner-mobile-book.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).

  • 3 images below the first screen load straight away

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

  • About 4.3 g of CO₂ per visit

    4.34 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.34 g of CO₂e: 520.6 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 8491
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 27 tap targets too small

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

  • 7 text elements with low contrast

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

  • 12 images without alt text

    12 images have no alt text, which hurts accessibility and image search.

  • 29 links without text

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

  • 5 form fields without a label

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

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

2 to fixGoogle 8593
  • Invalid hreflang

    Your hreflang tags are invalid, so Google may show the wrong language version.

  • One H1 headline

    Your <h1> is empty.

  • 107 internal links, 25 external

    The homepage links to 107 pages on zanotti.com.br and 25 external pages.

7 checks passed
  • Meta description: 87 characters

    Your meta description is 87 characters: “Referência no segmento de fitas elásticas em toda a América e uma das maiores do mundo.”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Zanotti Elásticos - Excelência em fitas elásticas.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, CollectionPage, Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    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.

  • No llms.txt

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

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

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

Other pages

3 to fix75
  • 1 page without a title

    https://zanotti.com.br/partial-busca has no <title>, so Google invents the link text in results.

  • 2 pages without a meta description

    https://zanotti.com.br/partial-busca and https://zanotti.com.br/produtos/lancamentos have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://zanotti.com.br/partial-busca and https://zanotti.com.br/comprar have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://zanotti.com.br/partial-busca has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 2 pages slow to respond

    https://zanotti.com.br/sustentabilidade and https://zanotti.com.br/politica-de-privacidade took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 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.

Best practices

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    68 of 77 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • No social proof

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

  • Phone number is not tap-to-call

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

  • 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 451 words of copy

    The homepage carries about 451 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Acesse nosso book comemorativo!”.

  • 1 call to action

    The homepage has 1 call to action, for example “Acesse nosso book comemorativo!”.

  • 1 short form

    A short form (5 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 14 other companies contacted

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

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 zanotti.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
Tailwind CSS
Analytics
Google Tag Manager
Hosting
Servicos de Internet SA

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on zanotti.com.br, including 22 speed issues, 2 SEO issues and 1 conversion gap. 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