5 sec in total
518 ms
4.3 sec
190 ms
Welcome to umsa.edu.mx homepage info - get ready to check UMSA best content for Mexico right away, or after learning these important things about umsa.edu.mx
Visit umsa.edu.mxWe analyzed Umsa.edu.mx page load time and found that the first response time was 518 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
umsa.edu.mx performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.003
100/100
15%
Value0
0/100
10%
518 ms
127 ms
129 ms
189 ms
138 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 27% of them (23 requests) were addressed to the original Umsa.edu.mx, 32% (27 requests) were made to Static.xx.fbcdn.net and 22% (19 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Scontent.xx.fbcdn.net.
Page size can be reduced by 115.4 kB (7%)
1.6 MB
1.4 MB
In fact, the total size of Umsa.edu.mx main page is 1.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. 55% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 10.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 2.6 kB, which is 19% 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 10.1 kB or 73% of the original size.
Potential reduce by 36.8 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. UMSA images are well optimized though.
Potential reduce by 42.7 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 42.7 kB or 41% of the original size.
Potential reduce by 25.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. Umsa.edu.mx needs all CSS files to be minified and compressed as it can save up to 25.8 kB or 83% of the original size.
Number of requests can be reduced by 40 (49%)
82
42
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of UMSA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
umsa.edu.mx
518 ms
normalize.css
127 ms
base.css
129 ms
estructura.css
189 ms
modernizr-latest.js
138 ms
jsapi
20 ms
jquery.fancybox.css
128 ms
jquery.fancybox.pack.js
188 ms
modernizr-latest.js
56 ms
jquery.min.js
27 ms
jquery-ui.min.js
44 ms
body-background.png
134 ms
body-background-left.png
71 ms
body-background-right.png
70 ms
index-logo.png
135 ms
24-8992952137.png
252 ms
index-banner-doblez.png
73 ms
index-nav-secundaria.jpg
143 ms
index-nav-preparatoria.jpg
143 ms
index-nav-universidad.jpg
197 ms
index-nav-posgrados.jpg
193 ms
index-facebook.png
198 ms
index-twitter.png
205 ms
widgets.js
15 ms
footer-facebook.png
196 ms
footer-twitter.png
250 ms
analytics.js
12 ms
33-8201532382.png
486 ms
fancybox_sprite.png
240 ms
fancybox_loading.gif
245 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
24 ms
collect
26 ms
likebox.php
355 ms
syndication
96 ms
360429729729351680
155 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
3 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
6 ms
7qG9X2-O_normal.png
120 ms
kyEKgjk51ZE.css
282 ms
xgj7bXhJNEH.css
351 ms
Czh0gDTFcBt.css
420 ms
kE_Z8j4XNUS.css
482 ms
N-k91nHCZS2.css
560 ms
ZeuPykSxSED.css
552 ms
q68gy-v_YMF.js
550 ms
FJmpeSpHpjS.js
619 ms
0wM5s1Khldu.js
487 ms
1bNoFZUdlYZ.js
550 ms
njO1TPvGzoR.js
579 ms
OloiM1PZafe.js
642 ms
LTv6ZK-5zxz.js
819 ms
1FCa-btixu2.js
684 ms
Oagsvfb4VWi.js
684 ms
pObvZSrFc_4.js
689 ms
Kt4tkgSRvHH.js
686 ms
H3EKDTObx05.js
684 ms
eR-qA8bp1RM.js
752 ms
1QuX41zDRrx.js
756 ms
jot
24 ms
12821517_968199379900769_379378751507162129_n.png
556 ms
12806249_968199553234085_7897563356648201640_n.png
609 ms
12234849_1263710460321886_7214661473498966607_n.jpg
680 ms
934045_957028227702033_1371775989566671119_n.jpg
746 ms
734400_1680101225610887_2801754554831095308_n.jpg
751 ms
12548974_1031497470244493_9029591964861575947_n.jpg
748 ms
10399035_1023981391006365_1196476558489893788_n.jpg
749 ms
12790928_565503890275300_946969773792908344_n.jpg
751 ms
12745428_1022514451156266_7664884170720369601_n.jpg
750 ms
12196043_524968417668488_1949161932732211513_n.jpg
814 ms
1977423_1047386595326617_1369034517261166904_n.jpg
820 ms
1463250_492612280918642_5901225621271262005_n.jpg
817 ms
3879_1742821502630464_2552361716531914219_n.jpg
818 ms
12705468_186321381724068_8305734755187290745_n.jpg
815 ms
10001584_977581768962530_3952802341555532050_n.png
1258 ms
12321333_977581098962597_5845135393854842171_n.png
1354 ms
1934363_977418995645474_8157409594980424765_n.jpg
1090 ms
8251_977027745684599_1999381954080236494_n.png
2184 ms
1917151_977009622353078_5200476273292476313_n.png
1350 ms
wL6VQj7Ab77.png
104 ms
s7jcwEQH7Sx.png
105 ms
QDwYpIaRyfG.png
107 ms
K00K-UgnsKu.png
107 ms
gxbPuQdXIZP.png
70 ms
I6-MnjEovm5.js
70 ms
pQrUxxo5oQp.js
72 ms
umsa.edu.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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
umsa.edu.mx best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Page has valid source maps
umsa.edu.mx SEO score
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
N/A
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Umsa.edu.mx can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Spanish. Our system also found out that Umsa.edu.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.
umsa.edu.mx
Open Graph description is not detected on the main page of UMSA. 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: