wtf.com

wtf.com is SSL secured

Free website and domain report on wtf.com

Last Updated: 16th July, 2021 Update Now
Overview

Snoop Summary for wtf.com

This is a free and comprehensive report about wtf.com. Wtf.com is hosted in United States on a server with an IP address of 172.67.220.206, where USD is the local currency and the local language is English. Our records indicate that wtf.com is owned/operated by Cloudflare, Inc.. Wtf.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If wtf.com was to be sold it would possibly be worth $811 USD (based on the daily revenue potential of the website over a 24 month period). Wtf.com is somewhat popular with an estimated 385 daily unique visitors. This report was last updated 16th July, 2021.

About wtf.com

Site Preview:
Title: WTF!?
Description: WTF.com is a forum focused on ranting, debating the news topics of the day, and general off-topic discussions often with a touch of humor. A real community...
Keywords and Tags: adult content, bulletin boards, forum
Related Terms: imgur wtf, ranting, wtf, wtf face, wtf videos
Fav Icon:
Age: Over 28 years old
Domain Created: 12th August, 1995
Domain Updated: 19th February, 2019
Domain Expires: 11th August, 2024
Review

Snoop Score

2/5

Valuation

$811 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,139,017
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 385
Monthly Visitors: 11,723
Yearly Visitors: 140,580
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $33 USD
Yearly Revenue: $401 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: wtf.com 7
Domain Name: wtf 3
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.36 seconds
Load Time Comparison: Faster than 50% of sites

PageSpeed Insights

Avg. (All Categories) 89
Performance 88
Accessibility 79
Best Practices 87
SEO 92
Progressive Web App 100
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.wtf.com/
Updated: 16th July, 2021

3.92 seconds
First Contentful Paint (FCP)
33%
31%
36%

0.01 seconds
First Input Delay (FID)
97%
1%
2%

88

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for wtf.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 1.1 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.038
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://wtf.com/
http/1.1
0
84.718000143766
787
0
301
https://wtf.com/
http/1.1
85.454999934882
351.96699993685
1026
0
301
text/html
https://www.wtf.com/
h2
352.67399996519
737.23899992183
19280
95047
200
text/html
Document
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/fonts/materialdesignicons-webfont.woff2?v=5.8.55
h2
753.48700024188
951.4560000971
304426
303580
200
font/woff2
Font
https://www.wtf.com/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=35&l=1&d=1626119561&k=76d5785332cf089fa6b659d300af9f951e8f5fa2
h2
757.80500005931
1077.2330001928
48501
315500
200
text/css
Stylesheet
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/css/materialdesignicons.min.css?d=1626119560
h2
757.99700012431
941.695000045
42506
255165
200
text/css
Stylesheet
https://www.wtf.com/css.php?css=public%3Anode_list.less%2Cpublic%3Anotices.less%2Cpublic%3Ashare_controls.less%2Cpublic%3Auix.less%2Cpublic%3Auix_socialMedia.less%2Cpublic%3Auix_welcomeSection.less%2Cpublic%3Aextra.less&s=35&l=1&d=1626119561&k=320b8d971da187b335241d9759fd44d02bb68bd2
h2
758.4700002335
1086.5980000235
14876
72755
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Roboto:300,400,500,600,700
h2
758.77400022
777.57300017402
1473
8172
200
text/css
Stylesheet
https://www.wtf.com/js/xf/preamble.min.js?_v=c82ff921
h2
759.08800028265
891.83400012553
2389
3146
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-5907984-1
h2
1123.6740001477
1158.9440000243
40358
99913
200
application/javascript
Script
https://www.wtf.com/styles/wtf/wtf/logotext.png
h2
1123.8540001214
1191.5890001692
6679
5789
200
image/png
Image
https://www.wtf.com/styles/wtf/wtf/mascot.png
h2
1124.063000083
1178.5940001719
16350
15466
200
image/png
Image
https://www.wtf.com/images/footerFinger.png
h2
1124.257999938
1216.5120001882
2222
1335
200
image/png
Image
https://www.wtf.com/images/wtfSign.png
h2
1124.4920003228
1145.8760001697
1568
684
200
image/png
Image
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
h2
1079.7570003197
1085.5970000848
31891
89476
200
text/javascript
Script
https://www.wtf.com/js/vendor/vendor-compiled.js?_v=c82ff921
h2
1095.7090002485
1192.7640000358
22811
70571
200
application/javascript
Script
https://www.wtf.com/js/xf/core-compiled.js?_v=c82ff921
h2
1121.710000094
1236.3900002092
65032
223548
200
application/javascript
Script
https://www.wtf.com/js/xf/notice.min.js?_v=c82ff921
h2
1122.0110002905
1255.3850002587
2647
4125
200
application/javascript
Script
https://www.wtf.com/js/themehouse/reactplus/defaultReaction.min.js?_v=c82ff921
h2
1122.3639999516
1254.5839999802
1459
1318
200
application/javascript
Script
https://www.wtf.com/js/themehouse/reactplus/hiddenContent.min.js?_v=c82ff921
h2
1122.5980003364
1196.2500000373
1552
1576
200
application/javascript
Script
https://www.wtf.com/js/themehouse/uix_dark/ripple.min.js?_v=c82ff921
h2
1122.7910001762
1269.985999912
1474
1420
200
application/javascript
Script
https://www.wtf.com/js/themehouse/global/20210125.min.js?_v=c82ff921
h2
1122.955000028
1224.7490002774
4868
11049
200
application/javascript
Script
https://www.wtf.com/js/themehouse/uix_dark/index.min.js?_v=c82ff921
h2
1123.2360000722
1243.5550000519
3838
8230
200
application/javascript
Script
https://www.wtf.com/js/themehouse/uix_dark/vendor/hover-intent/jquery.hoverIntent.min.js?_v=c82ff921
h2
1123.4059999697
1212.6589999534
1840
2244
200
application/javascript
Script
https://www.wtf.com/js/themehouse/uix_dark/defer.min.js?_v=c82ff921
h2
1124.8170002364
1225.2750000916
4966
17957
200
application/javascript
Script
https://www.wtf.com/js/themehouse/uix_dark/deferNodesCollapse.min.js?_v=c82ff921
h2
1125.0070002861
1240.2230002917
2175
2914
200
application/javascript
Script
https://www.wtf.com/js/themehouse/uix_dark/deferWidthToggle.min.js?_v=c82ff921
h2
1125.2150000073
1238.1750000641
1942
2380
200
application/javascript
Script
https://www.wtf.com/styles/wtf/wtf/welcome.png
h2
1137.9660000093
1213.5720001534
165267
164376
200
image/png
Image
https://www.wtf.com/images/prefixes/fringe.png
h2
1141.2680000067
1179.162000306
1723
841
200
image/png
Image
https://www.wtf.com/images/prefixes/other.png
h2
1142.0080000535
1192.0710001141
1602
716
200
image/png
Image
https://www.wtf.com/images/prefixes/scrapbook.png
h2
1144.5140000433
1166.7150002904
1538
647
200
image/png
Image
https://www.wtf.com/images/prefixes/notice.png
h2
1146.4730002917
1168.0459999479
1318
428
200
image/png
Image
https://www.wtf.com/styles/wtf/wtf/spriteMain.png
h2
1152.7130003087
1179.4890002348
7205
6308
200
image/png
Image
https://www.wtf.com/styles/wtf/wtf/spriteSocial.png
h2
1153.2040000893
1177.9910000041
4603
3708
200
image/png
Image
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/fonts/materialdesignicons-webfont.woff2?v=5.5.55
h2
1156.2520000152
1318.0360002443
304424
303580
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v27/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
1167.2690003179
1170.3230002895
11805
11048
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
1172.6770000532
1175.9780002758
11789
11032
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v27/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
h2
1241.5940002538
1246.3270002045
11806
11048
200
font/woff2
Font
https://www.wtf.com/data/avatars/s/3/3948.jpg?1401502290
h2
1261.5740001202
1346.8570001423
4808
3927
200
image/jpeg
Image
https://www.wtf.com/data/avatars/s/27/27190.jpg?1620296918
h2
1261.9700003415
1342.4980002455
2456
1573
200
image/jpeg
Image
https://www.wtf.com/data/avatars/s/26/26297.jpg?1618048481
h2
1262.2179999016
1331.6490002908
1931
1050
200
image/jpeg
Image
https://www.wtf.com/data/avatars/s/18/18326.jpg?1621619418
h2
1262.4710001983
1340.8139999956
1551
671
200
image/jpeg
Image
https://www.wtf.com/data/avatars/s/5/5578.jpg?1493549275
h2
1262.8870001063
1389.793000184
2546
1663
200
image/jpeg
Image
https://www.wtf.com/data/avatars/s/4/4139.jpg?1333482290
h2
1263.0150001496
1337.6859999262
2844
1963
200
image/jpeg
Image
https://www.wtf.com/data/avatars/s/0/442.jpg?1579295339
h2
1263.6770000681
1335.4050000198
2405
1522
200
image/jpeg
Image
https://www.wtf.com/data/avatars/s/23/23040.jpg?1623451298
h2
1263.8360001147
1334.9330001511
2487
1604
200
image/jpeg
Image
https://www.wtf.com/data/avatars/s/22/22353.jpg?1394571881
h2
1264.0920002013
1332.5660000555
2418
1533
200
image/jpeg
Image
https://www.google-analytics.com/analytics.js
h2
1567.1680001542
1572.1869999543
20313
49377
200
text/javascript
Script
https://www.wtf.com/job.php
h2
1658.3450003527
1862.5920000486
948
14
200
application/json
XHR
https://www.google-analytics.com/j/collect?v=1&_v=j91&a=474715296&t=pageview&_s=1&dl=https%3A%2F%2Fwww.wtf.com%2F&ul=en-us&de=UTF-8&dt=WTF!%3F&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=418605027&gjid=2086647793&cid=644326420.1626472619&tid=UA-5907984-1&_gid=1978857592.1626472619&_r=1&gtm=2ou7e0&z=13984886
h2
1693.0880001746
1696.7050000094
636
1
200
text/plain
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
748.78
9.614
950.608
13.005
1086.231
14.12
1106.145
32.824
1138.986
132.785
1272.786
23.261
1315.881
37.858
1357.151
7.504
1365.776
26.752
1398.677
35.521
1434.93
9.825
1444.92
7.166
1459.577
83.154
1548.181
12.44
1560.643
13.819
1575.022
31.703
1607.307
7.332
1615.241
37.414
1672.034
28.736
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Properly size images — Potential savings of 14 KiB
Images can slow down the page's load time. Wtf.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.wtf.com/styles/wtf/wtf/mascot.png
15466
14435
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Wtf.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Wtf.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Wtf.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 97 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Wtf.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.wtf.com/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=35&l=1&d=1626119561&k=76d5785332cf089fa6b659d300af9f951e8f5fa2
48501
45018
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/css/materialdesignicons.min.css?d=1626119560
42506
42454
https://www.wtf.com/css.php?css=public%3Anode_list.less%2Cpublic%3Anotices.less%2Cpublic%3Ashare_controls.less%2Cpublic%3Auix.less%2Cpublic%3Auix_socialMedia.less%2Cpublic%3Auix_welcomeSection.less%2Cpublic%3Aextra.less&s=35&l=1&d=1626119561&k=320b8d971da187b335241d9759fd44d02bb68bd2
14876
11486
Reduce unused JavaScript — Potential savings of 66 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.wtf.com/js/xf/core-compiled.js?_v=c82ff921
65032
46733
https://www.googletagmanager.com/gtag/js?id=UA-5907984-1
40358
20942
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 93 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.wtf.com/styles/wtf/wtf/welcome.png
164376
95122
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 390 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.wtf.com/
385.561
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Wtf.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.wtf.com/js/themehouse/uix_dark/deferWidthToggle.min.js?_v=c82ff921
136
https://www.wtf.com/js/themehouse/uix_dark/deferNodesCollapse.min.js?_v=c82ff921
125
https://www.wtf.com/js/themehouse/uix_dark/index.min.js?_v=c82ff921
78
https://www.wtf.com/js/themehouse/uix_dark/defer.min.js?_v=c82ff921
70
https://www.wtf.com/js/vendor/vendor-compiled.js?_v=c82ff921
59
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.wtf.com/styles/wtf/wtf/welcome.png
0

Diagnostics

Avoids enormous network payloads — Total size was 1,189 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/fonts/materialdesignicons-webfont.woff2?v=5.8.55
304426
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/fonts/materialdesignicons-webfont.woff2?v=5.5.55
304424
https://www.wtf.com/styles/wtf/wtf/welcome.png
165267
https://www.wtf.com/js/xf/core-compiled.js?_v=c82ff921
65032
https://www.wtf.com/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=35&l=1&d=1626119561&k=76d5785332cf089fa6b659d300af9f951e8f5fa2
48501
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/css/materialdesignicons.min.css?d=1626119560
42506
https://www.googletagmanager.com/gtag/js?id=UA-5907984-1
40358
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
31891
https://www.wtf.com/js/vendor/vendor-compiled.js?_v=c82ff921
22811
https://www.google-analytics.com/analytics.js
20313
Avoid chaining critical requests — 17 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Wtf.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.wtf.com/
263.355
15.864
4.056
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
151.297
112.612
2.163
Unattributable
102.439
7.008
0.161
Minimizes main-thread work — 0.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
222.25
Style & Layout
198.415
Other
123.876
Rendering
55.752
Parse HTML & CSS
47.082
Script Parsing & Compilation
24.856
Garbage Collection
7.272
Keep request counts low and transfer sizes small — 50 requests • 1,189 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
50
1217359
Font
5
644250
Image
20
233521
Script
16
209555
Stylesheet
4
107356
Document
1
19280
Other
4
3397
Media
0
0
Third-party
8
130071
Minimize third-party usage — Third-party code blocked the main thread for 20 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
31891
20.638
40358
0
36873
0
20949
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.028564985284168
0.0055278580526931
0.0020428378747335
0.00063435139382297
0.00041526540404418
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.wtf.com/
614
66
Avoid non-composited animations — 3 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 1.1 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.5 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.0 s
The timing of the largest text or image that is painted.

Other

First Meaningful Paint — 1.1 s
The time taken for the primary content of the page to be rendered.

Opportunities

Eliminate render-blocking resources — Potential savings of 430 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Wtf.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.wtf.com/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=35&l=1&d=1626119561&k=76d5785332cf089fa6b659d300af9f951e8f5fa2
48501
120
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/css/materialdesignicons.min.css?d=1626119560
42506
80
https://fonts.googleapis.com/css?family=Roboto:300,400,500,600,700
1473
230
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Wtf.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://wtf.com/
190
https://wtf.com/
150
https://www.wtf.com/
0

Diagnostics

Serve static assets with an efficient cache policy — 37 resources found
Wtf.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20313
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/fonts/materialdesignicons-webfont.woff2?v=5.8.55
604800000
304426
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/fonts/materialdesignicons-webfont.woff2?v=5.5.55
604800000
304424
https://www.wtf.com/styles/wtf/wtf/welcome.png
604800000
165267
https://www.wtf.com/js/xf/core-compiled.js?_v=c82ff921
604800000
65032
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/css/materialdesignicons.min.css?d=1626119560
604800000
42506
https://www.wtf.com/js/vendor/vendor-compiled.js?_v=c82ff921
604800000
22811
https://www.wtf.com/styles/wtf/wtf/mascot.png
604800000
16350
https://www.wtf.com/styles/wtf/wtf/spriteMain.png
604800000
7205
https://www.wtf.com/styles/wtf/wtf/logotext.png
604800000
6679
https://www.wtf.com/js/themehouse/uix_dark/defer.min.js?_v=c82ff921
604800000
4966
https://www.wtf.com/js/themehouse/global/20210125.min.js?_v=c82ff921
604800000
4868
https://www.wtf.com/data/avatars/s/3/3948.jpg?1401502290
604800000
4808
https://www.wtf.com/styles/wtf/wtf/spriteSocial.png
604800000
4603
https://www.wtf.com/js/themehouse/uix_dark/index.min.js?_v=c82ff921
604800000
3838
https://www.wtf.com/data/avatars/s/4/4139.jpg?1333482290
604800000
2844
https://www.wtf.com/js/xf/notice.min.js?_v=c82ff921
604800000
2647
https://www.wtf.com/data/avatars/s/5/5578.jpg?1493549275
604800000
2546
https://www.wtf.com/data/avatars/s/23/23040.jpg?1623451298
604800000
2487
https://www.wtf.com/data/avatars/s/27/27190.jpg?1620296918
604800000
2456
https://www.wtf.com/data/avatars/s/22/22353.jpg?1394571881
604800000
2418
https://www.wtf.com/data/avatars/s/0/442.jpg?1579295339
604800000
2405
https://www.wtf.com/js/xf/preamble.min.js?_v=c82ff921
604800000
2389
https://www.wtf.com/images/footerFinger.png
604800000
2222
https://www.wtf.com/js/themehouse/uix_dark/deferNodesCollapse.min.js?_v=c82ff921
604800000
2175
https://www.wtf.com/js/themehouse/uix_dark/deferWidthToggle.min.js?_v=c82ff921
604800000
1942
https://www.wtf.com/data/avatars/s/26/26297.jpg?1618048481
604800000
1931
https://www.wtf.com/js/themehouse/uix_dark/vendor/hover-intent/jquery.hoverIntent.min.js?_v=c82ff921
604800000
1840
https://www.wtf.com/images/prefixes/fringe.png
604800000
1723
https://www.wtf.com/images/prefixes/other.png
604800000
1602
https://www.wtf.com/images/wtfSign.png
604800000
1568
https://www.wtf.com/js/themehouse/reactplus/hiddenContent.min.js?_v=c82ff921
604800000
1552
https://www.wtf.com/data/avatars/s/18/18326.jpg?1621619418
604800000
1551
https://www.wtf.com/images/prefixes/scrapbook.png
604800000
1538
https://www.wtf.com/js/themehouse/uix_dark/ripple.min.js?_v=c82ff921
604800000
1474
https://www.wtf.com/js/themehouse/reactplus/defaultReaction.min.js?_v=c82ff921
604800000
1459
https://www.wtf.com/images/prefixes/notice.png
604800000
1318
Avoid an excessive DOM size — 934 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
934
Maximum DOM Depth
i
25
Maximum Child Elements
32

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/fonts/materialdesignicons-webfont.woff2?v=5.5.55
161.78400022909
https://fonts.gstatic.com/s/roboto/v27/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
3.0539999715984
https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
3.3010002225637
https://fonts.gstatic.com/s/roboto/v27/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
4.7329999506474
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://www.wtf.com/styles/wtf/wtf/mascot.png
img
https://www.wtf.com/styles/wtf/wtf/logotext.png
https://www.wtf.com/images/wtfSign.png
img
79

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of wtf.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Wtf.com may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`[aria-*]` attributes do not match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
Failing Elements

Contrast

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
87

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that wtf.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
Mustache
2.2.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://wtf.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for wtf.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wtf.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
100

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of wtf.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Registers a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wtf.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest has a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 86
Performance 62
Accessibility 93
Best Practices 87
SEO 90
Progressive Web App 100
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.wtf.com/
Updated: 16th July, 2021

4.83 seconds
First Contentful Paint (FCP)
24%
21%
55%

0.01 seconds
First Input Delay (FID)
96%
2%
2%

62

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for wtf.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Total Blocking Time — 80 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 100 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://wtf.com/
http/1.1
0
55.657000048086
755
0
301
https://wtf.com/
http/1.1
56.153999990784
306.51400005445
1013
0
301
text/html
https://www.wtf.com/
h2
306.99700000696
632.65399995726
19276
95030
200
text/html
Document
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/fonts/materialdesignicons-webfont.woff2?v=5.8.55
h2
645.49999998417
781.49399999529
304430
303580
200
font/woff2
Font
https://www.wtf.com/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=35&l=1&d=1626119561&k=76d5785332cf089fa6b659d300af9f951e8f5fa2
h2
649.60500004236
898.03200005554
48508
315500
200
text/css
Stylesheet
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/css/materialdesignicons.min.css?d=1626119560
h2
649.85000004526
757.28400005028
42510
255165
200
text/css
Stylesheet
https://www.wtf.com/css.php?css=public%3Anode_list.less%2Cpublic%3Anotices.less%2Cpublic%3Ashare_controls.less%2Cpublic%3Auix.less%2Cpublic%3Auix_socialMedia.less%2Cpublic%3Auix_welcomeSection.less%2Cpublic%3Aextra.less&s=35&l=1&d=1626119561&k=320b8d971da187b335241d9759fd44d02bb68bd2
h2
650.27600002941
870.28000003193
14937
72755
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Roboto:300,400,500,600,700
h2
651.43500000704
663.30300003756
1553
10111
200
text/css
Stylesheet
https://www.wtf.com/js/xf/preamble.min.js?_v=c82ff921
h2
651.57400001772
724.89099996164
2379
3146
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-5907984-1
h2
945.11299999431
968.23400002904
40358
99913
200
application/javascript
Script
https://www.wtf.com/styles/wtf/wtf/logotext.png
h2
945.4759999644
982.06900001969
6683
5789
200
image/png
Image
https://www.wtf.com/styles/wtf/wtf/mascot.png
h2
947.91300001089
975.83100001793
16356
15466
200
image/png
Image
https://www.wtf.com/images/footerFinger.png
h2
948.8709999714
982.40099998657
2226
1335
200
image/png
Image
https://www.wtf.com/images/wtfSign.png
h2
949.17599996552
980.58900004253
1574
684
200
image/png
Image
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
h2
872.30499996804
877.2609999869
31891
89476
200
text/javascript
Script
https://www.wtf.com/js/vendor/vendor-compiled.js?_v=c82ff921
h2
883.46000004094
981.20399995241
22739
70571
200
application/javascript
Script
https://www.wtf.com/js/xf/core-compiled.js?_v=c82ff921
h2
900.76400001999
1014.3480000552
65033
223548
200
application/javascript
Script
https://www.wtf.com/js/xf/notice.min.js?_v=c82ff921
h2
943.00299999304
1012.641999987
2653
4125
200
application/javascript
Script
https://www.wtf.com/js/themehouse/reactplus/defaultReaction.min.js?_v=c82ff921
h2
943.24199995026
1011.6090000374
1455
1318
200
application/javascript
Script
https://www.wtf.com/js/themehouse/reactplus/hiddenContent.min.js?_v=c82ff921
h2
943.88499995694
1016.4329999825
1554
1576
200
application/javascript
Script
https://www.wtf.com/js/themehouse/uix_dark/ripple.min.js?_v=c82ff921
h2
944.15800005663
1016.6579999495
1466
1420
200
application/javascript
Script
https://www.wtf.com/js/themehouse/global/20210125.min.js?_v=c82ff921
h2
944.36600001063
1030.1159999799
4874
11049
200
application/javascript
Script
https://www.wtf.com/js/themehouse/uix_dark/index.min.js?_v=c82ff921
h2
944.64899995364
1017.6549999742
3838
8230
200
application/javascript
Script
https://www.wtf.com/js/themehouse/uix_dark/vendor/hover-intent/jquery.hoverIntent.min.js?_v=c82ff921
h2
944.91600000765
1017.4600000028
1836
2244
200
application/javascript
Script
https://www.wtf.com/js/themehouse/uix_dark/defer.min.js?_v=c82ff921
h2
949.41500003915
1021.3239999721
4916
17957
200
application/javascript
Script
https://www.wtf.com/js/themehouse/uix_dark/deferNodesCollapse.min.js?_v=c82ff921
h2
949.59199998993
1017.0739999739
2179
2914
200
application/javascript
Script
https://www.wtf.com/js/themehouse/uix_dark/deferWidthToggle.min.js?_v=c82ff921
h2
949.89100005478
1017.2670000466
1936
2380
200
application/javascript
Script
https://www.wtf.com/images/prefixes/fringe.png
h2
981.9210000569
1013.5109999683
1737
841
200
image/png
Image
https://www.wtf.com/images/prefixes/other.png
h2
982.8180000186
1015.7780000009
1598
716
200
image/png
Image
https://www.wtf.com/images/prefixes/scrapbook.png
h2
983.01700002048
1015.4999999795
1530
647
200
image/png
Image
https://www.wtf.com/images/prefixes/notice.png
h2
983.15300000831
1013.0699999863
1320
428
200
image/png
Image
https://www.wtf.com/styles/wtf/wtf/spriteMain.png
h2
984.21999998391
1016.1379999481
7199
6308
200
image/png
Image
https://www.wtf.com/styles/wtf/wtf/spriteSocial.png
h2
985.04499997944
1012.2500000289
4603
3708
200
image/png
Image
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/fonts/materialdesignicons-webfont.woff2?v=5.5.55
h2
992.49900004361
1128.0790000455
304428
303580
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v27/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
h2
1011.072000023
1016.871000058
11634
11048
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
1021.1549999658
1025.1439999556
11788
11032
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v27/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
1032.3639999842
1036.0309999669
11804
11048
200
font/woff2
Font
https://www.google-analytics.com/analytics.js
h2
1358.6199999554
1362.5969999703
20313
49377
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j91&a=549251322&t=pageview&_s=1&dl=https%3A%2F%2Fwww.wtf.com%2F&ul=en-us&de=UTF-8&dt=WTF!%3F&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=1402218224&gjid=1913189121&cid=1405757877.1626472641&tid=UA-5907984-1&_gid=261857050.1626472641&_r=1&gtm=2ou7e0&z=1935568826
h2
1384.6190000186
1387.6569999848
636
1
200
text/plain
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
645.405
8.265
769.334
12.277
910.073
18.813
928.992
34.952
963.964
137.578
1102.182
27.507
1154.054
7.337
1175.575
21.386
1198.438
5.79
1205.81
41.938
1249.936
7.801
1260.034
48.022
1308.875
38.958
1348.763
6.873
1359.724
8.924
1376.76
18.174
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Properly size images
Images can slow down the page's load time. Wtf.com should consider serving more appropriate-sized images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Wtf.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Wtf.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 330 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.wtf.com/
326.654
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Wtf.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.wtf.com/js/themehouse/uix_dark/deferWidthToggle.min.js?_v=c82ff921
136
https://www.wtf.com/js/themehouse/uix_dark/deferNodesCollapse.min.js?_v=c82ff921
125
https://www.wtf.com/js/themehouse/uix_dark/index.min.js?_v=c82ff921
78
https://www.wtf.com/js/themehouse/uix_dark/defer.min.js?_v=c82ff921
69
https://www.wtf.com/js/vendor/vendor-compiled.js?_v=c82ff921
59
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 1,003 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/fonts/materialdesignicons-webfont.woff2?v=5.8.55
304430
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/fonts/materialdesignicons-webfont.woff2?v=5.5.55
304428
https://www.wtf.com/js/xf/core-compiled.js?_v=c82ff921
65033
https://www.wtf.com/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=35&l=1&d=1626119561&k=76d5785332cf089fa6b659d300af9f951e8f5fa2
48508
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/css/materialdesignicons.min.css?d=1626119560
42510
https://www.googletagmanager.com/gtag/js?id=UA-5907984-1
40358
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
31891
https://www.wtf.com/js/vendor/vendor-compiled.js?_v=c82ff921
22739
https://www.google-analytics.com/analytics.js
20313
https://www.wtf.com/
19276
Avoid chaining critical requests — 17 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Wtf.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.6 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.wtf.com/
877.292
43.16
12.392
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
340.092
297.972
7.164
Unattributable
305.42
14.588
0.676
https://www.googletagmanager.com/gtag/js?id=UA-5907984-1
177.092
57.836
10.268
https://www.wtf.com/js/xf/preamble.min.js?_v=c82ff921
96.012
19.744
2.756
https://www.google-analytics.com/analytics.js
77.496
67.764
4.52
https://www.wtf.com/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=35&l=1&d=1626119561&k=76d5785332cf089fa6b659d300af9f951e8f5fa2
75.252
0
0
https://www.wtf.com/js/xf/core-compiled.js?_v=c82ff921
67.452
41.428
20.108
Keep request counts low and transfer sizes small — 39 requests • 1,003 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
39
1027518
Font
5
644084
Script
16
209420
Stylesheet
4
107508
Image
10
44826
Document
1
19276
Other
3
2404
Media
0
0
Third-party
8
129977
Minimize third-party usage — Third-party code blocked the main thread for 230 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
31891
154.908
40358
55.152
20949
15.124
36779
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00034848827785916
0.00033844338480316
2.9033133500271E-5
2.9033133500271E-5
2.9033133500271E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 8 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.wtf.com/
2058
275
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
3420
110
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
8574
96
https://www.wtf.com/js/xf/core-compiled.js?_v=c82ff921
8490
84
https://www.googletagmanager.com/gtag/js?id=UA-5907984-1
3619
78
https://www.wtf.com/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=35&l=1&d=1626119561&k=76d5785332cf089fa6b659d300af9f951e8f5fa2
3240
75
https://www.google-analytics.com/analytics.js
4663
73
https://www.wtf.com/js/xf/preamble.min.js?_v=c82ff921
6090
70
Avoid non-composited animations — 3 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Speed Index — 5.1 s
The time taken for the page contents to be visibly populated.

Other

First Meaningful Paint — 3.8 s
The time taken for the primary content of the page to be rendered.

Opportunities

Defer offscreen images — Potential savings of 15 KiB
Time to Interactive can be slowed down by resources on the page. Wtf.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.wtf.com/styles/wtf/wtf/mascot.png
15466
15466
Reduce unused CSS — Potential savings of 97 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Wtf.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.wtf.com/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=35&l=1&d=1626119561&k=76d5785332cf089fa6b659d300af9f951e8f5fa2
48508
45062
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/css/materialdesignicons.min.css?d=1626119560
42510
42465
https://www.wtf.com/css.php?css=public%3Anode_list.less%2Cpublic%3Anotices.less%2Cpublic%3Ashare_controls.less%2Cpublic%3Auix.less%2Cpublic%3Auix_socialMedia.less%2Cpublic%3Auix_welcomeSection.less%2Cpublic%3Aextra.less&s=35&l=1&d=1626119561&k=320b8d971da187b335241d9759fd44d02bb68bd2
14937
11974
Reduce unused JavaScript — Potential savings of 66 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.wtf.com/js/xf/core-compiled.js?_v=c82ff921
65033
47099
https://www.googletagmanager.com/gtag/js?id=UA-5907984-1
40358
20942

Diagnostics

Serve static assets with an efficient cache policy — 27 resources found
Wtf.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20313
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/fonts/materialdesignicons-webfont.woff2?v=5.8.55
604800000
304430
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/fonts/materialdesignicons-webfont.woff2?v=5.5.55
604800000
304428
https://www.wtf.com/js/xf/core-compiled.js?_v=c82ff921
604800000
65033
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/css/materialdesignicons.min.css?d=1626119560
604800000
42510
https://www.wtf.com/js/vendor/vendor-compiled.js?_v=c82ff921
604800000
22739
https://www.wtf.com/styles/wtf/wtf/mascot.png
604800000
16356
https://www.wtf.com/styles/wtf/wtf/spriteMain.png
604800000
7199
https://www.wtf.com/styles/wtf/wtf/logotext.png
604800000
6683
https://www.wtf.com/js/themehouse/uix_dark/defer.min.js?_v=c82ff921
604800000
4916
https://www.wtf.com/js/themehouse/global/20210125.min.js?_v=c82ff921
604800000
4874
https://www.wtf.com/styles/wtf/wtf/spriteSocial.png
604800000
4603
https://www.wtf.com/js/themehouse/uix_dark/index.min.js?_v=c82ff921
604800000
3838
https://www.wtf.com/js/xf/notice.min.js?_v=c82ff921
604800000
2653
https://www.wtf.com/js/xf/preamble.min.js?_v=c82ff921
604800000
2379
https://www.wtf.com/images/footerFinger.png
604800000
2226
https://www.wtf.com/js/themehouse/uix_dark/deferNodesCollapse.min.js?_v=c82ff921
604800000
2179
https://www.wtf.com/js/themehouse/uix_dark/deferWidthToggle.min.js?_v=c82ff921
604800000
1936
https://www.wtf.com/js/themehouse/uix_dark/vendor/hover-intent/jquery.hoverIntent.min.js?_v=c82ff921
604800000
1836
https://www.wtf.com/images/prefixes/fringe.png
604800000
1737
https://www.wtf.com/images/prefixes/other.png
604800000
1598
https://www.wtf.com/images/wtfSign.png
604800000
1574
https://www.wtf.com/js/themehouse/reactplus/hiddenContent.min.js?_v=c82ff921
604800000
1554
https://www.wtf.com/images/prefixes/scrapbook.png
604800000
1530
https://www.wtf.com/js/themehouse/uix_dark/ripple.min.js?_v=c82ff921
604800000
1466
https://www.wtf.com/js/themehouse/reactplus/defaultReaction.min.js?_v=c82ff921
604800000
1455
https://www.wtf.com/images/prefixes/notice.png
604800000
1320
Avoid an excessive DOM size — 920 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
920
Maximum DOM Depth
i
25
Maximum Child Elements
32
Minimize main-thread work — 2.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
707.624
Script Evaluation
587.8
Other
495.836
Parse HTML & CSS
202.184
Script Parsing & Compilation
80.724
Rendering
78.208

Metrics

First Contentful Paint — 3.8 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 5.8 s
The timing of the largest text or image that is painted.
Time to Interactive — 8.6 s
The time taken for the page to become fully interactive.

Opportunities

Eliminate render-blocking resources — Potential savings of 1,420 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Wtf.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.wtf.com/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=35&l=1&d=1626119561&k=76d5785332cf089fa6b659d300af9f951e8f5fa2
48508
600
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/css/materialdesignicons.min.css?d=1626119560
42510
450
https://www.wtf.com/css.php?css=public%3Anode_list.less%2Cpublic%3Anotices.less%2Cpublic%3Ashare_controls.less%2Cpublic%3Auix.less%2Cpublic%3Auix_socialMedia.less%2Cpublic%3Auix_welcomeSection.less%2Cpublic%3Aextra.less&s=35&l=1&d=1626119561&k=320b8d971da187b335241d9759fd44d02bb68bd2
14937
150
https://fonts.googleapis.com/css?family=Roboto:300,400,500,600,700
1553
780
https://www.wtf.com/js/xf/preamble.min.js?_v=c82ff921
2379
150
Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Wtf.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://wtf.com/
630
https://wtf.com/
480
https://www.wtf.com/
0

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.wtf.com/styles/wtf/fonts/icons/material-icons/fonts/materialdesignicons-webfont.woff2?v=5.5.55
135.58000000194
https://fonts.gstatic.com/s/roboto/v27/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
5.7990000350401
https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
3.9889999898151
https://fonts.gstatic.com/s/roboto/v27/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
3.6669999826699
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://www.wtf.com/styles/wtf/wtf/logotext.png

Other

First Contentful Paint (3G) — 7650 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
93

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of wtf.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Wtf.com may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`button`, `link`, and `menuitem` elements do not have accessible names.
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

Contrast

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
87

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that wtf.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
Mustache
2.2.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://wtf.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for wtf.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wtf.com on mobile screens.
Document uses legible font sizes — 99.73% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
.p-footer-rssLink>span
0.22%
10.4px
sub, sup
0.02%
9.75px
.far, .fa, .fas, .fab, .fal
0.02%
10.4px
99.73%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 63% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
104x15
60x15
48x15
94x15
74x15
87x15
67x24
140x24
175x24
67x24
a
25x30
a
25x30
RSS

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
100

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of wtf.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Registers a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wtf.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest has a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 172.67.220.206
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization: Cloudflare, Inc.
Country: US
City: wafangdian
State: California
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Network Solutions, LLC 162.159.134.53
Security

Visitor Safety

Mature Content: Yes
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 76/100
WOT Child Safety: 27/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 11th June, 2021
Valid To: 10th June, 2022
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: c959965e
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 20347722222903626108204008772710610491
Serial Number (Hex): 0F4ED42926B0467EB7D6AC0574EAB63B
Valid From: 11th June, 2024
Valid To: 10th June, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
Timestamp : Jun 11 06:22:41.011 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:A7:CF:3D:28:41:31:A4:49:4D:1D:66:
84:FF:B1:67:A5:78:A3:2D:5A:6A:E0:55:84:91:AB:7E:
01:92:26:80:81:02:20:04:2A:F1:33:5D:9F:38:50:75:
C7:40:A7:50:E0:E5:A3:F1:9D:4C:D2:AF:82:CD:41:F9:
61:ED:0C:3A:A7:0E:A8
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 22:45:45:07:59:55:24:56:96:3F:A1:2F:F1:F7:6D:86:
E0:23:26:63:AD:C0:4B:7F:5D:C6:83:5C:6E:E2:0F:02
Timestamp : Jun 11 06:22:41.038 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:B3:EB:42:71:11:7E:A2:B0:57:2C:4E:
D9:25:06:29:A7:EC:10:53:FC:CC:74:CC:80:24:F7:FB:
42:73:C6:A6:A1:02:20:5A:CA:0C:2B:EE:B2:85:0B:77:
23:0B:D3:23:B9:64:E2:C8:90:34:2B:86:5C:F1:B4:F3:
1A:C5:C0:A0:B2:AB:8D
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
Timestamp : Jun 11 06:22:40.944 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:B1:5C:4B:8C:DB:D1:EC:0A:2F:96:28:
53:16:3B:01:C5:25:D5:D1:19:D9:63:19:CF:79:B3:83:
07:B9:54:F2:FB:02:20:20:F1:3E:B6:80:EF:66:6F:1B:
07:86:28:E8:3B:4E:9F:E6:75:1F:1C:CA:DD:63:41:D8:
A5:0C:32:F1:C5:41:6E
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.wtf.com
DNS:sni.cloudflaressl.com
DNS:wtf.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 16th July, 2021
Content-Type: text/html; charset=utf-8
Expires: 19th November, 1981
Cache-Control: private, no-cache, max-age=0
Server: cloudflare
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Vary: Accept-Encoding
Set-Cookie: *
Last-Modified: 16th July, 2021
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=QRMwjUXh0At7H0Eyk4rRIFf2Rhhj45rWX6SES1JMQ64%2BabzDvClth1vp5Gxi6%2Fq1kSf1piec3zYr4%2BQ9Zy8viNWPLPP1FYj013dl5U0uaekTRm7coeVu3oHhTO9%2BkQ%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"report_to":"cf-nel","max_age":604800}
Strict-Transport-Security: max-age=0
CF-RAY: 66fe7b8cdee118b1-EWR
alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400, h3=":443"; ma=86400

Whois Lookup

Created: 12th August, 1995
Changed: 19th February, 2019
Expires: 11th August, 2024
Registrar: Network Solutions, LLC
Status: clientTransferProhibited
Nameservers: simon.ns.cloudflare.com
wally.ns.cloudflare.com
Owner Name: PERFECT PRIVACY, LLC
Owner Street: 5335 Gate Parkway care of Network Solutions PO Box 459
Owner Post Code: 32256
Owner City: Jacksonville
Owner State: FL
Owner Country: US
Owner Phone: +1.5707088780
Owner Email: gt6db45u3r5@networksolutionsprivateregistration.com
Admin Name: PERFECT PRIVACY, LLC
Admin Street: 5335 Gate Parkway care of Network Solutions PO Box 459
Admin Post Code: 32256
Admin City: Jacksonville
Admin State: FL
Admin Country: US
Admin Phone: +1.5707088780
Admin Email: gt6db45u3r5@networksolutionsprivateregistration.com
Tech Name: PERFECT PRIVACY, LLC
Tech Street: 5335 Gate Parkway care of Network Solutions PO Box 459
Tech Post Code: 32256
Tech City: Jacksonville
Tech State: FL
Tech Country: US
Tech Phone: +1.5707088780
Tech Email: gt6db45u3r5@networksolutionsprivateregistration.com
Full Whois: Domain Name: WTF.COM
Registry Domain ID: 4910724_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.networksolutions.com
Registrar URL: http://networksolutions.com
Updated Date: 2019-02-19T19:22:30Z
Creation Date: 1995-08-12T04:00:00Z
Registrar Registration Expiration Date: 2024-08-11T04:00:00Z
Registrar: Network Solutions, LLC
Registrar IANA ID: 2
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: PERFECT PRIVACY, LLC
Registrant Organization:
Registrant Street: 5335 Gate Parkway care of Network Solutions PO Box 459
Registrant City: Jacksonville
Registrant State/Province: FL
Registrant Postal Code: 32256
Registrant Country: US
Registrant Phone: +1.5707088780
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: gt6db45u3r5@networksolutionsprivateregistration.com
Registry Admin ID:
Admin Name: PERFECT PRIVACY, LLC
Admin Organization:
Admin Street: 5335 Gate Parkway care of Network Solutions PO Box 459
Admin City: Jacksonville
Admin State/Province: FL
Admin Postal Code: 32256
Admin Country: US
Admin Phone: +1.5707088780
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: gt6db45u3r5@networksolutionsprivateregistration.com
Registry Tech ID:
Tech Name: PERFECT PRIVACY, LLC
Tech Organization:
Tech Street: 5335 Gate Parkway care of Network Solutions PO Box 459
Tech City: Jacksonville
Tech State/Province: FL
Tech Postal Code: 32256
Tech Country: US
Tech Phone: +1.5707088780
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: gt6db45u3r5@networksolutionsprivateregistration.com
Name Server: SIMON.NS.CLOUDFLARE.COM
Name Server: WALLY.NS.CLOUDFLARE.COM
DNSSEC: unsigned
Registrar Abuse Contact Email: abuse@web.com
Registrar Abuse Contact Phone: +1.8777228662
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-07-16T21:56:52Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en


This listing is a Network Solutions Private Registration. Mail
correspondence to this address must be sent via USPS Express Mail(TM) or
USPS Certified Mail(R); all other mail will not be processed. Be sure to
include the registrant's domain name in the address.

The data in Networksolutions.com's WHOIS database is provided to you by
Networksolutions.com for information purposes only, that is, to assist you in
obtaining information about or related to a domain name registration
record. Networksolutions.com makes this information available "as is," and
does not guarantee its accuracy. By submitting a WHOIS query, you
agree that you will use this data only for lawful purposes and that,
under no circumstances will you use this data to: (1) allow, enable,
or otherwise support the transmission of mass unsolicited, commercial
advertising or solicitations via direct mail, electronic mail, or by
telephone; or (2) enable high volume, automated, electronic processes
that apply to Networksolutions.com (or its systems). The compilation,
repackaging, dissemination or other use of this data is expressly
prohibited without the prior written consent of Networksolutions.com.
Networksolutions.com reserves the right to modify these terms at any time.
By submitting this query, you agree to abide by these terms.

For more information on Whois status codes, please visit
https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en.

Nameservers

Name IP Address
simon.ns.cloudflare.com 173.245.59.232
wally.ns.cloudflare.com 172.64.32.239
Related

Subdomains

Domain Subdomain
forum

Similar Sites

Domain Valuation Snoop Score
0/5
$1,347 USD 1/5
$354,988 USD 3/5
0/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
$10 USD 1/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$649 USD 2/5
0/5
0/5