Programmable

Website review, no card needed

vwco.com.br logo

vwco.com.br website review

Visit site (opens in a new tab)Reviewed 30 October 202644 issues · 83 checks

This review found 44 issues worth fixing on vwco.com.br, 17 of them high impact, across 83 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

Site score

74C

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.9 s2.0 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.5 s
Aug 8, 20262.6 s
Aug 15, 20262.7 s
Aug 22, 20262.8 s
Aug 29, 20262.7 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 19, 20262.4 s
Sep 26, 20262.3 s
Oct 3, 20262.4 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
302 ms149 msMay 9Oct 24213 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026188 ms
May 16, 2026185 ms
May 23, 2026171 ms
May 30, 2026175 ms
Jun 6, 2026168 ms
Jun 13, 2026171 ms
Jun 20, 2026177 ms
Jun 27, 2026173 ms
Jul 4, 2026177 ms
Jul 11, 2026174 ms
Jul 18, 2026167 ms
Jul 25, 2026187 ms
Aug 1, 2026188 ms
Aug 8, 2026194 ms
Aug 15, 2026210 ms
Aug 22, 2026211 ms
Aug 29, 2026209 ms
Sep 5, 2026217 ms
Sep 12, 2026216 ms
Sep 19, 2026211 ms
Sep 26, 2026246 ms
Oct 3, 2026256 ms
Oct 10, 2026270 ms
Oct 17, 2026284 ms
Oct 24, 2026213 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

vwco.com.br (opens in a new tab)
Full-page screenshot of vwco.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix69

  • Use efficient cache lifetimes

    4.3 s · 14.6 MB

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

  • Improve image delivery

    4.1 s · 895 KiB

    6 images could be 895 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.1 s faster on a phone.

  • Render-blocking requests

    1.3 s

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Cloudflare CDN, JSDelivr CDN and cloudfront.net and others), adding 14.9 MB and 10 ms of main-thread time.

  • cloudfront.net adds 0 ms

    0 ms

    cloudfront.net costs a phone 0 ms of main-thread work and 14.6 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.

  • Mobile performance score: 69

    69/100

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

  • Reduce unused CSS

    170 ms · 64 KiB

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

  • Font display

    100 ms

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

  • 2 long tasks on the main thread

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

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

2 checks passed

  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 327 ms of it running JavaScript. That is comfortably low.

  • Server response: 17 ms

    17 ms

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

Core Web Vitals

8 to fix100

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

  • Largest Contentful Paint: 11.2 s

    11.2 s

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

  • Time to Interactive: 11.3 s

    11.3 s

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

  • Speed Index: 5.9 s

    5.9 s

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

  • Tap response (INP) got 33% slower for real visitors

    +33%

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

  • Real-user TTFB: 860 ms

    860 ms

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

  • 18 images without width and height

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

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

    +12%

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

6 checks passed

  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 181 ms

    181 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 58 ms

    58 ms

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

Images and page weight

3 to fix45

  • Page weight: 15.5 MB in 44 requests

    15.5 MB

    Your homepage downloads 15.5 MB in 44 requests on a phone: images 14.6 MB (23), fonts 657 KiB (7) and scripts 135 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 8 images over 500 KB

    8 images weigh 14.2 MB together. On a phone connection a single image that size takes seconds.

  • 10 images in older formats

    10 images (14.6 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.

  • About 4.4 g of CO₂ per visit

    4.40 g

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

2 checks passed

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8793

  • 9 text elements with low contrast

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

  • 18 images without alt text

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

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

    All page content should be contained by landmarks: 18 elements on the page fail 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.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h2 → h5, h3 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.

1 checks passed

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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

10 to fixGoogle 7352

  • 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 (29 characters)

    Your title is only 29 characters: “Volkswagen Caminhões e Ônibus”. 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 canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 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 XML sitemap

    No XML sitemap at https://vwco.com.br/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 2 links crawlers can't follow

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

  • 76 internal links, 30 external

    The homepage links to 76 pages on vwco.com.br and 30 external pages.

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://vwco.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 (1,187 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix58

  • 3 linked pages are broken

    Your homepage links to https://vwco.com.br/caminhoes/e-Delivery, https://vwco.com.br/caminhoes/Delivery and https://vwco.com.br/caminhoes/Constellation, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 13 pages share a title

    /, https://vwco.com.br/institucional/1223, https://vwco.com.br/pesquisa, https://vwco.com.br/ofertas, https://vwco.com.br/seminovos and https://vwco.com.br/concessionarias and 7 others all use the title “Volkswagen Caminhões e Ônibus”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages without a meta description

    https://vwco.com.br/institucional/1223, https://vwco.com.br/pesquisa, https://vwco.com.br/ofertas, https://vwco.com.br/seminovos, https://vwco.com.br/concessionarias and https://vwco.com.br/institucional/9 and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://vwco.com.br/institucional/1223, https://vwco.com.br/pesquisa, https://vwco.com.br/ofertas, https://vwco.com.br/seminovos, https://vwco.com.br/concessionarias and https://vwco.com.br/institucional/9 and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://vwco.com.br/pesquisa, https://vwco.com.br/concessionarias, https://vwco.com.br/institucional/9 and https://vwco.com.br/institucional/1 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

3 to fixGoogle 8885

  • 13 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 7 distorted images

    7 images are displayed at the wrong aspect ratio, so they look 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

4 to fix42

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

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

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

2 checks passed

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 6 cookies set on arrival

    6

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 vwco.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
jQuery
Analytics
Google Tag Manager
Hosting
CloudFront

Company

Founded
1980
Headquarters
Resende

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on vwco.com.br, including 14 speed issues, 10 SEO issues and 4 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