Tools & Wizards About Us
autoban.com.br screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 0

    Best Practices

  • 82

    SEO

    Google-friendlier than
    44% of websites

autoban.com.br

CCR AutoBAn | Rodovia Bandeirantes-Anhanguera

Page Load Speed

6 sec in total

First Response

555 ms

Resources Loaded

4.7 sec

Page Rendered

728 ms

autoban.com.br screenshot

About Website

Click here to check amazing AutoB An content for Brazil. Otherwise, check out these important facts you probably never knew about autoban.com.br

Trabalhamos constantemente para tornar a rodovia AutoBAn | Bandeirantes-Anhanguera cada vez melhor para os motoristas e passageiros. Confira!

Visit autoban.com.br

Key Findings

We analyzed Autoban.com.br page load time and found that the first response time was 555 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

autoban.com.br performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.502

16/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

autoban.com.br

555 ms

autoban.com.br

1335 ms

gtm.js

290 ms

all.min.css

204 ms

main.css

489 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 85% of them (57 requests) were addressed to the original Autoban.com.br, 4% (3 requests) were made to Cdnjs.cloudflare.com and 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Autoban.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 500.3 kB (18%)

Content Size

2.8 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Autoban.com.br main page is 2.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 302.3 kB

  • Original 366.7 kB
  • After minification 352.5 kB
  • After compression 64.4 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 302.3 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 184.9 kB

  • Original 2.3 MB
  • After minification 2.1 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. AutoB An images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 9.0 kB

  • Original 96.0 kB
  • After minification 95.7 kB
  • After compression 87.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-19%

Potential reduce by 4.2 kB

  • Original 21.7 kB
  • After minification 21.7 kB
  • After compression 17.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Autoban.com.br needs all CSS files to be minified and compressed as it can save up to 4.2 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (30%)

Requests Now

60

After Optimization

42

  • Images
  • JavaScript
  • CSS

The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AutoB An. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

autoban.com.br

autoban.com.br

555 ms

autoban.com.br

autoban.com.br

1335 ms

gtm.js

gtm.js

290 ms

all.min.css

all.min.css

204 ms

main.css

main.css

489 ms

home.css

home.css

759 ms

modernizr.min.js

modernizr.min.js

626 ms

selectivizr-min.js

selectivizr-min.js

623 ms

api.js

api.js

186 ms

maps.maplink.global

maps.maplink.global

509 ms

polyfills.js

polyfills.js

611 ms

pt-BR.js

pt-BR.js

614 ms

ga.js

ga.js

65 ms

event.mousewheel.js

event.mousewheel.js

256 ms

ccrTitleBolder.js

ccrTitleBolder.js

933 ms

jquery.unobtrusive-ajax.min.js

jquery.unobtrusive-ajax.min.js

911 ms

jquery.validate.min.js

jquery.validate.min.js

933 ms

jquery.validate.unobtrusive.min.js

jquery.validate.unobtrusive.min.js

934 ms

jquery.dd.js

jquery.dd.js

934 ms

all.min.js

all.min.js

71 ms

script.js

script.js

936 ms

__utm.gif

__utm.gif

30 ms

collect

collect

32 ms

recaptcha__en.js

recaptcha__en.js

451 ms

black-header.png

black-header.png

561 ms

logo-area.png

logo-area.png

548 ms

h1.png

h1.png

533 ms

expand-button.png

expand-button.png

547 ms

expand-menu.png

expand-menu.png

561 ms

conditions.png

conditions.png

534 ms

autoban.png

autoban.png

663 ms

shadows-s1ea43a2940.png

shadows-s1ea43a2940.png

633 ms

togglers-s3433579965.png

togglers-s3433579965.png

633 ms

right.png

right.png

635 ms

tail.png

tail.png

645 ms

tile.png

tile.png

655 ms

background-single.png

background-single.png

776 ms

map-download.png

map-download.png

775 ms

background-autoban.jpg

background-autoban.jpg

1758 ms

20210715_3270ab49e42a4ea9a7d4e0be70bd0632_chatbot-956x193-autoban-op2-red.jpg

20210715_3270ab49e42a4ea9a7d4e0be70bd0632_chatbot-956x193-autoban-op2-red.jpg

919 ms

boxes-s871ea4cb71.png

boxes-s871ea4cb71.png

797 ms

box-sc0b23f88c8.png

box-sc0b23f88c8.png

803 ms

20220628_9ef2a19bd04c448d823f6cb156d194e1_moedas-banner-web-autoban.jpg

20220628_9ef2a19bd04c448d823f6cb156d194e1_moedas-banner-web-autoban.jpg

1344 ms

20211210_5344f0e5e6f0414abc59cf699770fc15_banner-site-ccr-autoban2.jpg

20211210_5344f0e5e6f0414abc59cf699770fc15_banner-site-ccr-autoban2.jpg

1212 ms

20220614_a24644a3f60e4a7fb66d941a9496fcaf_junho-vermelho.png

20220614_a24644a3f60e4a7fb66d941a9496fcaf_junho-vermelho.png

1519 ms

image-red-text.png

image-red-text.png

946 ms

20220529_a22042c2998a4eb9923b45f066a8ae65_gerando-novos-caminhos.jpg

20220529_a22042c2998a4eb9923b45f066a8ae65_gerando-novos-caminhos.jpg

1332 ms

20220419_65f2e877026a439eaa6aed3e665c0e50_ccr0046cri00-956-x-193-2-v4.jpg

20220419_65f2e877026a439eaa6aed3e665c0e50_ccr0046cri00-956-x-193-2-v4.jpg

1383 ms

20211222_2b155c04edd142488ab5fb79ef80de5d_ccr0008cri437-956-x-193.jpg

20211222_2b155c04edd142488ab5fb79ef80de5d_ccr0008cri437-956-x-193.jpg

1632 ms

20220530_389e36eeb55c459f97d494498564d317_afaste-se.jpg

20220530_389e36eeb55c459f97d494498564d317_afaste-se.jpg

1490 ms

20190723_cf2c14588b8e410e916d9f31ca83fd0b_banner-le.png

20190723_cf2c14588b8e410e916d9f31ca83fd0b_banner-le.png

1488 ms

background.png

background.png

1526 ms

h3-bullet.png

h3-bullet.png

1625 ms

red-button-bullet.png

red-button-bullet.png

1328 ms

red-button-bullet.png

red-button-bullet.png

1349 ms

whatsapp.png

whatsapp.png

1344 ms

phone-0800.png

phone-0800.png

1435 ms

talk-ombudsman.png

talk-ombudsman.png

1441 ms

talk-ombudsman-bd.png

talk-ombudsman-bd.png

1437 ms

require-jquery.min.js

require-jquery.min.js

1492 ms

fa-brands-400.woff

fa-brands-400.woff

138 ms

david_sans-webfont.woff

david_sans-webfont.woff

1329 ms

ccr_i-webfont.woff

ccr_i-webfont.woff

1539 ms

ccr_bi-webfont.woff

ccr_bi-webfont.woff

1539 ms

logos-s7daaab5c49.png

logos-s7daaab5c49.png

1532 ms

logo-tesla.png

logo-tesla.png

1528 ms

home.js

home.js

152 ms

Accessibility Review

autoban.com.br accessibility score

87

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

SEO Factors

autoban.com.br SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Autoban.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Autoban.com.br main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

autoban.com.br

Open Graph description is not detected on the main page of AutoB An. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: