Tools & Wizards About Us
registro1.uam.mx screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

registro1.uam.mx

Admisión a Licenciatura UAM

Page Load Speed

3.4 sec in total

First Response

502 ms

Resources Loaded

2.7 sec

Page Rendered

202 ms

registro1.uam.mx screenshot

About Website

Visit registro1.uam.mx now to see the best up-to-date Registro 1 UAM content for Mexico and also check out these interesting facts you probably never knew about registro1.uam.mx

Visit registro1.uam.mx

Key Findings

We analyzed Registro1.uam.mx page load time and found that the first response time was 502 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

registro1.uam.mx performance score

0

Network Requests Diagram

502 ms

analytics.js

36 ms

bootstrap.min.css

545 ms

jquery.fancybox.css

145 ms

jcarousel.css

144 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Registro1.uam.mx, 9% (4 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Admision.uam.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 497.8 kB (52%)

Content Size

957.6 kB

After Optimization

459.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Registro1.uam.mx main page is 957.6 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. 25% of websites need less resources to load. Images take 340.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 19.8 kB

  • Original 24.9 kB
  • After minification 20.6 kB
  • After compression 5.1 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 4.3 kB, which is 17% 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 19.8 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 15.4 kB

  • Original 340.8 kB
  • After minification 325.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. Registro 1 UAM images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 212.5 kB

  • Original 300.8 kB
  • After minification 259.3 kB
  • After compression 88.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 212.5 kB or 71% of the original size.

CSS Optimization

-86%

Potential reduce by 250.0 kB

  • Original 291.1 kB
  • After minification 241.8 kB
  • After compression 41.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. Registro1.uam.mx needs all CSS files to be minified and compressed as it can save up to 250.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (55%)

Requests Now

38

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

502 ms

analytics.js

analytics.js

36 ms

bootstrap.min.css

bootstrap.min.css

545 ms

jquery.fancybox.css

jquery.fancybox.css

145 ms

jcarousel.css

jcarousel.css

144 ms

flexslider.css

flexslider.css

143 ms

style.css

style.css

279 ms

default.css

default.css

270 ms

logotipo.png

logotipo.png

413 ms

collect

collect

38 ms

1.jpg

1.jpg

283 ms

2.jpg

2.jpg

284 ms

3.jpg

3.jpg

491 ms

14.jpg

14.jpg

493 ms

12.jpg

12.jpg

629 ms

11.jpg

11.jpg

694 ms

7.jpg

7.jpg

631 ms

10.jpg

10.jpg

755 ms

13.jpg

13.jpg

764 ms

jquery.js

jquery.js

906 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

698 ms

bootstrap.min.js

bootstrap.min.js

837 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

898 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

825 ms

prettify.js

prettify.js

902 ms

jquery.quicksand.js

jquery.quicksand.js

902 ms

setting.js

setting.js

960 ms

jquery.flexslider.js

jquery.flexslider.js

1177 ms

animate.js

animate.js

1033 ms

custom.js

custom.js

1037 ms

css

css

26 ms

prettify.css

prettify.css

898 ms

font-awesome.css

font-awesome.css

1037 ms

custom-fonts.css

custom-fonts.css

1024 ms

overwrite.css

overwrite.css

1168 ms

animate.css

animate.css

1307 ms

green.png

green.png

140 ms

white.png

white.png

140 ms

bg_direction_nav.png

bg_direction_nav.png

141 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

9 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

9 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

12 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

12 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

345 ms

SEO Factors

registro1.uam.mx SEO score

0

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Registro1.uam.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Registro1.uam.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

registro1.uam.mx

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