documentingreality.com

documentingreality.com is SSL secured

Free website and domain report on documentingreality.com

Last Updated: 26th October, 2023 Update Now
Overview

Snoop Summary for documentingreality.com

This is a free and comprehensive report about documentingreality.com. The domain documentingreality.com is currently hosted on a server located in United States with the IP address 104.26.0.36, where the local currency is USD and English is the local language. Our records indicate that documentingreality.com is owned/operated by Cloudflare, Inc.. Documentingreality.com is expected to earn an estimated $98 USD per day from advertising revenue. The sale of documentingreality.com would possibly be worth $71,319 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Documentingreality.com receives an estimated 23,099 unique visitors every day - a massive amount of traffic! This report was last updated 26th October, 2023.

About documentingreality.com

Site Preview:
Title:
Description: A message board with death pictures, videos, chat and research. Also crime and general chat about art, science and technology.
Keywords and Tags: extreme, gruesome content, popular, pornography, violence
Related Terms:
Fav Icon:
Age: Over 15 years old
Domain Created: 4th August, 2008
Domain Updated: 23rd May, 2020
Domain Expires: 4th August, 2025
Review

Snoop Score

3/5 (Great!)

Valuation

$71,319 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 33,020
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: 23,099
Monthly Visitors: 703,061
Yearly Visitors: 8,431,135
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $98 USD
Monthly Revenue: $2,973 USD
Yearly Revenue: $35,654 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: documentingreality.com 22
Domain Name: documentingreality 18
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 3.34 seconds
Load Time Comparison: Faster than 20% of sites

PageSpeed Insights

Avg. (All Categories) 68
Performance 85
Accessibility 78
Best Practices 50
SEO 92
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.documentingreality.com/forum/
Updated: 30th November, 2022

1.66 seconds
First Contentful Paint (FCP)
79%
15%
6%

0.00 seconds
First Input Delay (FID)
99%
1%
0%

85

Performance

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

Metrics

Time to Interactive — 2.4 s
The time taken for the page to become fully interactive.
Total Blocking Time — 70 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
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Documentingreality.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Documentingreality.com should consider serving more appropriate-sized images.
Defer offscreen images — Potential savings of 13 KiB
Time to Interactive can be slowed down by resources on the page. Documentingreality.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.documentingreality.com/forum/images/300-X-80.jpg
7643
7643
https://www.documentingreality.com/forum/images/Logo-480-3.webp
5460
5460
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Documentingreality.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Documentingreality.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Documentingreality.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 77 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.googletagmanager.com/gtag/js?id=G-6FFVCHQTKT&l=dataLayer&cx=c
76865
31441
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
35029
23519
https://www.googletagmanager.com/gtm.js?id=GTM-N8CQWZ7
47966
23425
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 370 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.documentingreality.com/forum/
370.201
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Documentingreality.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
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.
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.documentingreality.com/forum/gfx/misc/opt_header.jpg
0
Avoids enormous network payloads — Total size was 350 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=G-6FFVCHQTKT&l=dataLayer&cx=c
76865
https://www.googletagmanager.com/gtm.js?id=GTM-N8CQWZ7
47966
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
35029
https://www.documentingreality.com/forum/gfx/misc/opt_header.jpg
21345
https://www.google-analytics.com/analytics.js
20663
https://www.documentingreality.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1669824000
16955
https://www.documentingreality.com/forum/
15594
https://ajax.googleapis.com/ajax/libs/yui/2.9.0/build/yahoo-dom-event/yahoo-dom-event.js?v=387
14363
https://www.documentingreality.com/forum/images/dr_banner_2.jpg
13198
https://www.documentingreality.com/cdn-cgi/challenge-platform/h/b/scripts/pica.js
8710
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Documentingreality.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.4 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.documentingreality.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1669824000
406.299
388.719
1.855
https://www.documentingreality.com/forum/
106.41
13.049
2.919
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
496.876
Other
66.854
Style & Layout
32.639
Rendering
25.394
Parse HTML & CSS
18.037
Garbage Collection
16.449
Script Parsing & Compilation
15.514
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 47 requests • 350 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
47
358140
Script
13
241026
Image
22
77692
Document
1
15594
Other
9
14190
Stylesheet
2
9638
Media
0
0
Font
0
0
Third-party
9
207580
Minimize third-party usage — Third-party code blocked the main thread for 0 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)
124831
0
54932
0
21287
0
6530
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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.documentingreality.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1669824000
3110
199
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 documentingreality.com on mobile screens.

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.

Audits

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://documentingreality.com/
http/1.1
0
44.466000050306
809
0
301
text/plain
https://documentingreality.com/
http/1.1
44.973999960348
157.42699988186
891
0
301
text/html
http://www.documentingreality.com/
http/1.1
157.74900000542
240.74900010601
840
0
301
text/plain
https://www.documentingreality.com/
http/1.1
241.33399990387
429.22200006433
929
0
301
text/html
https://www.documentingreality.com/forum/
h2
429.57699997351
798.78500010818
15594
78666
200
text/html
Document
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
h2
806.41499999911
811.26199988648
35029
97163
200
text/javascript
Script
https://www.documentingreality.com/forum/images/Logo-480-3.webp
h2
806.71499995515
884.66800004244
6365
5460
200
image/webp
Image
https://ajax.googleapis.com/ajax/libs/yui/2.9.0/build/yahoo-dom-event/yahoo-dom-event.js?v=387
h2
806.82600010186
813.00000008196
14363
37510
200
text/javascript
Script
https://ajax.googleapis.com/ajax/libs/yui/2.9.0/build/connection/connection-min.js?v=387
h2
807.02199996449
810.76300004497
5540
13257
200
text/javascript
Script
https://www.documentingreality.com/forum/clientscript/vbulletin_global.js?v=387
h2
807.19499988481
883.81100003608
8487
23479
200
application/javascript
Script
https://www.documentingreality.com/forum/clientscript/vbulletin_menu.js?v=387
h2
807.42500000633
913.21599995717
3422
8730
200
application/javascript
Script
https://www.documentingreality.com/clientscript/vbulletin_important.css?v=387
h2
807.59000009857
861.26399994828
1125
404
200
text/css
Stylesheet
https://www.documentingreality.com/forum/responsive.css
h2
807.80599988066
858.6709999945
8513
35629
200
text/css
Stylesheet
https://www.documentingreality.com/forum/clientscript/vbptcr.js
h2
807.97700001858
861.88199999742
1260
790
200
application/javascript
Script
https://www.documentingreality.com/forum/responsive.js?v=0.1
h2
915.36400001496
992.26400000043
1078
334
200
application/javascript
Script
https://www.documentingreality.com/forum/gfx/misc/navbits_start.gif
h2
917.12999995798
958.15200009383
1222
215
200
image/gif
Image
https://www.documentingreality.com/forum/images/dr_banner_2.jpg
h2
917.29800007306
1002.136999974
13198
12181
200
image/jpeg
Image
https://www.documentingreality.com/forum/images/300-X-80.jpg
h2
917.4790000543
958.49299989641
8668
7643
200
image/jpeg
Image
https://www.documentingreality.com/forum/gfx/buttons/collapse_tcat.gif
h2
917.59500000626
973.87399990112
1173
174
200
image/gif
Image
https://www.documentingreality.com/forum/gfx/misc/tGFX.gif
h2
917.96200000681
946.64700003341
1351
345
200
image/gif
Image
https://www.documentingreality.com/forum/gfx/misc/tlastpost.png
h2
918.11299999245
952.23900000565
1337
328
200
image/png
Image
https://www.documentingreality.com/forum/gfx/misc/tthreads.png
h2
918.2200001087
987.91499994695
1414
406
200
image/png
Image
https://www.documentingreality.com/forum/gfx/misc/tposts.png
h2
918.32799999975
989.0749999322
1387
379
200
image/png
Image
https://www.documentingreality.com/forum/gfx/statusicon/forum_old.gif
h2
918.4729999397
993.37900010869
2292
1291
200
image/gif
Image
https://www.documentingreality.com/forum/gfx/misc/tfooter.gif
h2
918.68199990131
963.0050000269
1061
57
200
image/gif
Image
https://www.documentingreality.com/forum/gfx/buttons/collapse_thead.gif
h2
918.89300011098
957.82199990936
1215
207
200
image/gif
Image
https://www.documentingreality.com/forum/images/newskull.png
h2
919.0360000357
967.04100002535
5154
4150
200
image/png
Image
https://www.documentingreality.com/forum/gfx/misc/stats.gif
h2
919.20899995603
960.10900009423
2579
1569
200
image/gif
Image
https://www.documentingreality.com/clientscript/vbulletin_md5.js?v=387
h2
886.48899993859
949.82700003311
2868
5464
200
application/javascript
Script
https://www.documentingreality.com/forum/images/dot.gif
h2
919.28800009191
1001.3540000655
1066
62
200
image/gif
Image
https://static.cloudflareinsights.com/beacon.min.js/vaafb692b2aea4879b33c060e79fe94621666317369993
h2
919.35399989597
987.49099997804
6530
17031
200
text/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-N8CQWZ7
h2
919.50699989684
932.94199998491
47966
122175
200
application/javascript
Script
https://www.documentingreality.com/forum/gfx/misc/stripes2.png
h2
921.13299993798
989.99899998307
1098
98
200
image/png
Image
https://www.documentingreality.com/forum/gfx/misc/opt_header.jpg
h2
921.43499990925
976.18900006637
21345
20328
200
image/jpeg
Image
https://www.documentingreality.com/forum/gfx/misc/bg.png
h2
921.87700001523
959.46000004187
1224
217
200
image/png
Image
https://www.documentingreality.com/forum/gfx/misc/tile_sub3.gif
h2
922.13799990714
957.1710000746
1153
145
200
image/gif
Image
https://www.documentingreality.com/forum/gfx/misc/cat_back.gif
h2
922.54800000228
970.07300006226
1092
91
200
image/gif
Image
https://www.documentingreality.com/forum/gfx/misc/tile_sub2.gif
h2
922.72399994545
1012.9470000975
1152
146
200
image/gif
Image
https://www.documentingreality.com/forum/gfx/misc/tile_sub.gif
h2
922.85199998878
995.94100005925
1146
146
200
image/gif
Image
https://www.google-analytics.com/analytics.js
h2
1029.0180000011
1033.3269999828
20663
50230
200
text/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-6FFVCHQTKT&l=dataLayer&cx=c
h2
1030.4940000642
1053.3529999666
76865
217679
200
application/javascript
Script
https://www.documentingreality.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1669824000
h2
1039.4739999902
1078.2039999031
16955
39390
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=1048983611&t=pageview&_s=1&dl=https%3A%2F%2Fwww.documentingreality.com%2Fforum%2F&ul=en-us&de=UTF-8&dt=True%20Crime%20Pictures%20%26%20Videos%20Documented%20From%20The%20Real%20World.&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAEABAAAAACAAI~&jid=1054670636&gjid=1225605010&cid=1030201840.1669835213&tid=UA-197997-28&_gid=509361938.1669835213&_r=1&gtm=2wgbs0N8CQWZ7&z=529233814
h2
1071.5189999901
1077.0870000124
624
1
200
text/plain
XHR
https://www.documentingreality.com/cdn-cgi/challenge-platform/h/b/scripts/pica.js
h2
1095.6119999755
1227.0110000391
8710
19678
200
application/javascript
Other
https://region1.google-analytics.com/g/collect?v=2&tid=G-6FFVCHQTKT&gtm=2oebs0&_p=1048983611&cid=1030201840.1669835213&ul=en-us&sr=800x600&uaa=x86&uab=&uafvl=&uamb=0&uam=&uap=macOS&uapv=10.15.7&uaw=0&_s=1&sid=1669835212&sct=1&seg=0&dl=https%3A%2F%2Fwww.documentingreality.com%2Fforum%2F&dt=True%20Crime%20Pictures%20%26%20Videos%20Documented%20From%20The%20Real%20World.&en=page_view&_fv=1&_ss=1
1131.2710000202
1135.9129999764
0
0
-1
Ping
https://www.documentingreality.com/cdn-cgi/rum?
h2
1224.1360000335
1263.0610000342
351
0
204
text/plain
XHR
https://www.documentingreality.com/cdn-cgi/challenge-platform/h/b/cv/result/7725dcdca9002292
h2
2213.0859999452
2244.7830000892
1036
2
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)
802.956
14.392
863.419
13.155
877.095
5.801
920.359
9.815
931.651
6.792
938.453
7.551
953.607
22.711
976.331
13.964
995.364
6.553
1004.552
7.51
1015.013
5.139
1021.599
10.086
1032.13
8.349
1041.935
6.418
1054.483
18.435
1082.768
5.066
1096.453
37.371
1229.51
9.133
1816.395
397.946
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.

Metrics

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

Audits

Max Potential First Input Delay — 200 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.2 s
The time taken for the primary content of the page to be rendered.

Other

Avoid multiple page redirects — Potential savings of 680 ms
Redirects can cause additional delays before the page can begin loading. Documentingreality.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://documentingreality.com/
190
https://documentingreality.com/
150
http://www.documentingreality.com/
190
https://www.documentingreality.com/
150
https://www.documentingreality.com/forum/
0
Serve static assets with an efficient cache policy — 10 resources found
Documentingreality.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
20663
https://www.documentingreality.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1669824000
14400000
16955
https://static.cloudflareinsights.com/beacon.min.js/vaafb692b2aea4879b33c060e79fe94621666317369993
86400000
6530
https://www.documentingreality.com/forum/responsive.css
2678400000
8513
https://www.documentingreality.com/forum/clientscript/vbulletin_global.js?v=387
2678400000
8487
https://www.documentingreality.com/forum/clientscript/vbulletin_menu.js?v=387
2678400000
3422
https://www.documentingreality.com/clientscript/vbulletin_md5.js?v=387
2678400000
2868
https://www.documentingreality.com/forum/clientscript/vbptcr.js
2678400000
1260
https://www.documentingreality.com/clientscript/vbulletin_important.css?v=387
2678400000
1125
https://www.documentingreality.com/forum/responsive.js?v=0.1
2678400000
1078
Avoid an excessive DOM size — 1,009 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
1009
Maximum DOM Depth
18
Maximum Child Elements
118

Other

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
https://www.documentingreality.com/forum/gfx/buttons/collapse_thead.gif
https://www.documentingreality.com/forum/gfx/buttons/collapse_thead.gif
Registers an `unload` listener
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.
Source
78

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of documentingreality.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.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`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 alternate 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"]`
Documentingreality.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
KC

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
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.

Navigation

Some elements have 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.
Failing Elements

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that documentingreality.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.
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
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
YUI 2
2.9.0
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 — 2 insecure requests 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://documentingreality.com/
Allowed
http://www.documentingreality.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
https://www.documentingreality.com/forum/images/300-X-80.jpg
755 x 91 (8.30)
300 x 80 (3.75)
Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.documentingreality.com/forum/gfx/misc/tfooter.gif
761 x 8
1 x 8
761 x 8

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Audits

Uses deprecated APIs — 2 warnings found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
`window.webkitStorageInfo` is deprecated. Please use `navigator.webkitTemporaryStorage` or `navigator.webkitPersistentStorage` instead.
...
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for documentingreality.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 documentingreality.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

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

PWA

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

PWA Optimized

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

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register 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.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set 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
Manifest doesn't have 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) 61
Performance 43
Accessibility 80
Best Practices 50
SEO 91
PWA 40
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.documentingreality.com/forum/
Updated: 30th November, 2022

1.71 seconds
First Contentful Paint (FCP)
77%
16%
7%

0.02 seconds
First Input Delay (FID)
94%
3%
3%

43

Performance

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

Metrics

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Documentingreality.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Documentingreality.com should consider serving more appropriate-sized images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Documentingreality.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Documentingreality.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Documentingreality.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 77 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.googletagmanager.com/gtag/js?id=G-6FFVCHQTKT&l=dataLayer&cx=c
76861
31619
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
35030
23520
https://www.googletagmanager.com/gtm.js?id=GTM-N8CQWZ7
47986
23435
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.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Documentingreality.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
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.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 328 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=G-6FFVCHQTKT&l=dataLayer&cx=c
76861
https://www.googletagmanager.com/gtm.js?id=GTM-N8CQWZ7
47986
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
35030
https://www.google-analytics.com/analytics.js
20664
https://www.documentingreality.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1669824000
16773
https://www.documentingreality.com/forum/
15586
https://ajax.googleapis.com/ajax/libs/yui/2.9.0/build/yahoo-dom-event/yahoo-dom-event.js?v=387
14366
https://www.documentingreality.com/forum/images/dr_banner_2.jpg
13200
https://www.documentingreality.com/cdn-cgi/challenge-platform/h/b/scripts/pica.js
9387
https://www.documentingreality.com/forum/images/300-X-80.jpg
8656
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Documentingreality.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.
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 45 requests • 328 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
45
336181
Script
13
240872
Image
20
55203
Document
1
15586
Other
9
14875
Stylesheet
2
9645
Media
0
0
Font
0
0
Third-party
9
207601
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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 — 10 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.documentingreality.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1669824000
8400
948
https://www.googletagmanager.com/gtag/js?id=G-6FFVCHQTKT&l=dataLayer&cx=c
7016
259
https://www.documentingreality.com/clientscript/vbulletin_md5.js?v=387
5604
139
https://www.documentingreality.com/forum/
2550
132
https://www.google-analytics.com/analytics.js
6894
122
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
3912
99
https://ajax.googleapis.com/ajax/libs/yui/2.9.0/build/yahoo-dom-event/yahoo-dom-event.js?v=387
4238
84
https://www.googletagmanager.com/gtm.js?id=GTM-N8CQWZ7
5747
67
https://www.documentingreality.com/forum/
650
57
https://www.googletagmanager.com/gtm.js?id=GTM-N8CQWZ7
5552
52
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 documentingreality.com on mobile screens.

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.

Audits

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://documentingreality.com/
http/1.1
0
83.20300001651
815
0
301
text/plain
https://documentingreality.com/
http/1.1
83.654000074603
730.80899997149
889
0
301
text/html
http://www.documentingreality.com/
http/1.1
732.83200000878
787.84200001974
834
0
301
text/plain
https://www.documentingreality.com/
http/1.1
791.28500004299
1490.1770000579
939
0
301
text/html
https://www.documentingreality.com/forum/
h2
1491.8380000163
2538.5470000328
15586
78539
200
text/html
Document
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
h2
2558.6850000545
2564.7159999935
35030
97163
200
text/javascript
Script
https://www.documentingreality.com/forum/images/Logo-480-3.webp
h2
2558.9460000629
2632.961000083
6369
5460
200
image/webp
Image
https://ajax.googleapis.com/ajax/libs/yui/2.9.0/build/yahoo-dom-event/yahoo-dom-event.js?v=387
h2
2559.1320000822
2565.8640000038
14366
37510
200
text/javascript
Script
https://ajax.googleapis.com/ajax/libs/yui/2.9.0/build/connection/connection-min.js?v=387
h2
2559.4630000414
2565.3569999849
5540
13257
200
text/javascript
Script
https://www.documentingreality.com/forum/clientscript/vbulletin_global.js?v=387
h2
2559.9710000679
2621.1449999828
8491
23479
200
application/javascript
Script
https://www.documentingreality.com/forum/clientscript/vbulletin_menu.js?v=387
h2
2560.4080000194
2625.7479999913
3422
8730
200
application/javascript
Script
https://www.documentingreality.com/clientscript/vbulletin_important.css?v=387
h2
2561.0840000445
2670.1009999961
1125
404
200
text/css
Stylesheet
https://www.documentingreality.com/forum/responsive.css
h2
2561.6170000285
2631.4390000189
8520
35629
200
text/css
Stylesheet
https://www.documentingreality.com/forum/clientscript/vbptcr.js
h2
2561.9319999823
2610.7460000785
1257
790
200
application/javascript
Script
https://www.documentingreality.com/forum/responsive.js?v=0.1
h2
2674.5560000418
2739.091000054
1076
334
200
application/javascript
Script
https://www.documentingreality.com/forum/gfx/misc/navbits_start.gif
h2
2715.262999991
2769.9470000807
1222
215
200
image/gif
Image
https://www.documentingreality.com/forum/images/dr_banner_2.jpg
h2
2715.530000045
2758.7550000753
13200
12181
200
image/jpeg
Image
https://www.documentingreality.com/forum/images/300-X-80.jpg
h2
2715.7280000392
2789.4540000707
8656
7643
200
image/jpeg
Image
https://www.documentingreality.com/forum/gfx/buttons/collapse_tcat.gif
h2
2715.9260000335
2774.5369999902
1181
174
200
image/gif
Image
https://www.documentingreality.com/forum/gfx/misc/tGFX.gif
h2
2716.2050000625
2778.7680000765
1345
345
200
image/gif
Image
https://www.documentingreality.com/forum/gfx/misc/tlastpost.png
h2
2716.3779999828
2783.4150000708
1330
328
200
image/png
Image
https://www.documentingreality.com/forum/gfx/misc/tthreads.png
h2
2716.5629999945
2774.0880000638
1412
406
200
image/png
Image
https://www.documentingreality.com/forum/gfx/misc/tposts.png
h2
2716.8580000289
2772.4190000445
1390
379
200
image/png
Image
https://www.documentingreality.com/forum/gfx/statusicon/forum_old.gif
h2
2717.1589999925
2811.1860000063
2296
1291
200
image/gif
Image
https://www.documentingreality.com/forum/gfx/misc/tfooter.gif
h2
2717.5259999931
2768.4170000721
1056
57
200
image/gif
Image
https://www.documentingreality.com/forum/gfx/buttons/collapse_thead.gif
h2
2717.684000032
2803.978000069
1216
207
200
image/gif
Image
https://www.documentingreality.com/forum/images/newskull.png
h2
2717.9509999696
2781.0659999959
5159
4150
200
image/png
Image
https://www.documentingreality.com/forum/gfx/misc/stats.gif
h2
2718.1480000727
2759.7790000727
2573
1569
200
image/gif
Image
https://www.documentingreality.com/clientscript/vbulletin_md5.js?v=387
h2
2634.4769999851
2688.804000034
2876
5464
200
application/javascript
Script
https://www.documentingreality.com/forum/images/dot.gif
h2
2718.6820000643
2776.7590000294
1072
62
200
image/gif
Image
https://static.cloudflareinsights.com/beacon.min.js/vaafb692b2aea4879b33c060e79fe94621666317369993
h2
2719.0239999909
2805.7280000066
6530
17031
200
text/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-N8CQWZ7
h2
2719.3220000481
2733.9800000191
47986
122173
200
application/javascript
Script
https://www.documentingreality.com/forum/gfx/misc/stripes2.png
h2
2722.127999994
2775.4160000477
1103
98
200
image/png
Image
https://www.documentingreality.com/forum/gfx/misc/bg.png
h2
2722.6810000138
2779.1640000651
1222
217
200
image/png
Image
https://www.documentingreality.com/forum/images/nav-click.png
h2
2723.3530000085
2754.3719999958
1103
107
200
image/png
Image
https://www.documentingreality.com/forum/gfx/misc/tile_sub2.gif
h2
2726.5860000625
2811.6370000644
1152
146
200
image/gif
Image
https://www.documentingreality.com/forum/gfx/misc/tile_sub.gif
h2
2726.9540000707
2771.1930000223
1146
146
200
image/gif
Image
https://www.documentingreality.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1669824000
h2
2897.2960000392
2931.0040000128
16773
38768
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
2914.3920000643
2918.718000059
20664
50230
200
text/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-6FFVCHQTKT&l=dataLayer&cx=c
h2
2916.3059999701
2932.3929999955
76861
217660
200
application/javascript
Script
https://www.documentingreality.com/cdn-cgi/rum?
h2
2928.2469999744
2950.3040000563
351
0
204
text/plain
XHR
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=1275119264&t=pageview&_s=1&dl=https%3A%2F%2Fwww.documentingreality.com%2Fforum%2F&ul=en-us&de=UTF-8&dt=True%20Crime%20Pictures%20%26%20Videos%20Documented%20From%20The%20Real%20World.&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAEABAAAAACAAI~&jid=1464338636&gjid=774200170&cid=1763647912.1669835238&tid=UA-197997-28&_gid=1970064927.1669835239&_r=1&gtm=2wgbs0N8CQWZ7&z=167423850
h2
2965.9039999824
2970.2430000762
624
1
200
text/plain
XHR
https://www.google-analytics.com/g/collect?v=2&tid=G-6FFVCHQTKT&gtm=2oebs0&_p=1275119264&cid=1763647912.1669835238&ul=en-us&sr=360x640&uaa=&uab=&uafvl=&uamb=1&uam=Moto%20G4&uap=Android&uapv=6.0&uaw=0&_s=1&sid=1669835238&sct=1&seg=0&dl=https%3A%2F%2Fwww.documentingreality.com%2Fforum%2F&dt=True%20Crime%20Pictures%20%26%20Videos%20Documented%20From%20The%20Real%20World.&en=page_view&_fv=1&_ss=1
3037.3560000444
3042.2549999785
0
0
-1
Ping
https://www.documentingreality.com/cdn-cgi/challenge-platform/h/b/scripts/pica.js
h2
3045.3660000348
3065.0509999832
9387
21832
200
application/javascript
Other
https://www.documentingreality.com/cdn-cgi/challenge-platform/h/b/cv/result/7725dd77cf5208b6
h2
3867.0850000344
3923.8980000373
1036
2
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)
2546.13
32.94
2675.182
24.851
2700.868
21.03
2721.919
16.038
2739.935
10.77
2753.989
69.606
2824.327
14.29
2858.207
12.004
2870.545
13.109
2886.473
13.154
2902.234
16.628
2924.332
6.029
2937.946
30.507
2977.351
64.702
3395.063
474.244
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.

Other

Defer offscreen images — Potential savings of 16 KiB
Time to Interactive can be slowed down by resources on the page. Documentingreality.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.documentingreality.com/forum/images/dr_banner_2.jpg
12181
12181
https://www.documentingreality.com/forum/images/newskull.png
4150
4150
Serve static assets with an efficient cache policy — 10 resources found
Documentingreality.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
20664
https://www.documentingreality.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1669824000
14400000
16773
https://static.cloudflareinsights.com/beacon.min.js/vaafb692b2aea4879b33c060e79fe94621666317369993
86400000
6530
https://www.documentingreality.com/forum/responsive.css
2678400000
8520
https://www.documentingreality.com/forum/clientscript/vbulletin_global.js?v=387
2678400000
8491
https://www.documentingreality.com/forum/clientscript/vbulletin_menu.js?v=387
2678400000
3422
https://www.documentingreality.com/clientscript/vbulletin_md5.js?v=387
2678400000
2876
https://www.documentingreality.com/forum/clientscript/vbptcr.js
2678400000
1257
https://www.documentingreality.com/clientscript/vbulletin_important.css?v=387
2678400000
1125
https://www.documentingreality.com/forum/responsive.js?v=0.1
2678400000
1076
Avoid an excessive DOM size — 1,007 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
1007
Maximum DOM Depth
18
Maximum Child Elements
117
Reduce JavaScript execution time — 2.7 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.documentingreality.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1669824000
1926.068
1851.18
9.908
https://www.documentingreality.com/forum/
743.28
94.228
22.384
https://www.googletagmanager.com/gtag/js?id=G-6FFVCHQTKT&l=dataLayer&cx=c
267.02
245.236
20.012
Unattributable
228.796
11.564
0
https://www.google-analytics.com/analytics.js
127.552
116.62
5.976
https://www.googletagmanager.com/gtm.js?id=GTM-N8CQWZ7
126.296
114.66
10.052
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
119.74
102.708
8.616
https://static.cloudflareinsights.com/beacon.min.js/vaafb692b2aea4879b33c060e79fe94621666317369993
57.936
48.96
1.616
Minimize main-thread work — 3.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
2618.076
Other
384.6
Style & Layout
243.696
Parse HTML & CSS
146.876
Rendering
115.964
Script Parsing & Compilation
88.62
Garbage Collection
53.628

Metrics

First Contentful Paint — 3.9 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 7.8 s
The time taken for the page to become fully interactive.
Speed Index — 7.5 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 1,150 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).
Largest Contentful Paint — 4.1 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 950 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 4.0 s
The time taken for the primary content of the page to be rendered.

Other

Reduce initial server response time — Root document took 1,050 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.documentingreality.com/forum/
1047.695
Avoid multiple page redirects — Potential savings of 2,220 ms
Redirects can cause additional delays before the page can begin loading. Documentingreality.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://documentingreality.com/
630
https://documentingreality.com/
480
http://www.documentingreality.com/
630
https://www.documentingreality.com/
480
https://www.documentingreality.com/forum/
0
Reduce the impact of third-party code — Third-party code blocked the main thread for 300 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)
124847
200.012
21288
62.552
54936
32.9
6530
0
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
https://www.documentingreality.com/forum/gfx/buttons/collapse_thead.gif
https://www.documentingreality.com/forum/gfx/buttons/collapse_thead.gif
Registers an `unload` listener
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.
Source
First Contentful Paint (3G) — 7596 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
80

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of documentingreality.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.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`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 alternate 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.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

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"]`
Documentingreality.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
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.

Navigation

Some elements have 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.
Failing Elements

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that documentingreality.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.
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
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
YUI 2
2.9.0
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 — 2 insecure requests 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://documentingreality.com/
Allowed
http://www.documentingreality.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
https://www.documentingreality.com/forum/images/300-X-80.jpg
318 x 91 (3.49)
300 x 80 (3.75)
Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.documentingreality.com/forum/images/300-X-80.jpg
318 x 91
300 x 80
636 x 182
https://www.documentingreality.com/forum/images/Logo-480-3.webp
356 x 72
480 x 97
712 x 144
https://www.documentingreality.com/forum/gfx/statusicon/forum_old.gif
44 x 43
44 x 43
88 x 86
https://www.documentingreality.com/forum/gfx/misc/tGFX.gif
29 x 30
29 x 30
58 x 60
https://www.documentingreality.com/forum/gfx/buttons/collapse_tcat.gif
15 x 15
15 x 15
30 x 30
https://www.documentingreality.com/forum/gfx/misc/navbits_start.gif
15 x 15
15 x 15
30 x 30

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Audits

Uses deprecated APIs — 2 warnings found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
`window.webkitStorageInfo` is deprecated. Please use `navigator.webkitTemporaryStorage` or `navigator.webkitPersistentStorage` instead.
...
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for documentingreality.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 documentingreality.com on mobile screens.
Document uses legible font sizes — 95.68% 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
body
1.24%
11px
.tcat
1.22%
11px
.thead
0.68%
10px
center
0.39%
10px
.login-form
0.17%
10.6667px
.thead3
0.07%
10px
0.54%
< 12px
95.68%
≥ 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.
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.

Mobile Friendly

Tap targets are not sized appropriately — 82% 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
15x15
189x13
137x20
137x20
137x20
137x20
212x25

Content Best Practices

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

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

PWA

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

PWA Optimized

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

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register 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.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set 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
Manifest doesn't have 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: 104.26.0.36
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: BG
City: wafangdian
State: District of Columbia
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy.com, LLC 23.13.154.6
Security

Visitor Safety

Mature Content: Yes
McAfee WebAdvisor Rating: Slightly Risky
WOT Rating:
WOT Trustworthiness: 84/100
WOT Child Safety: 9/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: documentingreality.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 10th May, 2022
Valid To: 10th May, 2023
Subject: CN = documentingreality.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: 84f4be5c
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 3301827281004295205321975655023187545
Serial Number (Hex): 027BE8A7530D6E4568E0E247816F1659
Valid From: 10th May, 2024
Valid To: 10th May, 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 : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : May 10 02:28:38.442 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:65:15:1E:54:65:28:4A:46:3D:8C:94:71:
47:9E:9A:5A:A8:73:0D:21:9E:46:00:CD:2F:37:B8:32:
AE:05:63:9C:02:21:00:E9:95:51:55:1C:85:5A:EB:5E:
76:75:4A:FB:6E:2B:72:34:5F:09:CB:62:F6:92:8C:EE:
17:10:8A:A9:A6:66:A7
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : May 10 02:28:38.428 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:EF:08:2E:E6:0A:16:3D:09:8A:26:AF:
7B:4D:FD:30:AA:0B:6B:16:CA:94:30:DF:BA:43:81:5F:
30:1D:92:B3:86:02:21:00:B6:FB:2E:A7:87:9A:CB:B4:
9B:9D:53:BF:7C:38:AA:26:1D:0D:70:5A:0A:C0:CE:79:
7E:9D:1C:5A:05:BB:7E:04
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B3:73:77:07:E1:84:50:F8:63:86:D6:05:A9:DC:11:09:
4A:79:2D:B1:67:0C:0B:87:DC:F0:03:0E:79:36:A5:9A
Timestamp : May 10 02:28:38.458 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:85:4F:FA:22:26:90:FF:43:C5:79:34:
5D:0B:0F:9D:67:FA:55:44:58:09:FE:59:AA:B8:91:C2:
BE:00:3E:18:0C:02:20:51:95:94:4C:22:1C:ED:65:4F:
10:75:87:D4:DD:AC:25:F4:83:55:92:FC:39:4F:62:92:
78:C9:B9:68:DB:37:1F
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.documentingreality.com
DNS:documentingreality.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 403 Forbidden
Date: 30th November, 2022
Content-Type: text/plain; charset=UTF-8
Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: 1st January, 1970
Server: cloudflare
Content-Length: 16
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
Referrer-Policy: same-origin
Server-Timing: cf-q-config;dur=6.0000002122251e-06
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=8FYFSQl791zAZCE8ua31SFFpQoPhSNPIku7lqhI57DGwIEgsjh3%2BzNh5vCJDk5oojiZ9zmbRw%2FSe%2Fe5TJo2P31sk0e1yeP1oSJV0qZ%2FBw%2FSnGFH5J7hhkKaqdhe%2BzVqKAG2wOO146IU%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
X-Content-Type-Options: nosniff
CF-RAY: 7725dcb91b3b061f-IAD
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 4th August, 2008
Changed: 23rd May, 2020
Expires: 4th August, 2025
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: eric.ns.cloudflare.com
lisa.ns.cloudflare.com
Owner Name: Registration Private
Owner Organization: Domains By Proxy, LLC
Owner Street: DomainsByProxy.com
2155 E Warner Rd
Owner Post Code: 85284
Owner City: Tempe
Owner State: Arizona
Owner Country: US
Owner Phone: +1.4806242599
Owner Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=DOCUMENTINGREALITY.COM
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
2155 E Warner Rd
Admin Post Code: 85284
Admin City: Tempe
Admin State: Arizona
Admin Country: US
Admin Phone: +1.4806242599
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=DOCUMENTINGREALITY.COM
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
2155 E Warner Rd
Tech Post Code: 85284
Tech City: Tempe
Tech State: Arizona
Tech Country: US
Tech Phone: +1.4806242599
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=DOCUMENTINGREALITY.COM
Full Whois: Domain Name: DOCUMENTINGREALITY.COM
Registry Domain ID: 1512101092_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2020-05-23T16:27:34Z
Creation Date: 2008-08-04T19:46:24Z
Registrar Registration Expiration Date: 2025-08-04T19:46:24Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 2155 E Warner Rd
Registrant City: Tempe
Registrant State/Province: Arizona
Registrant Postal Code: 85284
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: +1.4806242598
Registrant Fax Ext:
Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=DOCUMENTINGREALITY.COM
Registry Admin ID: Not Available From Registry
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin Street: 2155 E Warner Rd
Admin City: Tempe
Admin State/Province: Arizona
Admin Postal Code: 85284
Admin Country: US
Admin Phone: +1.4806242599
Admin Phone Ext:
Admin Fax: +1.4806242598
Admin Fax Ext:
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=DOCUMENTINGREALITY.COM
Registry Tech ID: Not Available From Registry
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 2155 E Warner Rd
Tech City: Tempe
Tech State/Province: Arizona
Tech Postal Code: 85284
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: +1.4806242598
Tech Fax Ext:
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=DOCUMENTINGREALITY.COM
Name Server: ERIC.NS.CLOUDFLARE.COM
Name Server: LISA.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-11-30T19:06:48Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

Nameservers

Name IP Address
eric.ns.cloudflare.com 172.64.33.112
lisa.ns.cloudflare.com 173.245.58.131
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
$15,337 USD 2/5
$994 USD 2/5