13.1 sec in total
548 ms
12.2 sec
409 ms
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.orgWe 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.
screen.org performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value8.6 s
1/100
25%
Value8.1 s
21/100
10%
Value1,050 ms
25/100
30%
Value0.018
100/100
15%
Value17.2 s
4/100
10%
548 ms
116 ms
2088 ms
1270 ms
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 size can be reduced by 168.5 kB (17%)
964.6 kB
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.
Potential reduce by 145.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 145.0 kB or 87% of the original size.
Potential reduce by 9.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.
Potential reduce by 9.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.
Potential reduce by 4.6 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.
Number of requests can be reduced by 61 (79%)
77
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.
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
autoptimize_single_52799d935694b4dbd6e4d44cb7c58d5a.css
1114 ms
autoptimize_single_d6bdaba8cfc45a003036487d64e8fa92.css
928 ms
autoptimize_single_7f538c52122c4ce8706ab80b3b1dcc04.css
1127 ms
autoptimize_single_8617d5dd629c15e40747247528a28d02.css
1876 ms
autoptimize_single_158a747fc6391ef446508410b48bba96.css
995 ms
autoptimize_single_f4d5c4150f6e99fa0f2e6aab00b191df.css
1961 ms
autoptimize_single_d597ee0583d2eaad1734740c4f0a4e7c.css
1119 ms
autoptimize_single_7cfb88165516851e9a459af84828bce1.css
1124 ms
autoptimize_single_a950802b82fafe7960025a2b7691fdf6.css
1139 ms
autoptimize_single_2bdaa6f8ec787cc8fca04304ba330ae3.css
1132 ms
autoptimize_single_b144818be9f2a78ae70fdcfd32982297.css
2035 ms
autoptimize_single_3dbaefe2f320fb8dbc9da43e71fb7b81.css
2012 ms
autoptimize_single_ab8e83a1e0e93a157e10b979b4f08e4f.css
2184 ms
autoptimize_single_4ae17b12c88c810c2f052683a2270b1d.css
2774 ms
autoptimize_single_713a0dfeb16d4ea92bee1cefdd472576.css
2805 ms
css
48 ms
jquery.min.js
3344 ms
jquery-migrate.min.js
2894 ms
v4-shims.min.js
2965 ms
jquery.bind-first-0.2.3.min.js
3026 ms
js.cookie-2.1.3.min.js
3624 ms
public.js
4161 ms
ecs_ajax_pagination.js
3753 ms
custom.js
3846 ms
isotope.pkgd.min.js
4085 ms
search.js
4245 ms
ecs.js
3647 ms
6938094.js
48 ms
js
63 ms
js
90 ms
autoptimize_single_5f62ec07de668165f994aa810478295c.css
4503 ms
autoptimize_single_18907b385f049d230070d7118ea6b56f.css
4624 ms
hooks.min.js
4706 ms
i18n.min.js
4938 ms
index.js
5065 ms
index.js
5118 ms
6938094.js
84 ms
dynamic-conditions-public.js
5375 ms
jquery.sticky.min.js
4557 ms
jquery.smartmenus.min.js
4753 ms
imagesloaded.min.js
4818 ms
webpack.runtime.min.js
4836 ms
frontend-modules.min.js
5284 ms
waypoints.min.js
4509 ms
core.min.js
5446 ms
frontend.min.js
5535 ms
ecspro.js
5499 ms
webpack-pro.runtime.min.js
5386 ms
frontend.min.js
5200 ms
elements-handlers.min.js
5517 ms
jet-blocks.min.js
5622 ms
jet-elements.min.js
5892 ms
jet-tabs-frontend.min.js
5529 ms
fbevents.js
113 ms
gtm.js
32 ms
screenrights-logo-1x-p6gkfsusr129avgxoyn08c8ng27o9qv3g75jcqsoga.png
2428 ms
Royalty-Payments-FI-p6gkfsuuhay0t9q1vmehnq6tqkpsqc0z4tjkl6lonc.jpg
3327 ms
International-652x366-p6gkfvod1t1vs3lyf5mdd7h7iqbwdfc657i110hi4o.jpg
3865 ms
Film-TV-Disbursements-FI-p6gkftsoo4zb4vooq4t487yabyl5y14pgy722gkah4.jpg
4098 ms
Residuals-Main-colour-balanced-scaled-p6gkftsoo4zb4vooq4t487yabyl5y14pgy722gkah4.jpg
4400 ms
heads-652x366-p6gkfwm78n363pkl9o0zxp8o4479l4fwhc5iiag3yg.jpg
4281 ms
CreativeWorkshops-p6gkftsoo4zb4vooq4t487yabyl5y14pgy722gkah4.jpg
4523 ms
The-Ocean-is-a-she_652x366-300x168.jpeg
4564 ms
Copyright2018_652x366-300x168.png
4982 ms
heads-652x366.jpg
5151 ms
AI-Copyright-Reference-Group-300x168.png
5348 ms
placeholder.png
5280 ms
banner.js
334 ms
web-interactives-embed.js
180 ms
6938094.js
252 ms
conversations-embed.js
146 ms
collectedforms.js
223 ms
Royalty_Payments_1100x500.jpg
5814 ms
insight.min.js
44 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
47 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
57 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
70 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
83 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
84 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
83 ms
fa-solid-900.woff
5787 ms
insight_tag_errors.gif
289 ms
fa-regular-400.woff
5631 ms
DIN-Medium.woff
4750 ms
fa-brands-400.woff
5998 ms
screen.org accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
screen.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
screen.org SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
screen.org
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: