7.6 sec in total
1.6 sec
5.8 sec
296 ms
Click here to check amazing Canalpuebla content. Otherwise, check out these important facts you probably never knew about canalpuebla.com
Visit canalpuebla.comWe analyzed Canalpuebla.com page load time and found that the first response time was 1.6 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
canalpuebla.com performance score
1559 ms
27 ms
25 ms
208 ms
266 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 85% of them (82 requests) were addressed to the original Canalpuebla.com, 5% (5 requests) were made to Netdna.bootstrapcdn.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Canalpuebla.com.
Page size can be reduced by 246.4 kB (79%)
311.2 kB
64.7 kB
In fact, the total size of Canalpuebla.com main page is 311.2 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. 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. CSS take 121.6 kB which makes up the majority of the site volume.
Potential reduce by 87.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 20.3 kB, which is 20% 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 87.9 kB or 88% of the original size.
Potential reduce by 58.1 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 58.1 kB or 65% of the original size.
Potential reduce by 100.5 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. Canalpuebla.com needs all CSS files to be minified and compressed as it can save up to 100.5 kB or 83% of the original size.
Number of requests can be reduced by 31 (33%)
94
63
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Canalpuebla. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
canalpuebla.com
1559 ms
analytics.js
27 ms
powr.js
25 ms
wp-emoji-release.min.js
208 ms
bootstrap-oscitas.css
266 ms
font-awesome.min.css
226 ms
settings.css
172 ms
captions.php
1941 ms
bootstrap.min.css
9 ms
font-awesome.css
17 ms
css
35 ms
style.css
254 ms
bootstrap-multiselect.css
302 ms
css
35 ms
style-front-end.css
346 ms
jquery.js
413 ms
jquery-migrate.min.js
351 ms
bootstrap.min.js
695 ms
respond.min.js
685 ms
jquery.themepunch.plugins.min.js
763 ms
jquery.themepunch.revolution.min.js
767 ms
bootstrap.min.js
30 ms
collect
13 ms
comment-reply.min.js
413 ms
jquery.placeholder.js
480 ms
functions.js
487 ms
custom.js
491 ms
jquery.cookie.js
551 ms
bootstrap-multiselect.js
567 ms
jquery.form.min.js
566 ms
ajax_handled.js
566 ms
loading-more.js
567 ms
wp-embed.min.js
633 ms
Logos_CanalPuebla_vectores1.png
487 ms
Screen-Shot-2016-03-17-at-6.51.56-PM-360x240.png
489 ms
play-icon.png
486 ms
feat-bg.png
485 ms
Screen-Shot-2016-03-17-at-6.52.02-PM-360x240.png
490 ms
Screen-Shot-2016-03-17-at-6.52.07-PM-360x240.png
488 ms
Screen-Shot-2016-03-17-at-6.52.12-PM-360x240.png
538 ms
Screen-Shot-2016-03-17-at-6.52.17-PM-360x240.png
490 ms
Screen-Shot-2016-03-17-at-6.52.22-PM-360x240.png
491 ms
Screen-Shot-2016-03-16-at-1.23.54-PM-360x240.png
589 ms
Screen-Shot-2016-03-16-at-1.24.00-PM-360x240.png
575 ms
Screen-Shot-2016-03-16-at-1.23.47-PM-360x240.png
630 ms
Screen-Shot-2016-03-16-at-1.22.55-PM-230x150.png
588 ms
Screen-Shot-2016-03-16-at-1.26.39-PM-230x150.png
634 ms
Screen-Shot-2016-03-14-at-10.27.44-AM-230x150.png
654 ms
Screen-Shot-2015-07-06-at-6.48.52-PM-230x150.png
711 ms
Screen-Shot-2015-07-06-at-6.49.21-PM-230x150.png
774 ms
Screen-Shot-2015-07-06-at-6.49.01-PM-230x150.png
711 ms
Screen-Shot-2015-07-06-at-6.49.16-PM-230x150.png
721 ms
Screen-Shot-2015-06-19-at-8.55.17-AM-230x150.png
832 ms
Screen-Shot-2015-06-03-at-12.54.18-PM-230x150.png
739 ms
Screen-Shot-2015-04-28-at-10.49.24-AM-230x150.png
894 ms
Screen-Shot-2015-04-28-at-10.49.47-AM-230x150.png
870 ms
Screen-Shot-2015-04-15-at-18.45.02-230x150.png
888 ms
Screen-Shot-2016-01-22-at-6.04.42-PM-230x150.png
893 ms
Screen-Shot-2015-11-17-at-12.44.06-PM-230x150.png
972 ms
Screen-Shot-2015-11-12-at-9.50.34-AM-230x150.png
983 ms
Screen-Shot-2015-11-05-at-3.11.11-PM-230x150.png
959 ms
Screen-Shot-2015-11-03-at-10.21.06-AM-230x150.png
970 ms
Screen-Shot-2015-10-21-at-1.19.52-PM-230x150.png
1086 ms
750x100-TD.jpg
1018 ms
Screen-Shot-2016-03-17-at-6.52.12-PM-230x150.png
1990 ms
Screen-Shot-2016-03-17-at-6.52.17-PM-230x150.png
1934 ms
Screen-Shot-2016-03-17-at-6.52.22-PM-230x150.png
1962 ms
Screen-Shot-2016-03-16-at-1.24.00-PM-230x150.png
1933 ms
Screen-Shot-2016-03-16-at-1.22.11-PM-230x150.png
1924 ms
fontawesome-webfont.woff
8 ms
glyphicons-halflings-regular.woff
7 ms
sdk.js
30 ms
all.js
9 ms
fontawesome-webfont.woff
1483 ms
glyphicons-halflings-regular.woff
1606 ms
Screen-Shot-2016-03-15-at-10.18.34-AM-230x150.png
1659 ms
Screen-Shot-2016-03-15-at-10.16.29-AM-230x150.png
1688 ms
Screen-Shot-2016-03-14-at-10.44.42-AM-230x150.png
1630 ms
Screen-Shot-2016-03-14-at-10.26.02-AM-230x150.png
1634 ms
Screen-Shot-2016-03-10-at-10.57.50-230x150.png
1700 ms
Screen-Shot-2016-03-10-at-10.57.30-230x150.png
1730 ms
166 ms
Screen-Shot-2016-03-10-at-10.57.24-230x150.png
1742 ms
xd_arbiter.php
42 ms
xd_arbiter.php
46 ms
Screen-Shot-2014-07-18-at-19.53.25-230x150.png
1649 ms
Screen-Shot-2014-07-24-at-12.58.55-230x150.png
1710 ms
360x146-PD.jpg
1674 ms
canal-puebla-360x146-px.png
1701 ms
banners_small-1.png
1697 ms
Screen-Shot-2014-07-18-at-19.53.25-165x108.png
1692 ms
Screen-Shot-2014-07-24-at-12.58.55-165x108.png
1637 ms
Screen-Shot-2016-03-16-at-1.22.55-PM-165x108.png
1659 ms
Screen-Shot-2016-03-16-at-1.26.39-PM-165x108.png
1655 ms
Screen-Shot-2016-03-14-at-10.27.44-AM-165x108.png
1675 ms
Screen-Shot-2016-03-14-at-10.27.03-AM-165x108.png
1647 ms
360x146-LaMejor.jpg
1669 ms
canalpuebla.com SEO score
ZH
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Canalpuebla.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Canalpuebla.com 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.
canalpuebla.com
Open Graph description is not detected on the main page of Canalpuebla. 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: