23.7 sec in total
384 ms
23 sec
318 ms
Welcome to um.es homepage info - get ready to check Um best content for Spain right away, or after learning these important things about um.es
Web de la Universidad de Murcia
Visit um.esWe analyzed Um.es page load time and found that the first response time was 384 ms and then it took 23.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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
um.es performance score
name
value
score
weighting
Value13.2 s
0/100
10%
Value15.6 s
0/100
25%
Value16.3 s
0/100
10%
Value9,170 ms
0/100
30%
Value0.667
8/100
15%
Value33.8 s
0/100
10%
384 ms
878 ms
536 ms
280 ms
927 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 83% of them (45 requests) were addressed to the original Um.es, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source 81cbde6d-620a-4c34-9bc2-769947509df3.v4.gen66.tecnico.ulisboa.pt.
Page size can be reduced by 1.2 MB (40%)
3.0 MB
1.8 MB
In fact, the total size of Um.es main page is 3.0 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. 25% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 80.9 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 80.9 kB or 84% of the original size.
Potential reduce by 19.2 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. Um images are well optimized though.
Potential reduce by 545.9 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 545.9 kB or 67% of the original size.
Potential reduce by 586.3 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. Um.es needs all CSS files to be minified and compressed as it can save up to 586.3 kB or 82% of the original size.
Number of requests can be reduced by 13 (27%)
48
35
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Um. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
um.es
384 ms
www.um.es
878 ms
main.css
536 ms
main.css
280 ms
barebone.jsp
927 ms
main.css
660 ms
modernizr-2.6.2-respond-1.1.0.min.js
410 ms
jquery.min.js
17 ms
jquery-newsfeed.js
267 ms
bootstrap.min.js
296 ms
gen6.js
537 ms
main.js
277 ms
logo-um.jpg
400 ms
logo-cmn.jpg
394 ms
article
517 ms
flecha-prev.png
144 ms
flecha-next.png
139 ms
article
791 ms
administracion-E.png
280 ms
article
416 ms
article
423 ms
article
661 ms
article
539 ms
article
686 ms
article
567 ms
article
660 ms
article
815 ms
article
712 ms
article
802 ms
article
801 ms
article
967 ms
667a5b59-3a46-4a71-a2e9-725678bab278
854 ms
29328013-ab38-467f-b1bc-0190548e1e7b
928 ms
1F.png
936 ms
2T.png
935 ms
3.png
950 ms
4.png
987 ms
5s.png
1062 ms
6p.png
1068 ms
analytics.js
44 ms
979 ms
1026 ms
fontawesome-webfont.woff
1301 ms
collect
13 ms
principal-gprensa-liferay.php
135 ms
_.gif
582 ms
_.gif
303 ms
_.gif
584 ms
_.gif
19859 ms
_.gif
312 ms
181 ms
principal-agenda-liferay.php
146 ms
153 ms
glyphicons-halflings.png
153 ms
um.es accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
um.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
um.es 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
Tap targets are not sized appropriately
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Um.es 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 Um.es 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.
um.es
Open Graph description is not detected on the main page of Um. 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: