Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

feb.uva.nl

Economie en Bedrijfskunde - Universiteit van Amsterdam

Page Load Speed

3.7 sec in total

First Response

628 ms

Resources Loaded

2.7 sec

Page Rendered

378 ms

feb.uva.nl screenshot

About Website

Click here to check amazing Feb Uva content for Netherlands. Otherwise, check out these important facts you probably never knew about feb.uva.nl

In een internationale academische gemeenschap slaan we bij UvA Economie en Bedrijfskunde (EB) de brug tussen wetenschap en maatschappij. Al onze activiteiten zijn verbonden met onze academische kracht...

Visit feb.uva.nl

Key Findings

We analyzed Feb.uva.nl page load time and found that the first response time was 628 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

feb.uva.nl performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

faculteit-economie-en-bedrijfskunde.html

628 ms

gtm.js

89 ms

app.min.css

310 ms

uvacookiebar.js

377 ms

app.js

562 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Feb.uva.nl, 8% (2 requests) were made to Googletagmanager.com and 8% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (742 ms) relates to the external source Analytics.ic.uva.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 274.2 kB (74%)

Content Size

372.3 kB

After Optimization

98.1 kB

In fact, the total size of Feb.uva.nl main page is 372.3 kB. 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. Javascripts take 203.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 129.4 kB

  • Original 169.0 kB
  • After minification 155.8 kB
  • After compression 39.7 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 129.4 kB or 77% of the original size.

JavaScript Optimization

-71%

Potential reduce by 144.8 kB

  • Original 203.3 kB
  • After minification 203.3 kB
  • After compression 58.5 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 144.8 kB or 71% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

Number of requests can be reduced by 15 (65%)

Requests Now

23

After Optimization

8

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

Accessibility Review

feb.uva.nl accessibility score

94

Accessibility Issues

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

Buttons do not have an accessible name

Best Practices

feb.uva.nl best practices score

92

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

SEO Factors

feb.uva.nl SEO score

100

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

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Feb.uva.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Feb.uva.nl 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 Feb Uva. 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: