9.6 sec in total
3.8 sec
5.6 sec
277 ms
Visit screenplay.com now to see the best up-to-date SCREENPLAY content for United States and also check out these interesting facts you probably never knew about screenplay.com
Default Description
Visit screenplay.comWe analyzed Screenplay.com page load time and found that the first response time was 3.8 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
screenplay.com performance score
name
value
score
weighting
Value3.0 s
48/100
10%
Value5.4 s
20/100
25%
Value3.3 s
90/100
10%
Value360 ms
72/100
30%
Value0.008
100/100
15%
Value4.4 s
83/100
10%
3781 ms
147 ms
401 ms
140 ms
144 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 89% of them (32 requests) were addressed to the original Screenplay.com, 11% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Screenplay.com.
Page size can be reduced by 767.5 kB (26%)
3.0 MB
2.2 MB
In fact, the total size of Screenplay.com main page is 3.0 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. 40% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 48.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. This page needs HTML code to be minified as it can gain 9.4 kB, which is 16% 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 48.9 kB or 81% of the original size.
Potential reduce by 59.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. SCREENPLAY images are well optimized though.
Potential reduce by 435.7 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 435.7 kB or 77% of the original size.
Potential reduce by 223.5 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. Screenplay.com needs all CSS files to be minified and compressed as it can save up to 223.5 kB or 85% of the original size.
Number of requests can be reduced by 5 (15%)
33
28
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SCREENPLAY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for CSS and as a result speed up the page load time.
www.screenplay.com
3781 ms
3fbf5be356138db10b67590157b1785e.css
147 ms
41d58e4f534092e493e39484c1bf0677.js
401 ms
theme-styles.css
140 ms
theme-styles-responsive.css
144 ms
main.css
143 ms
colorstyles.css
142 ms
analytics.js
24 ms
logo-new.png
80 ms
dse.jpg
80 ms
gold-awd-2011.gif
89 ms
mms.jpg
155 ms
upbeat-editors-choice-100x81.jpg
87 ms
dp.jpg
154 ms
top10reviews.gif
153 ms
gold-awd-2009.gif
153 ms
gold-awd-2010.gif
154 ms
o4d0074.jpg
237 ms
WritingResourcesButton.jpg
323 ms
WBNewsletterButton.jpg
448 ms
WBISupportButton.jpg
338 ms
WBIEventsButton.jpg
421 ms
WBIForumsButton.jpg
460 ms
WBIDownloadsButton.jpg
493 ms
NotoSans-Regular-webfont.woff
386 ms
linkid.js
11 ms
collect
12 ms
fontawesome-webfont.woff
386 ms
collect
18 ms
slider-1-group-nobg_4.png
583 ms
slider-2-scw-nobg_1.png
610 ms
slider-3-dse-nobg_3.png
628 ms
slider-4-o4d-nobg_2.png
782 ms
switch.gif
545 ms
arrows.png
480 ms
eaabd2a65310c34af2e735e295093bc0.css
71 ms
screenplay.com accessibility score
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
Form elements do not have associated labels
screenplay.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
screenplay.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Screenplay.com 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 Screenplay.com 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.
screenplay.com
Open Graph description is not detected on the main page of SCREENPLAY. 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: