3.2 sec in total
871 ms
1.7 sec
612 ms
Click here to check amazing Splish Splash content for United States. Otherwise, check out these important facts you probably never knew about splishsplash.com
Experience thrills, exciting slides, and family fun at Splish Splash Waterpark, the ultimate destination for unforgettable water adventures and memories.
Visit splishsplash.comWe analyzed Splishsplash.com page load time and found that the first response time was 871 ms and then it took 2.3 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.
splishsplash.com performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value12.9 s
0/100
25%
Value11.3 s
5/100
10%
Value2,310 ms
5/100
30%
Value0.457
19/100
15%
Value21.7 s
1/100
10%
871 ms
130 ms
16 ms
52 ms
40 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 90% of them (74 requests) were addressed to the original Splishsplash.com, 4% (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 (871 ms) belongs to the original domain Splishsplash.com.
Page size can be reduced by 479.0 kB (26%)
1.8 MB
1.3 MB
In fact, the total size of Splishsplash.com main page is 1.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 100.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. This page needs HTML code to be minified as it can gain 23.4 kB, which is 19% 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 100.4 kB or 82% of the original size.
Potential reduce by 171.0 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, Splish Splash needs image optimization as it can save up to 171.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
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 55 (70%)
79
24
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Splish Splash. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
splishsplash.com
871 ms
www.splishsplash.com
130 ms
jquery.lc-f9e8e8c279baf6a1a278042afe4f395a-lc.min.js
16 ms
clientlib-base.lc-b0bf90295c846c4dbd7e678cf25e8209-lc.min.css
52 ms
clientlib-site.lc-b5cbd3978492a77aa1caea5d7db50984-lc.min.css
40 ms
clientlib-site-sny.lc-d5a589686fb73a134d64eed0e16bdcc3-lc.min.css
44 ms
sheerid.css
95 ms
sheerid.js
148 ms
zuora-min.js
78 ms
OtAutoBlock.js
110 ms
otSDKStub.js
116 ms
at.js
76 ms
api.js
99 ms
v1.lc-6589e22f1f3b92d3e4229aa505b71962-lc.min.css
66 ms
v1.lc-13f4178b78f095d478c563e4622c174e-lc.min.css
65 ms
v1.lc-faf1bf095ab30c08607d039682215167-lc.min.js
68 ms
v1.lc-20d5c5a90c0bcb937e71801560732c17-lc.min.css
68 ms
v1.lc-64a953a44fccd4f4583d3014b3f31c83-lc.min.js
68 ms
v1.lc-1239144f1129834a4f91523075d736d4-lc.min.js
70 ms
v1.lc-5fcb1b6e0a40d5809d2690f4dae11328-lc.min.css
71 ms
v1.lc-77d149fb7bdeb355f38a7e54f80cc316-lc.min.js
76 ms
v1.lc-4f003960d03aa512a37c5f9f16c80f05-lc.min.css
73 ms
v1.lc-2209305bd150cec777cde47698353c9f-lc.min.css
72 ms
v1.lc-9b0bcf8bdff04c92710b233f65181727-lc.min.js
75 ms
v1.lc-2cd73fbb8d81e2fbf250a1005fa5bc7b-lc.min.css
77 ms
v1.lc-f7c3081e3cc2f72847816ed213794e2d-lc.min.js
75 ms
v1.lc-6ef6215bebadd10b80cbc30888c76e0f-lc.min.js
77 ms
v1.lc-56b0cb04e202283f7feaa5934967b32d-lc.min.css
77 ms
v1.lc-23d768f78f72a06c631c2ba244a64472-lc.min.css
79 ms
v1.lc-eac2284e1f8b4f879ccc75d95dd00962-lc.min.js
77 ms
v1.lc-a3cd88e392feb11541f7ee4499de4173-lc.min.css
77 ms
v1.lc-bdbca4dae4bc83d56d508b80988b1342-lc.min.js
95 ms
v1.lc-0c7f4e2659227779b54e2d06c9e1df6f-lc.min.js
78 ms
v1.lc-ff054ce2f85d25a0201b52fb61ef42eb-lc.min.css
79 ms
v1.lc-6395b6111381485dd1cd7916de83f67f-lc.min.js
81 ms
v1.lc-b8ecb325b65a2639082ad932dfb1a9e8-lc.min.js
80 ms
v1.lc-9098a35f8d8fd0cbdabe4eafe9b2a709-lc.min.css
81 ms
v1.lc-d226558103755002b0138981ed3791fc-lc.min.css
82 ms
v1.lc-b8eafd78cdf7a116af0a7a6b30787dd1-lc.min.js
82 ms
v1.lc-75eb917db714a2658c9821de16facab1-lc.min.css
82 ms
v1.lc-ca59981720e6b80de5573df47eb4f5d4-lc.min.css
75 ms
v1.lc-c3cebbc7f30fcef2802ab474397478e7-lc.min.css
52 ms
v1.lc-881602282b12937b1eab0ad6f6e428f9-lc.min.css
57 ms
v1.lc-9379e71eab4cf8280a6ca072d66bc982-lc.min.css
53 ms
v1.lc-602419cc70ad0ce67c8f0322a1f7b53a-lc.min.css
38 ms
v3.lc-a0ec6518139dba2e50b56570a990892e-lc.min.css
39 ms
v1.lc-c3ab186d35c8fec76ca98c6e1d162d23-lc.min.css
37 ms
v1.lc-1bcb787e643e7d8eb818d45a7c7cfb81-lc.min.js
38 ms
v1.lc-8f795f0738839e75bc6e1aa8a5dcb122-lc.min.js
37 ms
v1.lc-e01a05ee30ebbfd84ab147848c848334-lc.min.js
34 ms
v1.lc-cdf7d0090a4f3cfaaea52c94c95004b0-lc.min.js
34 ms
v1.lc-49ece6f12b7301dcee933869ecc497ae-lc.min.js
34 ms
v3.lc-4ee6b8ef78fd276d02a74cf51b3c4668-lc.min.js
33 ms
v1.lc-8c5d2abc60ff2f6a3c84111500669777-lc.min.js
35 ms
v1.lc-f7e76d0aea6dc2d96f49bc7131c620e7-lc.min.js
34 ms
clientlib-site.lc-977cb55497e72f02c46a038a0d07b7f9-lc.min.js
33 ms
container.lc-0a6aff292f5cc42142779cde92054524-lc.min.js
29 ms
clientlib-base.lc-429a848fe92901cf60daa1aeb202be74-lc.min.js
33 ms
dd6734fd-9f90-4279-9773-7c54e35ae186.json
157 ms
SplishSplash.png
143 ms
SplishSplash_yellow.png
66 ms
4th%20of%20July%20(3).jpg
68 ms
Splish_Splash_400x300_0020_Layer%20Comp%2021.jpg
70 ms
image.jpg
67 ms
754_2042_cabanas.jpg
75 ms
image.jpg
66 ms
Splish_Splash_400x300_0007_Layer%20Comp%208.jpg
68 ms
image.jpg
68 ms
Pattern_2.png
71 ms
image.jpg
70 ms
Palace_Hyperlight_Key_Art_Horz_600x500_RGB.jpg
71 ms
Splish_Splash_300x400_0002_Layer%20Comp%203.jpg
71 ms
image.jpg
72 ms
newsletter-image--1-.jpeg
74 ms
app-apple.png
75 ms
app-google.png
427 ms
DutchWonderland.png
76 ms
LakeCompunce.png
77 ms
WetnWild.png
75 ms
WCO_New_Logo_Funnel_AEM.png
77 ms
location
80 ms
icomoon.ttf
37 ms
splishsplash.com accessibility score
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
splishsplash.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
splishsplash.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 Splishsplash.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 Splishsplash.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.
splishsplash.com
Open Graph data is detected on the main page of Splish Splash. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: