Tools & Wizards About Us
wescreenplay.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wescreenplay.com

WeScreenplay - Hollywood's #1 Script Coverage Service

Page Load Speed

11.2 sec in total

First Response

142 ms

Resources Loaded

9 sec

Page Rendered

2.1 sec

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 142 ms and then it took 11.1 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

wescreenplay.com performance score

0

Network Requests Diagram

wescreenplay.com

142 ms

www.wescreenplay.com

104 ms

www.wescreenplay.com

372 ms

wp-emoji-release.min.js

78 ms

blocks.style.build.css

115 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 69% of them (76 requests) were addressed to the original Wescreenplay.com, 7% (8 requests) were made to S.w.org and 6% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 341.0 kB (31%)

Content Size

1.1 MB

After Optimization

770.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. HTML takes 380.6 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 326.8 kB

  • Original 380.6 kB
  • After minification 377.1 kB
  • After compression 53.8 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 326.8 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 2.8 kB

  • Original 372.1 kB
  • After minification 369.3 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

-1%

Potential reduce by 3.0 kB

  • Original 217.4 kB
  • After minification 217.4 kB
  • After compression 214.3 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 8.3 kB

  • Original 141.3 kB
  • After minification 139.3 kB
  • After compression 133.0 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 (79%)

Requests Now

98

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 98 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 45 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wescreenplay.com

wescreenplay.com

142 ms

www.wescreenplay.com

www.wescreenplay.com

104 ms

www.wescreenplay.com

www.wescreenplay.com

372 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

78 ms

blocks.style.build.css

blocks.style.build.css

115 ms

style.min.css

style.min.css

98 ms

styles.css

styles.css

103 ms

svgs-attachment.css

svgs-attachment.css

104 ms

rplg.css

rplg.css

104 ms

swiper.min.css

swiper.min.css

109 ms

style.css

style.css

162 ms

font-awesome-legacy.min.css

font-awesome-legacy.min.css

149 ms

grid-system.css

grid-system.css

146 ms

style.css

style.css

124 ms

element-clients.css

element-clients.css

159 ms

css

css

178 ms

responsive.css

responsive.css

165 ms

skin-original.css

skin-original.css

173 ms

menu-dynamic.css

menu-dynamic.css

177 ms

widget-nectar-posts.css

widget-nectar-posts.css

177 ms

js_composer.min.css

js_composer.min.css

187 ms

basic.min.css

basic.min.css

194 ms

theme-ie11.min.css

theme-ie11.min.css

198 ms

theme.min.css

theme.min.css

200 ms

pum-site-styles.css

pum-site-styles.css

216 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

204 ms

css

css

194 ms

jquery.min.js

jquery.min.js

221 ms

jquery-migrate.min.js

jquery-migrate.min.js

219 ms

svgs-inline-min.js

svgs-inline-min.js

222 ms

wpac-time.js

wpac-time.js

217 ms

blazy.min.js

blazy.min.js

228 ms

swiper.min.js

swiper.min.js

228 ms

rplg.js

rplg.js

227 ms

jquery.json.min.js

jquery.json.min.js

226 ms

gravityforms.min.js

gravityforms.min.js

226 ms

optimize.js

optimize.js

161 ms

js

js

192 ms

animate.min.css

animate.min.css

191 ms

css

css

180 ms

magnific.css

magnific.css

194 ms

core.css

core.css

195 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

169 ms

wp-polyfill.min.js

wp-polyfill.min.js

168 ms

index.js

index.js

841 ms

instantpage.js

instantpage.js

842 ms

jquery.easing.min.js

jquery.easing.min.js

838 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

836 ms

priority.js

priority.js

838 ms

transit.min.js

transit.min.js

835 ms

waypoints.js

waypoints.js

805 ms

imagesLoaded.min.js

imagesLoaded.min.js

794 ms

hoverintent.min.js

hoverintent.min.js

794 ms

magnific.js

magnific.js

788 ms

anime.min.js

anime.min.js

784 ms

superfish.js

superfish.js

777 ms

init.js

init.js

777 ms

touchswipe.min.js

touchswipe.min.js

775 ms

js_composer_front.min.js

js_composer_front.min.js

770 ms

dom-ready.min.js

dom-ready.min.js

761 ms

hooks.min.js

hooks.min.js

757 ms

i18n.min.js

i18n.min.js

760 ms

a11y.min.js

a11y.min.js

754 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

754 ms

css

css

21 ms

core.min.js

core.min.js

740 ms

pum-site-scripts.js

pum-site-scripts.js

736 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

734 ms

js

js

589 ms

hotjar-655047.js

hotjar-655047.js

1739 ms

uwt.js

uwt.js

2103 ms

fbevents.js

fbevents.js

1364 ms

WeScreenplay_Logo_Web_Dark.png

WeScreenplay_Logo_Web_Dark.png

1272 ms

wescreenplay_new_coverage_format.png

wescreenplay_new_coverage_format.png

1272 ms

fb_avatar.png

fb_avatar.png

1271 ms

WS-PopUp-Header-768x512.jpeg

WS-PopUp-Header-768x512.jpeg

1337 ms

WeScreenplay_bg_02a.jpg

WeScreenplay_bg_02a.jpg

1176 ms

bg-cta-01a.png

bg-cta-01a.png

805 ms

analytics.js

analytics.js

2955 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

2590 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

3739 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

3976 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

3975 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

3975 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

3975 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

3973 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

2586 ms

icomoon.woff

icomoon.woff

406 ms

identity.js

identity.js

910 ms

361287418361390

361287418361390

1183 ms

modules.cbd9768ba80ba0be5b17.js

modules.cbd9768ba80ba0be5b17.js

1183 ms

collect

collect

853 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

851 ms

collect

collect

1079 ms

adsct

adsct

1608 ms

adsct

adsct

1607 ms

1f600.svg

1f600.svg

1338 ms

1f60d.svg

1f60d.svg

1330 ms

1f642.svg

1f642.svg

1327 ms

270d.svg

270d.svg

1328 ms

2764.svg

2764.svg

1330 ms

1f44d.svg

1f44d.svg

1331 ms

1f49b.svg

1f49b.svg

1337 ms

1f60a.svg

1f60a.svg

1338 ms

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

271 ms

ScreenCraft_primary_logo_midnight_bv.png

ScreenCraft_primary_logo_midnight_bv.png

19 ms

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

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

16 ms

indiewire.png

indiewire.png

21 ms

imdb.png

imdb.png

17 ms

ew.png

ew.png

21 ms

SEO Factors

wescreenplay.com SEO score

0

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: