Website review, no card needed

polipet.com.br logo

polipet.com.br website review

Visit site (opens in a new tab)Reviewed 30 October 202643 issues · 91 checks

This review found 43 issues worth fixing on polipet.com.br, 14 of them high impact, across 91 checks. The most urgent: page weight: 7.7 MB in 124 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

Real-visitor load time (LCP)75th percentile, phones
2.3 s1.6 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20262.0 s
Aug 8, 20262.1 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
169 ms140 msMay 9Oct 24151 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026166 ms
May 16, 2026163 ms
May 23, 2026160 ms
May 30, 2026162 ms
Jun 6, 2026161 ms
Jun 13, 2026161 ms
Jun 20, 2026162 ms
Jun 27, 2026163 ms
Jul 4, 2026166 ms
Jul 11, 2026166 ms
Jul 18, 2026159 ms
Jul 25, 2026153 ms
Aug 1, 2026151 ms
Aug 8, 2026150 ms
Aug 15, 2026150 ms
Aug 22, 2026151 ms
Aug 29, 2026147 ms
Sep 5, 2026146 ms
Sep 12, 2026146 ms
Sep 19, 2026144 ms
Sep 26, 2026143 ms
Oct 3, 2026143 ms
Oct 10, 2026144 ms
Oct 17, 2026147 ms
Oct 24, 2026151 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 polipet.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. polipet.com.br at 0.4 s0.4 s
  2. polipet.com.br at 0.8 s0.8 s
  3. polipet.com.br at 1.1 s1.1 s
  4. polipet.com.br at 1.5 s1.5 s
  5. polipet.com.br at 1.9 s1.9 s
  6. polipet.com.br at 2.3 s2.3 s
  7. polipet.com.br at 2.6 s2.6 s
  8. polipet.com.br at 3.0 s3.0 s

Speed

9 to fix54
  • 6,252 HTML elements

    The page has 6,252 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    5.2 MB

    37 images could be 5.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 54

    54/100

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

  • Reduce unused JavaScript

    763 KiB

    About 763 KiB of JavaScript is downloaded but never used on this page.

  • Render-blocking requests

    750 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

  • 8 third-party services on the page

    8 third-party services load with your homepage (fbitsstatic.net, JSDelivr CDN and widde.io and others), adding 2.0 MB and 346 ms of main-thread time.

  • Document request latency

    502 KiB

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

  • fbitsstatic.net adds 165 ms

    165 ms

    fbitsstatic.net costs a phone 165 ms of main-thread work and 1.4 MB 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.7 s

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

  • Use efficient cache lifetimes

    150 ms · 91 KiB

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

  • Reduce unused CSS

    150 ms · 67 KiB

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

  • 10 long tasks on the main thread

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

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 93 ms

    93 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 9.8 s

    9.8 s

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

  • First Contentful Paint: 5.4 s

    5.4 s

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

  • Time to Interactive: 14.5 s

    14.5 s

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

  • Speed Index: 8.1 s

    8.1 s

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

  • 36 images without width and height

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

  • Cumulative Layout Shift: 0.113

    0.113

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

  • Tap response (INP) held steady for real visitors

    -9%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 172 ms

    172 ms

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

  • Real-user CLS: 0.10

    0.10

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 660 ms

    660 ms

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

  • Total Blocking Time: 69 ms

    69 ms

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

Images and page weight

2 to fix60
  • Page weight: 7.7 MB in 124 requests

    7.7 MB

    Your homepage downloads 7.7 MB in 124 requests on a phone: images 6.3 MB (84), HTML 753 KiB (1) and scripts 443 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (638 KiB) 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.

  • 1 image below the first screen load straight away

    1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.18 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.18 g of CO₂e: 261.0 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

12 to fixGoogle 8886
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 1 button without a name

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

  • 8 text elements with low contrast

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

  • 7 tap targets too small

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

  • 1 image without alt text

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

  • All page content should be contained by landmarks (14 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

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

  • 4 form fields without a label

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

  • ARIA role should be appropriate for the element (4 elements)

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

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

3 to fixGoogle 10087
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Polipet: petshop online e itens de garden e pisci…”). One clear main headline is easier for people and search engines.

  • Meta description is long (161 characters)

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

  • 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 X (Twitter) card tag

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

  • 1,183 internal links, 41 external

    The homepage links to 1,183 pages on polipet.com.br and 41 external pages.

5 checks passed
  • Title: 30 characters

    Your title is a healthy 30 characters: “Polipet: O Shopping do Seu Pet”.

  • Canonical URL set

    The canonical URL is https://www.polipet.com.br/.

  • Structured data in place

    Structured data found: FAQPage.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.polipet.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.

3 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 (3,528 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.polipet.com.br/llms.txt (4 KiB, 18 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix71
  • 1 page points its canonical at the homepage

    https://www.polipet.com.br/clubemaispolipet declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 4 pages share 2 titles

    / and https://www.polipet.com.br/clubemaispolipet all use the title “Polipet: O Shopping do Seu Pet”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.polipet.com.br/cashback, https://www.polipet.com.br/ofertas-do-mes, https://www.polipet.com.br/assinatura, https://www.polipet.com.br/retire-na-loja and https://www.polipet.com.br/marcas have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.polipet.com.br/listadedesejos and https://www.polipet.com.br/ListaDeDesejos use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://www.polipet.com.br/assinatura and https://www.polipet.com.br/clubemaispolipet have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.polipet.com.br/clubemaispolipet and https://www.polipet.com.br/compre-por-pet/cachorro/racao-para-cachorro took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8591
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “The source list for the Content Security Policy directive 'default-src' contains an invalid source: '*app.cartstack.com…”.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

    126 of 157 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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.

  • Thin social proof

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

  • 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 1,351 words of copy

    The homepage carries about 1,351 words of visible text.

3 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

Privacy and tracking

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 13 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Framework
Tailwind CSS
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on polipet.com.br, including 15 speed issues, 3 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