2.5 sec in total
316 ms
995 ms
1.2 sec
Welcome to storylandnh.com homepage info - get ready to check Story Land Nh best content for United States right away, or after learning these important things about storylandnh.com
Embark on an unforgettable family adventure at Story Land, the best children's amusement park in New Hampshire. Visit us and create cherished moments together!
Visit storylandnh.comWe analyzed Storylandnh.com page load time and found that the first response time was 316 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
storylandnh.com performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value13.5 s
0/100
25%
Value11.8 s
4/100
10%
Value2,880 ms
3/100
30%
Value0.407
24/100
15%
Value22.1 s
1/100
10%
316 ms
143 ms
27 ms
59 ms
54 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 90% of them (84 requests) were addressed to the original Storylandnh.com, 3% (3 requests) were made to Cdn.cookielaw.org and 2% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (316 ms) belongs to the original domain Storylandnh.com.
Page size can be reduced by 825.2 kB (4%)
21.7 MB
20.9 MB
In fact, the total size of Storylandnh.com main page is 21.7 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. Only a small number of websites need less resources to load. Images take 21.3 MB which makes up the majority of the site volume.
Potential reduce by 107.0 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. This page needs HTML code to be minified as it can gain 23.7 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 107.0 kB or 83% of the original size.
Potential reduce by 510.4 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. Story Land Nh images are well optimized though.
Potential reduce by 207.7 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 207.7 kB or 77% of the original size.
Number of requests can be reduced by 58 (64%)
90
32
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Story Land Nh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
storylandnh.com
316 ms
www.storylandnh.com
143 ms
jquery.lc-f9e8e8c279baf6a1a278042afe4f395a-lc.min.js
27 ms
clientlib-base.lc-b0bf90295c846c4dbd7e678cf25e8209-lc.min.css
59 ms
clientlib-site.lc-b5cbd3978492a77aa1caea5d7db50984-lc.min.css
54 ms
clientlib-site-stl.lc-9136316df9d4332160fdfc97c7859b1d-lc.min.css
53 ms
sheerid.css
99 ms
sheerid.js
165 ms
zuora-min.js
85 ms
OtAutoBlock.js
145 ms
otSDKStub.js
160 ms
at.js
78 ms
optimize.js
107 ms
api.js
96 ms
v1.lc-c11df7e567e0923a36ba68483159f377-lc.min.css
75 ms
v1.lc-77d149fb7bdeb355f38a7e54f80cc316-lc.min.js
75 ms
v1.lc-17ba1845a5d08e26c1b8670dcb2583a8-lc.min.css
77 ms
v1.lc-13f4178b78f095d478c563e4622c174e-lc.min.css
75 ms
v1.lc-9c1c61e84f692496edcf654baa0b4dd0-lc.min.js
76 ms
v1.lc-1735bf35eb88b690d9379d18f4400934-lc.min.css
78 ms
v1.lc-8a83e09f902fba10562a9ae6cf29d8cb-lc.min.js
79 ms
v1.lc-1239144f1129834a4f91523075d736d4-lc.min.js
78 ms
v1.lc-09c3ec6196fa2b1ef141256cd7411ed9-lc.min.css
80 ms
v1.lc-2209305bd150cec777cde47698353c9f-lc.min.css
81 ms
v1.lc-2cd73fbb8d81e2fbf250a1005fa5bc7b-lc.min.css
81 ms
v1.lc-f7c3081e3cc2f72847816ed213794e2d-lc.min.js
82 ms
v1.lc-9b0bcf8bdff04c92710b233f65181727-lc.min.js
83 ms
v1.lc-6ef6215bebadd10b80cbc30888c76e0f-lc.min.js
83 ms
v1.lc-56b0cb04e202283f7feaa5934967b32d-lc.min.css
90 ms
v1.lc-60c2fc266f9f4db09d173011648acf4a-lc.min.css
83 ms
v1.lc-f8acd4518370d436e6ce1efa68caf1c0-lc.min.js
84 ms
v1.lc-1680557a51a29974bb18a770272780df-lc.min.css
84 ms
v1.lc-dfbb45b835f3b7ae38378bc6b11bbfa6-lc.min.js
87 ms
v1.lc-0c7f4e2659227779b54e2d06c9e1df6f-lc.min.js
84 ms
v1.lc-9098a35f8d8fd0cbdabe4eafe9b2a709-lc.min.css
86 ms
v1.lc-d226558103755002b0138981ed3791fc-lc.min.css
86 ms
v1.lc-b8eafd78cdf7a116af0a7a6b30787dd1-lc.min.js
88 ms
v1.lc-ff054ce2f85d25a0201b52fb61ef42eb-lc.min.css
91 ms
v1.lc-6395b6111381485dd1cd7916de83f67f-lc.min.js
97 ms
v1.lc-b8ecb325b65a2639082ad932dfb1a9e8-lc.min.js
97 ms
v1.lc-b0b5303d6138b6bff9c0a2bea510276b-lc.min.css
94 ms
v1.lc-75eb917db714a2658c9821de16facab1-lc.min.css
67 ms
v1.lc-ca59981720e6b80de5573df47eb4f5d4-lc.min.css
53 ms
v1.lc-c3cebbc7f30fcef2802ab474397478e7-lc.min.css
50 ms
v1.lc-881602282b12937b1eab0ad6f6e428f9-lc.min.css
36 ms
v1.lc-9379e71eab4cf8280a6ca072d66bc982-lc.min.css
34 ms
v1.lc-602419cc70ad0ce67c8f0322a1f7b53a-lc.min.css
32 ms
v3.lc-a0ec6518139dba2e50b56570a990892e-lc.min.css
32 ms
v1.lc-c3ab186d35c8fec76ca98c6e1d162d23-lc.min.css
32 ms
v1.lc-41aaee6177ab094f03f399e25ae8f83d-lc.min.js
32 ms
v1.lc-1bcb787e643e7d8eb818d45a7c7cfb81-lc.min.js
32 ms
v1.lc-8f795f0738839e75bc6e1aa8a5dcb122-lc.min.js
32 ms
v1.lc-e01a05ee30ebbfd84ab147848c848334-lc.min.js
37 ms
v1.lc-cdf7d0090a4f3cfaaea52c94c95004b0-lc.min.js
31 ms
v1.lc-49ece6f12b7301dcee933869ecc497ae-lc.min.js
31 ms
v3.lc-4ee6b8ef78fd276d02a74cf51b3c4668-lc.min.js
31 ms
v1.lc-8c5d2abc60ff2f6a3c84111500669777-lc.min.js
31 ms
v1.lc-f7e76d0aea6dc2d96f49bc7131c620e7-lc.min.js
29 ms
clientlib-site.lc-977cb55497e72f02c46a038a0d07b7f9-lc.min.js
30 ms
container.lc-0a6aff292f5cc42142779cde92054524-lc.min.js
29 ms
clientlib-base.lc-429a848fe92901cf60daa1aeb202be74-lc.min.js
32 ms
29e72ce5-3644-4345-8ef7-5c987374a490.json
134 ms
2024-Storyland.png
121 ms
2024-storyland-white.png
58 ms
Moo_Lagoon_1300x800.jpg
59 ms
mh1.jpg
61 ms
Highlight%20Card%20(600x500)%20(3).png
62 ms
image.png
61 ms
Any_Day.png
63 ms
image.png
62 ms
Homepage%20Moo%20400x300.png
65 ms
image.png
66 ms
Home%20Page.jpg
64 ms
Stingray-Living-shores-aquarium-2.jpg
64 ms
pattern_2.jpg
65 ms
image.jpg
66 ms
Antique_Cars_1.png
69 ms
image.jpg
67 ms
image.jpg
69 ms
daniel_highlight.jpg
68 ms
image.jpg
67 ms
TeaTimeCinderella_f.jpg
70 ms
image.jpg
70 ms
Storyland%20Photos-66.jpg
103 ms
image.jpg
71 ms
newsletter-story-land.jpeg
71 ms
logo-white-mountains.jpeg
72 ms
LivingShores.png
72 ms
WaterCountry.png
73 ms
LakeCompunce.png
73 ms
SplishSplash.png
72 ms
location
83 ms
icomoon.ttf
24 ms
storylandnh.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
storylandnh.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
storylandnh.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Storylandnh.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 Storylandnh.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.
storylandnh.com
Open Graph data is detected on the main page of Story Land Nh. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: