Website review, no card needed

dunloppneus.com.br logo

dunloppneus.com.br website review

Visit site (opens in a new tab)Reviewed 28 October 202658 issues · 94 checks

This review found 58 issues worth fixing on dunloppneus.com.br, 22 of them high impact, across 94 checks. The most urgent: mobile performance score: 18. 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
4.2 s2.7 sMay 9Oct 244.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.0 s
May 16, 20263.0 s
May 23, 20263.0 s
May 30, 20263.0 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20263.0 s
Jul 4, 20263.1 s
Jul 11, 20263.2 s
Jul 18, 20263.1 s
Jul 25, 20263.2 s
Aug 1, 20263.2 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20263.1 s
Sep 12, 20263.1 s
Sep 19, 20263.2 s
Sep 26, 20263.3 s
Oct 3, 20263.5 s
Oct 10, 20263.7 s
Oct 17, 20263.9 s
Oct 24, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
265 ms179 msMay 9Oct 24192 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026255 ms
May 16, 2026249 ms
May 23, 2026235 ms
May 30, 2026211 ms
Jun 6, 2026195 ms
Jun 13, 2026189 ms
Jun 20, 2026189 ms
Jun 27, 2026194 ms
Jul 4, 2026198 ms
Jul 11, 2026200 ms
Jul 18, 2026205 ms
Jul 25, 2026206 ms
Aug 1, 2026205 ms
Aug 8, 2026212 ms
Aug 15, 2026214 ms
Aug 22, 2026214 ms
Aug 29, 2026213 ms
Sep 5, 2026210 ms
Sep 12, 2026206 ms
Sep 19, 2026202 ms
Sep 26, 2026194 ms
Oct 3, 2026190 ms
Oct 10, 2026193 ms
Oct 17, 2026194 ms
Oct 24, 2026192 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 dunloppneus.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dunloppneus.com.br at 0.8 s0.8 s
  2. dunloppneus.com.br at 1.7 s1.7 s
  3. dunloppneus.com.br at 2.5 s2.5 s
  4. dunloppneus.com.br at 3.4 s3.4 s
  5. dunloppneus.com.br at 4.2 s4.2 s
  6. dunloppneus.com.br at 5.0 s5.0 s
  7. dunloppneus.com.br at 5.9 s5.9 s
  8. dunloppneus.com.br at 6.7 s6.7 s

Speed

13 to fix18
  • Mobile performance score: 18

    18/100

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

  • Main-thread work: 6.3 s

    A phone's processor spends 6.3 s on main-thread work while loading, 4.1 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 CDN and Google Tag Manager and others), adding 6.1 MB and 2.4 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Google CDN adds 657 ms

    657 ms

    Google CDN costs a phone 657 ms of main-thread work and 2.7 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.

  • vtexassets.com adds 682 ms

    682 ms

    vtexassets.com costs a phone 682 ms of main-thread work and 2.2 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.

  • Document request latency

    750 ms

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

  • Reduce initial server response time

    740 ms

    Reduce initial server response time. Google estimates savings of 740 ms on a phone.

  • Use efficient cache lifetimes

    150 ms · 576 KiB

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

  • Google Tag Manager adds 511 ms

    511 ms

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

  • Reduce unused CSS

    300 ms · 83 KiB

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

  • 2,281 HTML elements

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

  • Server response: 840 ms

    840 ms

    Your server takes 840 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 69 KiB

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

  • Improve image delivery

    178 KiB

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

  • Render-blocking requests

    150 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 67 but mobile only 18. 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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

Core Web Vitals

14 to fix0
  • 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.5 s

    3.5 s

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

  • Time to Interactive: 28.2 s

    28.2 s

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

  • Speed Index: 13.6 s

    13.6 s

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

  • Largest Contentful Paint: 7.7 s

    7.7 s

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

  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Cumulative Layout Shift: 0.375

    0.375

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

  • Total Blocking Time: 988 ms

    988 ms

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Real-user INP: 213 ms

    213 ms

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

  • Real-user CLS: 0.24

    0.24

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

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

    +32%

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 4 images without width and height

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

1 checks passed
  • Tap response (INP) got 23% faster for real visitors

    -23%

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

Images and page weight

3 to fix53
  • Page weight: 4.9 MB in 169 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 169 requests on a phone: scripts 3.0 MB (78), other files 742 KiB (54) and fonts 364 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    7018e777-1140-48a2-b9da-99468428fc01___ee4df74395f314df01b79 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 far larger than shown

    39 KiB

    1 image is downloaded at several times the size a phone draws it, for example 155711-576-576 at 576 px wide, shown at 151 px. Resized copies would save about 39 KiB.

  • 1 image in older formats

    1 image (103 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 1.4 g of CO₂ per visit

    1.37 g

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

Accessibility

8 to fixGoogle 7687
  • Invalid ARIA attributes

    4 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Unlabelled dropdowns

    3 dropdowns have no label.

  • 4 tap targets too small

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

  • Orphan list items

    Some list items are not inside a list.

  • 2 images without alt text

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

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

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

  • 20 form fields without a label

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

  • 5 links without text

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

  • 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
  • 42 automated accessibility rules passed

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

SEO

4 to fixGoogle 8576
  • No meta description

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

  • Title is short (28 characters)

    Your title is only 28 characters: “Loja Oficial da Dunlop Pneus”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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 (also missing: 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.

  • 27 internal links, 7 external

    The homepage links to 27 pages on dunloppneus.com.br and 7 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Encontre o pneu ideal”.

  • Canonical URL set

    The canonical URL is https://www.dunloppneus.com.br/undefined/.

  • 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.dunloppneus.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://www.dunloppneus.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 (164 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix62
  • 2 pages without a title

    https://www.dunloppneus.com.br/pneus/suv-s-e-pick-ups and https://www.dunloppneus.com.br/pneu-dunlop-185-65r15-88h-sp-sport-fm800-/p have no <title>, so Google invents the link text in results.

  • 5 pages share a title

    /, https://www.dunloppneus.com.br/nossaslojas, https://www.dunloppneus.com.br/sobre-a-dunlop, https://www.dunloppneus.com.br/certificacoes and https://www.dunloppneus.com.br/dicas-e-manutencao all use the title “Loja Oficial da Dunlop Pneus”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://www.dunloppneus.com.br/pneus/suv-s-e-pick-ups, https://www.dunloppneus.com.br/noticias, https://www.dunloppneus.com.br/nossaslojas, https://www.dunloppneus.com.br/sobre-a-dunlop, https://www.dunloppneus.com.br/certificacoes and https://www.dunloppneus.com.br/dicas-e-manutencao have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 links to non-canonical URLs

    Your homepage links to 14 pages by a URL that isn't their canonical one, for example https://www.dunloppneus.com.br/pneus, whose canonical is https://www.dunloppneus.com.br/undefined/pneus. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages share a meta description

    https://www.dunloppneus.com.br/pneu-dunlop-175-65r14-82t-sp-touring-r1-l/p and https://www.dunloppneus.com.br/pneu-dunlop-175-70r14-88t-sp-touring-r1-l-xl-/p use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://www.dunloppneus.com.br/pneus/suv-s-e-pick-ups, https://www.dunloppneus.com.br/noticias, https://www.dunloppneus.com.br/sobre-a-dunlop and https://www.dunloppneus.com.br/codigo-de-conduta have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://www.dunloppneus.com.br/nossaslojas, https://www.dunloppneus.com.br/pneu-dunlop-175-65r14-82t-sp-touring-r1-l/p, https://www.dunloppneus.com.br/pneu-dunlop-175-70r14-88t-sp-touring-r1-l-xl-/p, https://www.dunloppneus.com.br/pneu-dunlop-185-65r15-88h-sp-sport-fm800-/p and https://www.dunloppneus.com.br/pneu-dunlop-185-60r15-84h-enasave-ec300--/p 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.

  • 3 pages slow to respond

    https://www.dunloppneus.com.br/pneus/caminhoes-e-onibus, https://www.dunloppneus.com.br/pneus/motos and https://www.dunloppneus.com.br/noticias took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

Best practices

4 to fixGoogle 8870
  • 5 broken images

    5 images failed to load on a phone, for example https://www.dunloppneus.com.br/.

  • 14 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Warning: No Google Conversion ID is defined. Please configure it in the Google Shopping Ads App.”.

  • 1 distorted image

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

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 187 words

    The homepage has only about 187 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

1 checks passed
  • Analytics in place

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

Privacy and tracking

  • 7 trackers load before any consent

    7

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

  • 27 cookies set on arrival

    27

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

  • 43 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 dunloppneus.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 58 issues on dunloppneus.com.br, including 27 speed issues, 4 SEO issues and 5 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