Tools & Wizards About Us
mediaserver.express screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

mediaserver.express

Media Server Express | Decentralized Live Streaming Demo.

Page Load Speed

1 sec in total

First Response

265 ms

Resources Loaded

694 ms

Page Rendered

88 ms

mediaserver.express screenshot

About Website

Visit mediaserver.express now to see the best up-to-date Media Server content and also check out these interesting facts you probably never knew about mediaserver.express

Create your own livestream channel and share it with the world. Unlimited concurrent users. Free. Censorship resistant.

Visit mediaserver.express

Key Findings

We analyzed Mediaserver.express page load time and found that the first response time was 265 ms and then it took 782 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

mediaserver.express performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

www.mediaserver.express

265 ms

css2

33 ms

three.min.js

32 ms

OrbitControls.js

81 ms

EffectComposer.js

84 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 9% of them (2 requests) were addressed to the original Mediaserver.express, 39% (9 requests) were made to Fonts.gstatic.com and 35% (8 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (265 ms) belongs to the original domain Mediaserver.express.

Page Optimization Overview & Recommendations

Page size can be reduced by 29.4 kB (73%)

Content Size

40.4 kB

After Optimization

11.0 kB

  • HTML

In fact, the total size of Mediaserver.express main page is 40.4 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. 20% of websites need less resources to load. HTML takes 40.4 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 29.4 kB

  • Original 40.4 kB
  • After minification 39.3 kB
  • After compression 11.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. 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 29.4 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (69%)

Requests Now

13

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.mediaserver.express

www.mediaserver.express

265 ms

css2

css2

33 ms

three.min.js

three.min.js

32 ms

OrbitControls.js

OrbitControls.js

81 ms

EffectComposer.js

EffectComposer.js

84 ms

RenderPass.js

RenderPass.js

89 ms

ShaderPass.js

ShaderPass.js

86 ms

CopyShader.js

CopyShader.js

86 ms

LuminosityHighPassShader.js

LuminosityHighPassShader.js

89 ms

UnrealBloomPass.js

UnrealBloomPass.js

85 ms

aos.css

aos.css

80 ms

aos.js

aos.js

92 ms

js

js

81 ms

medianetwork.svg

medianetwork.svg

59 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZg.ttf

53 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZg.ttf

59 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZg.ttf

73 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfMZg.ttf

81 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeMZg.ttf

81 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf

67 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZg.ttf

81 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYMZg.ttf

82 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYMZg.ttf

81 ms

Accessibility Review

mediaserver.express accessibility score

65

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

SEO Factors

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

Links do not have descriptive text

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

mediaserver.express

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