Tools & Wizards About Us
nightmareonelmstreet.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

nightmareonelmstreet.com

WarnerBros.com | A Nightmare on Elm Street (2010) | Movies

Page Load Speed

1.5 sec in total

First Response

182 ms

Resources Loaded

1.1 sec

Page Rendered

180 ms

nightmareonelmstreet.com screenshot

About Website

Visit nightmareonelmstreet.com now to see the best up-to-date Nightmare On Elm Street content and also check out these interesting facts you probably never knew about nightmareonelmstreet.com

<p align="LEFT">Freddy Krueger (Jackie Earle Haley) returns in <i>A Nightmare on Elm Street</i>, a contemporary re-imagining of the horror classic. </p>

Visit nightmareonelmstreet.com

Key Findings

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

Performance Metrics

nightmareonelmstreet.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value7,370 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value27.6 s

0/100

10%

Network Requests Diagram

nightmareonelmstreet.com

182 ms

nightmare-elm-street-2010

119 ms

polyfill.min.js

375 ms

Artic~ed3cd7cd.5586d596.js

9 ms

Artic~e6539ea4.700b773d.js

10 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Nightmareonelmstreet.com, 56% (9 requests) were made to Warnerbros.com and 19% (3 requests) were made to Assets.www.warnerbros.com. The less responsive or slowest element that took the longest time to load (375 ms) relates to the external source Cdn.polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 169.2 kB (59%)

Content Size

286.0 kB

After Optimization

116.8 kB

  • HTML
  • Images

In fact, the total size of Nightmareonelmstreet.com main page is 286.0 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. 25% of websites need less resources to load. HTML takes 184.1 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 158.4 kB

  • Original 184.1 kB
  • After minification 184.1 kB
  • After compression 25.7 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 158.4 kB or 86% of the original size.

Image Optimization

-11%

Potential reduce by 10.8 kB

  • Original 101.9 kB
  • After minification 91.1 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. Obviously, Nightmare On Elm Street needs image optimization as it can save up to 10.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 8 (57%)

Requests Now

14

After Optimization

6

  • Images
  • JavaScript

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nightmare On Elm Street. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

nightmareonelmstreet.com

nightmareonelmstreet.com

182 ms

nightmare-elm-street-2010

nightmare-elm-street-2010

119 ms

polyfill.min.js

polyfill.min.js

375 ms

Artic~ed3cd7cd.5586d596.js

Artic~ed3cd7cd.5586d596.js

9 ms

Artic~e6539ea4.700b773d.js

Artic~e6539ea4.700b773d.js

10 ms

bran~64dcb6c2.5781dc1b.js

bran~64dcb6c2.5781dc1b.js

12 ms

Artic~a6738d10.15b05c2e.js

Artic~a6738d10.15b05c2e.js

14 ms

TitleLayout.tsx.cf80f88c.js

TitleLayout.tsx.cf80f88c.js

26 ms

vendors~main.ebb95cd1.js

vendors~main.ebb95cd1.js

25 ms

main.b120ea2c.js

main.b120ea2c.js

13 ms

gtm.js

gtm.js

238 ms

default-wb-mobile.jpg

default-wb-mobile.jpg

202 ms

PrimeVideo_500x200.png

PrimeVideo_500x200.png

208 ms

nightmare_on_elm_street_2010_keyart.jpg

nightmare_on_elm_street_2010_keyart.jpg

250 ms

apple-tv-logo.jpg

apple-tv-logo.jpg

207 ms

amazon_500x200.png

amazon_500x200.png

209 ms

Accessibility Review

nightmareonelmstreet.com accessibility score

98

Accessibility Issues

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

nightmareonelmstreet.com best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

nightmareonelmstreet.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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

nightmareonelmstreet.com

Open Graph description is not detected on the main page of Nightmare On Elm Street. 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: