Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

screen.org

Screenrights | Rights & Royalty Management, Licensing Solutions

Page Load Speed

13.1 sec in total

First Response

548 ms

Resources Loaded

12.2 sec

Page Rendered

409 ms

screen.org screenshot

About Website

Click here to check amazing Screen content. Otherwise, check out these important facts you probably never knew about screen.org

Screenrights is a non-profit organisation that provides rights and royalty management services to the screen industry, and facilitates access to screen content for licensees.

Visit screen.org

Key Findings

We analyzed Screen.org page load time and found that the first response time was 548 ms and then it took 12.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

screen.org performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value1,050 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

screen.org

548 ms

www.screenrights.org

116 ms

autoptimize_17318a47723966ca0865b51668117729.css

2088 ms

autoptimize_single_464b2e3854e754ffe3a4422f7721385e.css

1270 ms

autoptimize_single_6c6e5d3fff15a8f1255042d22798fc48.css

989 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Screen.org, 77% (69 requests) were made to Screenrights.org and 7% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6 sec) relates to the external source Screenrights.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 168.5 kB (17%)

Content Size

964.6 kB

After Optimization

796.1 kB

In fact, the total size of Screen.org main page is 964.6 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. 50% of websites need less resources to load. Images take 348.0 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 145.0 kB

  • Original 165.9 kB
  • After minification 160.6 kB
  • After compression 20.9 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 145.0 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 9.0 kB

  • Original 348.0 kB
  • After minification 339.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. Screen images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 9.9 kB

  • Original 253.7 kB
  • After minification 253.7 kB
  • After compression 243.8 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

-2%

Potential reduce by 4.6 kB

  • Original 197.0 kB
  • After minification 196.9 kB
  • After compression 192.4 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. Screen.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 61 (79%)

Requests Now

77

After Optimization

16

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

Accessibility Review

screen.org accessibility score

86

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

screen.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

screen.org SEO score

96

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Screen.org 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 Screen.org 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 data is detected on the main page of Screen. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: