Tools & Wizards About Us
waterwizz.com screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

waterwizz.com

Water Wizz - Southern NE's Largest Outdoor Water Park

Page Load Speed

13.7 sec in total

First Response

6 sec

Resources Loaded

7.4 sec

Page Rendered

302 ms

waterwizz.com screenshot

About Website

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

Splash into summer fun at Water Wizz. Make your visit memorable with private cabana rentals. Buy tickets online. Family fun attractions.

Visit waterwizz.com

Key Findings

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

Performance Metrics

waterwizz.com performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.6 s

0/100

25%

SI (Speed Index)

Value19.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,970 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value1.042

2/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

Network Requests Diagram

waterwizz.com

6020 ms

style.css

33 ms

css

27 ms

popup_effect.min.css

30 ms

dipi-font.min.css

31 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 73% of them (77 requests) were addressed to the original Waterwizz.com, 13% (14 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (6 sec) belongs to the original domain Waterwizz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 399.3 kB (19%)

Content Size

2.1 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Waterwizz.com main page is 2.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. Only a small number of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 190.5 kB

  • Original 231.6 kB
  • After minification 224.7 kB
  • After compression 41.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 190.5 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 56.0 kB

  • Original 1.3 MB
  • After minification 1.3 MB

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. Water Wizz images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 73.1 kB

  • Original 275.0 kB
  • After minification 275.0 kB
  • After compression 201.8 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 73.1 kB or 27% of the original size.

CSS Optimization

-24%

Potential reduce by 79.7 kB

  • Original 325.5 kB
  • After minification 325.4 kB
  • After compression 245.8 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. Waterwizz.com needs all CSS files to be minified and compressed as it can save up to 79.7 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (79%)

Requests Now

76

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

waterwizz.com

waterwizz.com

6020 ms

style.css

style.css

33 ms

css

css

27 ms

popup_effect.min.css

popup_effect.min.css

30 ms

dipi-font.min.css

dipi-font.min.css

31 ms

general.min.css

general.min.css

35 ms

superfly-menu.css

superfly-menu.css

52 ms

taptap.css

taptap.css

37 ms

css

css

113 ms

all.min.css

all.min.css

40 ms

line-awesome.min.css

line-awesome.min.css

54 ms

dashicons.min.css

dashicons.min.css

61 ms

to-top-public.css

to-top-public.css

63 ms

wpforms-full.min.css

wpforms-full.min.css

64 ms

css

css

111 ms

style.min.css

style.min.css

68 ms

style.min.css

style.min.css

94 ms

css

css

161 ms

loftloader.min.css

loftloader.min.css

75 ms

choices.min.css

choices.min.css

73 ms

intl-tel-input.min.css

intl-tel-input.min.css

78 ms

richtext.min.css

richtext.min.css

91 ms

content.min.css

content.min.css

106 ms

wpforms-classic-full.min.css

wpforms-classic-full.min.css

102 ms

style-static.min.css

style-static.min.css

116 ms

jquery.min.js

jquery.min.js

110 ms

jquery-migrate.min.js

jquery-migrate.min.js

108 ms

public.min.js

public.min.js

110 ms

md5.js

md5.js

108 ms

util.js

util.js

108 ms

superfly-menu.js

superfly-menu.js

110 ms

taptap-accordion.js

taptap-accordion.js

109 ms

jquery.scrollbar.min.js

jquery.scrollbar.min.js

110 ms

to-top-public.js

to-top-public.js

110 ms

ana-track.js

ana-track.js

148 ms

modernizr.custom.js

modernizr.custom.js

145 ms

popup_effect.min.js

popup_effect.min.js

147 ms

taptap-horizontal-menu.js

taptap-horizontal-menu.js

144 ms

taptap-image-menu.js

taptap-image-menu.js

145 ms

taptap.js

taptap.js

147 ms

taptap-body-scroll-lock.js

taptap-body-scroll-lock.js

135 ms

scripts.min.js

scripts.min.js

132 ms

frontend-bundle.min.js

frontend-bundle.min.js

129 ms

frontend-bundle.min.js

frontend-bundle.min.js

129 ms

loftloader.min.js

loftloader.min.js

123 ms

common.js

common.js

115 ms

jquery.exitintent.min.js

jquery.exitintent.min.js

202 ms

jquery.fitvids.js

jquery.fitvids.js

190 ms

jquery.mobile.js

jquery.mobile.js

189 ms

jquery.validate.min.js

jquery.validate.min.js

188 ms

mailcheck.min.js

mailcheck.min.js

184 ms

punycode.min.js

punycode.min.js

179 ms

utils.min.js

utils.min.js

176 ms

wpforms.min.js

wpforms.min.js

176 ms

lazyload.min.js

lazyload.min.js

161 ms

gtm.js

gtm.js

252 ms

app.js

app.js

433 ms

WW_H_Wizzy_Color-11.png

WW_H_Wizzy_Color-11.png

126 ms

WW_H_Wizzy_Color-11.png.webp

WW_H_Wizzy_Color-11.png.webp

121 ms

Frame-10.png.webp

Frame-10.png.webp

125 ms

Frame-10-1.png

Frame-10-1.png

125 ms

Frame-7540.png.webp

Frame-7540.png.webp

128 ms

submit-spin.svg

submit-spin.svg

123 ms

MicrosoftTeams-image.png

MicrosoftTeams-image.png

130 ms

Thunder-Falls.jpg.webp

Thunder-Falls.jpg.webp

127 ms

Mussel-Beach.jpg.webp

Mussel-Beach.jpg.webp

127 ms

Frog-Print1.png.webp

Frog-Print1.png.webp

126 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

153 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

337 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

344 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

360 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

358 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

359 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

69 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

72 ms

modules.woff

modules.woff

70 ms

fa-brands-400.woff

fa-brands-400.woff

152 ms

fa-regular-400.woff

fa-regular-400.woff

136 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

135 ms

fa-regular-400.ttf

fa-regular-400.ttf

135 ms

fa-brands-400.ttf

fa-brands-400.ttf

133 ms

fa-solid-900.ttf

fa-solid-900.ttf

149 ms

fa-solid-900.woff

fa-solid-900.woff

355 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

359 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWV4exQ.ttf

357 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

388 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf

396 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

409 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf

408 ms

MicrosoftTeams-image-2-1-scaled.jpg

MicrosoftTeams-image-2-1-scaled.jpg

453 ms

Group-34.png

Group-34.png

91 ms

image-201.png

image-201.png

90 ms

Group-52.png

Group-52.png

210 ms

Switzer-Medium.otf

Switzer-Medium.otf

209 ms

Kisna-Regular.otf

Kisna-Regular.otf

211 ms

Switzer-Semibold.otf

Switzer-Semibold.otf

208 ms

js

js

89 ms

queueclient.min.js

queueclient.min.js

85 ms

js

js

198 ms

fbevents.js

fbevents.js

197 ms

Group-52.png

Group-52.png

55 ms

queueclient.min.js

queueclient.min.js

312 ms

queueconfigloader.min.js

queueconfigloader.min.js

3 ms

queueconfigloader.min.js

queueconfigloader.min.js

3 ms

queueclientConfig.js

queueclientConfig.js

328 ms

Accessibility Review

waterwizz.com accessibility score

89

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.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

waterwizz.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

waterwizz.com SEO score

79

Search Engine Optimization Advices

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

waterwizz.com

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