8.3 sec in total
1.8 sec
6.2 sec
296 ms
Visit contro.ly now to see the best up-to-date Contro content for Brazil and also check out these interesting facts you probably never knew about contro.ly
Todo um banco no seu bolso! O Controly é um cartão pré-pago, uma conta corrente e um aplicativo de gestão.
Visit contro.lyWe analyzed Contro.ly page load time and found that the first response time was 1.8 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
contro.ly performance score
1834 ms
301 ms
930 ms
34 ms
26 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 77% of them (54 requests) were addressed to the original Contro.ly, 6% (4 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Contro.ly.
Page size can be reduced by 1.2 MB (34%)
3.7 MB
2.5 MB
In fact, the total size of Contro.ly main page is 3.7 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. 75% 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 3.1 MB which makes up the majority of the site volume.
Potential reduce by 22.9 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 9.1 kB, which is 33% 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 22.9 kB or 82% of the original size.
Potential reduce by 759.6 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. Obviously, Contro needs image optimization as it can save up to 759.6 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 211.4 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 211.4 kB or 68% of the original size.
Potential reduce by 248.1 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. Contro.ly needs all CSS files to be minified and compressed as it can save up to 248.1 kB or 84% of the original size.
Number of requests can be reduced by 23 (36%)
64
41
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Contro. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
contro.ly
1834 ms
manifest.cache
301 ms
styles.css
930 ms
jquery.min.js
34 ms
css
26 ms
css
39 ms
modernizr.video.js
491 ms
video_background.js
638 ms
swfobject.js
641 ms
transit.min.js
581 ms
typed.js
885 ms
dzsparallaxer.css
637 ms
dzsparallaxer.js
732 ms
script.js
362 ms
loading_site.gif
761 ms
logo.png
181 ms
drawer-icon.png
151 ms
btn_stop_off.png
179 ms
logo_grande.png
172 ms
icone_celular.png
168 ms
icone_plus.png
347 ms
icone_cartao.png
347 ms
icone_sol.png
497 ms
icone_guy_relax.png
497 ms
icone_moeda.png
498 ms
icone_porco.png
515 ms
icone_guy_conquista.png
514 ms
btn_play_off.png
516 ms
btn_next_off.png
518 ms
bg_cidade.jpg
1069 ms
device_hand_mask.png
1055 ms
Downalod_App_Storedefault.png
628 ms
Downalod_Googledefault.png
646 ms
mao_cartao.png
1023 ms
como_funciona_baixar.gif
922 ms
como_funciona_cadastrar.gif
1528 ms
como_funciona_saldo.gif
1075 ms
como_funciona_usar.gif
1948 ms
bg_saldo.jpg
1484 ms
bg_saldo.jpg
1509 ms
bg_chat.jpg
1385 ms
chat_completo.png
1566 ms
chat_balao_controly_02.png
1561 ms
chat_balao_usuario_02.png
1634 ms
chat_balao_controly_01.png
1661 ms
chat_balao_usuario_01.png
1683 ms
chat_campo_texto.png
2022 ms
beneficios_seguro.gif
3824 ms
anim_mundo.gif
2088 ms
iframe_api
66 ms
anim_saques.gif
1746 ms
qLBu5CQmSMt1H43OiWJ77aCWcynf_cDxXwCLxiixG1c.ttf
16 ms
4GwpJM7qx9X5Obd9KsnKxQ.ttf
28 ms
www-widgetapi.js
21 ms
bg_vem_ser_livre.jpg
2149 ms
naKRoiHc5-8
65 ms
TdmkPO17P0k
70 ms
redes_instagram.png
1808 ms
redes_facebook.png
1924 ms
redes_linkedin.png
1944 ms
redes_twitter.png
1999 ms
www-embed-player-vflQrT_sR.css
12 ms
www-embed-player.js
58 ms
base.js
121 ms
celular_objetivos.png
1944 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
73 ms
ad_status.js
72 ms
device_hand.png
2524 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
48 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
48 ms
contro.ly SEO score
EN
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Contro.ly can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Portuguese language. Our system also found out that Contro.ly 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.
contro.ly
Open Graph description is not detected on the main page of Contro. 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: