Tools & Wizards About Us
horroronscreen.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

horroronscreen.com

Horror on Screen – Perspective

Page Load Speed

1.5 sec in total

First Response

94 ms

Resources Loaded

1.2 sec

Page Rendered

259 ms

horroronscreen.com screenshot

About Website

Welcome to horroronscreen.com homepage info - get ready to check Horror On Screen best content for United States right away, or after learning these important things about horroronscreen.com

The horror movies website for short reviews & best horror movies lists, where horror fans discover which horror movies are worth watching.

Visit horroronscreen.com

Key Findings

We analyzed Horroronscreen.com page load time and found that the first response time was 94 ms and then it took 1.5 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

horroronscreen.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.359

30/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

horroronscreen.com

94 ms

www.horroronscreen.com

159 ms

73475.css

130 ms

gdsr.css.php

110 ms

df983.js

63 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 24% of them (19 requests) were addressed to the original Horroronscreen.com, 14% (11 requests) were made to Apis.google.com and 9% (7 requests) were made to Ssl.gstatic.com. The less responsive or slowest element that took the longest time to load (714 ms) relates to the external source I0.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (55%)

Content Size

2.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Horroronscreen.com main page is 2.4 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. 70% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 117.1 kB

  • Original 147.5 kB
  • After minification 143.9 kB
  • After compression 30.4 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 117.1 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 725 B

  • Original 540.0 kB
  • After minification 539.2 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. Horror On Screen images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 841.2 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 415.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 841.2 kB or 67% of the original size.

CSS Optimization

-77%

Potential reduce by 358.8 kB

  • Original 463.8 kB
  • After minification 455.5 kB
  • After compression 105.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. Horroronscreen.com needs all CSS files to be minified and compressed as it can save up to 358.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (63%)

Requests Now

72

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

horroronscreen.com

horroronscreen.com

94 ms

www.horroronscreen.com

www.horroronscreen.com

159 ms

73475.css

73475.css

130 ms

gdsr.css.php

gdsr.css.php

110 ms

df983.js

df983.js

63 ms

55ff0.js

55ff0.js

70 ms

9b467.js

9b467.js

60 ms

f898b.js

f898b.js

31 ms

ef0b1.js

ef0b1.js

58 ms

devicepx-jetpack.js

devicepx-jetpack.js

5 ms

gprofiles.js

gprofiles.js

6 ms

1e102.js

1e102.js

67 ms

in.js

in.js

13 ms

e-201705.js

e-201705.js

5 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

75 ms

analytics.js

analytics.js

71 ms

best-of-2015-630x343.png

best-of-2015-630x343.png

714 ms

Judgement-Photo-1-630x343.jpg

Judgement-Photo-1-630x343.jpg

142 ms

100812-pet-sematary-630x343.jpg

100812-pet-sematary-630x343.jpg

147 ms

Picture43.png

Picture43.png

122 ms

cooltext8096809387-300x113.png

cooltext8096809387-300x113.png

36 ms

social_email.png

social_email.png

28 ms

social_rss.png

social_rss.png

28 ms

social_twitter.png

social_twitter.png

29 ms

social_facebook.png

social_facebook.png

28 ms

social_youtube.png

social_youtube.png

79 ms

social_googleplus.png

social_googleplus.png

77 ms

8-2-20105-39-00AM_zpsbdcc4a8f-630x343.jpg

8-2-20105-39-00AM_zpsbdcc4a8f-630x343.jpg

179 ms

widgets.js

widgets.js

80 ms

collect

collect

126 ms

secureAnonymousFramework

secureAnonymousFramework

118 ms

pinit.js

pinit.js

84 ms

g.gif

g.gif

91 ms

sdk.js

sdk.js

148 ms

platform.js

platform.js

148 ms

hovercard.css

hovercard.css

15 ms

services.css

services.css

34 ms

best-of-2015-80x65.png

best-of-2015-80x65.png

173 ms

8-2-20105-39-00AM_zpsbdcc4a8f-80x65.jpg

8-2-20105-39-00AM_zpsbdcc4a8f-80x65.jpg

205 ms

Judgement-Photo-1-80x65.jpg

Judgement-Photo-1-80x65.jpg

174 ms

100812-pet-sematary-80x65.jpg

100812-pet-sematary-80x65.jpg

106 ms

AAABVuGyrgAA

AAABVuGyrgAA

3 ms

button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js

button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js

72 ms

pinit_main.js

pinit_main.js

4 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

17 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

15 ms

follow

follow

99 ms

subscribe_embed

subscribe_embed

196 ms

48 ms

follow_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html

follow_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html

35 ms

postmessageRelay

postmessageRelay

105 ms

info.json

info.json

146 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

95 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

158 ms

rs=AGLTcCN3N_vBjtMRSOzNaAzgSgq-2RWGrQ

rs=AGLTcCN3N_vBjtMRSOzNaAzgSgq-2RWGrQ

4 ms

rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA

rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA

10 ms

rs=AGLTcCNecN5M_BAOq_3Is6SHVhoxNN2gMw

rs=AGLTcCNecN5M_BAOq_3Is6SHVhoxNN2gMw

53 ms

971028622-postmessagerelay.js

971028622-postmessagerelay.js

69 ms

rpc:shindig_random.js

rpc:shindig_random.js

69 ms

vxNK-E6B13CyehuDCmvQvw.woff

vxNK-E6B13CyehuDCmvQvw.woff

72 ms

grlryt2bdKIyfMSOhzd1eA.woff

grlryt2bdKIyfMSOhzd1eA.woff

89 ms

d-QWLnp4didxos_6urzFtg.woff

d-QWLnp4didxos_6urzFtg.woff

90 ms

www-subscribe-embed-vfltcNtU0.css

www-subscribe-embed-vfltcNtU0.css

21 ms

www-subscribe-embed.js

www-subscribe-embed.js

31 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

www-hitchhiker-vfl-Nn88d.png

www-hitchhiker-vfl-Nn88d.png

28 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

9 ms

cb=gapi.loaded_2

cb=gapi.loaded_2

2 ms

border_3.gif

border_3.gif

4 ms

subscribe_embed

subscribe_embed

46 ms

spacer.gif

spacer.gif

3 ms

border_3.gif

border_3.gif

3 ms

bubbleSprite_3.png

bubbleSprite_3.png

4 ms

bubbleDropR_3.png

bubbleDropR_3.png

5 ms

bubbleDropB_3.png

bubbleDropB_3.png

4 ms

jot

jot

67 ms

www-subscribe-embed-card-vflf8c5XQ.css

www-subscribe-embed-card-vflf8c5XQ.css

3 ms

www-subscribe-embed-card.js

www-subscribe-embed-card.js

4 ms

Accessibility Review

horroronscreen.com accessibility score

85

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

horroronscreen.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

horroronscreen.com SEO score

75

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

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

horroronscreen.com

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