2.1 sec in total
163 ms
1.4 sec
555 ms
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.comWe analyzed Quassy.com page load time and found that the first response time was 163 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
quassy.com performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value23.3 s
0/100
25%
Value12.3 s
3/100
10%
Value2,540 ms
4/100
30%
Value0.118
85/100
15%
Value20.1 s
2/100
10%
163 ms
352 ms
255 ms
32 ms
302 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 49% of them (17 requests) were addressed to the original Quassy.com, 9% (3 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (431 ms) belongs to the original domain Quassy.com.
Page size can be reduced by 28.2 kB (1%)
4.8 MB
4.8 MB
In fact, the total size of Quassy.com main page is 4.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 4.6 MB which makes up the majority of the site volume.
Potential reduce by 19.6 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 19.6 kB or 73% of the original size.
Potential reduce by 8.3 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.
Potential reduce by 355 B
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.
Potential reduce by 0 B
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.
Number of requests can be reduced by 11 (38%)
29
18
The browser has sent 29 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 12 to 1 for JavaScripts and as a result speed up the page load time.
quassy.com
163 ms
www.quassy.com
352 ms
gtm.js
255 ms
97ca0e9e78fe23bb7beb0fd57a4bf1658d5715fd.css
32 ms
signup-form-widget.min.js
302 ms
eb3897edf729ea7ab08724ba2837e570810f37b7.js
121 ms
quassy-logo.png
119 ms
Quassy_262x174_Holiday_Season_Pass.jpg
118 ms
Quassy_262x174_Lobsters.jpg
117 ms
Spin_Yourself_Silly.jpg
229 ms
Haunt_home_page_NEW.jpg
233 ms
tracking.js
249 ms
Grand_Carsoul.jpg
431 ms
16c25408a9cdcca49c8cd8739578f21a7d72378d.jpg
147 ms
Quassy_1920x1080_Homepage.jpg
315 ms
Grand_Carsoul.jpg
146 ms
Quassy_550x300_Lake_Quassy.jpg
200 ms
Quassy_550x300_Catered-Outings.jpg
202 ms
Quassy_550x300_birthday_parties.jpg
200 ms
u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7alwg.ttf
231 ms
u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EH7alwg.ttf
245 ms
u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDH7alwg.ttf
313 ms
fontawesome-webfont.woff
208 ms
analytics.js
155 ms
hotjar-233084.js
265 ms
fbevents.js
215 ms
underscore-min.js
204 ms
collect
41 ms
collect
69 ms
721692638447690
29 ms
api.js
121 ms
modules.5cffd253af12af6303c3.js
74 ms
ga-audiences
127 ms
box-1ada912494ba7fc7aca15fcef1c2a7ae.html
70 ms
recaptcha__en.js
40 ms
quassy.com accessibility score
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
quassy.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
Page has valid source maps
quassy.com SEO score
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
EN
N/A
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.
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: