5.4 sec in total
503 ms
3.2 sec
1.7 sec
Click here to check amazing Atizapan content for Mexico. Otherwise, check out these important facts you probably never knew about atizapan.gob.mx
Visit atizapan.gob.mxWe analyzed Atizapan.gob.mx page load time and found that the first response time was 503 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
atizapan.gob.mx performance score
503 ms
218 ms
127 ms
129 ms
128 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 57% of them (67 requests) were addressed to the original Atizapan.gob.mx, 11% (13 requests) were made to Maps.googleapis.com and 10% (12 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Atizapan.gob.mx.
Page size can be reduced by 2.7 MB (12%)
21.8 MB
19.1 MB
In fact, the total size of Atizapan.gob.mx main page is 21.8 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. 85% 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. Images take 19.6 MB which makes up the majority of the site volume.
Potential reduce by 39.6 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 39.6 kB or 79% of the original size.
Potential reduce by 996.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. Atizapan images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 74% of the original size.
Potential reduce by 366.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. Atizapan.gob.mx needs all CSS files to be minified and compressed as it can save up to 366.9 kB or 84% of the original size.
Number of requests can be reduced by 49 (46%)
106
57
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Atizapan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.atizapan.gob.mx
503 ms
style.css
218 ms
bootstrap_tab.min.css
127 ms
bootstrap_dropdown.min.css
129 ms
res_tab_icon.css
128 ms
bootstrap.custom.css
205 ms
public.css
147 ms
styles.css
189 ms
jquery.fancybox.css
190 ms
sdm_wp_styles.css
191 ms
jquery.js
369 ms
jquery-migrate.min.js
251 ms
jquery.fancybox.js
316 ms
sdm_wp_scripts.js
254 ms
nextend-frontend.css
268 ms
n2-ss-8.css
320 ms
n2.js
314 ms
nextend-frontend.js
574 ms
smartslider-frontend.js
471 ms
n2-ss-8.js
390 ms
smartslider-simple-type-frontend.js
391 ms
jquery.form.min.js
362 ms
scripts.js
377 ms
bootstrap.min.js
378 ms
bootstrap-paginator.min.js
378 ms
public.js
415 ms
main.js
447 ms
bootstrap-dropdown.js
437 ms
bootstrap-tab.js
440 ms
bootstrap-tabdrop.js
467 ms
wp-embed.min.js
499 ms
wp-emoji-release.min.js
514 ms
facebook.png
325 ms
embed
450 ms
twitter.png
312 ms
youtube.png
312 ms
MUSEO%20ALM.jpg
1852 ms
overlay_pixel.png
306 ms
overlay.png
306 ms
Untitled-1.pngnew-logo.png
305 ms
menu.png
305 ms
content_texture.png
305 ms
recomendaciones.jpg
375 ms
cruz-roja.jpg
310 ms
GRAFFITI.jpg
762 ms
FOTOGRAF%C3%8DA.jpg
374 ms
bandas-banner.jpg
534 ms
papa.png
763 ms
convocatorias.jpeg
762 ms
nuevo-banner.jpg
524 ms
toros.jpg
533 ms
DIF1.jpeg
856 ms
predial.jpg
943 ms
atencion.png
860 ms
predial.png
860 ms
sapasa.png
858 ms
derechos-humanos.png
943 ms
empleo.png
943 ms
boletin.png
945 ms
four_gray_px.png
946 ms
CIA_3921.JPG
1757 ms
CIA_4632.jpg
1400 ms
CIA_3357.JPG
1662 ms
CIA_4811.jpg
1639 ms
two_gray_px.png
1111 ms
arrow_gray.png
1138 ms
analytics.js
105 ms
LVKF6Fhm76I
223 ms
raleway-regular-webfont.woff
1088 ms
raleway-light-webfont.woff
1154 ms
raleway-extrabold-webfont.woff
1229 ms
raleway-bold-webfont.woff
1304 ms
raleway-medium-webfont.woff
1316 ms
collect
147 ms
www-embed-player-vflfNyN_r.css
28 ms
www-embed-player.js
45 ms
base.js
92 ms
js
165 ms
init_embed.js
114 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
35 ms
ad_status.js
124 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
127 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
134 ms
common.js
73 ms
map.js
96 ms
google4.png
115 ms
overlay.js
112 ms
util.js
111 ms
onion.js
109 ms
search_impl.js
109 ms
StaticMapService.GetMapImage
224 ms
stats.js
55 ms
openhand_8_8.cur
91 ms
ViewportInfoService.GetViewportInfo
97 ms
ViewportInfoService.GetViewportInfo
63 ms
kh
87 ms
transparent.png
36 ms
controls.js
21 ms
css
130 ms
entity11.png
73 ms
vt
170 ms
vt
155 ms
vt
143 ms
vt
147 ms
vt
156 ms
vt
144 ms
vt
165 ms
vt
168 ms
vt
176 ms
vt
197 ms
mapcnt6.png
45 ms
sv5.png
48 ms
tmapctrl.png
35 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
10 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
26 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
26 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
25 ms
AuthenticationService.Authenticate
24 ms
atizapan.gob.mx SEO score
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Atizapan.gob.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 Atizapan.gob.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.
atizapan.gob.mx
Open Graph description is not detected on the main page of Atizapan. 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: