4 sec in total
915 ms
2.9 sec
147 ms
Click here to check amazing CCIB content. Otherwise, check out these important facts you probably never knew about ccib.com.mx
Visit ccib.com.mxWe analyzed Ccib.com.mx page load time and found that the first response time was 915 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
ccib.com.mx performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value7.1 s
6/100
25%
Value13.5 s
2/100
10%
Value910 ms
31/100
30%
Value0.109
87/100
15%
Value15.2 s
7/100
10%
915 ms
43 ms
68 ms
67 ms
111 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 47% of them (55 requests) were addressed to the original Ccib.com.mx, 13% (15 requests) were made to Pbs.twimg.com and 9% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (915 ms) belongs to the original domain Ccib.com.mx.
Page size can be reduced by 859.4 kB (40%)
2.1 MB
1.3 MB
In fact, the total size of Ccib.com.mx main page is 2.1 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. 65% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 43.0 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 43.0 kB or 78% of the original size.
Potential reduce by 9.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. CCIB images are well optimized though.
Potential reduce by 426.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 426.4 kB or 71% of the original size.
Potential reduce by 380.9 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. Ccib.com.mx needs all CSS files to be minified and compressed as it can save up to 380.9 kB or 85% of the original size.
Number of requests can be reduced by 74 (69%)
108
34
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CCIB. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
ccib.com.mx
915 ms
webfont.js
43 ms
styles.css
68 ms
fancybox.css
67 ms
settings.css
111 ms
woocommerce-layout.css
67 ms
woocommerce.css
147 ms
css
43 ms
easy-twitter-feed-widget.css
79 ms
bootstrap.css
208 ms
main.css
197 ms
jquery-ui-1.10.2.custom.min.css
141 ms
easy-responsive-shortcodes.css
134 ms
font-awesome.css
191 ms
jetpack.css
242 ms
jquery.js
276 ms
jquery-migrate.min.js
211 ms
jquery.fancybox.js
275 ms
jquery.themepunch.tools.min.js
327 ms
jquery.themepunch.revolution.min.js
351 ms
ccib.com.mx
665 ms
wp_clock.php
704 ms
colorbox-1.css
281 ms
jquery.form.min.js
329 ms
scripts.js
329 ms
add-to-cart.min.js
343 ms
jquery.blockUI.min.js
367 ms
woocommerce.min.js
368 ms
jquery.cookie.min.js
374 ms
cart-fragments.min.js
389 ms
devicepx-jetpack.js
22 ms
gprofiles.js
59 ms
wpgroho.js
392 ms
jquery.ui.core.min.js
421 ms
jquery.ui.datepicker.min.js
453 ms
jquery.ui.widget.min.js
427 ms
jquery.ui.mouse.min.js
441 ms
jquery.ui.slider.min.js
446 ms
jquery-ui-timepicker.js
554 ms
touch-fix.min.js
481 ms
bootstrap.min.js
524 ms
js
37 ms
e-201611.js
19 ms
underscore.min.js
488 ms
css
19 ms
custom.js
473 ms
widget-easy-twitter-feed-widget.js
508 ms
custom.js
521 ms
jquery.colorbox.js
541 ms
fb.js
497 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
6 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
22 ms
guC5lwT5Dw7anV_xfpCGqw.ttf
22 ms
Luunk03-uSz9LnB7oNEUuvesZW2xOQ-xsNqO47m55DA.ttf
22 ms
logo.png
288 ms
0000uno.jpg
374 ms
02SELLOS.jpg
374 ms
03_003.jpg
475 ms
SELLOS1.jpg
464 ms
ccV.jpg
456 ms
pattern-1.png
97 ms
fontawesome-webfont.woff
153 ms
fontawesome-webfont.woff
207 ms
RUQfOodOMiVVYqFZcSlT9w.ttf
5 ms
pattern-2.png
96 ms
widgets.js
131 ms
g.gif
24 ms
admin-ajax.php
587 ms
hovercard.css
46 ms
services.css
56 ms
all.js
17 ms
141 ms
xd_arbiter.php
28 ms
xd_arbiter.php
36 ms
overlay.png
84 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
31 ms
syndication
104 ms
532252344155533312
242 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
59 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
132 ms
TtFMwaY2_normal.jpeg
152 ms
CJViPj9UAAE_1OY.jpg:small
262 ms
CIrtV84VAAAtTUC.jpg:small
159 ms
CIdaX86UcAEJ3Os.jpg:small
164 ms
CINA_izUcAABKgW.jpg:small
157 ms
CHlMYIiUcAAu-aE.jpg:small
161 ms
CG_u-sLVAAATTiv.jpg:small
354 ms
CFY1WorUIAAjUnU.jpg:small
290 ms
CE0yxnWVIAAQdRO.jpg:small
256 ms
CDsYqpyUEAAI2AP.jpg:small
238 ms
CDJy7NWW0AAp8df.jpg:small
251 ms
CB8CwCgUEAAJ2tl.jpg:small
312 ms
CAzowUwUcAACw42.jpg:small
340 ms
B_70zBLUkAA3kNQ.jpg:small
311 ms
B_Nb5z-VEAAJ96U.jpg:small
377 ms
woocommerce-smallscreen.css
32 ms
ping
68 ms
like_box.php
360 ms
jot
32 ms
McLpmVM3wCm.css
22 ms
VH4VPudaxfN.css
28 ms
q68gy-v_YMF.js
39 ms
FJmpeSpHpjS.js
59 ms
0wM5s1Khldu.js
37 ms
1bNoFZUdlYZ.js
36 ms
10436243_951639341556684_3893106630257281970_n.png
154 ms
11231690_834811329906153_2780349797862431472_n.jpg
99 ms
1453534_681515035201793_1399049271_n.jpg
13 ms
6677_196680640706710_1612294027765803220_n.jpg
128 ms
12592780_10205079971188571_6623891617233801085_n.jpg
11 ms
1947866_1069624676434014_2463189132421211912_n.jpg
80 ms
10484140_1081109181951226_6947598746873141378_n.jpg
126 ms
wL6VQj7Ab77.png
5 ms
s7jcwEQH7Sx.png
5 ms
I6-MnjEovm5.js
7 ms
pQrUxxo5oQp.js
3 ms
ccib.com.mx 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
ccib.com.mx best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
ccib.com.mx SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ccib.com.mx 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 Ccib.com.mx 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.
ccib.com.mx
Open Graph description is not detected on the main page of CCIB. 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: