Tools & Wizards About Us
pemex.gob.mx screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pemex.gob.mx

PEMEX | Transformación para impulsar a México

Page Load Speed

24.7 sec in total

First Response

452 ms

Resources Loaded

23.6 sec

Page Rendered

618 ms

pemex.gob.mx screenshot

About Website

Visit pemex.gob.mx now to see the best up-to-date PEMEX content for Mexico and also check out these interesting facts you probably never knew about pemex.gob.mx

Visit pemex.gob.mx

Key Findings

We analyzed Pemex.gob.mx page load time and found that the first response time was 452 ms and then it took 24.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

pemex.gob.mx performance score

0

Network Requests Diagram

pemex.gob.mx

452 ms

www.pemex.com

296 ms

default.aspx

781 ms

init.js

1172 ms

ScriptResource.axd

701 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Pemex.gob.mx, 70% (78 requests) were made to Pemex.com and 8% (9 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Freegeoip.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (48%)

Content Size

2.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pemex.gob.mx main page is 2.6 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. 50% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 168.2 kB

  • Original 218.5 kB
  • After minification 215.5 kB
  • After compression 50.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 168.2 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 30.4 kB

  • Original 862.8 kB
  • After minification 832.4 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. PEMEX images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 794.8 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 389.3 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 794.8 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 249.4 kB

  • Original 301.5 kB
  • After minification 263.3 kB
  • After compression 52.1 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. Pemex.gob.mx needs all CSS files to be minified and compressed as it can save up to 249.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (53%)

Requests Now

99

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pemex.gob.mx

pemex.gob.mx

452 ms

www.pemex.com

www.pemex.com

296 ms

default.aspx

default.aspx

781 ms

init.js

init.js

1172 ms

ScriptResource.axd

ScriptResource.axd

701 ms

blank.js

blank.js

285 ms

ScriptResource.axd

ScriptResource.axd

1189 ms

css

css

181 ms

controls-E9893CF.css

controls-E9893CF.css

447 ms

Menu-F9ECF129.css

Menu-F9ECF129.css

447 ms

page-layouts-21.css

page-layouts-21.css

586 ms

pmx_hide_home.css

pmx_hide_home.css

585 ms

corev4-34399E9B.css

corev4-34399E9B.css

883 ms

pmx_all_files.css

pmx_all_files.css

715 ms

pmx_custom.css

pmx_custom.css

886 ms

bootstrap.min.css

bootstrap.min.css

883 ms

pmx_ribbon_off.css

pmx_ribbon_off.css

1332 ms

jquery-latest.min.js

jquery-latest.min.js

1084 ms

WebResource.axd

WebResource.axd

857 ms

addthis_widget.js

addthis_widget.js

368 ms

pmx_site.min.v2.js

pmx_site.min.v2.js

660 ms

equalheight.js

equalheight.js

682 ms

pemexcom.js

pemexcom.js

775 ms

deferred.js

deferred.js

799 ms

css

css

33 ms

fancybox-buttons.css

fancybox-buttons.css

122 ms

pmx_indicadores.css

pmx_indicadores.css

111 ms

pmx_reset.css

pmx_reset.css

122 ms

pmx_global.css

pmx_global.css

469 ms

carousel.css

carousel.css

383 ms

qklchreset.css

qklchreset.css

235 ms

cse.js

cse.js

162 ms

bg-page.png

bg-page.png

489 ms

logo-pmx@1x.png

logo-pmx@1x.png

314 ms

WebResource.axd

WebResource.axd

136 ms

barco-pemex.jpg

barco-pemex.jpg

966 ms

datos_abiertos2.jpg

datos_abiertos2.jpg

485 ms

trabajador-plataforma-01.png

trabajador-plataforma-01.png

19840 ms

e-pot_01.jpg

e-pot_01.jpg

311 ms

e-sisi_01.jpg

e-sisi_01.jpg

481 ms

e-anticorrupcion_01.jpg

e-anticorrupcion_01.jpg

481 ms

cbn_pgr_cedac.jpg

cbn_pgr_cedac.jpg

491 ms

cbn_tranparencia_focalizada.jpg

cbn_tranparencia_focalizada.jpg

489 ms

cbn_encuesta_tranparencia_focalizada.jpg

cbn_encuesta_tranparencia_focalizada.jpg

640 ms

bn-2016-024.jpg

bn-2016-024.jpg

851 ms

news-pin.png

news-pin.png

815 ms

responsabilidad_01.jpg

responsabilidad_01.jpg

992 ms

2016_22-nacional-01.jpg

2016_22-nacional-01.jpg

846 ms

contexto.png

contexto.png

985 ms

cadena.png

cadena.png

987 ms

cadena-verde.png

cadena-verde.png

988 ms

cadena-rojo.png

cadena-rojo.png

989 ms

performance.png

performance.png

990 ms

sustentabilidad.png

sustentabilidad.png

991 ms

bdi.png

bdi.png

992 ms

inf-susttentabilidad2014.png

inf-susttentabilidad2014.png

1621 ms

pemexpass.png

pemexpass.png

993 ms

guia-pemex.png

guia-pemex.png

1072 ms

informes.png

informes.png

1073 ms

inversionistas.png

inversionistas.png

1074 ms

redes-sociales-facebook.png

redes-sociales-facebook.png

1075 ms

redes-sociales-twitter.png

redes-sociales-twitter.png

1090 ms

redes-sociales-youtube.png

redes-sociales-youtube.png

1129 ms

redes-sociales-linkedin.png

redes-sociales-linkedin.png

1130 ms

redes-sociales-flickr.png

redes-sociales-flickr.png

1386 ms

redes-sociales-rss.png

redes-sociales-rss.png

1395 ms

logo75.png

logo75.png

1359 ms

bg-menu.png

bg-menu.png

1359 ms

cse.js

cse.js

354 ms

home-over.png

home-over.png

1133 ms

bgximg-D77A2B8A.png

bgximg-D77A2B8A.png

1132 ms

Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf

Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf

172 ms

b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf

b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf

178 ms

b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf

b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf

332 ms

blk-70.png

blk-70.png

1127 ms

ga.js

ga.js

157 ms

20438 ms

300lo.json

300lo.json

191 ms

473.f0906bfa8f59dff7c7a4.js

473.f0906bfa8f59dff7c7a4.js

169 ms

texto.png

texto.png

964 ms

slider-flechas.png

slider-flechas.png

1143 ms

banners-flechas.png

banners-flechas.png

1143 ms

date.png

date.png

1125 ms

warning.png

warning.png

1120 ms

news-image.png

news-image.png

1222 ms

sh.953eb77977227bfd253ee158.html

sh.953eb77977227bfd253ee158.html

319 ms

hashtag.png

hashtag.png

1072 ms

tag.png

tag.png

854 ms

bg-redes.png

bg-redes.png

1316 ms

bg-relevantes.png

bg-relevantes.png

752 ms

redes-sociales-1.png

redes-sociales-1.png

837 ms

external-small.png

external-small.png

833 ms

jsapi

jsapi

404 ms

__utm.gif

__utm.gif

87 ms

layers.486057f6e3ab422798c9.js

layers.486057f6e3ab422798c9.js

67 ms

collect

collect

336 ms

es.js

es.js

94 ms

pixel

pixel

155 ms

default+en.css

default+en.css

40 ms

default.css

default.css

180 ms

default+en.I.js

default+en.I.js

322 ms

fql

fql

206 ms

shares.json

shares.json

169 ms

pixel

pixel

63 ms

default.css

default.css

77 ms

match-result

match-result

88 ms

share

share

291 ms

async-ads.js

async-ads.js

237 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

89 ms

small-logo.png

small-logo.png

56 ms

search_box_icon.png

search_box_icon.png

56 ms

clear.png

clear.png

55 ms

SEO Factors

pemex.gob.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 Pemex.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 Pemex.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.

Social Sharing Optimization

pemex.gob.mx

Open Graph description is not detected on the main page of PEMEX. 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: