880 ms in total
146 ms
557 ms
177 ms
Welcome to handson.org homepage info - get ready to check Hands On best content for United States right away, or after learning these important things about handson.org
Hands On offerings sign-language & sign-interpreted performances in the not-for-profit theatrical arena in theaters in New York City and across the country.
Visit handson.orgWe analyzed Handson.org page load time and found that the first response time was 146 ms and then it took 734 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
handson.org performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value7.2 s
5/100
25%
Value16.1 s
0/100
10%
Value2,990 ms
3/100
30%
Value0.417
23/100
15%
Value23.1 s
1/100
10%
146 ms
30 ms
33 ms
34 ms
36 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 95% of them (59 requests) were addressed to the original Handson.org, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to D1ev1rt26nhnwq.cloudfront.net. The less responsive or slowest element that took the longest time to load (147 ms) belongs to the original domain Handson.org.
Page size can be reduced by 326.7 kB (16%)
2.1 MB
1.7 MB
In fact, the total size of Handson.org 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. 35% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 24.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. 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 24.4 kB or 77% of the original size.
Potential reduce by 126.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. Hands On images are well optimized though.
Potential reduce by 119.9 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 119.9 kB or 67% of the original size.
Potential reduce by 55.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. Handson.org needs all CSS files to be minified and compressed as it can save up to 55.8 kB or 80% of the original size.
Number of requests can be reduced by 36 (61%)
59
23
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hands On. 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 from 19 to 1 for CSS and as a result speed up the page load time.
handson.org
146 ms
node.css
30 ms
defaults.css
33 ms
system.css
34 ms
system-menus.css
36 ms
user.css
34 ms
content-module.css
35 ms
ckeditor.css
45 ms
ctools.css
48 ms
superfish.css
47 ms
superfish-vertical.css
49 ms
superfish-navbar.css
50 ms
textsize.css
50 ms
views_slideshow.css
60 ms
fieldgroup.css
62 ms
views.css
62 ms
event.css
65 ms
style.css
64 ms
jquery.min.js
96 ms
drupal.js
75 ms
googleanalytics.js
76 ms
jquery.hoverIntent.minified.js
78 ms
jquery.bgiframe.min.js
81 ms
superfish.js
81 ms
supersubs.js
91 ms
supposition.js
91 ms
sftouchscreen.js
93 ms
sfsmallscreen.js
95 ms
superfish.js
97 ms
jquery.textsize.js
107 ms
jquery.cookie.min.js
107 ms
jquery.cycle.all.min.js
123 ms
views_slideshow.js
110 ms
eventblock.js
112 ms
progress.js
113 ms
tableheader.js
121 ms
style.css
77 ms
layout.css
19 ms
ccmtblv2.png
106 ms
ga.js
76 ms
bg-header.jpg
42 ms
logo.jpg
38 ms
bg-primary.gif
109 ms
BUTTON_0.jpg
25 ms
rtc_cmyk_k_withmargins.jpg
147 ms
caps.jpg
22 ms
NYSCA%20logo.jpg
40 ms
RadioCity.jpg
116 ms
Atlantic4_0.png
87 ms
video.jpg
104 ms
NewVic.png
103 ms
Shakespeare_0.jpg
119 ms
buyaticket.png
122 ms
facebook.png
121 ms
twitter.png
125 ms
youtube.png
131 ms
bg-footer.gif
135 ms
arrows-ffffff.png
137 ms
previous.png
137 ms
next.png
141 ms
charcoal.woff
146 ms
__utm.gif
13 ms
handson.org 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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
handson.org 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
handson.org 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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Handson.org 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 Handson.org 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.
handson.org
Open Graph description is not detected on the main page of Hands On. 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: