Website review, no card needed

b2pneus.com.br logo

b2pneus.com.br website review

Visit site (opens in a new tab)Reviewed 4 November 202653 issues · 95 checks

This review found 53 issues worth fixing on b2pneus.com.br, 21 of them high impact, across 95 checks. The most urgent: vtexassets.com adds 1.7 s. 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
3.9 s3.4 sMay 16Oct 313.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.5 s
May 23, 20263.5 s
May 30, 20263.5 s
Jun 6, 20263.6 s
Jun 13, 20263.6 s
Jun 20, 20263.7 s
Jun 27, 20263.7 s
Jul 4, 20263.7 s
Jul 11, 20263.6 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 1, 20263.6 s
Aug 8, 20263.7 s
Aug 15, 20263.7 s
Aug 22, 20263.7 s
Aug 29, 20263.7 s
Sep 5, 20263.8 s
Sep 12, 20263.7 s
Sep 19, 20263.6 s
Sep 26, 20263.6 s
Oct 3, 20263.6 s
Oct 10, 20263.7 s
Oct 17, 20263.8 s
Oct 24, 20263.9 s
Oct 31, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
207 ms163 msMay 16Oct 31184 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026172 ms
May 23, 2026174 ms
May 30, 2026169 ms
Jun 6, 2026170 ms
Jun 13, 2026169 ms
Jun 20, 2026168 ms
Jun 27, 2026170 ms
Jul 4, 2026168 ms
Jul 11, 2026169 ms
Jul 18, 2026169 ms
Jul 25, 2026172 ms
Aug 1, 2026176 ms
Aug 8, 2026173 ms
Aug 15, 2026183 ms
Aug 22, 2026185 ms
Aug 29, 2026185 ms
Sep 5, 2026196 ms
Sep 12, 2026195 ms
Sep 19, 2026195 ms
Sep 26, 2026201 ms
Oct 3, 2026202 ms
Oct 10, 2026202 ms
Oct 17, 2026196 ms
Oct 24, 2026189 ms
Oct 31, 2026184 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 b2pneus.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. b2pneus.com.br at 0.9 s0.9 s
  2. b2pneus.com.br at 1.7 s1.7 s
  3. b2pneus.com.br at 2.6 s2.6 s
  4. b2pneus.com.br at 3.5 s3.5 s
  5. b2pneus.com.br at 4.3 s4.3 s
  6. b2pneus.com.br at 5.2 s5.2 s
  7. b2pneus.com.br at 6.0 s6.0 s
  8. b2pneus.com.br at 6.9 s6.9 s

Speed

13 to fix33
  • vtexassets.com adds 1.7 s

    1.7 s

    vtexassets.com costs a phone 1.7 s of main-thread work and 1.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    1.5 s

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

  • Google Tag Manager adds 1.0 s

    1.0 s

    Google Tag Manager costs a phone 1.0 s of main-thread work and 551 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 33

    33/100

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

  • Main-thread work: 8.2 s

    A phone's processor spends 8.2 s on main-thread work while loading, 4.6 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 (vtexassets.com, Google Tag Manager and Facebook and others), adding 3.0 MB and 3.9 s of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 405 KiB

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

  • Reduce unused CSS

    600 ms · 83 KiB

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

  • Reduce unused JavaScript

    629 KiB

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    450 ms · 66 KiB

    Polyfills for old browsers add 66 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

  • Facebook adds 305 ms

    305 ms

    Facebook costs a phone 305 ms of main-thread work and 226 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.

  • TikTok adds 282 ms

    282 ms

    TikTok costs a phone 282 ms of main-thread work and 150 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.

  • Improve image delivery

    80 KiB

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

  • 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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 41 ms

    41 ms

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

Core Web Vitals

10 to fix67
  • 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 FCP: 3.4 s

    3.4 s

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

  • Time to Interactive: 21.7 s

    21.7 s

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

  • Largest Contentful Paint: 8.2 s

    8.2 s

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

  • Total Blocking Time: 2.8 s

    2.8 s

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

  • Speed Index: 10.6 s

    10.6 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

    Real visitors wait 1.6 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.

  • 11 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +8%

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

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

    +10%

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

3 checks passed
  • Real-user INP: 139 ms

    139 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix83
  • Page weight: 3.2 MB in 149 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 149 requests on a phone: scripts 1.9 MB (54), fonts 798 KiB (5) and images 233 KiB (44). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    bg-modal-cep-mob.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 in older formats

    3 images (141 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 (53 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.90 g

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

11 to fixGoogle 7284
  • Images must have alternative text (4 elements)

    Images must have alternative text: 4 elements on the page fail this check, rated critical by axe-core.

  • Unlabelled dropdowns

    3 dropdowns have no label.

  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 3 tap targets too small

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

  • 2 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

    All page content should be contained by landmarks: 10 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.

  • 5 form fields without a label

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

  • 4 links without text

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

  • Alternative text of images should not be repeated as text (2 elements)

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

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

4 to fixGoogle 8581
  • No H1 headline

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

  • Structured data has 1 problem

    Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 11 links crawlers can't follow

    11 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 44 internal links, 8 external

    The homepage links to 44 pages on b2pneus.com.br and 8 external pages.

5 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “Pneus Dunlop, Falken e Sumitomo 100% nacionais com 5 anos de garantia. Sua loja online de pneus com as melhores condiçõ…”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “B2 Pneus - Loja Oficial Dunlop Pneus”.

  • Canonical URL set

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

  • 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.b2pneus.com.br/sitemap.xml.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    58%

    The HTML your server sends has 170 of the 291 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

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

Other pages

4 to fix79
  • 2 linked pages hidden from search

    https://www.b2pneus.com.br/pneu and https://www.b2pneus.com.br/137 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 7 pages share a title

    /, https://www.b2pneus.com.br/sobre-a-empresa, https://www.b2pneus.com.br/fale-conosco, https://www.b2pneus.com.br/nossas-lojas, https://www.b2pneus.com.br/centro-montagem and https://www.b2pneus.com.br/garantia and 1 other all use the title “B2 Pneus - Loja Oficial Dunlop Pneus”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages share a meta description

    https://www.b2pneus.com.br/pneu, https://www.b2pneus.com.br/137, https://www.b2pneus.com.br/sobre-a-empresa, https://www.b2pneus.com.br/fale-conosco, https://www.b2pneus.com.br/nossas-lojas and https://www.b2pneus.com.br/centro-montagem and 2 others use the same meta description. A description written for each page earns more clicks.

  • 10 pages without an H1

    https://www.b2pneus.com.br/pneu-dunlop-175-65-r14-82t-touring-r1/p, https://www.b2pneus.com.br/pneu-dunlop-185-65-r15-88h-sport-fm800/p, https://www.b2pneus.com.br/pneu-dunlop-175-70-r14-88t-touring-r1/p, https://www.b2pneus.com.br/pneu-dunlop-185-60-r15-88h-sport-fm800/p, https://www.b2pneus.com.br/sobre-a-empresa and https://www.b2pneus.com.br/fale-conosco and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.b2pneus.com.br/fale-conosco and https://www.b2pneus.com.br/nossas-lojas have 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.

  • 9 pages slow to respond

    https://www.b2pneus.com.br/137, https://www.b2pneus.com.br/pneu-dunlop-175-65-r14-82t-touring-r1/p, https://www.b2pneus.com.br/pneu-dunlop-185-65-r15-88h-sport-fm800/p, https://www.b2pneus.com.br/pneu-dunlop-185-60-r15-88h-sport-fm800/p, https://www.b2pneus.com.br/sobre-a-empresa and https://www.b2pneus.com.br/fale-conosco and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 20 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 8885
  • 13 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Unexpected token '}'”.

  • 2 distorted images

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

  • 3 low-resolution images

    3 images are 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 291 words of copy

    The homepage carries about 291 words of visible text.

3 checks passed
  • 1 short form

    A short form (3 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok 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.

  • 18 cookies set on arrival

    18

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

  • 31 other companies contacted

    Loading the homepage contacts 31 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 b2pneus.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
React
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 53 issues on b2pneus.com.br, including 23 speed issues, 4 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