Tools & Wizards About Us
in3.uoc.edu screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

in3.uoc.edu

Internet Interdisciplinary Institute (IN3) - UOC R&I

Page Load Speed

3.9 sec in total

First Response

153 ms

Resources Loaded

3.4 sec

Page Rendered

312 ms

in3.uoc.edu screenshot

About Website

Visit in3.uoc.edu now to see the best up-to-date IN3 UOC content for Spain and also check out these interesting facts you probably never knew about in3.uoc.edu

L'Internet Interdisciplinary Institute (IN3) és un institut de recerca de la UOC especialitzat en recerca sobre la societat en xarxa i el coneixement

Visit in3.uoc.edu

Key Findings

We analyzed In3.uoc.edu page load time and found that the first response time was 153 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

in3.uoc.edu performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value1,050 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.11

87/100

15%

TTI (Time to Interactive)

Value13.0 s

13/100

10%

Network Requests Diagram

in3.uoc.edu

153 ms

in3.uoc.edu

289 ms

index.html

154 ms

index.html

371 ms

gef.min.css

496 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original In3.uoc.edu, 72% (21 requests) were made to Uoc.edu and 7% (2 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Uoc.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.9 kB (6%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of In3.uoc.edu main page is 1.2 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. 35% of websites need less resources to load. Images take 886.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 48.7 kB

  • Original 58.4 kB
  • After minification 53.7 kB
  • After compression 9.8 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 48.7 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 16.8 kB

  • Original 886.9 kB
  • After minification 870.0 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. IN3 UOC images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 430 B

  • Original 179.8 kB
  • After minification 179.8 kB
  • After compression 179.3 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.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 63.7 kB
  • After minification 63.7 kB
  • After compression 63.7 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. In3.uoc.edu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 6 (33%)

Requests Now

18

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

in3.uoc.edu

in3.uoc.edu

153 ms

in3.uoc.edu

in3.uoc.edu

289 ms

index.html

index.html

154 ms

index.html

index.html

371 ms

gef.min.css

gef.min.css

496 ms

webReader.js

webReader.js

156 ms

portal.min.css

portal.min.css

529 ms

portal.min.ca.js

portal.min.ca.js

573 ms

iframe_api

iframe_api

218 ms

player.js

player.js

212 ms

logo-uoc-default.png

logo-uoc-default.png

219 ms

logo-ucc.jpg

logo-ucc.jpg

352 ms

hrs4r-home.svg

hrs4r-home.svg

213 ms

logo-footer.png

logo-footer.png

282 ms

gtm.js

gtm.js

283 ms

UOCSans-Regular.otf

UOCSans-Regular.otf

495 ms

UOCSans-Bold.otf

UOCSans-Bold.otf

357 ms

UOCSerif-Regular.otf

UOCSerif-Regular.otf

524 ms

UOCSerif-Bold.otf

UOCSerif-Bold.otf

632 ms

icons.woff

icons.woff

595 ms

lazyload-8.17.0.min.js

lazyload-8.17.0.min.js

459 ms

UOCSans-Italic.otf

UOCSans-Italic.otf

792 ms

UOCSans-BoldItalic.otf

UOCSans-BoldItalic.otf

1030 ms

www-widgetapi.js

www-widgetapi.js

5 ms

hqdefault.jpg

hqdefault.jpg

139 ms

ma-mobil-pantalla.jpeg

ma-mobil-pantalla.jpeg

15 ms

retirada-amiant.jpeg

retirada-amiant.jpeg

51 ms

diana-roig-sanz.jpeg

diana-roig-sanz.jpeg

52 ms

1713364833559.jpeg

1713364833559.jpeg

878 ms

Accessibility Review

in3.uoc.edu accessibility score

91

Accessibility Issues

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-*] attributes do not match their roles

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

Links do not have a discernible name

Best Practices

in3.uoc.edu best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

in3.uoc.edu SEO score

98

Search Engine Optimization Advices

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

    CA

  • Language Claimed

    CA

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise In3.uoc.edu can be misinterpreted by Google and other search engines. Our service has detected that Catalan is used on the page, and it matches the claimed language. Our system also found out that In3.uoc.edu main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

in3.uoc.edu

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