4.6 sec in total
185 ms
3.7 sec
664 ms
Visit rbs.com.br now to see the best up-to-date RBS content for Brazil and also check out these interesting facts you probably never knew about rbs.com.br
Grupo RBS
Visit rbs.com.brWe analyzed Rbs.com.br page load time and found that the first response time was 185 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
rbs.com.br performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value19.0 s
0/100
25%
Value10.0 s
9/100
10%
Value1,710 ms
11/100
30%
Value0.138
79/100
15%
Value19.5 s
2/100
10%
185 ms
356 ms
63 ms
94 ms
205 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Rbs.com.br, 7% (8 requests) were made to Googletagmanager.com and 4% (4 requests) were made to D335luupugsy2.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Gruporbs.com.br.
Page size can be reduced by 574.0 kB (10%)
5.8 MB
5.2 MB
In fact, the total size of Rbs.com.br main page is 5.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. Only a small number of websites need less resources to load. Images take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 67.8 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. This page needs HTML code to be minified as it can gain 23.8 kB, which is 29% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 67.8 kB or 83% of the original size.
Potential reduce by 453.0 kB
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. RBS images are well optimized though.
Potential reduce by 36.3 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.
Potential reduce by 16.8 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. Rbs.com.br has all CSS files already compressed.
Number of requests can be reduced by 68 (66%)
103
35
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of RBS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
www.gruporbs.com.br
185 ms
www.gruporbs.com.br
356 ms
gtm.js
63 ms
animate.css
94 ms
bootstrap.min.css
205 ms
et-line-icons.css
213 ms
font-awesome.min.css
214 ms
themify-icons.css
217 ms
swiper.min.css
201 ms
justified-gallery.min.css
166 ms
magnific-popup.css
404 ms
settings.css
465 ms
layers.css
460 ms
navigation.css
466 ms
bootsnav.css
443 ms
main.css
445 ms
responsive.css
467 ms
contrast.css
481 ms
custom.css
480 ms
js
86 ms
js
87 ms
478e7376-fcb2-4266-87e0-5292d948be90-loader.js
584 ms
jquery-3.1.1.slim.min.js
41 ms
jquery.min.js
61 ms
jquery.js
557 ms
modernizr.js
468 ms
bootstrap.bundle.js
558 ms
jquery.easing.1.3.js
556 ms
skrollr.min.js
770 ms
smooth-scroll.js
772 ms
jquery.appear.js
772 ms
bootsnav.js
765 ms
jquery.nav.js
766 ms
wow.min.js
770 ms
page-scroll.js
871 ms
swiper.min.js
870 ms
jquery.count-to.js
868 ms
jquery.stellar.js
878 ms
jquery.magnific-popup.min.js
867 ms
isotope.pkgd.min.js
868 ms
imagesloaded.pkgd.min.js
886 ms
classie.js
1056 ms
hamburger-menu.js
885 ms
jquery.validate.min.js
54 ms
additional-methods.min.js
54 ms
ca31312c-1616-46a4-bc76-a8a4cccc5480-loader.js
177 ms
counter.js
1052 ms
insight.min.js
62 ms
js
52 ms
js
82 ms
js
79 ms
tfa.js
279 ms
jquery.fitvids.js
769 ms
skill.bars.jquery.js
752 ms
insight_tag_errors.gif
610 ms
justified-gallery.min.js
715 ms
jquery.easypiechart.min.js
876 ms
instafeed.min.js
878 ms
retina.min.js
774 ms
jquery.themepunch.tools.min.js
683 ms
jquery.themepunch.revolution.min.js
683 ms
json
460 ms
main.js
633 ms
downloads.js
629 ms
xjquery.mask.min.js
626 ms
js
309 ms
img-download.jpg
599 ms
8580b55594f212cf04f3a56c3f77db6d.png
844 ms
33eebc15cdce1e58776832bde10468d6.png
843 ms
1e750ffce6cd28aec18720b9fb8d4db9.png
894 ms
92eab9a8048b9850185648ad8e007435.png
893 ms
b09ceec4df1e56ac3d5056b40f89d6f4.png
857 ms
js
359 ms
analytics.js
354 ms
fa-solid-900.woff
693 ms
fa-regular-400.woff
753 ms
radomir_tinkov_-_gilroy-medium-webfont.woff
803 ms
traffic-source-cookie.min.js
111 ms
radomir_tinkov_-_gilroy-black-webfont.woff
593 ms
radomir_tinkov_-_gilroy-semibold-webfont.woff
595 ms
fa-brands-400.woff
681 ms
1cc72261d50d3365277cdd54a40f865d.png
796 ms
5bb68e58dd2c1e74b60ac71a4d558617.png
894 ms
0b5820ea1292db95d51c6a8216bbdf37.png
893 ms
7335771678f8b2ac9337ef35551bc754.png
801 ms
fa21c48fe15d13047195f77ef859ee61.png
864 ms
592519c98f7f18ed893503da14412485.png
974 ms
c8bc25693bc33bd804d5d4647f6ceb94.png
967 ms
5949a513c2c46c2afc200eafe5b01e29.png
1024 ms
ceec4a1181b3bf39726d21af13b5d255.png
1055 ms
47f817cda274de235286cdbf5d78f6cb.jpg
1245 ms
7d7da7654044421c5b081866b50888e5.jpg
1246 ms
c93639425e04c469231cff9fe9f6f23b.jpg
1314 ms
d23b2b0246b5d435161d5b383b70c8b0.jpg
1346 ms
7d7d8c1c975825d663390cccbf0df361.png
1363 ms
cds-pips.js
87 ms
eid.es5.js
88 ms
collect
90 ms
f9a0aa290c21cc75598aff4425a9ae70.jpeg
1284 ms
a2551f516578b5b879727adeb62a87ef.jpg
1327 ms
logo-tgr-white.svg
1132 ms
5fc68536e829112fd60809236d7ab3d0.jpeg
1392 ms
icon-move-light.png
1197 ms
7c59ca73198ce3933f1a6cb93bf9ec11.png
1614 ms
2cdd136c793c4c8d67993c57d0371f2a.jpeg
1467 ms
icon-move-black.png
1287 ms
23e7fa9f3bde10737b9bcb4638c1cdce.jpg
1537 ms
22d8b675ea8c598cc8b29688ce3e531b.jpg
1547 ms
5a9505301e7217e7eb0d3dac9ac07450.jpg
1572 ms
bundle.js
597 ms
neurolead.min.js
175 ms
rbs.com.br accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
rbs.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
rbs.com.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rbs.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Rbs.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.
rbs.com.br
Open Graph description is not detected on the main page of RBS. 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: