16.7 sec in total
5.8 sec
10.6 sec
282 ms
Click here to check amazing Status Puebla content for Mexico. Otherwise, check out these important facts you probably never knew about statuspuebla.com.mx
Visit statuspuebla.com.mxWe analyzed Statuspuebla.com.mx page load time and found that the first response time was 5.8 sec and then it took 10.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
statuspuebla.com.mx performance score
name
value
score
weighting
Value9.7 s
0/100
10%
Value23.3 s
0/100
25%
Value17.4 s
0/100
10%
Value910 ms
31/100
30%
Value0.061
97/100
15%
Value32.1 s
0/100
10%
5795 ms
112 ms
167 ms
26 ms
117 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 52% of them (67 requests) were addressed to the original Statuspuebla.com.mx, 16% (20 requests) were made to Static.xx.fbcdn.net and 11% (14 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Statuspuebla.com.mx.
Page size can be reduced by 2.0 MB (38%)
5.3 MB
3.3 MB
In fact, the total size of Statuspuebla.com.mx main page is 5.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. 65% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 46.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 46.3 kB or 80% of the original size.
Potential reduce by 131.1 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. Status Puebla images are well optimized though.
Potential reduce by 645.2 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 645.2 kB or 72% of the original size.
Potential reduce by 1.2 MB
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. Statuspuebla.com.mx needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 88% of the original size.
Number of requests can be reduced by 66 (52%)
126
60
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Status Puebla. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
www.statuspuebla.com.mx
5795 ms
wp-emoji-release.min.js
112 ms
layerslider.css
167 ms
css
26 ms
bnsfc-style.css
117 ms
styles.css
119 ms
settings.css
223 ms
style.css
203 ms
main.css
551 ms
plugins.css
509 ms
media.css
395 ms
dashicons.min.css
387 ms
js_composer.css
703 ms
greensock.js
446 ms
jquery.js
666 ms
jquery-migrate.min.js
506 ms
layerslider.kreaturamedia.jquery.js
670 ms
layerslider.transitions.js
673 ms
popup.js
618 ms
jquery.themepunch.tools.min.js
828 ms
jquery.themepunch.revolution.min.js
895 ms
css
15 ms
prettyPhoto.css
760 ms
owl.carousel.css
692 ms
owl.theme.default.css
695 ms
animate.min.css
867 ms
jquery.form.min.js
802 ms
scripts.js
866 ms
plugins.min.js
1068 ms
main.js
961 ms
jquery.prettyPhoto.js
969 ms
js_composer_front.js
969 ms
owl.carousel.js
1153 ms
imagesloaded.pkgd.min.js
954 ms
underscore.min.js
1064 ms
waypoints.min.js
1151 ms
vc_grid_style_all.js
1158 ms
vc_grid_style_load_more.js
1157 ms
vc_grid_style_lazy.js
1218 ms
vc_grid_style_pagination.js
1204 ms
vc_grid.js
1200 ms
masonry.pkgd.min.js
1251 ms
vc_grid_style_all_masonry.js
1157 ms
vc_grid_style_lazy_masonry.js
1122 ms
vc_grid_style_load_more_masonry.js
1196 ms
ajax-search-nav.png
585 ms
logocorel8.jpg
588 ms
BANNER-676-X-75-PX-FUNCIONARIOS.jpg
626 ms
backmondras.jpg
921 ms
backvale.jpg
929 ms
backmecinas.jpg
977 ms
socorro.jpg
996 ms
TV3.jpg
789 ms
applealaire.jpg
804 ms
alairetune.jpg
1085 ms
logocorelpeque.png
933 ms
widgets.js
83 ms
archivonarrow-regular-webfont.woff
1055 ms
archivonarrow-bold-webfont.woff
1054 ms
momizat.ttf
1175 ms
font-awesome.ttf
1220 ms
archivonarrow-bolditalic-webfont.woff
1118 ms
archivonarrow-italic-webfont.woff
1208 ms
zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff
4 ms
IQHow_FEYlDC4Gzy_m8fcgFhaRv2pGgT5Kf0An0s4MM.woff
10 ms
likebox.php
692 ms
admin-ajax.php
2260 ms
admin-ajax.php
1325 ms
admin-ajax.php
2377 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
126 ms
syndication
96 ms
534541311689236481
161 ms
ebiMDO3r-8l.css
299 ms
jGc-59L_9lo.css
373 ms
6qHpHChjY_J.css
444 ms
ztINr5qMqM_.css
566 ms
uVjHKJ0glvg.css
577 ms
TKuNj0xVh4A.js
575 ms
FJmpeSpHpjS.js
632 ms
0wM5s1Khldu.js
505 ms
1bNoFZUdlYZ.js
507 ms
njO1TPvGzoR.js
599 ms
1QuX41zDRrx.js
601 ms
Oagsvfb4VWi.js
695 ms
LTv6ZK-5zxz.js
831 ms
1FCa-btixu2.js
701 ms
proxy.jpg
41 ms
proxy.jpg
29 ms
proxy.jpg
28 ms
proxy.jpg
31 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
36 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
63 ms
ale_normal.jpg
128 ms
vale_normal.jpg
155 ms
-Kd3pfso_normal.jpeg
186 ms
Cd6p-ewUsAE3xwv.jpg:small
247 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
40 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
33 ms
proxy.jpg
60 ms
proxy.jpg
4 ms
proxy.jpg
6 ms
proxy.jpg
7 ms
1620410_794588287236361_556950749_n.jpg
297 ms
safe_image.php
300 ms
safe_image.php
363 ms
314125_494454027249790_1458070934_n.jpg
356 ms
642_103574406701708_6054950722696092962_n.jpg
497 ms
14455_4106747554711_2009620952_n.jpg
489 ms
12472343_10153632485988935_6331265391033298798_n.jpg
494 ms
971423_139002646310810_775940248_n.jpg
496 ms
12734260_132545920467598_8520391059948301680_n.jpg
495 ms
11210506_392687367589801_4875363351676622067_n.jpg
492 ms
12376287_1514138682220341_8240139910973957126_n.jpg
556 ms
11188274_893469314048635_2555493410795047809_n.jpg
558 ms
10351065_1196339477061238_6879790950469969266_n.jpg
693 ms
12795369_1190341187661067_5338009813891331475_n.png
961 ms
12814768_1189395291088990_2450552765878594336_n.jpg
627 ms
12801495_1189395231088996_2833377870053800782_n.jpg
564 ms
wL6VQj7Ab77.png
81 ms
s7jcwEQH7Sx.png
82 ms
QDwYpIaRyfG.png
82 ms
K00K-UgnsKu.png
81 ms
jot.html
27 ms
violencia-contra-la-mujer.jpg
166 ms
I6-MnjEovm5.js
72 ms
pQrUxxo5oQp.js
135 ms
eukid29.jpg
279 ms
congreso14.jpg
170 ms
print.css
112 ms
statuspuebla.com.mx accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
statuspuebla.com.mx best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
statuspuebla.com.mx SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Statuspuebla.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 Statuspuebla.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.
statuspuebla.com.mx
Open Graph description is not detected on the main page of Status Puebla. 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: