Tools & Wizards About Us
zazpollosymas.mx screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

zazpollosymas.mx

Inicio - Zaz Pollos y Más

Page Load Speed

14.3 sec in total

First Response

6 sec

Resources Loaded

7.3 sec

Page Rendered

992 ms

zazpollosymas.mx screenshot

About Website

Click here to check amazing Zaz Pollos Ymas content for Mexico. Otherwise, check out these important facts you probably never knew about zazpollosymas.mx

Menú Zaz Pollos entero$139 medio$75 cuarto$45 Con salsa y tortillas Otras DeliZaz 4 flautas$49 7 alitas$69 hamburguesa de res$65 nuggets$35 ensalda césar$69 Acompañamientos $24 arroz frijoles codito p...

Visit zazpollosymas.mx

Key Findings

We analyzed Zazpollosymas.mx page load time and found that the first response time was 6 sec and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

zazpollosymas.mx performance score

0

Network Requests Diagram

zazpollosymas.mx

5984 ms

css

23 ms

styles.css

142 ms

css

37 ms

genericons.css

203 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 47% of them (55 requests) were addressed to the original Zazpollosymas.mx, 20% (24 requests) were made to Google.com and 11% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (6 sec) belongs to the original domain Zazpollosymas.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 916.5 kB (22%)

Content Size

4.1 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zazpollosymas.mx main page is 4.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. 70% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 39.6 kB

  • Original 48.3 kB
  • After minification 47.1 kB
  • After compression 8.7 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 82% of the original size.

Image Optimization

-1%

Potential reduce by 26.1 kB

  • Original 2.8 MB
  • After minification 2.8 MB

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. Zaz Pollos Ymas images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 736.7 kB

  • Original 1.1 MB
  • After minification 1.0 MB
  • After compression 319.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 736.7 kB or 70% of the original size.

CSS Optimization

-74%

Potential reduce by 114.1 kB

  • Original 153.8 kB
  • After minification 132.5 kB
  • After compression 39.8 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. Zazpollosymas.mx needs all CSS files to be minified and compressed as it can save up to 114.1 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (49%)

Requests Now

105

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zaz Pollos Ymas. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

zazpollosymas.mx

zazpollosymas.mx

5984 ms

css

css

23 ms

styles.css

styles.css

142 ms

css

css

37 ms

genericons.css

genericons.css

203 ms

style.css

style.css

268 ms

app.css

app.css

139 ms

wppizza-responsive.css

wppizza-responsive.css

204 ms

wppizza-prettyPhoto.css

wppizza-prettyPhoto.css

194 ms

jquery.js

jquery.js

400 ms

jquery-migrate.min.js

jquery-migrate.min.js

212 ms

scripts.min.js

scripts.min.js

265 ms

jquery.validate.min.js

jquery.validate.min.js

273 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

276 ms

wppizza.prettyPhoto.custom.js.php

wppizza.prettyPhoto.custom.js.php

383 ms

easy-columns.css

easy-columns.css

336 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

322 ms

flexslider.css

flexslider.css

289 ms

public.css

public.css

292 ms

jquery.form.min.js

jquery.form.min.js

390 ms

scripts.js

scripts.js

389 ms

functions.js

functions.js

389 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

433 ms

lib.core.js

lib.core.js

417 ms

lib.view.js

lib.view.js

474 ms

client.js

client.js

422 ms

client.js

client.js

430 ms

tag.item.js

tag.item.js

433 ms

tag.ui.js

tag.ui.js

466 ms

handler.image.js

handler.image.js

489 ms

cropped-bgmenu.jpg

cropped-bgmenu.jpg

1013 ms

logoweb-e1437424637546.png

logoweb-e1437424637546.png

176 ms

moto.png

moto.png

176 ms

banner-_principal.jpg

banner-_principal.jpg

1047 ms

banner-_principal2.jpg

banner-_principal2.jpg

831 ms

menu1.jpg

menu1.jpg

298 ms

menu2.jpg

menu2.jpg

223 ms

menu3.jpg

menu3.jpg

222 ms

gajo.jpg

gajo.jpg

309 ms

menu5.jpg

menu5.jpg

399 ms

zanahoria.jpg

zanahoria.jpg

398 ms

paquete5.jpg

paquete5.jpg

401 ms

paquete7.jpg

paquete7.jpg

475 ms

paquete8.jpg

paquete8.jpg

506 ms

paquete9.jpg

paquete9.jpg

476 ms

facebook_logo.png

facebook_logo.png

586 ms

twitter_logo.png

twitter_logo.png

585 ms

foursquare_logo.png

foursquare_logo.png

659 ms

embed

embed

175 ms

bgmenu.jpg

bgmenu.jpg

752 ms

title-dark.png

title-dark.png

639 ms

bgpaquetes.jpg

bgpaquetes.jpg

824 ms

extra_clean_paper.png

extra_clean_paper.png

889 ms

concrete_wall.png

concrete_wall.png

952 ms

ODelI1aHBYDBqgeIAH2zlFzCdIATDt8zXO3QNtzVeJ8.ttf

ODelI1aHBYDBqgeIAH2zlFzCdIATDt8zXO3QNtzVeJ8.ttf

29 ms

toadOcfmlt9b38dHJxOBGEBls_1aQwi4AfipSOlE3SU.ttf

toadOcfmlt9b38dHJxOBGEBls_1aQwi4AfipSOlE3SU.ttf

34 ms

toadOcfmlt9b38dHJxOBGGAlZ1PukdtTN2z-JxSzbe8.ttf

toadOcfmlt9b38dHJxOBGGAlZ1PukdtTN2z-JxSzbe8.ttf

35 ms

fpTVHK8qsXbIeTHTrnQH6KQ4IK8jcFikBX2R8jKe4LU.ttf

fpTVHK8qsXbIeTHTrnQH6KQ4IK8jcFikBX2R8jKe4LU.ttf

42 ms

M2Jd71oPJhLKp0zdtTvoM6xot8ENfkYez2Lz7rcrw70.ttf

M2Jd71oPJhLKp0zdtTvoM6xot8ENfkYez2Lz7rcrw70.ttf

34 ms

fpTVHK8qsXbIeTHTrnQH6I48KljrVa8Zcyi9xGGohEU.ttf

fpTVHK8qsXbIeTHTrnQH6I48KljrVa8Zcyi9xGGohEU.ttf

33 ms

_weQNDK6Uf40CiGFKBBUjp0EAVxt0G0biEntp43Qt6E.ttf

_weQNDK6Uf40CiGFKBBUjp0EAVxt0G0biEntp43Qt6E.ttf

14 ms

analytics.js

analytics.js

43 ms

style.css

style.css

747 ms

css

css

15 ms

style.css

style.css

754 ms

ajax-loader.gif

ajax-loader.gif

810 ms

collect

collect

34 ms

bg_direction_nav.png

bg_direction_nav.png

797 ms

js

js

84 ms

init_embed.js

init_embed.js

53 ms

common.js

common.js

53 ms

map.js

map.js

65 ms

google4.png

google4.png

72 ms

overlay.js

overlay.js

29 ms

util.js

util.js

90 ms

onion.js

onion.js

86 ms

search_impl.js

search_impl.js

118 ms

stats.js

stats.js

81 ms

openhand_8_8.cur

openhand_8_8.cur

53 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

73 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

117 ms

kh

kh

122 ms

transparent.png

transparent.png

102 ms

controls.js

controls.js

58 ms

vt

vt

120 ms

vt

vt

154 ms

vt

vt

178 ms

vt

vt

168 ms

vt

vt

167 ms

vt

vt

170 ms

vt

vt

180 ms

vt

vt

200 ms

vt

vt

206 ms

vt

vt

218 ms

vt

vt

208 ms

vt

vt

241 ms

vt

vt

222 ms

vt

vt

255 ms

vt

vt

243 ms

vt

vt

258 ms

vt

vt

272 ms

vt

vt

281 ms

vt

vt

281 ms

vt

vt

288 ms

vt

vt

299 ms

vt

vt

310 ms

vt

vt

320 ms

css

css

113 ms

entity11.png

entity11.png

75 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

72 ms

mapcnt6.png

mapcnt6.png

80 ms

sv5.png

sv5.png

66 ms

tmapctrl.png

tmapctrl.png

52 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

17 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

23 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

31 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

32 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

25 ms

SEO Factors

zazpollosymas.mx SEO score

0

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zazpollosymas.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 Zazpollosymas.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.

Social Sharing Optimization

zazpollosymas.mx

Open Graph data is detected on the main page of Zaz Pollos Ymas. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: