33.2 sec in total
13.8 sec
18.7 sec
603 ms
Visit centralkeys.com.br now to see the best up-to-date Centralkeys content for Brazil and also check out these interesting facts you probably never knew about centralkeys.com.br
Visit centralkeys.com.brWe analyzed Centralkeys.com.br page load time and found that the first response time was 13.8 sec and then it took 19.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. This domain responded with an error, which can significantly jeopardize Centralkeys.com.br rating and web reputation
centralkeys.com.br performance score
13837 ms
25 ms
8 ms
8 ms
9 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 79% of them (125 requests) were addressed to the original Centralkeys.com.br, 4% (6 requests) were made to Facebook.com and 3% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (13.8 sec) belongs to the original domain Centralkeys.com.br.
Page size can be reduced by 845.9 kB (67%)
1.3 MB
417.7 kB
In fact, the total size of Centralkeys.com.br main page is 1.3 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. Javascripts take 719.3 kB which makes up the majority of the site volume.
Potential reduce by 181.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 53.7 kB, which is 24% 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 181.9 kB or 83% of the original size.
Potential reduce by 40.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, Centralkeys needs image optimization as it can save up to 40.6 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 497.9 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 497.9 kB or 69% of the original size.
Potential reduce by 125.4 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. Centralkeys.com.br needs all CSS files to be minified and compressed as it can save up to 125.4 kB or 83% of the original size.
Number of requests can be reduced by 54 (37%)
145
91
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Centralkeys. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
centralkeys.com.br
13837 ms
css
25 ms
jquery-ui.css
8 ms
jquery-1.11.1.js
8 ms
jquery-ui.js
9 ms
default.css
998 ms
jquery.jqzoom.css
357 ms
ga.js
48 ms
__utm.gif
12 ms
jquery-ui.css
670 ms
shadowbox.css
287 ms
zfonts.css
405 ms
WebResource.axd
457 ms
ScriptResource.axd
266 ms
ScriptResource.axd
405 ms
ScriptResource.axd
400 ms
jquery-1.7.2.min.js
670 ms
MaskField.js
536 ms
shadowbox.js
798 ms
eventos.js
566 ms
jquery-ui-1.8.custom.min.js
1265 ms
autoComplete.js
609 ms
carrinho.js
664 ms
jquery.slidingmessage.js
683 ms
jquery.dialogextend.js
744 ms
jquery.slides.min.js
806 ms
counter.js
807 ms
jquery.scrollTo.js
816 ms
conversion.js
18 ms
gtm.js
33 ms
1664.jpg
2070 ms
icon_facebook.png
390 ms
icon_twitter.png
438 ms
icon_vimeo.png
440 ms
icon_afiliados.png
444 ms
img_forma_pagamento_foot.png
591 ms
selo_site_seguro.jpg
525 ms
rodapeP.png
573 ms
img_titulo_afiliados.jpg
576 ms
img_titulo_inscrevase_afiliados.jpg
580 ms
1656.jpg
2200 ms
1668.jpg
2173 ms
1676.jpg
2077 ms
1666.jpg
2272 ms
1650.jpg
2105 ms
1657.jpg
2411 ms
1661.jpg
2438 ms
1671.jpg
2621 ms
1649.jpg
2440 ms
1660.jpg
2466 ms
1679.png
2436 ms
1672.jpg
2584 ms
1659.jpg
2877 ms
1670.jpg
2743 ms
1665.jpg
2714 ms
1655.jpg
2741 ms
1680.png
2723 ms
1678.png
2942 ms
1681.png
2936 ms
1667.jpg
3064 ms
1651.jpg
2933 ms
1675.jpg
2952 ms
1648.jpg
3022 ms
1663.jpg
3227 ms
763620.jpg
3224 ms
763610.jpg
3238 ms
763616.jpg
3238 ms
105.jpg
3230 ms
114.jpg
3389 ms
121.jpg
3381 ms
112.jpg
3381 ms
119.jpg
3393 ms
120.jpg
3404 ms
113.jpg
3554 ms
30.jpg
3519 ms
analytics.js
12 ms
collect
13 ms
all.js
81 ms
bg_pattern_topbar.png
914 ms
bt_redes_sociais.gif
913 ms
widgets.js
8 ms
colabreg-webfont.woff
903 ms
icon_carrinho.gif
909 ms
icon_login.gif
907 ms
centralkeys-logo.png
905 ms
bg_menu.png
1082 ms
bg_menu_hover.png
1119 ms
bg_linha_menu.gif
1096 ms
bg_box_busca_novo.png
1095 ms
bt_buscar_novo.png
1115 ms
colabmed-webfont.woff
1084 ms
bg_tarja_tituloshome.png
1198 ms
bg_titulo_vermelho.png
1199 ms
bg_baseprodutos.png
1194 ms
bg_spot_off.png
1196 ms
bg_contador_listaprod_new.png
1196 ms
tag_promocao.png
1247 ms
bg_modal.png
1412 ms
bg_luz_listaproduto.png
1421 ms
bg_box_desconto.gif
1419 ms
bg_destaque_home.png
1417 ms
bg_txt_destaquehome.png
1418 ms
bt_comprar_destaque.png
1433 ms
bg_titulo_amarelo.png
1545 ms
colabbol-webfont.woff
1541 ms
TNtGAwzXtCEY_5hzRlIJNHYhjbSpvc47ee6xR_80Hnw.ttf
774 ms
187TYb8ysVvxar86IcDsZ3YhjbSpvc47ee6xR_80Hnw.ttf
847 ms
9QCBVh5lYUzIUw5Y0GO2jqCWcynf_cDxXwCLxiixG1c.ttf
849 ms
835 ms
colabthi-webfont.woff
1535 ms
fbds.js
762 ms
conversion_async.js
830 ms
fbevents.js
828 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
100 ms
ui-bg_flat_75_ffffff_40x100.png
776 ms
bg_legenda_vitrine.png
777 ms
bg_contador_vitrine_1.png
802 ms
bullet_vitrine.png
946 ms
tag_pre_venda.png
942 ms
70 ms
91 ms
115 ms
73 ms
72 ms
xd_arbiter.php
93 ms
xd_arbiter.php
150 ms
colabreg-webfont.ttf
952 ms
follow_button.6a78875565a912489e9aef879c881358.pt.html
27 ms
48 ms
jot
94 ms
colabmed-webfont.ttf
672 ms
761885.jpg
1561 ms
763621.jpg
1463 ms
763155.jpg
1447 ms
763535.jpg
1392 ms
746981.jpg
1470 ms
761408.jpg
1413 ms
747878.jpg
1293 ms
763614.jpg
1282 ms
colabbol-webfont.ttf
182 ms
colabthi-webfont.ttf
147 ms
763604.jpg
1272 ms
763623.jpg
1327 ms
763624.jpg
1359 ms
763628.jpg
1511 ms
763622.jpg
1484 ms
763640.jpg
1406 ms
763641.jpg
1374 ms
763629.jpg
1357 ms
763591.jpg
1356 ms
763638.jpg
1356 ms
763636.jpg
1301 ms
763633.jpg
1300 ms
763637.jpg
1316 ms
79.jpg
1476 ms
3 ms
like.php
100 ms
L70CG02Crze.js
143 ms
LVx-xkvaJ0b.png
154 ms
centralkeys.com.br SEO score
EN
PT
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Centralkeys.com.br 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 Centralkeys.com.br main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
centralkeys.com.br
Open Graph description is not detected on the main page of Centralkeys. 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: