2.4 sec in total
523 ms
1.6 sec
232 ms
Welcome to bcrfondos.bancobcr.com homepage info - get ready to check Bcrfondos Bancobcr best content for Costa Rica right away, or after learning these important things about bcrfondos.bancobcr.com
Le damos la bienvenida a BCR SAFI. Cuando quiera invertir piense en nosotros
Visit bcrfondos.bancobcr.comWe analyzed Bcrfondos.bancobcr.com page load time and found that the first response time was 523 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
bcrfondos.bancobcr.com performance score
523 ms
292 ms
479 ms
148 ms
147 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 72% of them (42 requests) were addressed to the original Bcrfondos.bancobcr.com, 17% (10 requests) were made to Google.com and 5% (3 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (683 ms) belongs to the original domain Bcrfondos.bancobcr.com.
Page size can be reduced by 248.9 kB (33%)
753.4 kB
504.5 kB
In fact, the total size of Bcrfondos.bancobcr.com main page is 753.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 349.0 kB which makes up the majority of the site volume.
Potential reduce by 25.3 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 25.3 kB or 77% of the original size.
Potential reduce by 8.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. Bcrfondos Bancobcr images are well optimized though.
Potential reduce by 162.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 162.9 kB or 53% of the original size.
Potential reduce by 52.7 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. Bcrfondos.bancobcr.com needs all CSS files to be minified and compressed as it can save up to 52.7 kB or 80% of the original size.
Number of requests can be reduced by 33 (61%)
54
21
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bcrfondos Bancobcr. 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 from 11 to 1 for CSS and as a result speed up the page load time.
bcrfondos.bancobcr.com
523 ms
jquery-1.2.1.pack.js;waf2d1579bc3a0ae4b
292 ms
jquery-1.8.2.min.js;wa010bb6c024641d31
479 ms
reemplazo_home_config.js;wa93f16bc9cb994d3a
148 ms
reemplazo_home.js;waa00300a0d5116ab3
147 ms
reemplazo_home_redireccion_nomovil.js;wa7a28497ab8c704e8
148 ms
general_home.js;wa926c7933ae3371f1
302 ms
browser_version.js;waca673e6b0349ae2f
225 ms
general_home_personas.js;waf885f1c106b17d9e
301 ms
jquery.fancybox-1.3.4.pack.js;waff9b0ce5d6888bcc
249 ms
jquery-ui-personalized-1.5.2.min.js;wa52ffc0362294f081
455 ms
jquery-fieldselection.js;wa9e69551353e020dc
326 ms
vkeyboard.js;wa0163544dda848d4d
363 ms
jquery.wt-rotator.min.js;waf181fd71c9f50049
589 ms
banner.js;wa7d0423e342cb5080
375 ms
header.css;wad6a1aae6f9abd67b
401 ms
footer.css;wab0486109c76ce297
436 ms
design_home_nuevo.css;waebc9fd9757c5a09e
524 ms
layout_home_nuevo.css;wac6aadd6d91632833
497 ms
banner.css;waea44718ee2a290c4
512 ms
rotator.css;waf75422c2fb068241
542 ms
teclado.css;wa7037e903e68349ac
502 ms
jquery.fancybox-1.3.4.css;wa0d63b81fb2a4db4a
516 ms
home.css;wa0c9df4e41635dfc1
532 ms
deg_bg.jpg
96 ms
icono_per.png
93 ms
icono_co.png
97 ms
icono_for.png
89 ms
banner_select.jpg
156 ms
banner_principal_4.jpg
683 ms
banner_principal_6.jpg
229 ms
banner_itrim_dwn.jpg
159 ms
banner_rf_dwn.jpg
170 ms
banner_binf_dwn.jpg
171 ms
safi_capacita.png
360 ms
logo_bcr_footer.png
240 ms
bg_colorheader.jpg
235 ms
logo_bcrsafi.png
275 ms
cse.js
70 ms
footer_bg.jpg
327 ms
footer_bullet.png
328 ms
ga.js
53 ms
cse.js
101 ms
bg_banner_principal.png
276 ms
vtip.png
306 ms
__utm.gif
15 ms
collect
60 ms
jsapi
36 ms
default+es.css
11 ms
default.css
63 ms
default+es.I.js
23 ms
default.css
63 ms
async-ads.js
67 ms
google_custom_search_watermark.gif
58 ms
small-logo.png
38 ms
search_box_icon.png
38 ms
clear.gif
38 ms
nav_logo114.png
40 ms
bcrfondos.bancobcr.com SEO score
ES
ES
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bcrfondos.bancobcr.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Bcrfondos.bancobcr.com 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.
bcrfondos.bancobcr.com
Open Graph description is not detected on the main page of Bcrfondos Bancobcr. 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: