1.2 sec in total
87 ms
996 ms
132 ms
Visit hands.wtf now to see the best up-to-date Hands content for United States and also check out these interesting facts you probably never knew about hands.wtf
3 letters. 2 hands. WTF.
Visit hands.wtfWe analyzed Hands.wtf page load time and found that the first response time was 87 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
hands.wtf performance score
name
value
score
weighting
Value1.0 s
100/100
10%
Value7.1 s
5/100
25%
Value2.1 s
99/100
10%
Value1,420 ms
15/100
30%
Value0.016
100/100
15%
Value26.4 s
0/100
10%
87 ms
48 ms
25 ms
24 ms
278 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 26% of them (14 requests) were addressed to the original Hands.wtf, 66% (35 requests) were made to S3.amazonaws.com and 4% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (719 ms) relates to the external source S3.amazonaws.com.
Page size can be reduced by 584.0 kB (11%)
5.2 MB
4.6 MB
In fact, the total size of Hands.wtf main page is 5.2 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. 60% of websites need less resources to load. Images take 4.4 MB which makes up the majority of the site volume.
Potential reduce by 30.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. This page needs HTML code to be minified as it can gain 11.6 kB, which is 33% 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 30.7 kB or 87% of the original size.
Potential reduce by 5.2 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 images are well optimized though.
Potential reduce by 548.2 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 548.2 kB or 77% of the original size.
We found no issues to fix!
51
51
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hands. According to our analytics all requests are already optimized.
hands.wtf
87 ms
reset.css
48 ms
app.css
25 ms
keyboard.css
24 ms
sex.gif
278 ms
bundle.js
78 ms
preloader_hand_01.png
175 ms
preloader_hand_02.png
173 ms
preloader_hand_03.png
19 ms
preloader_hand_04.png
164 ms
sdk.js
177 ms
cursor.png
111 ms
fwa-sod.png
112 ms
fwa-mod.png
112 ms
GT-Cinetype-Mono.woff
106 ms
hand_rig.js
414 ms
shadow.png
69 ms
bg_404_d.jpg
113 ms
bg_LLP_d.jpg
279 ms
bg_USA_d.png
141 ms
bg_MLB_d.jpg
140 ms
bg_NBA_d.jpg
111 ms
bg_NFL_d.jpg
140 ms
bg_ASS_d.jpg
180 ms
bg_NYC_d.jpg
299 ms
BG_R_d.jpg
295 ms
BG_S_d.jpg
253 ms
BG_U_d.jpg
291 ms
px.jpg
352 ms
nx.jpg
329 ms
py.jpg
353 ms
ny.jpg
354 ms
pz.jpg
351 ms
nz.jpg
353 ms
side1.jpg
682 ms
side2.jpg
679 ms
0.jpg
680 ms
6.jpg
684 ms
9.jpg
680 ms
BRO.jpg
684 ms
DUH.jpg
682 ms
K.jpg
705 ms
L.jpg
703 ms
SUP.jpg
705 ms
T.jpg
706 ms
X.jpg
719 ms
studio.jpg
704 ms
F.jpg
706 ms
H.jpg
707 ms
lol.jpg
708 ms
188 ms
xd_arbiter.php
182 ms
xd_arbiter.php
577 ms
hands.wtf 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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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
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.
hands.wtf best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
hands.wtf SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hands.wtf can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Hands.wtf 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.
hands.wtf
Open Graph data is detected on the main page of Hands. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: