Website review, no card needed

passaromarron.com.br logo

passaromarron.com.br website review

Visit site (opens in a new tab)Reviewed 27 October 202649 issues · 90 checks

This review found 49 issues worth fixing on passaromarron.com.br, 24 of them high impact, across 90 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
6.3 s4.9 sMay 9Oct 245.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.1 s
May 16, 20265.2 s
May 23, 20265.3 s
May 30, 20265.6 s
Jun 6, 20265.9 s
Jun 13, 20266.1 s
Jun 20, 20266.2 s
Jun 27, 20266.1 s
Jul 4, 20266.0 s
Jul 11, 20265.9 s
Jul 18, 20265.8 s
Jul 25, 20265.6 s
Aug 1, 20265.4 s
Aug 8, 20265.3 s
Aug 15, 20265.2 s
Aug 22, 20265.3 s
Aug 29, 20265.3 s
Sep 5, 20265.3 s
Sep 12, 20265.2 s
Sep 19, 20265.2 s
Sep 26, 20265.2 s
Oct 3, 20265.2 s
Oct 10, 20265.1 s
Oct 17, 20265.1 s
Oct 24, 20265.0 s
Real-visitor tap response (INP)75th percentile, phones
466 ms401 msMay 9Oct 24414 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026415 ms
May 16, 2026413 ms
May 23, 2026414 ms
May 30, 2026415 ms
Jun 6, 2026413 ms
Jun 13, 2026413 ms
Jun 20, 2026411 ms
Jun 27, 2026410 ms
Jul 4, 2026413 ms
Jul 11, 2026413 ms
Jul 18, 2026415 ms
Jul 25, 2026409 ms
Aug 1, 2026408 ms
Aug 8, 2026421 ms
Aug 15, 2026431 ms
Aug 22, 2026448 ms
Aug 29, 2026458 ms
Sep 5, 2026454 ms
Sep 12, 2026450 ms
Sep 19, 2026445 ms
Sep 26, 2026435 ms
Oct 3, 2026427 ms
Oct 10, 2026416 ms
Oct 17, 2026411 ms
Oct 24, 2026414 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 passaromarron.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. passaromarron.com.br at 1.1 s1.1 s
  2. passaromarron.com.br at 2.3 s2.3 s
  3. passaromarron.com.br at 3.4 s3.4 s
  4. passaromarron.com.br at 4.6 s4.6 s
  5. passaromarron.com.br at 5.7 s5.7 s
  6. passaromarron.com.br at 6.9 s6.9 s
  7. passaromarron.com.br at 8.0 s8.0 s
  8. passaromarron.com.br at 9.2 s9.2 s

Speed

10 to fix24
  • Use efficient cache lifetimes

    13.8 s · 10.1 MB

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

  • Improve image delivery

    7.5 s · 7.3 MB

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

  • Reduce unused JavaScript

    3.8 s · 947 KiB

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

  • Render-blocking requests

    2.9 s

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

  • Font display

    1.4 s

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

  • Mobile performance score: 24

    24/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.5 MB and 1.4 s of main-thread time.

  • Reduce unused CSS

    750 ms · 96 KiB

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

  • Google Tag Manager adds 741 ms

    741 ms

    Google Tag Manager costs a phone 741 ms of main-thread work and 743 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: 3.8 s

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

  • 16 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 14 KiB

    14 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    31 KiB

    Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

    Desktop scores 62 but mobile only 24. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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: 56 ms

    56 ms

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

Core Web Vitals

12 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 LCP: 5.2 s

    5.2 s

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

  • Real-user CLS: 0.51

    0.51

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

  • Real-user FCP: 4.2 s

    4.2 s

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

  • Real-user TTFB: 2.0 s

    2.0 s

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

  • Largest Contentful Paint: 33.5 s

    33.5 s

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

  • Speed Index: 19.0 s

    19.0 s

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

  • Time to Interactive: 34.5 s

    34.5 s

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

  • Cumulative Layout Shift: 0.514

    0.514

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Real-user INP: 421 ms

    421 ms

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

  • Total Blocking Time: 475 ms

    475 ms

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

Images and page weight

5 to fix36
  • Page weight: 11.4 MB in 197 requests

    11.4 MB

    Your homepage downloads 11.4 MB in 197 requests on a phone: images 9.0 MB (36), scripts 1.9 MB (65) and fonts 335 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 4.6 MB together. On a phone connection a single image that size takes seconds.

  • 8 images in older formats

    8 images (5.7 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

    Feriado-Prolongado-Pe-Na-Areia-EOPM-1080x1350-Mobile-rvf6c4e 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 far larger than shown

    144 KiB

    3 images are downloaded at several times the size a phone draws them, for example KV-Bate-Volta-Bertioga-1080x1350-Mobile.png at 1,080 px wide, shown at 350 px. Resized copies would save about 144 KiB.

  • 1 image below the first screen load straight away

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

  • About 3.2 g of CO₂ per visit

    3.24 g

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

Accessibility

10 to fixGoogle 9190
  • 21 tap targets too small

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

  • [role="img"] and [role="image"] elements must have alternative text (19 elements)

    [role="img"] and [role="image"] elements must have alternative text: 19 elements on the page fail this check, rated serious by axe-core.

  • 12 text elements with low contrast

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

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

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 32 links without text

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

  • 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 (3 elements)

    ARIA role should be appropriate for the element: 3 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).

2 checks passed
  • Every image has alt text

    All 25 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • 2 H1 headlines

    There are 2 <h1> headlines (“Destinos mais vendidos” and “Conheça novos destinos”). One clear main headline is easier for people and search engines.

  • 126 internal links, 23 external

    The homepage links to 126 pages on passaromarron.com.br and 23 external pages.

7 checks passed
  • Meta description: 128 characters

    Your meta description is 128 characters: “Viaje com a Pássaro Marron: compre sua passagem de ônibus online, embarque rápido e com máxima segurança no trajeto. Re…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Pássaro Marron | Passagens de ônibus para os melhores destinos”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.passaromarron.com.br/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

4 to fix81
  • 2 pages share a title

    https://www.passaromarron.com.br/codigo-de-conduta and https://www.passaromarron.com.br/relacao_com_investidores all use the title “Empresa de Onibus Pássaro Marron S/A | Termos de Uso”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.passaromarron.com.br/pe-na-areia has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.passaromarron.com.br/codigo-de-conduta and https://www.passaromarron.com.br/relacao_com_investidores use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://www.passaromarron.com.br/central-de-ajuda, https://www.passaromarron.com.br/missao-visao-e-valores, https://www.passaromarron.com.br/codigo-de-conduta, https://www.passaromarron.com.br/pe-na-areia and https://www.passaromarron.com.br/metropolitano have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

  • 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

1 to fixGoogle 10084
  • 4 broken images

    4 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343173052&tm=gtm002&Ver=2&mid=17428248-4cce-4a88-9e61-235fd5883847&bo=1&sid=fab74140d22211f1866d616d2a73240d&vid=fab77a30d22211f1a6f473f83cc93731&vids=1&msclkid=N&pid=.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    57 of 61 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 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 226 words

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

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

2 checks passed
  • 3 short forms

    3 short forms (4 fields at most) are right on the homepage.

  • Analytics in place

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

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 19 cookies set on arrival

    19

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

  • 25 other companies contacted

    Loading the homepage contacts 25 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 passaromarron.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
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

Company

Employees
1,631
Headquarters
Guaratinguetá

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on passaromarron.com.br, including 22 speed issues, 1 SEO issue 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