5.9 sec in total
227 ms
3.9 sec
1.7 sec
Visit unav.es now to see the best up-to-date Unav content for Spain and also check out these interesting facts you probably never knew about unav.es
Universidad no estatal con campus en Pamplona, San Sebastián, Madrid y Barcelona. Obra corporativa del Opus Dei fundada por san Josemaría Escrivá de Balaguer
Visit unav.esWe analyzed Unav.es page load time and found that the first response time was 227 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
unav.es performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value30.5 s
0/100
25%
Value16.2 s
0/100
10%
Value1,290 ms
18/100
30%
Value0.393
26/100
15%
Value25.9 s
0/100
10%
227 ms
521 ms
470 ms
204 ms
104 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Unav.es, 94% (89 requests) were made to Unav.edu and 1% (1 request) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Unav.edu.
Page size can be reduced by 408.5 kB (8%)
4.9 MB
4.5 MB
In fact, the total size of Unav.es main page is 4.9 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 306.2 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 55.4 kB, which is 16% 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 306.2 kB or 89% of the original size.
Potential reduce by 100.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. Unav images are well optimized though.
Potential reduce by 2.0 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 38 (45%)
85
47
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Unav. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
unav.es
227 ms
www.unav.es
521 ms
www.unav.edu
470 ms
combo
204 ms
main.css
104 ms
clay.css
231 ms
main.css
18 ms
combo
108 ms
js_loader_config
20 ms
combo
256 ms
combo
150 ms
combo
358 ms
js_bundle_config
229 ms
main.css
467 ms
combo
297 ms
jquery-3.5.1.min.js
318 ms
jquery.resizeimagetoparent.min.js
307 ms
jquery-scrolltofixed.js
278 ms
jquery-ui.min.js
433 ms
jquery.tablesorter.js
405 ms
theme.default.min.css
400 ms
bootstrap-select.js
414 ms
ie10-viewport-bug-workaround.js
382 ms
ie-emulation-modes-warning.js
452 ms
all.js
69 ms
unav72.js
520 ms
unavfuncion.js
521 ms
unavfuncion_menu_responsive.js
521 ms
slick.min.js
435 ms
lazysizes.min.js
439 ms
jquery.lazy.min.js
442 ms
iframeapi.js
871 ms
main.js
553 ms
weglot.min.js
41 ms
gtm.js
95 ms
otSDKStub.js
29 ms
unav-white-logo.svg
138 ms
unav-black-logo.svg
143 ms
8a3300c6-8a81-1d29-741b-4c9aba002624
25 ms
33cdaa69-0442-69fa-938f-ced1fd71a10a
25 ms
549c697f-7e25-0e9a-be15-fade6163f7c5
134 ms
e36c232d-24f3-94ee-dee1-f55e8697b596
25 ms
3f88cff8-1aba-545c-50d2-666cf3d14a35
25 ms
acac5ae2-e8bd-2954-3078-527f4313599f
141 ms
51f473cd-9018-3562-699a-a6d69ab4fa00
25 ms
e47db857-fad0-d0ce-04af-987e968992d3
27 ms
e031cb10-2532-58cf-0e10-df247d00714b
25 ms
scroll-up.svg
134 ms
9 ms
buscar-ico.svg
24 ms
Roboto-Regular.ttf
202 ms
130 ms
Roboto-Light.ttf
396 ms
flecha-white.svg
112 ms
53ea9649-7c5c-deba-2157-684df67b0984
337 ms
flecha-black.svg
114 ms
flecha-hover.svg
335 ms
9e41cf10-9d81-bcba-fe5c-6a0500f37cc2
115 ms
a1521737-ca6d-5c03-6f1d-b8734d6dbbb2
338 ms
RobotoCondensed-Bold.ttf
326 ms
glyphicons-halflings-regular.woff
325 ms
Roboto-Black.ttf
439 ms
invoke
417 ms
Roboto-Thin.ttf
561 ms
invoke
394 ms
invoke
389 ms
invoke
532 ms
8047c724-f7ea-cf93-a62e-8b6b40e8d5fa
488 ms
eae175fe-b354-21ec-57df-e3343581e726
484 ms
6d7785da-933a-0ca9-bfdf-0771948b104f
343 ms
8e06d5ac-6228-77a6-88b0-4f0c9cfd8178
346 ms
6768bb46-a3eb-ff2f-3353-575ca94eee85
671 ms
12475973-7f27-3ff8-4ce0-3cf7266b4e9d
490 ms
683512cc-c97a-4177-0b06-bfae3935f6a5
346 ms
8477712a-08ee-3446-682f-4596c5517ce4
347 ms
09b0a09c-81ea-e63f-defb-cdeebd509942
260 ms
4e1785bf-fe87-238d-be26-c6534d3f6aff
261 ms
b2cd52aa-9afe-7c80-bd68-ead227b18efc
262 ms
04157fe3-6b87-1e45-f010-de7dd57d83d8
263 ms
29b2f66e-431d-8669-c12a-e6267e28955a
376 ms
63b63984-0ea1-9b83-0b84-231ea8973348
325 ms
329f5118-2e11-68cd-34ac-2b65baa622da
264 ms
2d40b45d-f147-d3a4-fabc-5e47fbc0f4a7
346 ms
688ca5e0-63e2-7ebf-6ca4-e0a14c2fb722
147 ms
e3a722c2-3086-8996-4f9e-45a5c7dee453
1032 ms
c63adda1-36ef-b127-619f-04ec2c503ade
58 ms
d9456a51-7112-8e14-3586-b15b9b002e24
51 ms
2b3d4195-51a7-9381-1a2f-2eb8063f700b
12 ms
190962e3-60d5-92e4-93d1-698bf013a3ac
92 ms
2dca960a-08b9-13bf-ccfc-52c68f11a64e
10 ms
787e7c7b-475c-2924-12d9-a64237d5e6f5
96 ms
fe092766-2233-ecf6-faee-49fc808fb4c2
162 ms
f00fec88-bc09-8128-c320-c5dae43e3bc1
12 ms
4c776124-f77d-9499-b6cc-f9d9b0f2b616
10 ms
ff8015cf-2104-9507-1ab5-ebc948fd9808
39 ms
unav.es accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
unav.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
unav.es SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Unav.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 Unav.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.
unav.es
Open Graph description is not detected on the main page of Unav. 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: