Tools & Wizards About Us
mct-master.github.io screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    53% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

mct-master.github.io

The MCT Blog | The student-led blog of the University of Oslo (UiO) international master’s programme in Music, Communication & Technology (MCT)

Page Load Speed

3.4 sec in total

First Response

84 ms

Resources Loaded

2.5 sec

Page Rendered

859 ms

mct-master.github.io screenshot

About Website

Visit mct-master.github.io now to see the best up-to-date MCT Master Github content for China and also check out these interesting facts you probably never knew about mct-master.github.io

The student-led blog of the University of Oslo (UiO) international master’s programme in Music, Communication & Technology (MCT)

Visit mct-master.github.io

Key Findings

We analyzed Mct-master.github.io page load time and found that the first response time was 84 ms and then it took 3.3 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

mct-master.github.io performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

88/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value4.4 s

75/100

10%

TBT (Total Blocking Time)

Value2,580 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.195

63/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

mct-master.github.io

84 ms

mct-master.github.io

109 ms

main.css

38 ms

jquery.js

41 ms

hamburger-nav.js

36 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 52% of them (12 requests) were addressed to the original Mct-master.github.io, 26% (6 requests) were made to Fonts.gstatic.com and 13% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Uio.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 13.6 kB (1%)

Content Size

1.5 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Mct-master.github.io main page is 1.5 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 11.2 kB

  • Original 14.2 kB
  • After minification 11.3 kB
  • After compression 3.0 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 2.8 kB, which is 20% 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 11.2 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 2.4 kB

  • Original 1.4 MB
  • After minification 1.4 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. MCT Master Github images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.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 3 (20%)

Requests Now

15

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mct-master.github.io

mct-master.github.io

84 ms

mct-master.github.io

mct-master.github.io

109 ms

main.css

main.css

38 ms

jquery.js

jquery.js

41 ms

hamburger-nav.js

hamburger-nav.js

36 ms

nav-dropdown-click-handler.js

nav-dropdown-click-handler.js

35 ms

css2

css2

146 ms

analytics.js

analytics.js

404 ms

2022_07_20_stefanof_MCT_logo_grey.png

2022_07_20_stefanof_MCT_logo_grey.png

266 ms

2022_08_23_aysimab_teamc.jpeg

2022_08_23_aysimab_teamc.jpeg

1915 ms

2022_10_03_telematic_concert.jpg

2022_10_03_telematic_concert.jpg

238 ms

2022_08_26_ahmetem_team_b_square.jpeg

2022_08_26_ahmetem_team_b_square.jpeg

327 ms

2022_08_26_kristeic_teamA_thumbnail.jpg

2022_08_26_kristeic_teamA_thumbnail.jpg

329 ms

2022_06_21_joachipo_modem.jpg

2022_06_21_joachipo_modem.jpg

239 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

517 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

518 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

523 ms

KFOkCnqEu92Fr1MmgWxP.ttf

KFOkCnqEu92Fr1MmgWxP.ttf

721 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

721 ms

KFOlCnqEu92Fr1MmYUtvAw.ttf

KFOlCnqEu92Fr1MmYUtvAw.ttf

723 ms

minima-social-icons.svg

minima-social-icons.svg

413 ms

collect

collect

317 ms

collect

collect

226 ms

Accessibility Review

mct-master.github.io accessibility score

85

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.

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

Links do not have a discernible name

Best Practices

mct-master.github.io 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

mct-master.github.io SEO score

92

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

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

mct-master.github.io

Open Graph data is detected on the main page of MCT Master Github. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: