9xbuddy.org

9xbuddy.org is SSL secured

Free website and domain report on 9xbuddy.org

Last Updated: 5th October, 2024 Update Now
Overview

Snoop Summary for 9xbuddy.org

This is a free and comprehensive report about 9xbuddy.org. The domain 9xbuddy.org is currently hosted on a server located in United States with the IP address 172.67.182.163, where the local currency is USD and English is the local language. Our records indicate that 9xbuddy.org is privately registered by Privacy service provided by Withheld for Privacy ehf. 9xbuddy.org is expected to earn an estimated $1,472 USD per day from advertising revenue. The sale of 9xbuddy.org would possibly be worth $1,074,449 USD. This figure is based on the daily revenue potential of the website over a 24 month period. 9xbuddy.org receives an estimated 234,558 unique visitors every day - an insane amount of traffic! This report was last updated 5th October, 2024.

About 9xbuddy.org

Site Preview: 9xbuddy.org 9xbuddy.org
Title: 9xbuddy : Online video download helper
Description: helps you download videos from sites like youtube, twitter, facebook, dailymotion and many other with ease.
Keywords and Tags: 123moviesfree com, 5movies, 9xbuddy, animeflv, avgle, m4ufree, media downloads, offmp3, porntrex, soap2day, thisvid, veporn, watchcartoononline, watchcartoononline io, xfantasy, xfantasy tv
Related Terms: 9xbuddy zee5, dailymotion, dailymotion com
Fav Icon:
Age: Over 7 years old
Domain Created: 11th April, 2017
Domain Updated: 10th September, 2021
Domain Expires: 11th April, 2022
Review

Snoop Score

4/5 (Excellent!)

Valuation

$1,074,449 USD
Note: All valuation figures are estimates.

Popularity

Very High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 7,796
Alexa Reach: 0.0099%
SEMrush Rank (US): 14,522
SEMrush Authority Score: 44
Moz Domain Authority: 0
Moz Page Authority: 0

Rank By Country

Country Alexa Rank
Austria Flag Austria 4,040
Australia Flag Australia 6,835
Brazil Flag Brazil 10,831
Canada Flag Canada 10,678
China Flag China 21,104
Germany Flag Germany 10,721
Algeria Flag Algeria 3,375
Egypt Flag Egypt 5,922
Spain Flag Spain 9,399
France Flag France 16,172
United Kingdom Flag United Kingdom 3,380
Greece Flag Greece 4,909
Hong Kong Flag Hong Kong 9,548
Hungary Flag Hungary 2,716
Indonesia Flag Indonesia 5,127
India Flag India 14,023
Italy Flag Italy 6,809
Korea Republic Of Flag Korea Republic Of 3,542
Madagascar Flag Madagascar 210
Malaysia Flag Malaysia 5,362
Nigeria Flag Nigeria 8,542
Netherlands Flag Netherlands 5,899
Peru Flag Peru 4,424
Philippines Flag Philippines 4,174
Pakistan Flag Pakistan 24,899
Russian Federation Flag Russian Federation 10,799
Sweden Flag Sweden 9,037
Singapore Flag Singapore 4,202
Thailand Flag Thailand 4,639
Turkey Flag Turkey 12,677
Taiwan, Province Of China Flag Taiwan, Province Of China 12,663
United States Flag United States 8,430
Yemen Flag Yemen 1,277
South Africa Flag South Africa 7,073

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 11,576 0
Traffic: 181,163 0
Cost: $90,314 USD $0 USD
Traffic

Visitors

Daily Visitors: 234,558
Monthly Visitors: 7,139,207
Yearly Visitors: 85,613,670
Note: All visitors figures are estimates.

Visitors By Country

Country Visitors (Unique) Percentage
Austria Flag Austria Daily: 2,346
Monthly: 71,392
Yearly: 856,137
1%
Australia Flag Australia Daily: 4,457
Monthly: 135,645
Yearly: 1,626,660
1.9%
Brazil Flag Brazil Daily: 5,864
Monthly: 178,480
Yearly: 2,140,342
2.5%
Canada Flag Canada Daily: 3,518
Monthly: 107,088
Yearly: 1,284,205
1.5%
China Flag China Daily: 12,432
Monthly: 378,378
Yearly: 4,537,525
5.3%
Germany Flag Germany Daily: 6,333
Monthly: 192,759
Yearly: 2,311,569
2.7%
Algeria Flag Algeria Daily: 2,815
Monthly: 85,670
Yearly: 1,027,364
1.2%
Egypt Flag Egypt Daily: 5,629
Monthly: 171,341
Yearly: 2,054,728
2.4%
Spain Flag Spain Daily: 3,753
Monthly: 114,227
Yearly: 1,369,819
1.6%
France Flag France Daily: 2,815
Monthly: 85,670
Yearly: 1,027,364
1.2%
United Kingdom Flag United Kingdom Daily: 16,654
Monthly: 506,884
Yearly: 6,078,571
7.1%
Greece Flag Greece Daily: 2,346
Monthly: 71,392
Yearly: 856,137
1%
Hong Kong Flag Hong Kong Daily: 1,642
Monthly: 49,974
Yearly: 599,296
0.7%
Hungary Flag Hungary Daily: 2,346
Monthly: 71,392
Yearly: 856,137
1%
Indonesia Flag Indonesia Daily: 6,099
Monthly: 185,619
Yearly: 2,225,955
2.6%
India Flag India Daily: 11,728
Monthly: 356,960
Yearly: 4,280,684
5%
Italy Flag Italy Daily: 5,629
Monthly: 171,341
Yearly: 2,054,728
2.4%
Korea Republic Of Flag Korea Republic Of Daily: 14,308
Monthly: 435,492
Yearly: 5,222,434
6.1%
Madagascar Flag Madagascar Daily: 4,926
Monthly: 149,923
Yearly: 1,797,887
2.1%
Malaysia Flag Malaysia Daily: 3,284
Monthly: 99,949
Yearly: 1,198,591
1.4%
Nigeria Flag Nigeria Daily: 2,815
Monthly: 85,670
Yearly: 1,027,364
1.2%
Netherlands Flag Netherlands Daily: 3,518
Monthly: 107,088
Yearly: 1,284,205
1.5%
Other Daily: 33,542
Monthly: 1,020,907
Yearly: 12,242,755
14.3%
Peru Flag Peru Daily: 3,049
Monthly: 92,810
Yearly: 1,112,978
1.3%
Philippines Flag Philippines Daily: 2,111
Monthly: 64,253
Yearly: 770,523
0.9%
Pakistan Flag Pakistan Daily: 1,407
Monthly: 42,835
Yearly: 513,682
0.6%
Russian Federation Flag Russian Federation Daily: 8,444
Monthly: 257,011
Yearly: 3,082,092
3.6%
Sweden Flag Sweden Daily: 1,173
Monthly: 35,696
Yearly: 428,068
0.5%
Singapore Flag Singapore Daily: 2,580
Monthly: 78,531
Yearly: 941,750
1.1%
Thailand Flag Thailand Daily: 3,987
Monthly: 121,367
Yearly: 1,455,432
1.7%
Turkey Flag Turkey Daily: 2,580
Monthly: 78,531
Yearly: 941,750
1.1%
Taiwan, Province Of China Flag Taiwan, Province Of China Daily: 2,346
Monthly: 71,392
Yearly: 856,137
1%
United States Flag United States Daily: 42,924
Monthly: 1,306,475
Yearly: 15,667,302
18.3%
Yemen Flag Yemen Daily: 2,815
Monthly: 85,670
Yearly: 1,027,364
1.2%
South Africa Flag South Africa Daily: 2,346
Monthly: 71,392
Yearly: 856,137
1%
Note: All visitors figures are estimates.
Revenue

Revenue

Daily Revenue: $1,472 USD
Monthly Revenue: $44,798 USD
Yearly Revenue: $537,219 USD
Note: All revenue figures are estimates.

Revenue By Country

Country Revenue Percentage
Austria Flag Austria Daily: $1 USD
Monthly: $17 USD
Yearly: $200 USD
<0.1%
Australia Flag Australia Daily: $7 USD
Monthly: $218 USD
Yearly: $2,611 USD
0.5%
Brazil Flag Brazil Daily: $4 USD
Monthly: $117 USD
Yearly: $1,400 USD
0.3%
Canada Flag Canada Daily: $8 USD
Monthly: $254 USD
Yearly: $3,051 USD
0.6%
China Flag China Daily: $17 USD
Monthly: $527 USD
Yearly: $6,318 USD
1.2%
Germany Flag Germany Daily: $22 USD
Monthly: $679 USD
Yearly: $8,141 USD
1.5%
Algeria Flag Algeria Daily: $0 USD
Monthly: $7 USD
Yearly: $84 USD
<0.1%
Egypt Flag Egypt Daily: $1 USD
Monthly: $18 USD
Yearly: $217 USD
<0.1%
Spain Flag Spain Daily: $3 USD
Monthly: $94 USD
Yearly: $1,130 USD
0.2%
France Flag France Daily: $5 USD
Monthly: $167 USD
Yearly: $2,004 USD
0.4%
United Kingdom Flag United Kingdom Daily: $73 USD
Monthly: $2,215 USD
Yearly: $26,568 USD
4.9%
Greece Flag Greece Daily: $0 USD
Monthly: $14 USD
Yearly: $168 USD
<0.1%
Hong Kong Flag Hong Kong Daily: $0 USD
Monthly: $9 USD
Yearly: $103 USD
<0.1%
Hungary Flag Hungary Daily: $0 USD
Monthly: $7 USD
Yearly: $82 USD
<0.1%
Indonesia Flag Indonesia Daily: $6 USD
Monthly: $171 USD
Yearly: $2,048 USD
0.4%
India Flag India Daily: $46 USD
Monthly: $1,402 USD
Yearly: $16,818 USD
3.1%
Italy Flag Italy Daily: $5 USD
Monthly: $138 USD
Yearly: $1,653 USD
0.3%
Korea Republic Of Flag Korea Republic Of Daily: $17 USD
Monthly: $509 USD
Yearly: $6,108 USD
1.1%
Madagascar Flag Madagascar Daily: $0 USD
Monthly: $1 USD
Yearly: $12 USD
<0.1%
Malaysia Flag Malaysia Daily: $2 USD
Monthly: $49 USD
Yearly: $590 USD
0.1%
Nigeria Flag Nigeria Daily: $1 USD
Monthly: $29 USD
Yearly: $345 USD
0.1%
Netherlands Flag Netherlands Daily: $4 USD
Monthly: $120 USD
Yearly: $1,440 USD
0.3%
Other Daily: $0 USD
Monthly: $0 USD
Yearly: $0 USD
<0.1%
Peru Flag Peru Daily: $0 USD
Monthly: $7 USD
Yearly: $89 USD
<0.1%
Philippines Flag Philippines Daily: $1 USD
Monthly: $34 USD
Yearly: $403 USD
0.1%
Pakistan Flag Pakistan Daily: $1 USD
Monthly: $23 USD
Yearly: $281 USD
0.1%
Russian Federation Flag Russian Federation Daily: $2 USD
Monthly: $62 USD
Yearly: $743 USD
0.1%
Sweden Flag Sweden Daily: $1 USD
Monthly: $18 USD
Yearly: $216 USD
<0.1%
Singapore Flag Singapore Daily: $1 USD
Monthly: $21 USD
Yearly: $256 USD
<0.1%
Thailand Flag Thailand Daily: $1 USD
Monthly: $37 USD
Yearly: $449 USD
0.1%
Turkey Flag Turkey Daily: $1 USD
Monthly: $38 USD
Yearly: $453 USD
0.1%
Taiwan, Province Of China Flag Taiwan, Province Of China Daily: $0 USD
Monthly: $8 USD
Yearly: $95 USD
<0.1%
United States Flag United States Daily: $1,239 USD
Monthly: $37,711 USD
Yearly: $452,234 USD
84.2%
Yemen Flag Yemen Daily: $0 USD
Monthly: $1 USD
Yearly: $14 USD
<0.1%
South Africa Flag South Africa Daily: $2 USD
Monthly: $75 USD
Yearly: $896 USD
0.2%
Note: All revenue figures are estimates.
SEO

Backlinks Analysis (SEMrush)

Backlinks: 22,763
Referring Domains: 376
Referring IPs: 226
9xbuddy.org has 22,763 backlinks according to SEMrush. 98% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve 9xbuddy.org'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.
94% of 9xbuddy.org'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: http://baseclips.ru/load/dance/the_motans_feat_irina_rimes_poem/6-1-0-59809
Target: https://9xbuddy.org/process?url=https%3A%2F%2Fyoutu.be%2F6HCnT_NqrQI

2
Source: https://rr-go.com/go/144632/?categoryID=59&geo=us&lang=cn&r&subcategoryID=102
Target: http://9xbuddy.org/?ref=ratrating.com

3
Source: http://9xbuddy.com/download?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Di0g8toTz-ek
Target: https://9xbuddy.org/download?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Di0g8toTz-ek

4
Source: http://baseclips.ru/load/pop/mason_ramsey_twang/8-1-0-62550
Target: https://9xbuddy.org/process?url=https%3A%2F%2Fyoutu.be%2Fxwe8F_AhLY0

5
Source: https://9xbuddy.in/sites/trilulilu
Target: https://9xbuddy.org/sites/trilulilu

Top Ranking Keywords (US)

1
Keyword: 9xbuddy
Ranked Page: https://9xbuddy.org/

2
Keyword: porntrex
Ranked Page: https://9xbuddy.org/sites/porntrex

3
Keyword: xfantasy
Ranked Page: https://9xbuddy.org/sites/xfantasy

4
Keyword: m4ufree
Ranked Page: https://9xbuddy.org/sites/m4ufree

5
Keyword: watchcartoononline io
Ranked Page: https://9xbuddy.org/sites/watchcartoononline

Domain Analysis

Value Length
Domain: 9xbuddy.org 11
Domain Name: 9xbuddy 7
Extension (TLD): org 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.83 seconds
Load Time Comparison: Faster than 81% of sites

PageSpeed Insights

Avg. (All Categories) 94
Performance 90
Accessibility 98
Best Practices 83
SEO 100
PWA 100
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://9xbuddy.org
Updated: 17th June, 2022

1.22 seconds
First Contentful Paint (FCP)
87%
8%
5%

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

Simulate loading on desktop
90

Performance

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

Metrics

First Contentful Paint — 0.5 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.0 s
The time taken for the page to become fully interactive.
Speed Index — 1.1 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 0.9 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.072
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 0.6 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://9xbuddy.org/
http/1.1
0
75.668999925256
745
0
301
text/plain
https://9xbuddy.org/
http/1.1
76.173999812454
429.3479998596
955
0
301
text/html
https://9xbuddy.org/en-1ay
h2
429.77599985898
733.9979999233
6751
19091
200
text/html
Document
https://9xbuddy.org/build/main.696f7cee80aa59044623.css
h2
749.18199982494
804.24099997617
6556
26904
200
text/css
Stylesheet
https://9xbuddy.org/cdn-cgi/challenge-platform/h/g/scripts/invisible.js?ts=1655467200
h2
749.85299981199
818.00299999304
18109
49270
200
application/javascript
Script
https://9xbuddy.org/build/291f13891176f90733ca.png
h2
752.53900000826
814.66299993917
3454
2501
200
image/png
Image
https://9xbuddy.org/build/main.696f7cee80aa59044623.js
h2
752.36499984749
831.86699985527
90754
284223
200
application/javascript
Script
https://9xbuddy.org/build/779.696f7cee80aa59044623.js
h2
933.98599978536
960.27599996887
6705
16288
200
application/javascript
Script
https://9xbuddy.org/build/669.696f7cee80aa59044623.js
h2
934.39599988051
985.55999994278
6019
13793
200
application/javascript
Script
https://9xbuddy.org/build/70.696f7cee80aa59044623.js
h2
934.90100000054
1002.9429998249
8313
22693
200
application/javascript
Script
https://9xbuddy.org/build/289.696f7cee80aa59044623.js
h2
935.34699990414
1034.023999935
4184
8946
200
application/javascript
Script
https://9xbuddy.org/cdn-cgi/challenge-platform/h/g/scripts/pica.js
h2
965.10099992156
1060.6869999319
9079
23660
200
application/javascript
Other
https://9xbuddy.org/cdn-cgi/challenge-platform/h/g/cv/result/71cc80ffe8e59c30
h2
1924.2819999345
1979.4849997852
1089
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)
782.048
7.935
852.05
7.328
891.344
105.674
997.154
6.572
1078.121
8.194
1086.327
18.047
1104.385
14.521
1118.933
5.096
1124.04
7.94
1538.714
428.481
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. 9xbuddy.org 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://9xbuddy.org/build/main.696f7cee80aa59044623.css
6556
70
Properly size images
Images can slow down the page's load time. 9xbuddy.org should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. 9xbuddy.org should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 9xbuddy.org should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 9xbuddy.org should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 9xbuddy.org should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 29 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://9xbuddy.org/build/main.696f7cee80aa59044623.js
90754
29314
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 310 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://9xbuddy.org/en-1ay
305.213
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. 9xbuddy.org should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://9xbuddy.org/build/779.696f7cee80aa59044623.js
69
https://9xbuddy.org/build/main.696f7cee80aa59044623.js
59
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://9xbuddy.org/build/291f13891176f90733ca.png
0
Avoids enormous network payloads — Total size was 159 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://9xbuddy.org/build/main.696f7cee80aa59044623.js
90754
https://9xbuddy.org/cdn-cgi/challenge-platform/h/g/scripts/invisible.js?ts=1655467200
18109
https://9xbuddy.org/cdn-cgi/challenge-platform/h/g/scripts/pica.js
9079
https://9xbuddy.org/build/70.696f7cee80aa59044623.js
8313
https://9xbuddy.org/en-1ay
6751
https://9xbuddy.org/build/779.696f7cee80aa59044623.js
6705
https://9xbuddy.org/build/main.696f7cee80aa59044623.css
6556
https://9xbuddy.org/build/669.696f7cee80aa59044623.js
6019
https://9xbuddy.org/build/289.696f7cee80aa59044623.js
4184
https://9xbuddy.org/build/291f13891176f90733ca.png
3454
Uses efficient cache policy on static assets — 1 resource found
9xbuddy.org 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://9xbuddy.org/cdn-cgi/challenge-platform/h/g/scripts/invisible.js?ts=1655467200
14400000
18109
Avoids an excessive DOM size — 166 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
166
Maximum DOM Depth
11
Maximum Child Elements
8
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. 9xbuddy.org should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.6 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://9xbuddy.org/cdn-cgi/challenge-platform/h/g/scripts/invisible.js?ts=1655467200
441.419
436.616
2.626
https://9xbuddy.org/build/main.696f7cee80aa59044623.js
116.368
108.027
4.488
https://9xbuddy.org/en-1ay
53.11
3.592
2.275
Minimizes main-thread work — 0.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
560.791
Other
46.587
Style & Layout
27.185
Script Parsing & Compilation
11.032
Rendering
9.01
Parse HTML & CSS
4.656
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 13 requests • 159 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
13
162713
Script
6
134084
Other
4
11868
Document
1
6751
Stylesheet
1
6556
Image
1
3454
Media
0
0
Font
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.071673723842045
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://9xbuddy.org/cdn-cgi/challenge-platform/h/g/scripts/invisible.js?ts=1655467200
946
214
https://9xbuddy.org/build/main.696f7cee80aa59044623.js
840
106
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 9xbuddy.org 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

Total Blocking Time — 220 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).

Audits

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

Other

Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. 9xbuddy.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://9xbuddy.org/
190
https://9xbuddy.org/
150
https://9xbuddy.org/en-1ay
0
98

Accessibility

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

Names and labels

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that 9xbuddy.org 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
React
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

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

Audits

Uses deprecated APIs — 1 warning 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.
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for 9xbuddy.org. 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 9xbuddy.org 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.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

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

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 9xbuddy.org. 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 9xbuddy.org on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest has a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

1.48 seconds
First Contentful Paint (FCP)
82%
12%
6%

0.02 seconds
First Input Delay (FID)
92%
4%
4%

Simulate loading on mobile
79

Performance

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

Metrics

First Contentful Paint — 1.5 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 3.3 s
The time taken for the page to become fully interactive.
Speed Index — 2.1 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.8 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 1.5 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://9xbuddy.org/
http/1.1
0
36.352999974042
762
0
301
text/plain
https://9xbuddy.org/
http/1.1
36.674000089988
146.39099990018
938
0
301
text/html
https://9xbuddy.org/en-1ay
h2
146.68700005859
257.41999992169
6756
19095
200
text/html
Document
https://9xbuddy.org/build/main.696f7cee80aa59044623.css
h2
268.6719999183
298.32999990322
6548
26904
200
text/css
Stylesheet
https://9xbuddy.org/cdn-cgi/challenge-platform/h/g/scripts/invisible.js?ts=1655467200
h2
268.85799993761
312.85699992441
17409
48017
200
application/javascript
Script
https://9xbuddy.org/build/05edbfb3a8c47979d2f8.png
h2
273.24900007807
295.47100001946
5842
4885
200
image/png
Image
https://9xbuddy.org/build/main.696f7cee80aa59044623.js
h2
273.16100010648
317.47299991548
90752
284223
200
application/javascript
Script
https://9xbuddy.org/build/779.696f7cee80aa59044623.js
h2
418.66399999708
445.7729998976
6707
16288
200
application/javascript
Script
https://9xbuddy.org/build/669.696f7cee80aa59044623.js
h2
419.08399993554
443.53200006299
6017
13793
200
application/javascript
Script
https://9xbuddy.org/build/70.696f7cee80aa59044623.js
h2
419.58700004034
446.42799999565
8319
22693
200
application/javascript
Script
https://9xbuddy.org/build/289.696f7cee80aa59044623.js
h2
419.98500004411
454.27799993195
4182
8946
200
application/javascript
Script
https://9xbuddy.org/build/291f13891176f90733ca.png
h2
427.08899988793
450.77600004151
3458
2501
200
image/png
Image
https://9xbuddy.org/cdn-cgi/challenge-platform/h/g/scripts/pica.js
h2
441.66400004178
471.18499991484
8507
21759
200
application/javascript
Other
https://9xbuddy.org/cdn-cgi/challenge-platform/h/g/cv/result/71cc81721e509c30
h2
1042.5839999225
1089.2779999413
1065
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)
300.84
6.474
343.455
15.842
375.312
96.747
474.049
6.428
496.519
6.888
503.418
12.201
515.643
9.071
801.527
281.91
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

Properly size images
Images can slow down the page's load time. 9xbuddy.org should consider serving more appropriate-sized images.
Defer offscreen images — Potential savings of 2 KiB
Time to Interactive can be slowed down by resources on the page. 9xbuddy.org should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://9xbuddy.org/build/291f13891176f90733ca.png
2501
2340
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 9xbuddy.org should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 9xbuddy.org should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 9xbuddy.org should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 110 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://9xbuddy.org/en-1ay
111.726
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. 9xbuddy.org should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://9xbuddy.org/build/779.696f7cee80aa59044623.js
69
https://9xbuddy.org/build/main.696f7cee80aa59044623.js
59
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 163 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://9xbuddy.org/build/main.696f7cee80aa59044623.js
90752
https://9xbuddy.org/cdn-cgi/challenge-platform/h/g/scripts/invisible.js?ts=1655467200
17409
https://9xbuddy.org/cdn-cgi/challenge-platform/h/g/scripts/pica.js
8507
https://9xbuddy.org/build/70.696f7cee80aa59044623.js
8319
https://9xbuddy.org/en-1ay
6756
https://9xbuddy.org/build/779.696f7cee80aa59044623.js
6707
https://9xbuddy.org/build/main.696f7cee80aa59044623.css
6548
https://9xbuddy.org/build/669.696f7cee80aa59044623.js
6017
https://9xbuddy.org/build/05edbfb3a8c47979d2f8.png
5842
https://9xbuddy.org/build/289.696f7cee80aa59044623.js
4182
Uses efficient cache policy on static assets — 1 resource found
9xbuddy.org 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://9xbuddy.org/cdn-cgi/challenge-platform/h/g/scripts/invisible.js?ts=1655467200
14400000
17409
Avoids an excessive DOM size — 166 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
166
Maximum DOM Depth
11
Maximum Child Elements
8
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. 9xbuddy.org 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.
Minimizes main-thread work — 1.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
1582.9
Other
155.476
Style & Layout
105.14
Rendering
42.896
Script Parsing & Compilation
41.484
Parse HTML & CSS
17.384
Garbage Collection
3.34
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 14 requests • 163 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
14
167262
Script
6
133386
Other
4
11272
Image
2
9300
Document
1
6756
Stylesheet
1
6548
Media
0
0
Font
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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 — 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://9xbuddy.org/cdn-cgi/challenge-platform/h/g/scripts/invisible.js?ts=1655467200
2790
564
https://9xbuddy.org/build/main.696f7cee80aa59044623.js
2280
387
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 9xbuddy.org 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.

Other

Eliminate render-blocking resources — Potential savings of 150 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. 9xbuddy.org 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://9xbuddy.org/build/main.696f7cee80aa59044623.css
6548
180
Reduce unused JavaScript — Potential savings of 29 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://9xbuddy.org/build/main.696f7cee80aa59044623.js
90752
29313
Reduce JavaScript execution time — 1.6 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://9xbuddy.org/cdn-cgi/challenge-platform/h/g/scripts/invisible.js?ts=1655467200
1146.68
1131.616
8.056
https://9xbuddy.org/build/main.696f7cee80aa59044623.js
437.884
399.828
20.872
https://9xbuddy.org/en-1ay
206.452
10.292
7.38
Unattributable
108.3
9.58
0.6
First Contentful Paint (3G) — 2820 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

Total Blocking Time — 850 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).

Audits

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

Other

Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. 9xbuddy.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://9xbuddy.org/
630
https://9xbuddy.org/
480
https://9xbuddy.org/en-1ay
0
97

Accessibility

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

Names and labels

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that 9xbuddy.org 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
React
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

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

Audits

Uses deprecated APIs — 1 warning 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.
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for 9xbuddy.org. 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 9xbuddy.org on mobile screens.
Document uses legible font sizes — 100% 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
100.00%
≥ 12px
Tap targets are sized appropriately — 100% 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.

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.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

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

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 9xbuddy.org. 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 9xbuddy.org on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest has a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

Server Location

Server IP Address: 172.67.182.163
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: Yes
Name: REDACTED FOR PRIVACY
Organization: Privacy service provided by Withheld for Privacy ehf
Country: IS
City: REDACTED FOR PRIVACY
State: Capital Region
Post Code: REDACTED FOR PRIVACY
Email:
Phone: REDACTED FOR PRIVACY
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
NAMECHEAP INC 104.16.100.56
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 28th May, 2022
Valid To: 28th May, 2023
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: 13570078483097290595543598333815015826
Serial Number (Hex): 0A358086566913D338049BE96B35C992
Valid From: 28th May, 2024
Valid To: 28th May, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

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

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

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : May 28 02:16:48.108 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:B0:71:A2:E4:85:FC:94:B3:8A:F1:C0:
AC:51:AF:B9:F7:50:2A:15:A4:17:EC:43:58:DD:22:C3:
2C:0F:EC:6C:5C:02:20:27:CF:F0:C5:6E:2B:92:7F:42:
45:5D:F9:8F:56:29:5F:FB:6C:4B:70:4F:65:A7:C7:12:
08:D4:23:7D:88:76:76
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : May 28 02:16:48.071 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:35:39:B7:2A:9A:71:BE:05:8F:13:1F:43:
78:E3:24:5C:EF:3B:6D:70:7F:13:A4:A5:F4:37:7D:C6:
8A:4B:D7:6A:02:20:1B:19:73:CB:BB:57:31:5E:35:38:
C4:5C:20:20:E2:25:CE:1F:EC:C9:25:16:5F:08:90:87:
33:1D:0F:1B:22:49
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B3:73:77:07:E1:84:50:F8:63:86:D6:05:A9:DC:11:09:
4A:79:2D:B1:67:0C:0B:87:DC:F0:03:0E:79:36:A5:9A
Timestamp : May 28 02:16:48.120 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:89:41:21:12:A2:49:2D:A0:46:AC:9C:
3D:1E:B9:B4:98:1E:B2:09:3D:04:58:C7:A8:B4:86:47:
AE:CA:D2:9D:4D:02:21:00:93:3B:1C:3F:AC:B4:78:EC:
68:74:08:3B:59:04:33:8B:F3:E5:C9:5A:D3:FA:D2:54:
F1:E7:F7:F9:D2:72:80:20
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.9xbuddy.org
DNS:9xbuddy.org
DNS:sni.cloudflaressl.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 404 Not Found
Date: 17th June, 2022
Content-Type: text/html; charset=UTF-8
Server: cloudflare
Connection: keep-alive
vary: Accept-Encoding
x-powered-by: PHP/8.0.20
x-frame-options: DENY
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=Oe6NUmVzBJkoYD%2FrWCrdxY0oJEUfTdptugBle3Wd499EU8gJtAE2Ws0%2FOgDMkJ1vbt%2B9mwECdqSjwfUR6WxIyPOnrMjG3d1EcOXiiB2Fayk67bTlTXVSRd6XK3qWhQ%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
X-Content-Type-Options: nosniff
CF-RAY: 71cc80e3be6c8c84-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 11th April, 2017
Changed: 10th September, 2021
Expires: 11th April, 2022
Registrar: NameCheap, Inc.
Status: clientTransferProhibited
Nameservers: art.ns.cloudflare.com
beth.ns.cloudflare.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: Privacy service provided by Withheld for Privacy ehf
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: Capital Region
Owner Country: IS
Owner Phone: REDACTED FOR PRIVACY
Owner Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Full Whois: Domain Name: 9xbuddy.org
Registry Domain ID: 1bf84e1677844d67b5649264820e56e9-LROR
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2021-10-09T01:02:45Z
Creation Date: 2017-11-04T13:42:53Z
Registry Expiry Date: 2022-11-04T13:42:53Z
Registrar: NameCheap, Inc.
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.6613102107
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Privacy service provided by Withheld for Privacy ehf
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: Capital Region
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: IS
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: art.ns.cloudflare.com
Name Server: beth.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2022-06-17T14:34:00Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Terms of Use: Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Donuts except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.

Nameservers

Name IP Address
art.ns.cloudflare.com 173.245.59.102
beth.ns.cloudflare.com 172.64.32.103
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$281,719 USD 4/5
0/5
0/5

Sites hosted on the same IP address

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