Tools & Wizards About Us

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

unav.es

Portada. Universidad de Navarra

Page Load Speed

5.9 sec in total

First Response

227 ms

Resources Loaded

3.9 sec

Page Rendered

1.7 sec

About Website

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.es

Key Findings

We 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.

Performance Metrics

unav.es performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value30.5 s

0/100

25%

SI (Speed Index)

Value16.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.393

26/100

15%

TTI (Time to Interactive)

Value25.9 s

0/100

10%

Network Requests Diagram

unav.es

227 ms

www.unav.es

521 ms

www.unav.edu

470 ms

combo

204 ms

main.css

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 Optimization Overview & Recommendations

Page size can be reduced by 408.5 kB (8%)

Content Size

4.9 MB

After Optimization

4.5 MB

  • HTML
  • Images
  • JavaScript

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.

HTML Optimization

-89%

Potential reduce by 306.2 kB

  • Original 344.4 kB
  • After minification 289.0 kB
  • After compression 38.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.

Image Optimization

-3%

Potential reduce by 100.2 kB

  • Original 3.7 MB
  • After minification 3.6 MB

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.

JavaScript Optimization

-0%

Potential reduce by 2.0 kB

  • Original 911.9 kB
  • After minification 911.7 kB
  • After compression 909.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 38 (45%)

Requests Now

85

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

unav.es accessibility score

78

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

unav.es best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

unav.es SEO score

76

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 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.

Social Sharing Optimization

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: