Tools & Wizards About Us
wescreenplay.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wescreenplay.com

WeScreenplay - Hollywood's #1 Script Coverage Service

Page Load Speed

2.2 sec in total

First Response

212 ms

Resources Loaded

1.7 sec

Page Rendered

218 ms

wescreenplay.com screenshot

About Website

Click here to check amazing We Screenplay content for United States. Otherwise, check out these important facts you probably never knew about wescreenplay.com

Hollywood's fastest coverage service. Get quality, detailed notes on your screenplay from real humans at the most affordable prices.

Visit wescreenplay.com

Key Findings

We analyzed Wescreenplay.com page load time and found that the first response time was 212 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

wescreenplay.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.373

28/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

wescreenplay.com

212 ms

www.wescreenplay.com

375 ms

style.min.css

18 ms

svgs-attachment.css

32 ms

rplg.css

48 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 73% of them (76 requests) were addressed to the original Wescreenplay.com, 9% (9 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (584 ms) relates to the external source Dev.visualwebsiteoptimizer.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 160.9 kB (15%)

Content Size

1.1 MB

After Optimization

900.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wescreenplay.com main page is 1.1 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. 80% 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 412.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 123.6 kB

  • Original 155.1 kB
  • After minification 151.4 kB
  • After compression 31.6 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 123.6 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 20.0 kB

  • Original 412.1 kB
  • After minification 392.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. We Screenplay images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 10.4 kB

  • Original 369.3 kB
  • After minification 369.3 kB
  • After compression 358.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.

CSS Optimization

-6%

Potential reduce by 6.9 kB

  • Original 124.8 kB
  • After minification 120.8 kB
  • After compression 117.9 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. Wescreenplay.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 77 (85%)

Requests Now

91

After Optimization

14

  • Images
  • JavaScript
  • CSS

The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of We 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 52 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wescreenplay.com

wescreenplay.com

212 ms

www.wescreenplay.com

www.wescreenplay.com

375 ms

style.min.css

style.min.css

18 ms

svgs-attachment.css

svgs-attachment.css

32 ms

rplg.css

rplg.css

48 ms

swiper.min.css

swiper.min.css

37 ms

style.css

style.css

35 ms

font-awesome-legacy.min.css

font-awesome-legacy.min.css

44 ms

grid-system.css

grid-system.css

32 ms

style.css

style.css

50 ms

element-clients.css

element-clients.css

62 ms

css

css

81 ms

responsive.css

responsive.css

63 ms

skin-original.css

skin-original.css

72 ms

menu-dynamic.css

menu-dynamic.css

74 ms

widget-nectar-posts.css

widget-nectar-posts.css

70 ms

js_composer.min.css

js_composer.min.css

75 ms

basic.min.css

basic.min.css

76 ms

theme-ie11.min.css

theme-ie11.min.css

102 ms

theme.min.css

theme.min.css

82 ms

pum-site-styles.css

pum-site-styles.css

83 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

87 ms

css

css

67 ms

DOMPurify.min.js

DOMPurify.min.js

81 ms

jquery.min.js

jquery.min.js

84 ms

jquery-migrate.min.js

jquery-migrate.min.js

97 ms

svgs-inline-min.js

svgs-inline-min.js

99 ms

wpac-time.js

wpac-time.js

95 ms

blazy.min.js

blazy.min.js

100 ms

swiper.min.js

swiper.min.js

97 ms

rplg.js

rplg.js

100 ms

jquery.bind-first-0.2.3.min.js

jquery.bind-first-0.2.3.min.js

100 ms

js.cookie-2.1.3.min.js

js.cookie-2.1.3.min.js

101 ms

public.js

public.js

102 ms

jquery.json.min.js

jquery.json.min.js

209 ms

gravityforms.min.js

gravityforms.min.js

211 ms

utils.min.js

utils.min.js

210 ms

200838.js

200838.js

90 ms

animate.min.css

animate.min.css

209 ms

css

css

64 ms

style-non-critical.css

style-non-critical.css

211 ms

magnific.css

magnific.css

207 ms

core.css

core.css

196 ms

instantpage.js

instantpage.js

220 ms

jquery.easing.min.js

jquery.easing.min.js

192 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

191 ms

priority.js

priority.js

207 ms

transit.min.js

transit.min.js

206 ms

waypoints.js

waypoints.js

193 ms

imagesLoaded.min.js

imagesLoaded.min.js

191 ms

hoverintent.min.js

hoverintent.min.js

190 ms

magnific.js

magnific.js

187 ms

anime.min.js

anime.min.js

184 ms

superfish.js

superfish.js

184 ms

init.js

init.js

186 ms

touchswipe.min.js

touchswipe.min.js

180 ms

js_composer_front.min.js

js_composer_front.min.js

180 ms

dom-ready.min.js

dom-ready.min.js

177 ms

css

css

24 ms

hooks.min.js

hooks.min.js

176 ms

i18n.min.js

i18n.min.js

174 ms

a11y.min.js

a11y.min.js

167 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

166 ms

vendor-theme.min.js

vendor-theme.min.js

296 ms

scripts-theme.min.js

scripts-theme.min.js

163 ms

core.min.js

core.min.js

293 ms

pum-site-scripts.js

pum-site-scripts.js

293 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

293 ms

gtm.js

gtm.js

323 ms

hotjar-655047.js

hotjar-655047.js

363 ms

uwt.js

uwt.js

363 ms

analytics-browser-1.9.1-min.js.gz

analytics-browser-1.9.1-min.js.gz

347 ms

j.php

j.php

584 ms

WeScreenplay_Logo_Web_Dark.png

WeScreenplay_Logo_Web_Dark.png

258 ms

wescreenplay_new_coverage_format.png

wescreenplay_new_coverage_format.png

258 ms

WS-Newsletter-Modal.jpg

WS-Newsletter-Modal.jpg

261 ms

banner.js

banner.js

362 ms

200838.js

200838.js

362 ms

fb.js

fb.js

361 ms

feedbackweb-new.js

feedbackweb-new.js

362 ms

leadflows.js

leadflows.js

362 ms

collectedforms.js

collectedforms.js

341 ms

web-interactives-embed.js

web-interactives-embed.js

363 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

128 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

128 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

179 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

191 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

191 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

192 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

192 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

191 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

191 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

91 ms

icomoon.woff

icomoon.woff

60 ms

WeScreenplay_bg_02a.jpg

WeScreenplay_bg_02a.jpg

91 ms

main.js

main.js

62 ms

adsct

adsct

200 ms

adsct

adsct

160 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

49 ms

ScreenCraft_primary_logo_midnight_bv.png

ScreenCraft_primary_logo_midnight_bv.png

13 ms

tsl-logo-text-color-512x85.png

tsl-logo-text-color-512x85.png

11 ms

indiewire.png

indiewire.png

13 ms

imdb.png

imdb.png

13 ms

ew.png

ew.png

10 ms

Accessibility Review

wescreenplay.com accessibility score

88

Accessibility Issues

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

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

wescreenplay.com 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

High

Page has valid source maps

SEO Factors

wescreenplay.com SEO score

93

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 Wescreenplay.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 Wescreenplay.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.

Social Sharing Optimization

wescreenplay.com

Open Graph data is detected on the main page of We Screenplay. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: