Tools & Wizards About Us
quassy.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

quassy.com

Quassy Amusement and Waterpark | Fun & Attractions in CT

Page Load Speed

2.1 sec in total

First Response

45 ms

Resources Loaded

1.9 sec

Page Rendered

210 ms

quassy.com screenshot

About Website

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

Quassy Amusement and Waterpark on Lake Quassapaug is a top amusement park and waterpark in CT. Enjoy park rides, Quassy Beach, fun games and the arcade.

Visit quassy.com

Key Findings

We analyzed Quassy.com page load time and found that the first response time was 45 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

quassy.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value2,190 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value17.9 s

4/100

10%

Network Requests Diagram

quassy.com

45 ms

quassy.com

128 ms

www.quassy.com

876 ms

gtm.js

47 ms

7c14d883140b2954b6f6834921097076588e95fc.css

91 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 34% of them (18 requests) were addressed to the original Quassy.com, 8% (4 requests) were made to Nexus.ensighten.com and 8% (4 requests) were made to Static.ctctcdn.com. The less responsive or slowest element that took the longest time to load (876 ms) belongs to the original domain Quassy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.1 kB (7%)

Content Size

545.5 kB

After Optimization

507.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Quassy.com main page is 545.5 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. 65% of websites need less resources to load. Javascripts take 360.7 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 30.2 kB

  • Original 39.9 kB
  • After minification 38.7 kB
  • After compression 9.7 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 30.2 kB or 76% of the original size.

Image Optimization

-5%

Potential reduce by 4.9 kB

  • Original 93.4 kB
  • After minification 88.5 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. Quassy images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.7 kB

  • Original 360.7 kB
  • After minification 360.7 kB
  • After compression 359.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 1.4 kB

  • Original 51.4 kB
  • After minification 51.4 kB
  • After compression 50.1 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. Quassy.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (44%)

Requests Now

41

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Quassy. 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 as a result speed up the page load time.

Network Requests Diagram

quassy.com

quassy.com

45 ms

quassy.com

quassy.com

128 ms

www.quassy.com

www.quassy.com

876 ms

gtm.js

gtm.js

47 ms

7c14d883140b2954b6f6834921097076588e95fc.css

7c14d883140b2954b6f6834921097076588e95fc.css

91 ms

Bootstrap.js

Bootstrap.js

106 ms

signup-form-widget.min.js

signup-form-widget.min.js

81 ms

54e2d94e01e4b35ca84b34bf7869a950a3937697.js

54e2d94e01e4b35ca84b34bf7869a950a3937697.js

172 ms

gtm.js

gtm.js

32 ms

tracking.js

tracking.js

122 ms

insight.min.js

insight.min.js

126 ms

quassy-logo.png

quassy-logo.png

162 ms

Green_Red_Blue_Lights.webp

Green_Red_Blue_Lights.webp

118 ms

Quassy_262x174_Holiday_Season_Pass.webp

Quassy_262x174_Holiday_Season_Pass.webp

116 ms

Quassy_262x174_Catered-Outings.webp

Quassy_262x174_Catered-Outings.webp

126 ms

Quassy_262x142_birthday_parties_copy.webp

Quassy_262x142_birthday_parties_copy.webp

181 ms

Quassy_1920x1080_Homepage.webp

Quassy_1920x1080_Homepage.webp

133 ms

Grand_Carousel.webp

Grand_Carousel.webp

267 ms

Quassy_Header_waterpark_copy.webp

Quassy_Header_waterpark_copy.webp

132 ms

Quassy_550x300_Lake_Quassy.webp

Quassy_550x300_Lake_Quassy.webp

256 ms

Quassy_550x300_Catered-Outings.webp

Quassy_550x300_Catered-Outings.webp

144 ms

Quassy_550x300_birthday_parties.webp

Quassy_550x300_birthday_parties.webp

254 ms

Quassy_Ride_Slide-City-Aerial-004_copy.webp

Quassy_Ride_Slide-City-Aerial-004_copy.webp

160 ms

serverComponent.php

serverComponent.php

45 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7alwg.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7alwg.ttf

174 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EH7alwg.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EH7alwg.ttf

191 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDH7alwg.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDH7alwg.ttf

246 ms

jquery.js

jquery.js

132 ms

0e41c0f8fc20d60369ac2dfedb5bddb7.js

0e41c0f8fc20d60369ac2dfedb5bddb7.js

66 ms

d3d14424fac71699bdbff068d9b1184b.js

d3d14424fac71699bdbff068d9b1184b.js

208 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

239 ms

insight_tag_errors.gif

insight_tag_errors.gif

133 ms

underscore-min.js

underscore-min.js

11 ms

analytics.js

analytics.js

45 ms

hotjar-233084.js

hotjar-233084.js

115 ms

fbevents.js

fbevents.js

44 ms

api.js

api.js

96 ms

collect

collect

17 ms

collect

collect

32 ms

js

js

81 ms

recaptcha__en.js

recaptcha__en.js

35 ms

modules.1a30a0a67c3c23c13060.js

modules.1a30a0a67c3c23c13060.js

16 ms

ga-audiences

ga-audiences

182 ms

li_sync

li_sync

157 ms

signup-form-widget.css

signup-form-widget.css

101 ms

0741c60039f132023b020c99669dc316.json

0741c60039f132023b020c99669dc316.json

144 ms

iframe

iframe

49 ms

ctct-close-x.svg

ctct-close-x.svg

24 ms

logo-ctct-white.svg

logo-ctct-white.svg

29 ms

generic

generic

16 ms

appnexus

appnexus

3 ms

rubicon

rubicon

5 ms

pixel

pixel

30 ms

Accessibility Review

quassy.com accessibility score

84

Accessibility Issues

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

High

ARIA IDs are not unique

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

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

quassy.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

quassy.com SEO score

92

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

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

quassy.com

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