xforum.live

xforum.live is SSL secured

Free website and domain report on xforum.live

Last Updated: 14th October, 2023 Update Now
Overview

Snoop Summary for xforum.live

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

About xforum.live

Site Preview:
Title: XForum
Description: A Desi Forum
Keywords and Tags: adult content, adult pic forum, bade ghar ki bahu betiyan story, bulletin boards, desi girls forum, desi nude forum, desibees hindi stories, forum, main meri family aur mera gaon, popular, xforum live, xforum videos, xossip english, xossip stories
Related Terms:
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

3/5 (Great!)

Valuation

$123,994 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 21,656
Alexa Reach:
SEMrush Rank (US): 1,104,096
SEMrush Authority Score: 48
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 2,614 0
Traffic: 749 0
Cost: $0 USD $0 USD
Traffic

Visitors

Daily Visitors: 40,162
Monthly Visitors: 1,222,405
Yearly Visitors: 14,659,130
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $170 USD
Monthly Revenue: $5,169 USD
Yearly Revenue: $61,992 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 1,561
Referring Domains: 173
Referring IPs: 140
Xforum.live has 1,561 backlinks according to SEMrush. 39% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve xforum.live's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of xforum.live's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://yumstories.com/index.php?topic=63550.72
Target: https://xforum.live/threads/family-novel.12617/

2
Source: https://yumstories.com/index.php?topic=61822.80
Target: https://xforum.live/threads/collection-of-some-pdf-stories.529/post-46650

3
Source: https://urimagegallery.com/adultery-masti-jindagi-ki-story-of-a-watchman-page-3-xforum.html
Target: https://xforum.live/uploads/smilies/perfect10.gif

4
Source: https://thesexlist.com/xforum-live/
Target: https://xforum.live/

5
Source: https://desipornlist.com/xforum-live/
Target: https://xforum.live/

Top Ranking Keywords (US)

1
Keyword: xforum live
Ranked Page: https://xforum.live/

2
Keyword: xforum videos
Ranked Page: https://xforum.live/forums/videos/

3
Keyword: desi nude forum
Ranked Page: https://xforum.live/forums/pics-adult.22/

4
Keyword: desibees hindi stories
Ranked Page: https://xforum.live/threads/completed-hindi-stories-list.211/

5
Keyword: main meri family aur mera gaon
Ranked Page: https://xforum.live/threads/main-meri-family-or-mera-gaon-avi.190/

Domain Analysis

Value Length
Domain: xforum.live 11
Domain Name: xforum 6
Extension (TLD): live 4

Page Speed Analysis

Average Load Time: 1.81 seconds
Load Time Comparison: Faster than 49% of sites

PageSpeed Insights

Avg. (All Categories) 89
Performance 95
Accessibility 96
Best Practices 75
SEO 92
PWA 89
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://xforum.live/
Updated: 31st January, 2023

1.83 seconds
First Contentful Paint (FCP)
77%
15%
8%

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

95

Performance

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

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 2.4 s
The time taken for the page to become fully interactive.
Total Blocking Time — 50 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 — 1.2 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
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://xforum.live/
http/1.1
0
166.05300002266
759
0
301
text/html
https://xforum.live/
h2
166.43300000578
496.08800001442
17122
85177
200
text/html
Document
https://fonts.googleapis.com/css2?family=Lobster&display=swap
h2
504.93200001074
511.69399998616
1181
1701
200
text/css
Stylesheet
https://fonts.googleapis.com/css2?family=EB+Garamond&display=swap
h2
505.13300002785
512.45099998778
1248
2421
200
text/css
Stylesheet
https://fonts.googleapis.com/css2?family=Caveat&family=Pacifico&display=swap
h2
505.3959999932
512.13099999586
1290
3130
200
text/css
Stylesheet
https://xforum.live/styles/fonts/fa/fa-light-300.woff2?_v=5.15.3
h2
505.73400000576
838.05800002301
184930
184144
200
font/woff2
Font
https://xforum.live/styles/fonts/fa/fa-solid-900.woff2?_v=5.15.3
h2
506.00699998904
827.83500000369
137610
136824
200
font/woff2
Font
https://xforum.live/styles/fonts/fa/fa-brands-400.woff2?_v=5.15.3
h2
506.32400001632
816.30100001348
77527
76740
200
font/woff2
Font
https://xforum.live/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=19&l=1&d=1675008636&k=fe537a0ccd3ce0e6910e30eca1f8726b9bf010f9
h2
506.58500002464
817.38399999449
66017
396823
200
text/css
Stylesheet
https://xforum.live/css.php?css=public%3Anode_list.less%2Cpublic%3Anotices.less%2Cpublic%3Axb.less%2Cpublic%3Aextra.less&s=19&l=1&d=1675008636&k=73e37b648fb614ffaacfe4c1c8f5d8ddb808ca7d
h2
506.70500000706
666.05900001014
11231
57351
200
text/css
Stylesheet
https://xforum.live/js/xf/preamble.min.js?_v=77adaac3
h2
506.77799998084
633.36899998831
2289
3159
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-129146910-1
h2
874.21300000278
888.42199998908
45658
115776
200
application/javascript
Script
https://fonts.googleapis.com/css2?family=Caveat|EB+Garamond|Lobster
506.38099998469
519.40400002059
0
0
-1
Stylesheet
https://xforum.live/uploads/images/xfnew.png
h2
874.88700001268
1030.0760000246
4232
3453
200
image/png
Image
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
h2
831.16300002439
837.04000001308
31984
89476
200
text/javascript
Script
https://xforum.live/js/vendor/vendor-compiled.js?_v=77adaac3
h2
859.73899997771
1011.5089999745
13979
43704
200
application/javascript
Script
https://xforum.live/js/xf/core-compiled.js?_v=77adaac3
h2
873.64499998512
1071.6869999887
62884
211632
200
application/javascript
Script
https://xforum.live/js/xf/notice.min.js?_v=77adaac3
h2
873.86499997228
941.75900000846
2106
3108
200
application/javascript
Script
https://xforum.live/js/SvgAdblockDetected/advertising.js?_v=77adaac3
h2
874.07700001495
940.46800001524
836
19
200
application/javascript
Script
https://xforum.live/styles/SvgAdblockDetected/img/block.png
h2
875.652000017
1134.1290000128
62745
61964
200
image/png
Image
https://static.cloudflareinsights.com/beacon.min.js/vaafb692b2aea4879b33c060e79fe94621666317369993
h2
875.77500002226
928.20899997605
6530
17031
200
text/javascript
Script
https://fonts.googleapis.com/css2?family=Caveat|EB+Garamond|Lobster
872.84500000533
885.41300001089
0
0
-1
Stylesheet
https://xforum.live/styles/flatawesome/xenforo/bodybg.png
h2
899.6460000053
1009.6650000196
29860
29075
200
image/png
Image
https://xforum.live/data/assets/style_properties/block-header.png
h2
902.70400000736
1057.9349999898
1178
645
404
text/html
Image
https://xforum.live/data/avatars/l/84/84519.jpg?1672577627
h2
1050.0079999911
1404.022999981
1310414
1309626
200
image/jpeg
Image
https://xforum.live/data/avatars/l/20/20643.jpg?1593277190
h2
1050.3090000129
1113.6069999775
8119
7336
200
image/jpeg
Image
https://xforum.live/data/avatars/l/117/117178.jpg?1643363090
h2
1050.5869999761
1118.432999996
1611
794
200
image/jpeg
Image
https://xforum.live/data/avatars/l/42/42812.jpg?1601792658
h2
1050.8389999741
1124.2820000043
2124
1342
200
image/jpeg
Image
https://xforum.live/data/avatars/l/168/168937.jpg?1674110856
h2
1051.22199998
1276.1559999781
1928
1138
200
image/jpeg
Image
https://xforum.live/data/avatars/l/164/164940.jpg?1671877339
h2
1051.5790000209
1119.5319999824
6990
6209
200
image/jpeg
Image
https://xforum.live/data/avatars/l/48/48374.jpg?1614703782
h2
1051.8530000118
1123.8829999929
55006
54222
200
image/jpeg
Image
https://xforum.live/data/avatars/l/21/21720.jpg?1599825310
h2
1052.0699999761
1122.4909999873
11223
10443
200
image/jpeg
Image
https://xforum.live/data/avatars/s/34/34370.jpg?1616279417
h2
1052.90900002
1130.7900000247
1840
1062
200
image/jpeg
Image
https://xforum.live/data/avatars/s/168/168561.jpg?1674027156
h2
1053.974999988
1117.3410000047
2641
1857
200
image/jpeg
Image
https://www.googletagmanager.com/gtag/js?id=G-643TECKK0C&l=dataLayer&cx=c
h2
1096.0039999918
1119.1059999983
78468
222915
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
1100.7349999854
1106.3469999935
20594
50234
200
text/javascript
Script
https://xforum.live/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1675195200
h2
1143.4630000149
1166.7400000151
18423
44131
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j99&aip=1&a=1953838400&t=pageview&_s=1&dl=https%3A%2F%2Fxforum.live%2F&ul=en-us&de=UTF-8&dt=XForum&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAACAAI~&jid=1678686935&gjid=879271240&cid=756573414.1675197757&tid=UA-129146910-1&_gid=2045740486.1675197757&_r=1&_slc=1&gtm=2ou1p0&z=321821606
h2
1295.3519999865
1299.8769999831
496
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j99&tid=UA-129146910-1&cid=756573414.1675197757&jid=1678686935&gjid=879271240&_gid=2045740486.1675197757&_u=YEBAAUAAAAAAACAAI~&z=82751913
h2
1333.152999985
1337.2780000209
566
1
200
text/plain
XHR
https://www.google-analytics.com/g/collect?v=2&tid=G-643TECKK0C&gtm=2oe1p0&_p=1953838400&cid=756573414.1675197757&ul=en-us&sr=800x600&uaW=1&uaa=x86&uab=&uafvl=&uamb=0&uam=&uap=macOS&uapv=10.15.7&uaw=0&_s=1&sid=1675197756&sct=1&seg=0&dl=https%3A%2F%2Fxforum.live%2F&dt=XForum&en=page_view&_fv=1&_ss=1
1342.003000027
1352.3079999723
0
0
-1
Ping
https://xforum.live/cdn-cgi/rum?
h2
1357.1099999826
1370.5329999793
336
0
204
text/plain
XHR
https://xforum.live/cdn-cgi/challenge-platform/h/g/scripts/pica.js
h2
1359.3129999936
1376.3509999844
8668
19764
200
application/javascript
Other
https://xforum.live/cdn-cgi/challenge-platform/h/g/cv/result/792546540cc8eb8f
h2
2057.4350000243
2096.3500000071
927
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)
500.906
13.576
819.91
11.416
832.347
27.045
860.161
13.179
887.048
12.056
899.121
154.894
1062.612
11.656
1082.01
8.476
1090.54
11.504
1102.742
13.988
1119.24
11.204
1139.275
5.549
1147.803
12.394
1163.394
91.784
1256.572
11.241
1268.973
7.342
1276.652
20.408
1297.113
33.099
1333.357
10.867
1755.898
303.274
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

Eliminate render-blocking resources — Potential savings of 70 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Xforum.live should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css2?family=Lobster&display=swap
1181
230
https://fonts.googleapis.com/css2?family=EB+Garamond&display=swap
1248
230
https://xforum.live/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=19&l=1&d=1675008636&k=fe537a0ccd3ce0e6910e30eca1f8726b9bf010f9
66017
200
Properly size images — Potential savings of 30 KiB
Images can slow down the page's load time. Xforum.live should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://xforum.live/data/avatars/l/48/48374.jpg?1614703782
54222
25393
https://xforum.live/data/avatars/l/21/21720.jpg?1599825310
10443
4891
Defer offscreen images — Potential savings of 61 KiB
Time to Interactive can be slowed down by resources on the page. Xforum.live should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://xforum.live/styles/SvgAdblockDetected/img/block.png
61964
61964
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Xforum.live should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Xforum.live should consider minifying JS files.
Reduce unused CSS — Potential savings of 61 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Xforum.live should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://xforum.live/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=19&l=1&d=1675008636&k=fe537a0ccd3ce0e6910e30eca1f8726b9bf010f9
66017
62810
Reduce unused JavaScript — Potential savings of 95 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://xforum.live/js/xf/core-compiled.js?_v=77adaac3
62884
45703
https://www.googletagmanager.com/gtag/js?id=G-643TECKK0C&l=dataLayer&cx=c
78468
30765
https://www.googletagmanager.com/gtag/js?id=UA-129146910-1
45658
21032
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 330 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://xforum.live/
330.641
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Xforum.live should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://xforum.live/
190
https://xforum.live/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Xforum.live 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 2,240 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://xforum.live/data/avatars/l/84/84519.jpg?1672577627
1310414
https://xforum.live/styles/fonts/fa/fa-light-300.woff2?_v=5.15.3
184930
https://xforum.live/styles/fonts/fa/fa-solid-900.woff2?_v=5.15.3
137610
https://www.googletagmanager.com/gtag/js?id=G-643TECKK0C&l=dataLayer&cx=c
78468
https://xforum.live/styles/fonts/fa/fa-brands-400.woff2?_v=5.15.3
77527
https://xforum.live/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=19&l=1&d=1675008636&k=fe537a0ccd3ce0e6910e30eca1f8726b9bf010f9
66017
https://xforum.live/js/xf/core-compiled.js?_v=77adaac3
62884
https://xforum.live/styles/SvgAdblockDetected/img/block.png
62745
https://xforum.live/data/avatars/l/48/48374.jpg?1614703782
55006
https://www.googletagmanager.com/gtag/js?id=UA-129146910-1
45658
Avoid chaining critical requests — 13 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Xforum.live 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://xforum.live/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1675195200
306.82
287.48
1.967
https://xforum.live/
238.224
11.881
3.698
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
106.349
100.618
1.697
Unattributable
83.096
16.243
0
Minimizes main-thread work — 0.9 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
511.201
Style & Layout
168.749
Other
91.027
Rendering
50.595
Parse HTML & CSS
23.038
Garbage Collection
22.427
Script Parsing & Compilation
20.232
Keep request counts low and transfer sizes small — 43 requests • 2,240 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
43
2293570
Image
14
1499911
Font
3
400067
Script
11
283751
Stylesheet
7
80967
Document
1
17122
Other
7
11752
Media
0
0
Third-party
13
188015
Minimize third-party usage — Third-party code blocked the main thread for 40 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)
31984
37.772
124126
0
21090
0
6530
0
3719
0
566
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.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00082288219070134
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 — 2 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://xforum.live/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1675195200
2820
152
https://xforum.live/
394
77
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 xforum.live on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Metrics

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

Audits

Max Potential First Input Delay — 150 ms
Users could experience a delay when interacting with the page.

Other

Avoid an excessive DOM size — 1,204 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
1204
Maximum DOM Depth
23
Maximum Child Elements
50

Other

Efficiently encode images — Potential savings of 1,306 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://xforum.live/data/avatars/l/84/84519.jpg?1672577627
1309626
1292250
https://xforum.live/data/avatars/l/48/48374.jpg?1614703782
54222
45285
Serve images in next-gen formats — Potential savings of 1,375 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://xforum.live/data/avatars/l/84/84519.jpg?1672577627
1309626
1300825.2
https://xforum.live/data/avatars/l/48/48374.jpg?1614703782
54222
50250.15
https://xforum.live/styles/SvgAdblockDetected/img/block.png
61964
39495.75
https://xforum.live/styles/flatawesome/xenforo/bodybg.png
29075
17409.8
Serve static assets with an efficient cache policy — 24 resources found
Xforum.live 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://xforum.live/data/avatars/l/84/84519.jpg?1672577627
0
1310414
https://xforum.live/styles/fonts/fa/fa-light-300.woff2?_v=5.15.3
0
184930
https://xforum.live/styles/fonts/fa/fa-solid-900.woff2?_v=5.15.3
0
137610
https://xforum.live/styles/fonts/fa/fa-brands-400.woff2?_v=5.15.3
0
77527
https://xforum.live/js/xf/core-compiled.js?_v=77adaac3
0
62884
https://xforum.live/styles/SvgAdblockDetected/img/block.png
0
62745
https://xforum.live/data/avatars/l/48/48374.jpg?1614703782
0
55006
https://xforum.live/styles/flatawesome/xenforo/bodybg.png
0
29860
https://xforum.live/js/vendor/vendor-compiled.js?_v=77adaac3
0
13979
https://xforum.live/data/avatars/l/21/21720.jpg?1599825310
0
11223
https://xforum.live/data/avatars/l/20/20643.jpg?1593277190
0
8119
https://xforum.live/data/avatars/l/164/164940.jpg?1671877339
0
6990
https://xforum.live/uploads/images/xfnew.png
0
4232
https://xforum.live/data/avatars/s/168/168561.jpg?1674027156
0
2641
https://xforum.live/js/xf/preamble.min.js?_v=77adaac3
0
2289
https://xforum.live/data/avatars/l/42/42812.jpg?1601792658
0
2124
https://xforum.live/js/xf/notice.min.js?_v=77adaac3
0
2106
https://xforum.live/data/avatars/l/168/168937.jpg?1674110856
0
1928
https://xforum.live/data/avatars/s/34/34370.jpg?1616279417
0
1840
https://xforum.live/data/avatars/l/117/117178.jpg?1643363090
0
1611
https://xforum.live/js/SvgAdblockDetected/advertising.js?_v=77adaac3
0
836
https://www.google-analytics.com/analytics.js
7200000
20594
https://xforum.live/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1675195200
14400000
18423
https://static.cloudflareinsights.com/beacon.min.js/vaafb692b2aea4879b33c060e79fe94621666317369993
86400000
6530
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://xforum.live/styles/fonts/fa/fa-light-300.woff2?_v=5.15.3
332.32400001725
https://xforum.live/styles/fonts/fa/fa-solid-900.woff2?_v=5.15.3
321.82800001465
https://xforum.live/styles/fonts/fa/fa-brands-400.woff2?_v=5.15.3
309.97699999716
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://xforum.live/uploads/images/xfnew.png
96

Accessibility

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

Navigation

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

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links 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.
`<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"]`
Xforum.live may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`[aria-hidden="true"]` elements contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
Failing Elements

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

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
Mustache
2.2.1
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://xforum.live/
Allowed

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.
...
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: the server responded with a status of 404 (Not Found)
Refused to apply style from 'https://fonts.googleapis.com/css2?family=Caveat|EB+Garamond|Lobster' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
Refused to apply style from 'https://fonts.googleapis.com/css2?family=Caveat|EB+Garamond|Lobster' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
Refused to apply style from 'https://fonts.googleapis.com/css2?family=Caveat|EB+Garamond|Lobster' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for xforum.live. 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 xforum.live 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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

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

Crawling and Indexing

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

Manual Checks

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

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 xforum.live. This includes details about web app manifests.

Installable

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

PWA Optimized

Registers a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xforum.live 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.

PWA Optimized

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) 78
Performance 41
Accessibility 96
Best Practices 75
SEO 89
PWA 90
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://xforum.live/
Updated: 31st January, 2023

1.90 seconds
First Contentful Paint (FCP)
74%
15%
11%

0.01 seconds
First Input Delay (FID)
93%
4%
3%

41

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for xforum.live. 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

Properly size images — Potential savings of 5 KiB
Images can slow down the page's load time. Xforum.live should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://xforum.live/data/avatars/m/48/48374.jpg?1614703782
16086
5262
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Xforum.live should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Xforum.live should consider minifying JS files.
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 200 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://xforum.live/
200.665
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Xforum.live should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://xforum.live/
630
https://xforum.live/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Xforum.live 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 1,325 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://xforum.live/data/avatars/m/84/84519.jpg?1672577627
434599
https://xforum.live/styles/fonts/fa/fa-light-300.woff2?_v=5.15.3
184928
https://xforum.live/styles/fonts/fa/fa-solid-900.woff2?_v=5.15.3
137608
https://www.googletagmanager.com/gtag/js?id=G-643TECKK0C&l=dataLayer&cx=c
78302
https://xforum.live/styles/fonts/fa/fa-brands-400.woff2?_v=5.15.3
77523
https://xforum.live/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=19&l=1&d=1675008636&k=fe537a0ccd3ce0e6910e30eca1f8726b9bf010f9
65976
https://xforum.live/js/xf/core-compiled.js?_v=77adaac3
62886
https://xforum.live/styles/SvgAdblockDetected/img/block.png
62744
https://www.googletagmanager.com/gtag/js?id=UA-129146910-1
45583
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
31984
Avoid chaining critical requests — 13 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Xforum.live 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.
Keep request counts low and transfer sizes small — 43 requests • 1,325 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
43
1356952
Image
14
567595
Font
3
400059
Script
11
279818
Stylesheet
7
80914
Document
1
17264
Other
7
11302
Media
0
0
Third-party
14
188243
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.
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 — 16 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://xforum.live/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1675195200
10260
845
https://xforum.live/
1338
655
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
7260
332
https://www.googletagmanager.com/gtag/js?id=G-643TECKK0C&l=dataLayer&cx=c
4281
247
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
2718
149
https://xforum.live/js/xf/core-compiled.js?_v=77adaac3
7592
109
https://www.google-analytics.com/analytics.js
4161
99
Unattributable
639
92
https://www.googletagmanager.com/gtag/js?id=UA-129146910-1
2999
82
https://xforum.live/
1260
78
https://xforum.live/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=19&l=1&d=1675008636&k=fe537a0ccd3ce0e6910e30eca1f8726b9bf010f9
2921
78
Unattributable
4528
67
Unattributable
731
64
https://xforum.live/
825
59
https://xforum.live/js/xf/preamble.min.js?_v=77adaac3
6510
57
https://www.googletagmanager.com/gtag/js?id=UA-129146910-1
2868
53
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 xforum.live on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

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://xforum.live/
http/1.1
0
70.708999992348
749
0
301
text/html
https://xforum.live/
h2
71.83499999519
271.52599999681
17264
85464
200
text/html
Document
https://fonts.googleapis.com/css2?family=Lobster&display=swap
h2
289.48599999421
302.24699999962
1181
1701
200
text/css
Stylesheet
https://fonts.googleapis.com/css2?family=EB+Garamond&display=swap
h2
289.81899999781
298.95599999873
1246
2415
200
text/css
Stylesheet
https://fonts.googleapis.com/css2?family=Caveat&family=Pacifico&display=swap
h2
290.19200000039
301.68699999922
1280
3129
200
text/css
Stylesheet
https://xforum.live/styles/fonts/fa/fa-light-300.woff2?_v=5.15.3
h2
290.59999999299
507.92199998978
184928
184144
200
font/woff2
Font
https://xforum.live/styles/fonts/fa/fa-solid-900.woff2?_v=5.15.3
h2
290.81999999471
509.75199999812
137608
136824
200
font/woff2
Font
https://xforum.live/styles/fonts/fa/fa-brands-400.woff2?_v=5.15.3
h2
291.23999999138
441.55799999135
77523
76740
200
font/woff2
Font
https://xforum.live/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=19&l=1&d=1675008636&k=fe537a0ccd3ce0e6910e30eca1f8726b9bf010f9
h2
291.58599999209
488.05200000061
65976
396823
200
text/css
Stylesheet
https://xforum.live/css.php?css=public%3Anode_list.less%2Cpublic%3Anotices.less%2Cpublic%3Axb.less%2Cpublic%3Aextra.less&s=19&l=1&d=1675008636&k=73e37b648fb614ffaacfe4c1c8f5d8ddb808ca7d
h2
291.99499999231
385.96299999335
11231
57351
200
text/css
Stylesheet
https://xforum.live/js/xf/preamble.min.js?_v=77adaac3
h2
292.48299999745
366.79600000207
2290
3159
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-129146910-1
h2
585.15099999204
600.3950000013
45583
115575
200
application/javascript
Script
https://fonts.googleapis.com/css2?family=Caveat|EB+Garamond|Lobster
291.25300000305
304.35299999954
0
0
-1
Stylesheet
https://xforum.live/uploads/images/xfnew.png
h2
585.59999999125
654.24099999655
4234
3453
200
image/png
Image
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
h2
540.91299998981
548.67899999954
31984
89476
200
text/javascript
Script
https://xforum.live/js/vendor/vendor-compiled.js?_v=77adaac3
h2
563.05899999279
820.30599999416
13979
43704
200
application/javascript
Script
https://xforum.live/js/xf/core-compiled.js?_v=77adaac3
h2
581.65100000042
804.32899999141
62886
211632
200
application/javascript
Script
https://xforum.live/js/xf/notice.min.js?_v=77adaac3
h2
581.92099998996
735.42199999793
2118
3108
200
application/javascript
Script
https://xforum.live/js/SvgAdblockDetected/advertising.js?_v=77adaac3
h2
584.88599999691
653.67899999546
838
19
200
application/javascript
Script
https://xforum.live/styles/SvgAdblockDetected/img/block.png
h2
586.29599999404
740.75899999298
62744
61964
200
image/png
Image
https://static.cloudflareinsights.com/beacon.min.js/vaafb692b2aea4879b33c060e79fe94621666317369993
h2
586.56599999813
634.93800000288
6530
17031
200
text/javascript
Script
https://fonts.googleapis.com/css2?family=Caveat|EB+Garamond|Lobster
578.79099999263
603.91399999207
0
0
-1
Stylesheet
https://xforum.live/styles/flatawesome/xenforo/bodybg.png
h2
648.84399999573
794.76299999806
29856
29075
200
image/png
Image
https://xforum.live/data/assets/style_properties/block-header.png
h2
652.09999999206
974.40399999323
1177
645
404
text/html
Image
https://xforum.live/data/avatars/m/84/84519.jpg?1672577627
h2
967.39199999138
1209.0800000005
434599
433816
200
image/jpeg
Image
https://xforum.live/data/avatars/m/20/20643.jpg?1593277190
h2
967.63299999293
1037.7020000014
3862
3076
200
image/jpeg
Image
https://xforum.live/data/avatars/m/117/117178.jpg?1643363090
h2
967.77999999176
1034.8539999977
1399
590
200
image/jpeg
Image
https://xforum.live/data/avatars/m/42/42812.jpg?1601792658
h2
968.1239999918
1110.5099999986
1519
713
200
image/jpeg
Image
https://xforum.live/data/avatars/m/168/168937.jpg?1674110856
h2
968.41200000199
1038.2830000017
1662
849
200
image/jpeg
Image
https://xforum.live/data/avatars/m/164/164940.jpg?1671877339
h2
969.06799999124
1039.2799999972
3014
2232
200
image/jpeg
Image
https://xforum.live/data/avatars/m/48/48374.jpg?1614703782
h2
969.49399998994
1039.7999999986
16866
16086
200
image/jpeg
Image
https://xforum.live/data/avatars/m/21/21720.jpg?1599825310
h2
971.56199999154
1038.7579999951
4334
3552
200
image/jpeg
Image
https://xforum.live/data/avatars/s/34/34370.jpg?1616279417
h2
972.29499999958
1040.3919999953
1848
1062
200
image/jpeg
Image
https://www.googletagmanager.com/gtag/js?id=G-643TECKK0C&l=dataLayer&cx=c
h2
1027.7639999986
1046.1119999964
78302
222592
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
1036.6009999998
1045.2359999908
20594
50234
200
text/javascript
Script
https://xforum.live/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1675195200
h2
1115.6699999992
1135.9769999981
14714
34000
200
application/javascript
Script
https://www.google-analytics.com/g/collect?v=2&tid=G-643TECKK0C&gtm=2oe1u0&_p=1318619349&cid=414869811.1675197779&ul=en-us&sr=360x640&uaW=1&uaa=&uab=&uafvl=&uamb=1&uam=Moto%20G4&uap=Android&uapv=6.0&uaw=0&_s=1&sid=1675197778&sct=1&seg=0&dl=https%3A%2F%2Fxforum.live%2F&dt=XForum&en=page_view&_fv=1&_nsi=1&_ss=1
1418.6320000008
1455.8699999907
0
0
-1
Ping
https://www.google-analytics.com/j/collect?v=1&_v=j99&aip=1&a=1318619349&t=pageview&_s=1&dl=https%3A%2F%2Fxforum.live%2F&ul=en-us&de=UTF-8&dt=XForum&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YADAAUABAAAAACAAI~&jid=1308584952&gjid=950596884&cid=414869811.1675197779&tid=UA-129146910-1&_gid=2145558235.1675197779&_r=1&_slc=1&gtm=2ou1u0&z=812831752
h2
1453.7960000016
1457.9189999931
496
4
200
text/plain
XHR
https://xforum.live/cdn-cgi/rum?
h2
1470.1300000015
1482.2790000035
336
0
204
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j99&tid=UA-129146910-1&cid=414869811.1675197779&jid=1308584952&gjid=950596884&_gid=2145558235.1675197779&_u=YADAAUAAAAAAACAAI~&z=209810676
h2
1474.0159999928
1481.6909999936
566
1
200
text/plain
XHR
https://xforum.live/cdn-cgi/challenge-platform/h/g/scripts/pica.js
h2
1475.774999999
1495.8610000031
8216
18341
200
application/javascript
Other
https://www.google-analytics.com/collect?v=1&_v=j99&aip=1&a=1318619349&t=timing&_s=2&dl=https%3A%2F%2Fxforum.live%2F&ul=en-us&de=UTF-8&dt=XForum&sd=24-bit&sr=360x640&vp=360x640&je=0&plt=1459&pdt=0&dns=0&rrt=73&srt=201&tcp=0&dit=1107&clt=1114&_gst=1034&_gbt=1435&_u=YADAAUABAAAAACAAI~&jid=&gjid=&cid=414869811.1675197779&tid=UA-129146910-1&_gid=2145558235.1675197779&gtm=2ou1u0&z=1969723833
h2
1483.1520000007
1487.0859999937
481
35
200
image/gif
Image
https://xforum.live/cdn-cgi/challenge-platform/h/g/cv/result/792546dd8e86f8d5
h2
2795.6739999936
2841.0339999973
939
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)
280.497
19.417
492.818
19.595
512.485
28.428
540.957
22.904
563.908
15.929
579.896
5.026
585.099
8.368
595.862
9.111
608.273
37.218
645.51
327.316
983.739
15.192
999.099
13.246
1019.002
20.591
1039.731
54.532
1098.734
6.314
1107.876
10.541
1119.02
6.324
1128.823
166.145
1295.042
29.431
1334.708
61.625
1398.059
5.651
1406.049
16.728
1426.522
6.567
1433.157
24.706
1476.093
9.587
2373.758
422.441
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 — 2.7 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 5.2 s
The time taken for the page contents to be visibly populated.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 630 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Xforum.live should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css2?family=Lobster&display=swap
1181
780
https://fonts.googleapis.com/css2?family=EB+Garamond&display=swap
1246
780
https://fonts.googleapis.com/css2?family=Caveat&family=Pacifico&display=swap
1280
150
https://xforum.live/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=19&l=1&d=1675008636&k=fe537a0ccd3ce0e6910e30eca1f8726b9bf010f9
65976
1200
https://xforum.live/js/xf/preamble.min.js?_v=77adaac3
2290
150
Defer offscreen images — Potential savings of 61 KiB
Time to Interactive can be slowed down by resources on the page. Xforum.live should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://xforum.live/styles/SvgAdblockDetected/img/block.png
61964
61964
Reduce unused CSS — Potential savings of 62 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Xforum.live should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://xforum.live/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=19&l=1&d=1675008636&k=fe537a0ccd3ce0e6910e30eca1f8726b9bf010f9
65976
62984
Reduce unused JavaScript — Potential savings of 95 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://xforum.live/js/xf/core-compiled.js?_v=77adaac3
62886
45705
https://www.googletagmanager.com/gtag/js?id=G-643TECKK0C&l=dataLayer&cx=c
78302
30757
https://www.googletagmanager.com/gtag/js?id=UA-129146910-1
45583
21062
Avoid an excessive DOM size — 1,204 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
1204
Maximum DOM Depth
23
Maximum Child Elements
50
Reduce JavaScript execution time — 3.2 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://xforum.live/
1858.86
107.264
28.304
https://xforum.live/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1675195200
1734.04
1604.604
8.816
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
828.076
712.064
7.736
Unattributable
501.436
83.456
0
https://www.googletagmanager.com/gtag/js?id=G-643TECKK0C&l=dataLayer&cx=c
261.352
239.824
19.548
https://www.googletagmanager.com/gtag/js?id=UA-129146910-1
165.204
144.444
9.244
https://www.google-analytics.com/analytics.js
155.576
140.616
3.528
https://xforum.live/js/xf/preamble.min.js?_v=77adaac3
115.804
29.468
1.232
https://xforum.live/js/xf/core-compiled.js?_v=77adaac3
93.636
74.176
17.86
https://xforum.live/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=19&l=1&d=1675008636&k=fe537a0ccd3ce0e6910e30eca1f8726b9bf010f9
78.38
0
0

Metrics

Time to Interactive — 9.7 s
The time taken for the page to become fully interactive.
Total Blocking Time — 1,170 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 — 5.3 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 850 ms
Users could experience a delay when interacting with the page.

Other

Efficiently encode images — Potential savings of 431 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://xforum.live/data/avatars/m/84/84519.jpg?1672577627
433816
428162
https://xforum.live/data/avatars/m/48/48374.jpg?1614703782
16086
12860
Serve images in next-gen formats — Potential savings of 491 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://xforum.live/data/avatars/m/84/84519.jpg?1672577627
433816
430849.7
https://xforum.live/styles/SvgAdblockDetected/img/block.png
61964
39495.75
https://xforum.live/styles/flatawesome/xenforo/bodybg.png
29075
17409.8
https://xforum.live/data/avatars/m/48/48374.jpg?1614703782
16086
14579.5
Serve static assets with an efficient cache policy — 23 resources found
Xforum.live 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://xforum.live/data/avatars/m/84/84519.jpg?1672577627
0
434599
https://xforum.live/styles/fonts/fa/fa-light-300.woff2?_v=5.15.3
0
184928
https://xforum.live/styles/fonts/fa/fa-solid-900.woff2?_v=5.15.3
0
137608
https://xforum.live/styles/fonts/fa/fa-brands-400.woff2?_v=5.15.3
0
77523
https://xforum.live/js/xf/core-compiled.js?_v=77adaac3
0
62886
https://xforum.live/styles/SvgAdblockDetected/img/block.png
0
62744
https://xforum.live/styles/flatawesome/xenforo/bodybg.png
0
29856
https://xforum.live/data/avatars/m/48/48374.jpg?1614703782
0
16866
https://xforum.live/js/vendor/vendor-compiled.js?_v=77adaac3
0
13979
https://xforum.live/data/avatars/m/21/21720.jpg?1599825310
0
4334
https://xforum.live/uploads/images/xfnew.png
0
4234
https://xforum.live/data/avatars/m/20/20643.jpg?1593277190
0
3862
https://xforum.live/data/avatars/m/164/164940.jpg?1671877339
0
3014
https://xforum.live/js/xf/preamble.min.js?_v=77adaac3
0
2290
https://xforum.live/js/xf/notice.min.js?_v=77adaac3
0
2118
https://xforum.live/data/avatars/s/34/34370.jpg?1616279417
0
1848
https://xforum.live/data/avatars/m/168/168937.jpg?1674110856
0
1662
https://xforum.live/data/avatars/m/42/42812.jpg?1601792658
0
1519
https://xforum.live/data/avatars/m/117/117178.jpg?1643363090
0
1399
https://xforum.live/js/SvgAdblockDetected/advertising.js?_v=77adaac3
0
838
https://www.google-analytics.com/analytics.js
7200000
20594
https://xforum.live/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1675195200
14400000
14714
https://static.cloudflareinsights.com/beacon.min.js/vaafb692b2aea4879b33c060e79fe94621666317369993
86400000
6530
Minimize main-thread work — 5.9 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
3189.208
Style & Layout
1449.276
Other
617.496
Rendering
206.92
Parse HTML & CSS
174.512
Garbage Collection
143.848
Script Parsing & Compilation
105.256
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://xforum.live/styles/fonts/fa/fa-light-300.woff2?_v=5.15.3
217.32199999678
https://xforum.live/styles/fonts/fa/fa-solid-900.woff2?_v=5.15.3
218.93200000341
https://xforum.live/styles/fonts/fa/fa-brands-400.woff2?_v=5.15.3
150.31799999997
Reduce the impact of third-party code — Third-party code blocked the main thread for 830 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)
31984
584.644
123885
203.68
21571
41.868
6530
0
3707
0
566
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://xforum.live/uploads/images/xfnew.png
First Contentful Paint (3G) — 5217 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
96

Accessibility

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

Navigation

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

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links 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.
`<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"]`
Xforum.live may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`[aria-hidden="true"]` elements contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
Failing Elements

Contrast

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
Mustache
2.2.1
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://xforum.live/
Allowed

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.
...
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: the server responded with a status of 404 (Not Found)
Refused to apply style from 'https://fonts.googleapis.com/css2?family=Caveat|EB+Garamond|Lobster' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
Refused to apply style from 'https://fonts.googleapis.com/css2?family=Caveat|EB+Garamond|Lobster' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
Refused to apply style from 'https://fonts.googleapis.com/css2?family=Caveat|EB+Garamond|Lobster' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
89

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for xforum.live. 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 xforum.live on mobile screens.
Document uses legible font sizes — 98.06% 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
.label
1.67%
10.4px
.contentRow-extra
0.25%
11px
sub, sup
0.02%
9px
98.06%
≥ 12px

Content Best Practices

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

Crawling and Indexing

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

Crawling and Indexing

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

Mobile Friendly

Tap targets are not sized appropriately — 44% 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
27x15
28x15
31x15
29x15
25x15
25x15
35x15
38x15
33x15
33x15
27x15
28x15
35x15
35x15
39x15
42x15
39x15
28x15
44x15
46x15
25x15
89x15
65x15
49x15
59x15
51x15
74x15
69x15
57x15
81x15
67x15
59x15
82x15
52x15
55x15
55x15
56x15
39x15
39x15
54x15
41x15
52x15
57x15
ASR
27x15
69x15
101x15
81x15
56x15
74x15
51x15
64x15
39x15
31x15
41x15
42x15
54x15
39x15
51x15
40x15
73x15
54x15
75x15
54x15
57x15
57x15
20x15
41x15
52x15
78x24
64x15
41x15
31x15
28x15
42x15
69x15
57x15
49x15
107x15
70x15

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

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 xforum.live. This includes details about web app manifests.

Installable

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

PWA Optimized

Registers a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xforum.live 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.

PWA Optimized

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.21.60.216
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

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

Domain Registrar

Security

Visitor Safety

Mature Content: Yes
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 80/100
WOT Child Safety: 10/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 26th January, 2023
Valid To: 25th January, 2024
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: c959965e
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 15747085474606504274848895692248973560
Serial Number (Hex): 0BD8C741A229E48A09660E27CDE400F8
Valid From: 26th January, 2025
Valid To: 25th January, 2025
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 : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
Timestamp : Jan 26 07:49:27.200 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:FD:3F:09:FD:C4:92:8F:4B:D9:D3:2B:
1F:25:F4:B3:3C:12:E8:35:B7:43:E7:E5:3B:52:F1:A8:
4A:50:83:A8:68:02:20:34:51:E6:2A:59:B8:D6:B8:8C:
FC:4D:E0:DF:F0:09:19:D2:7A:1E:76:99:7E:57:01:EB:
00:9C:38:AD:AA:D2:2A
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 73:D9:9E:89:1B:4C:96:78:A0:20:7D:47:9D:E6:B2:C6:
1C:D0:51:5E:71:19:2A:8C:6B:80:10:7A:C1:77:72:B5
Timestamp : Jan 26 07:49:27.237 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:45:B0:6F:13:62:AA:BB:D6:D4:26:8B:71:
40:D0:D9:2E:67:0A:8A:52:F7:E7:14:FF:5B:25:37:CE:
35:6C:3E:55:02:20:2B:58:5F:F3:AF:46:FF:8B:5C:57:
2E:AE:36:B6:11:06:AC:68:36:70:0A:6F:F4:77:5E:5A:
E1:A4:6F:19:E3:11
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
Timestamp : Jan 26 07:49:27.180 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:F6:C2:87:FD:C1:27:17:15:EF:D6:1E:
D2:FD:56:87:4B:51:49:F0:21:16:65:3F:8F:BD:39:1F:
40:C8:57:90:0B:02:20:0B:9A:31:99:FA:47:62:8F:2B:
E0:6D:8A:03:F4:6F:A2:9D:84:78:C9:FE:3D:5B:87:6B:
A5:9A:D6:74:74:46:40
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.xforum.live
DNS:xforum.live
DNS:sni.cloudflaressl.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 31st January, 2023
Content-Type: text/html; charset=utf-8
expires: 19th November, 1981
Cache-Control: private, no-cache, max-age=0
Server: cloudflare
Connection: keep-alive
x-powered-by: PleskLin
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
vary: Accept-Encoding
set-cookie: *
last-modified: 31st January, 2023
strict-transport-security: max-age=15768000; includeSubDomains
CF-Cache-Status: DYNAMIC
Server-Timing: cf-q-config;dur=6.0000020312145e-06
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=Lu8WbSW9bBQYi057929zoiVrsSXcP1SPUYgryiiTcrbKl%2Fsp4Fd3GWbIpvAajEcMhKCM9Sp9NR34CnU%2FFYLJ3VJBcEN4SPTDCwEPAWU3dmgN0EUeCFK%2BVSd0qOIamw%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 7925463c6f30c440-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers:
Full Whois: xforum.live domain is not supported

Nameservers

Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

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

Sites hosted on the same IP address

Domain Valuation Snoop Score
$4,312 USD 2/5