7.7 sec in total
520 ms
4.1 sec
3 sec
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 520 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
screen.org performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value8.7 s
1/100
25%
Value8.4 s
19/100
10%
Value3,100 ms
2/100
30%
Value0.029
100/100
15%
Value19.9 s
2/100
10%
520 ms
188 ms
241 ms
805 ms
806 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Screen.org, 73% (64 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 (2 sec) relates to the external source Screenrights.org.
Page size can be reduced by 225.8 kB (29%)
790.2 kB
564.4 kB
In fact, the total size of Screen.org main page is 790.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 283.4 kB which makes up the majority of the site volume.
Potential reduce by 152.5 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 152.5 kB or 88% of the original size.
Potential reduce by 5.4 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 64.2 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 64.2 kB or 39% of the original size.
Potential reduce by 3.7 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 56 (74%)
76
20
The browser has sent 76 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 47 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
screen.org
520 ms
www.screenrights.org
188 ms
autoptimize_e9fc10a9c89d0279774c0c9c5dea03e4.css
241 ms
autoptimize_single_532980f4303af791dfa9cbdf644b522f.css
805 ms
autoptimize_single_99a9206e21cf27d5f376fd7cc5e4031c.css
806 ms
autoptimize_single_958193ea8475124c177edf38da4ecdda.css
824 ms
autoptimize_single_7f538c52122c4ce8706ab80b3b1dcc04.css
800 ms
autoptimize_single_0668d3eeddc0fb49a474df84be62477f.css
801 ms
autoptimize_single_158a747fc6391ef446508410b48bba96.css
820 ms
autoptimize_single_2bdaa6f8ec787cc8fca04304ba330ae3.css
823 ms
css
866 ms
jquery.min.js
823 ms
jquery-migrate.min.js
821 ms
v4-shims.min.js
819 ms
jquery.bind-first-0.2.3.min.js
863 ms
js.cookie-2.1.3.min.js
933 ms
public.js
863 ms
ecs_ajax_pagination.js
863 ms
custom.js
863 ms
isotope.pkgd.min.js
862 ms
search.js
970 ms
ecs.js
955 ms
6938094.js
1263 ms
autoptimize_single_52a4f58637c6b59d393304a0983a4679.css
921 ms
autoptimize_single_18907b385f049d230070d7118ea6b56f.css
931 ms
regenerator-runtime.min.js
886 ms
wp-polyfill.min.js
884 ms
index.js
1115 ms
dynamic-conditions-public.js
1116 ms
jquery.smartmenus.min.js
887 ms
imagesloaded.min.js
1116 ms
webpack.runtime.min.js
1117 ms
frontend-modules.min.js
1111 ms
waypoints.min.js
1117 ms
core.min.js
1118 ms
swiper.min.js
1175 ms
share-link.min.js
1149 ms
dialog.min.js
1136 ms
frontend.min.js
1136 ms
ecspro.js
1998 ms
webpack-pro.runtime.min.js
467 ms
hooks.min.js
451 ms
i18n.min.js
449 ms
frontend.min.js
454 ms
preloaded-elements-handlers.min.js
1463 ms
jet-blocks.min.js
440 ms
jet-elements.min.js
1457 ms
jet-tabs-frontend.min.js
442 ms
preloaded-modules.min.js
443 ms
jquery.sticky.min.js
1278 ms
gtm.js
551 ms
screenrights-logo-1x-p6gkfsusr129avgxoyn08c8ng27o9qv3g75jcqsoga.png
1102 ms
Royalty_Payments_1100x500.jpg
338 ms
Royalty-Payments-FI-p6gkfsuuhay0t9q1vmehnq6tqkpsqc0z4tjkl6lonc.jpg
338 ms
International-652x366-p6gkfvod1t1vs3lyf5mdd7h7iqbwdfc657i110hi4o.jpg
339 ms
Film-TV-Disbursements-FI-p6gkftsoo4zb4vooq4t487yabyl5y14pgy722gkah4.jpg
340 ms
Residuals-Main-colour-balanced-scaled-p6gkftsoo4zb4vooq4t487yabyl5y14pgy722gkah4.jpg
342 ms
heads-652x366-p6gkfwm78n363pkl9o0zxp8o4479l4fwhc5iiag3yg.jpg
347 ms
CreativeWorkshops-p6gkftsoo4zb4vooq4t487yabyl5y14pgy722gkah4.jpg
334 ms
Broadcasters-FI.jpg
335 ms
Kim-Dalton-OAM-300x168.jpg
337 ms
SR-CAM-logo-300x168.png
338 ms
iStock_000020447774_652x366-300x168.jpeg
338 ms
placeholder.png
339 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
194 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff
195 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
308 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff
308 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
359 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff
357 ms
fa-solid-900.woff
45 ms
fa-regular-400.woff
899 ms
DIN-Medium.woff
569 ms
fa-brands-400.woff
570 ms
feedbackweb-new.js
410 ms
collectedforms.js
411 ms
6938094.js
558 ms
6938094.js
409 ms
conversations-embed.js
349 ms
insight.min.js
310 ms
analytics.js
299 ms
hotjar-342326.js
388 ms
collect
89 ms
modules.61e17720cf639c3e96a7.js
97 ms
collect
217 ms
ga-audiences
39 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
30 ms
19 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: