Tools & Wizards About Us
horror.net screenshot

Report Summary

  • 75

    Performance

    Renders faster than
    83% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

horror.net

One moment, please...

Page Load Speed

771 ms in total

First Response

150 ms

Resources Loaded

461 ms

Page Rendered

160 ms

horror.net screenshot

About Website

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

Horror Search and Directory - Horror.net :: The Web's Deadliest Horror Network & Search Engine. Search through the best horror sites here in our search engine and directory.

Visit horror.net

Key Findings

We analyzed Horror.net page load time and found that the first response time was 150 ms and then it took 621 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

horror.net performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value1.6 s

99/100

25%

SI (Speed Index)

Value2.3 s

98/100

10%

TBT (Total Blocking Time)

Value890 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.6 s

58/100

10%

Network Requests Diagram

horror.net

150 ms

style.css

149 ms

show_ads.js

67 ms

header01.gif

183 ms

header02.gif

183 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 47% of them (7 requests) were addressed to the original Horror.net, 27% (4 requests) were made to Buried.com and 13% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (183 ms) belongs to the original domain Horror.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 164.5 kB (57%)

Content Size

289.9 kB

After Optimization

125.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Horror.net main page is 289.9 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. 20% of websites need less resources to load. Javascripts take 214.4 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 35.0 kB

  • Original 42.2 kB
  • After minification 40.5 kB
  • After compression 7.2 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 35.0 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 959 B

  • Original 31.8 kB
  • After minification 30.8 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 images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 128.0 kB

  • Original 214.4 kB
  • After minification 214.4 kB
  • After compression 86.4 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 128.0 kB or 60% of the original size.

CSS Optimization

-36%

Potential reduce by 557 B

  • Original 1.5 kB
  • After minification 1.5 kB
  • After compression 970 B

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. Horror.net needs all CSS files to be minified and compressed as it can save up to 557 B or 36% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

14

After Optimization

14

  • Images
  • JavaScript
  • CSS

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Horror. According to our analytics all requests are already optimized.

Network Requests Diagram

horror.net

horror.net

150 ms

style.css

style.css

149 ms

show_ads.js

show_ads.js

67 ms

header01.gif

header01.gif

183 ms

header02.gif

header02.gif

183 ms

urchin.js

urchin.js

7 ms

adsbygoogle.js

adsbygoogle.js

123 ms

frightmaster-left.jpg

frightmaster-left.jpg

113 ms

__utm.gif

__utm.gif

6 ms

bg.gif

bg.gif

25 ms

mainbg2.gif

mainbg2.gif

26 ms

search.gif

search.gif

26 ms

3315342-small.jpg

3315342-small.jpg

80 ms

5052448-small.jpg

5052448-small.jpg

80 ms

4972582-small.jpg

4972582-small.jpg

80 ms

Accessibility Review

horror.net accessibility score

82

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

horror.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Page has valid source maps

SEO Factors

horror.net SEO score

69

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Horror.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Horror.net main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

horror.net

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