roadrunners.com.br website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Other Google APIs/SDKs and others), adding 1.3 MB and 824 ms of main-thread time.

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

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

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

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

JSDelivr CDN costs a phone 22 ms of main-thread work and 299 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.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 KiB JavaScript is shipped twice across bundles.

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.

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 “Maratona de Curitiba 2026”.

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

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

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

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

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

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

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

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

Your homepage downloads 5.7 MB in 70 requests on a phone: images 3.4 MB (22), scripts 1.7 MB (19) and fonts 279 KiB (4). Under 2 MB keeps phones on slow connections fast.

6V8WJY7M1GF998GDF9DBLQMR2PA4T5NO46MQF1N6PBXJB5QCYL.png weighs 728 KiB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example 6V8WJY7M1GF998GDF9DBLQMR2PA4T5NO46MQF1N6PBXJB5QCYL.png at 1,141 px wide, shown at 313 px. Resized copies would save about 593 KiB.

HBBKXJ6C668OQDQUYQ4X82EPVC3EU3QKY10RPIU8RRWVH0ZNOT.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 (586 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.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Some list items are not inside a list.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://runnerhub.run/)”.

The homepage links to 60 pages on roadrunners.com.br and 17 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://roadrunners.run/estado, whose canonical is https://roadrunners.run/estado/sc. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://roadrunners.run/evento/2026-maratona-internacional-de-maringa and https://roadrunners.run/evento/2026-101-corrida-internacional-de-sao-silvestre took over 3 s to send their HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 560 words of visible text.

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

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

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.

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