Tools & Wizards About Us
findahaunt.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

findahaunt.com

Best haunted houses near you - Haunted Trails near you

Page Load Speed

3.2 sec in total

First Response

292 ms

Resources Loaded

2.3 sec

Page Rendered

561 ms

findahaunt.com screenshot

About Website

Visit findahaunt.com now to see the best up-to-date Findahaunt content for United States and also check out these interesting facts you probably never knew about findahaunt.com

FindAhaunt.com is the Haunted Attraction Search Engine. Type in a location and we show you all the Haunted Attractions nearby. Haunted Houses, Haunted Trails, Hayrides, and Pumpkin Patches

Visit findahaunt.com

Key Findings

We analyzed Findahaunt.com page load time and found that the first response time was 292 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

findahaunt.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

1/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value900 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.093

91/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

findahaunt.com

292 ms

main.css

170 ms

webfonts.css

77 ms

js

96 ms

fah.js

131 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 35% of them (16 requests) were addressed to the original Findahaunt.com, 11% (5 requests) were made to Secure.flashtalking.com and 9% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (580 ms) belongs to the original domain Findahaunt.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 314.1 kB (28%)

Content Size

1.1 MB

After Optimization

818.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Findahaunt.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. 45% of websites need less resources to load. Images take 707.3 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 9.9 kB

  • Original 15.0 kB
  • After minification 14.1 kB
  • After compression 5.1 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 9.9 kB or 66% of the original size.

Image Optimization

-5%

Potential reduce by 32.4 kB

  • Original 707.3 kB
  • After minification 674.9 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. Findahaunt images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 192.3 kB

  • Original 310.3 kB
  • After minification 273.7 kB
  • After compression 118.0 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 192.3 kB or 62% of the original size.

CSS Optimization

-80%

Potential reduce by 79.5 kB

  • Original 99.7 kB
  • After minification 88.8 kB
  • After compression 20.2 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. Findahaunt.com needs all CSS files to be minified and compressed as it can save up to 79.5 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (49%)

Requests Now

45

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

findahaunt.com

findahaunt.com

292 ms

main.css

main.css

170 ms

webfonts.css

webfonts.css

77 ms

js

js

96 ms

fah.js

fah.js

131 ms

show_ads.js

show_ads.js

43 ms

ga.js

ga.js

321 ms

all.js

all.js

313 ms

ca-pub-8102146977500927.js

ca-pub-8102146977500927.js

179 ms

zrt_lookup.html

zrt_lookup.html

276 ms

show_ads_impl.js

show_ads_impl.js

179 ms

dark-web-bug-small.png

dark-web-bug-small.png

267 ms

bg_spookyhouse.jpg

bg_spookyhouse.jpg

272 ms

topNav_bg.png

topNav_bg.png

449 ms

logo_small.png

logo_small.png

272 ms

sprites_social.png

sprites_social.png

126 ms

logo.png

logo.png

370 ms

graveyard.png

graveyard.png

580 ms

tombstones_fg.png

tombstones_fg.png

271 ms

Leander-webfont.woff

Leander-webfont.woff

238 ms

FAH-webfont.woff

FAH-webfont.woff

380 ms

ads

ads

219 ms

osd.js

osd.js

106 ms

__utm.gif

__utm.gif

61 ms

377 ms

xd_arbiter.php

xd_arbiter.php

175 ms

xd_arbiter.php

xd_arbiter.php

360 ms

dvbs_src.js

dvbs_src.js

189 ms

abg.js

abg.js

292 ms

mobile.css

mobile.css

262 ms

bst2tv3.html

bst2tv3.html

202 ms

verify.js

verify.js

250 ms

tablet.css

tablet.css

61 ms

print.css

print.css

124 ms

251 ms

j-1761743-1351882.js

j-1761743-1351882.js

222 ms

B9086839.130009409;dc_trk_aid=302912366;dc_trk_cid=69290829;ord=1459158719;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=

B9086839.130009409;dc_trk_aid=302912366;dc_trk_cid=69290829;ord=1459158719;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=

312 ms

AwakenSummer_728x90.html

AwakenSummer_728x90.html

49 ms

dvtp_src.js

dvtp_src.js

46 ms

html5API.js

html5API.js

199 ms

tweenjs-0.6.2.min.js

tweenjs-0.6.2.min.js

281 ms

preloadjs-0.6.2.min.js

preloadjs-0.6.2.min.js

288 ms

loader.gif

loader.gif

252 ms

dvtp_src_internal27.js

dvtp_src_internal27.js

41 ms

t2tv7.html

t2tv7.html

200 ms

manifest.js

manifest.js

23 ms

Accessibility Review

findahaunt.com accessibility score

76

Accessibility Issues

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

High

Links do not have a discernible name

Best Practices

findahaunt.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

findahaunt.com SEO score

90

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Findahaunt.com 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 Findahaunt.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

findahaunt.com

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