teenax.com

teenax.com is SSL secured

Free website and domain report on teenax.com

Last Updated: 18th October, 2024 Update Now
Overview

Snoop Summary for teenax.com

This is a free and comprehensive report about teenax.com. Teenax.com is hosted in United States on a server with an IP address of 104.21.233.196, where the local currency is USD and English is the local language. Our records indicate that teenax.com is owned/operated by DANESCO TRADING LTD.. Teenax.com has the potential to be earning an estimated $5 USD per day from advertising revenue. If teenax.com was to be sold it would possibly be worth $3,432 USD (based on the daily revenue potential of the website over a 24 month period). Teenax.com receives an estimated 1,645 unique visitors every day - a large amount of traffic! This report was last updated 18th October, 2024.

About teenax.com

Site Preview:
Title: Teenax Video
Description: Our site has moved to a new address. Please note the change of address.
Keywords and Tags: adult content, pornography
Related Terms:
Fav Icon:
Age: Over 22 years old
Domain Created: 21st July, 2002
Domain Updated: 24th June, 2024
Domain Expires: 21st July, 2025
Review

Snoop Score

3/5 (Great!)

Valuation

$3,432 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 476,116
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 1,645
Monthly Visitors: 50,069
Yearly Visitors: 600,425
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $5 USD
Monthly Revenue: $143 USD
Yearly Revenue: $1,711 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: teenax.com 10
Domain Name: teenax 6
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 2.05 seconds
Load Time Comparison: Faster than 31% of sites

PageSpeed Insights

Avg. (All Categories) 69
Performance 97
Accessibility 71
Best Practices 83
SEO 73
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://teenax.com
Updated: 4th July, 2022

2.78 seconds
First Contentful Paint (FCP)
49%
31%
20%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

97

Performance

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

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.1 s
The time taken for the page to become fully interactive.
Speed Index — 1.0 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 10 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.1 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

Max Potential First Input Delay — 70 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 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://teenax.com/
http/1.1
0
157.16499998234
946
0
302
text/html
https://teenax.com/en/territory-US.html
h2
157.52099989913
392.21499999985
22862
173985
200
text/html
Document
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
h2
402.49799983576
409.22599984333
35030
97163
200
text/javascript
Script
https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js
h2
402.70500001498
411.30999987945
69027
253668
200
text/javascript
Script
https://teenax.com/js/ytzjifjgcung.js?v4447
h2
415.99699994549
513.69499997236
4432
10280
200
application/x-javascript
Script
https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/themes/smoothness/jquery-ui.css
h2
403.1159998849
408.54400000535
9493
36536
200
text/css
Stylesheet
https://teenax.com/css/style.css?1.177
h2
403.38200004771
455.5869998876
6627
38799
200
text/css
Stylesheet
https://teenax.com/css/tuning.css?1.0
h2
403.62500003539
490.54999998771
1052
188
200
text/css
Stylesheet
https://teenax.com/js/custom.js?1.1
h2
416.13300004974
498.38899984024
1488
2318
200
application/x-javascript
Script
https://fonts.googleapis.com/css?family=Russo+One
h2
457.96799985692
478.59700000845
1189
987
200
text/css
Stylesheet
https://teenax.com/fonts/fontello.css
h2
458.26500002295
495.94599986449
7587
10191
200
text/css
Stylesheet
https://teenax.com/img/famfamfam-flags.png
h2
559.39399986528
585.62399982475
77518
76543
200
image/png
Image
https://teenax.com/img/l.png
h2
560.57900004089
611.28099984489
1981
1006
200
image/png
Image
https://teenax.com/img/imgbg.png
h2
560.78299996443
583.68099993095
1126
153
200
image/png
Image
data
582.4090000242
894.41599999554
5888
5888
200
application/octet-stream
Font
https://fonts.gstatic.com/s/russoone/v14/Z9XUDmZRWg6M1LvRYsHOz8mJvLuL9A.woff2
h2
604.20599998906
607.59099991992
8367
7440
200
font/woff2
Font
https://teenax.com/t/in
h2
737.02399991453
849.93799985386
1104
15
200
application/json
XHR
data
845.79900000244
845.96999990754
0
43
200
image/gif
Image
https://teenax.com/img/btt.png
h2
850.94000003301
874.31499990635
1212
246
200
image/png
Image
https://mno.teenax.com/m/4/4/i/r-QklSZd05FkuntaFPw.jpg
h2
851.05699999258
934.59199997596
16974
15972
200
image/jpeg
Image
https://ghi.teenax.com/g/Y/q/q/tjyjk7lsQ1dz6-jFtdg.jpg
h2
851.47199989296
940.4420000501
23503
22503
200
image/jpeg
Image
https://ghi.teenax.com/h/3/G/G/1DqKpO_nO8Hw4cKjaEw.jpg
h2
851.71299986541
935.0629998371
16193
15189
200
image/jpeg
Image
https://jkl.teenax.com/l/B/B/L/9dhZBLj76sxmpBIxITg.jpg
h2
851.95299983025
1222.9549998883
19029
18027
200
image/jpeg
Image
https://mno.teenax.com/n/-/-/M/G7aM2qIX9KgEwTKYs1Q.jpg
h2
852.3409999907
953.22899986058
18326
17312
200
image/jpeg
Image
https://mno.teenax.com/n/T/h/D/CdD7BD2ieA7kR9jpydA.jpg
h2
852.52700001001
938.41099995188
16664
15664
200
image/jpeg
Image
https://jkl.teenax.com/j/-/P/A/Yk1Ppcm9zmqVUV7Wzzw.jpg
h2
852.85499994643
957.36199989915
29223
28221
200
image/jpeg
Image
https://stu.teenax.com/s/4/7/z/O2_DRvvJEPuUxy4GqCA.jpg
h2
853.09199988842
922.14599996805
15964
14964
200
image/jpeg
Image
https://jkl.teenax.com/j/e/W/U/_i4yhl0gtC6N_wrIk_w.jpg
h2
853.25699998066
942.92299984954
17566
16562
200
image/jpeg
Image
https://ghi.teenax.com/i/l/G/W/DV3n5_nbjwCLBqakN0A.jpg
h2
853.6300000269
939.22499986365
17868
16862
200
image/jpeg
Image
https://pqr.teenax.com/p/y/Z/x/FKecq0rbUIvFjabZW5g.jpg
h2
853.98799995892
963.64500001073
20000
18988
200
image/jpeg
Image
https://ghi.teenax.com/h/2/n/G/h1yCMXmQg-OC9poKsbQ.jpg
h2
854.39799982123
933.57599992305
14212
13200
200
image/jpeg
Image
https://jkl.teenax.com/j/-/A/-/LWTbluPbmRXBmxAVtLQ.jpg
h2
854.75199995562
937.34800000675
16005
14999
200
image/jpeg
Image
https://ghi.teenax.com/g/t/V/8/_ajY4VbbPk-Z6CPALUA.jpg
h2
855.07299983874
951.31499995477
12487
11481
200
image/jpeg
Image
https://mno.teenax.com/n/b/2/W/ngpWtt90xzGgrI2Pz8w.jpg
h2
855.45899998397
936.78799993359
21941
20939
200
image/jpeg
Image
https://ghi.teenax.com/h/J/E/d/LI_kkJDPOg8nFcMpI3Q.jpg
h2
855.74699984863
946.16999989375
20458
19454
200
image/jpeg
Image
https://mno.teenax.com/n/6/a/N/zc-FM9m_x2HP_LSupPw.jpg
h2
855.99399986677
937.96300003305
15289
14283
200
image/jpeg
Image
https://pqr.teenax.com/q/_/0/Z/gDoc8ZRGNd7GrdVF14w.jpg
h2
856.36199987493
974.46900000796
19711
18713
200
image/jpeg
Image
https://jkl.teenax.com/k/X/F/t/IsK8krPcife1Mf7eq4Q.jpg
h2
856.59900004975
1056.7369998898
16923
15928
200
image/jpeg
Image
https://pqr.teenax.com/p/m/r/R/aizza82hkoh-IsjF1Hw.jpg
h2
857.03199985437
940.03099994734
23374
22370
200
image/jpeg
Image
https://mno.teenax.com/m/g/4/C/mtcrNcn4Dm40_rkwIYw.jpg
h2
857.25399991497
931.65599997155
23085
22085
200
image/jpeg
Image
https://pqr.teenax.com/r/8/B/h/sROnKC-VHbanP5cAbDA.jpg
h2
857.46699990705
986.29999998957
17324
16312
200
image/jpeg
Image
https://mno.teenax.com/n/v/A/D/bKW7dGYI6csQcI_Fo7Q.jpg
h2
857.7449999284
926.71300005168
15842
14844
200
image/jpeg
Image
https://pqr.teenax.com/q/s/3/Z/NECSqXV_ELu2Hm6Ps8w.jpg
h2
858.19399985485
943.82399995811
17596
16598
200
image/jpeg
Image
https://jkl.teenax.com/l/o/b/2/S6GBIoAYoGHaCPFFbnw.jpg
h2
858.49500005133
924.54699985683
11042
10032
200
image/jpeg
Image
https://mno.teenax.com/m/S/e/i/2OI6qJqa3bW469Sba5w.jpg
h2
858.74699987471
961.75899985246
17953
16943
200
image/jpeg
Image
https://stu.teenax.com/t/1/W/S/-mcekp_ov6YrLiAPsCQ.jpg
h2
859.03799999505
1089.3029998988
14333
13338
200
image/jpeg
Image
https://mno.teenax.com/m/I/e/l/iJeXxF3XeT4ZjhB3ljg.jpg
h2
859.32000004686
960.7079999987
19420
18418
200
image/jpeg
Image
https://ghi.teenax.com/g/2/z/-/Uw6Z9q9wwW1cHHGGhhA.jpg
h2
859.74700003862
1083.5489998572
23400
22407
200
image/jpeg
Image
https://ghi.teenax.com/g/h/Z/v/CbsuWf6W5F6aio08ygA.jpg
h2
860.05699983798
941.48799986579
16076
15068
200
image/jpeg
Image
https://jkl.teenax.com/k/B/4/g/J3K5YrmTp440T3_QWhg.jpg
h2
860.65399996005
962.1979999356
14476
13472
200
image/jpeg
Image
https://stu.teenax.com/s/g/d/D/BzExXCPJCFhLm0QSOMQ.jpg
h2
860.8289998956
964.95900000446
14885
13883
200
image/jpeg
Image
https://jkl.teenax.com/l/f/9/8/Fx5ed1p5IyxRrYU3AoA.jpg
h2
860.98099988885
1066.11899985
23190
22195
200
image/jpeg
Image
https://stu.teenax.com/t/w/5/w/BgGm6cUY_a2Q70HrlaA.jpg
h2
861.71599989757
975.05100001581
15438
14436
200
image/jpeg
Image
https://ghi.teenax.com/g/Z/m/4/uHN9kVphieam_Ge8mQA.jpg
h2
862.65499982983
1044.5639998652
15188
14181
200
image/jpeg
Image
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)
421.776
13.71
436.609
5.448
528.449
14.076
543.14
38.867
582.259
51.682
634.048
114.84
752.657
137.209
889.92
30.184
933.725
23.717
966.666
12.465
994.35
15.384
1022.144
15.155
1047.514
13.88
1062.986
12.169
1077.151
11.841
1094.263
14.295
1111.479
10.31
1127.008
9.85
1251.124
10.704
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. Teenax.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Teenax.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Teenax.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Teenax.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Teenax.com 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 — Potential savings of 128 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://teenax.com/img/famfamfam-flags.png
76543
57051
https://jkl.teenax.com/j/-/P/A/Yk1Ppcm9zmqVUV7Wzzw.jpg
28221
10836.35
https://jkl.teenax.com/l/f/9/8/Fx5ed1p5IyxRrYU3AoA.jpg
22195
9512.85
https://ghi.teenax.com/g/Y/q/q/tjyjk7lsQ1dz6-jFtdg.jpg
22503
9431.7
https://mno.teenax.com/m/g/4/C/mtcrNcn4Dm40_rkwIYw.jpg
22085
9233.65
https://pqr.teenax.com/p/m/r/R/aizza82hkoh-IsjF1Hw.jpg
22370
9182
https://ghi.teenax.com/g/2/z/-/Uw6Z9q9wwW1cHHGGhhA.jpg
22407
9179.65
https://mno.teenax.com/n/b/2/W/ngpWtt90xzGgrI2Pz8w.jpg
20939
8330.05
https://pqr.teenax.com/q/_/0/Z/gDoc8ZRGNd7GrdVF14w.jpg
18713
8242.2
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 240 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://teenax.com/en/territory-US.html
235.687
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Teenax.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://teenax.com/
190
https://teenax.com/en/territory-US.html
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Teenax.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://teenax.com/img/l.png
0
Avoids enormous network payloads — Total size was 861 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://teenax.com/img/famfamfam-flags.png
77518
https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js
69027
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
35030
https://jkl.teenax.com/j/-/P/A/Yk1Ppcm9zmqVUV7Wzzw.jpg
29223
https://ghi.teenax.com/g/Y/q/q/tjyjk7lsQ1dz6-jFtdg.jpg
23503
https://ghi.teenax.com/g/2/z/-/Uw6Z9q9wwW1cHHGGhhA.jpg
23400
https://pqr.teenax.com/p/m/r/R/aizza82hkoh-IsjF1Hw.jpg
23374
https://jkl.teenax.com/l/f/9/8/Fx5ed1p5IyxRrYU3AoA.jpg
23190
https://mno.teenax.com/m/g/4/C/mtcrNcn4Dm40_rkwIYw.jpg
23085
https://teenax.com/en/territory-US.html
22862
Uses efficient cache policy on static assets — 0 resources found
Teenax.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Teenax.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.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://teenax.com/en/territory-US.html
383.366
4.18
1.317
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
188.609
151.715
1.566
Unattributable
54.023
3.472
0.135
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)
Style & Layout
187.411
Script Evaluation
178.801
Rendering
132.931
Other
123.191
Parse HTML & CSS
23.095
Script Parsing & Compilation
6.794
Garbage Collection
3.613
Keep request counts low and transfer sizes small — 52 requests • 861 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
52
881999
Image
39
712795
Script
4
109977
Stylesheet
5
25948
Document
1
22862
Font
1
8367
Other
2
2050
Media
0
0
Third-party
5
123106
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)
113550
40.143
9556
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
3.2939322301024E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 3 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://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
1223
69
https://teenax.com/en/territory-US.html
204
57
https://teenax.com/js/ytzjifjgcung.js?v4447
620
52
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 teenax.com on mobile screens.

Budgets

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

Other

Eliminate render-blocking resources — Potential savings of 460 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Teenax.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/themes/smoothness/jquery-ui.css
9493
230
Reduce unused JavaScript — Potential savings of 59 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://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js
69027
60035

Other

Avoid an excessive DOM size — 3,831 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
3831
Maximum DOM Depth
10
Maximum Child Elements
120
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://fonts.gstatic.com/s/russoone/v14/Z9XUDmZRWg6M1LvRYsHOz8mJvLuL9A.woff2
3.3849999308586
Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
71

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
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.

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.

Names and labels

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

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.

Audio and video

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

Names and labels

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

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
442
412
42
558
205
444
94
469
140
455
912
167
629
108
708
552
948
341
438
163
636
270
701
889
255
956
819
637
655
289
47
656
626
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

Navigation

Heading elements are not 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.
Failing Elements
MOM

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
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.
83

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
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
1.12.4
jQuery UI
1.12.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://teenax.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 7 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium
3
High
73

SEO

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

Mobile Friendly

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

Content Best Practices

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

Crawling and Indexing

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

Content Best Practices

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

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

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of teenax.com on mobile screens.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide 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 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) 66
Performance 77
Accessibility 71
Best Practices 75
SEO 77
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://teenax.com
Updated: 4th July, 2022

3.17 seconds
First Contentful Paint (FCP)
42%
30%
28%

0.05 seconds
First Input Delay (FID)
95%
4%
1%

77

Performance

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

Metrics

Speed Index — 2.8 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 140 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.002
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Teenax.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Teenax.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Teenax.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Teenax.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Teenax.com 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.
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 40 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://teenax.com/en/territory-US.html
39.454
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Teenax.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://teenax.com/
630
https://teenax.com/en/territory-US.html
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Teenax.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Avoids enormous network payloads — Total size was 381 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
98217
https://teenax.com/img/famfamfam-flags.png
77520
https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js
69027
https://ghi.teenax.com/g/Y/q/q/tjyjk7lsQ1dz6-jFtdg.jpg
23509
https://teenax.com/en/territory-US.html
22789
https://jkl.teenax.com/l/B/B/L/9dhZBLj76sxmpBIxITg.jpg
19035
https://mno.teenax.com/m/4/4/i/r-QklSZd05FkuntaFPw.jpg
16974
https://ghi.teenax.com/h/3/G/G/1DqKpO_nO8Hw4cKjaEw.jpg
16195
https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/themes/smoothness/jquery-ui.css
9491
https://fonts.gstatic.com/s/russoone/v14/Z9XUDmZRWg6M1LvRYsHOz8mJvLuL9A.woff2
8366
Uses efficient cache policy on static assets — 0 resources found
Teenax.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Teenax.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://teenax.com/en/territory-US.html
656.748
14.148
5.412
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
357.892
277.844
5.376
Unattributable
114.736
10.28
0.616
https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js
67.2
54.164
12.572
Minimizes main-thread work — 1.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
439.456
Script Evaluation
358.024
Other
220.1
Rendering
108.828
Parse HTML & CSS
76.836
Script Parsing & Compilation
25.036
Keep request counts low and transfer sizes small — 21 requests • 381 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
21
389850
Script
4
173160
Image
8
157547
Stylesheet
5
25948
Document
1
22789
Font
1
8366
Other
2
2040
Media
0
0
Third-party
5
186290
Minimize third-party usage — Third-party code blocked the main thread for 140 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)
176735
140.124
9555
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0022748517990112
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 — 5 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://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
4646
242
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
4888
133
https://teenax.com/en/territory-US.html
630
122
https://teenax.com/en/territory-US.html
1260
56
https://teenax.com/en/territory-US.html
1359
50
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 teenax.com on mobile screens.

Budgets

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

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://teenax.com/
http/1.1
0
151.09499986283
940
0
302
text/html
https://teenax.com/en/territory-US.html
h2
151.54200000688
190.00299996696
22789
173985
200
text/html
Document
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
h2
202.75499997661
208.95999995992
98217
97163
200
text/javascript
Script
https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js
h2
202.90499995463
209.77399987169
69027
253668
200
text/javascript
Script
https://teenax.com/js/ytzjifjgcung.js?v4447
h2
210.3740000166
236.43299983814
4433
10280
200
application/x-javascript
Script
https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/themes/smoothness/jquery-ui.css
h2
203.39199993759
208.43499992043
9491
36536
200
text/css
Stylesheet
https://teenax.com/css/style.css?1.177
h2
203.52099998854
243.90199990012
6625
38799
200
text/css
Stylesheet
https://teenax.com/css/tuning.css?1.0
h2
203.74399982393
240.96299987286
1058
188
200
text/css
Stylesheet
https://teenax.com/js/custom.js?1.1
h2
210.6709999498
234.60899991915
1483
2318
200
application/x-javascript
Script
https://fonts.googleapis.com/css?family=Russo+One
h2
245.79199985601
263.48900003359
1189
987
200
text/css
Stylesheet
https://teenax.com/fonts/fontello.css
h2
246.03999988176
271.0659999866
7585
10191
200
text/css
Stylesheet
https://teenax.com/img/famfamfam-flags.png
h2
277.21700002439
312.91799992323
77520
76543
200
image/png
Image
https://fonts.gstatic.com/s/russoone/v14/Z9XUDmZRWg6M1LvRYsHOz8mJvLuL9A.woff2
h2
277.6559998747
281.98900003918
8366
7440
200
font/woff2
Font
data
277.46500005014
291.04200005531
5888
5888
200
application/octet-stream
Font
https://teenax.com/img/l.png
h2
341.30900003947
363.70699992403
1977
1006
200
image/png
Image
https://teenax.com/img/imgbg.png
h2
341.77899989299
365.16899988055
1122
153
200
image/png
Image
https://teenax.com/t/in
h2
438.4850000497
580.96099994145
1100
15
200
application/json
XHR
data
494.32499986142
494.46099996567
0
43
200
image/gif
Image
https://teenax.com/img/btt.png
h2
497.8650000412
523.50199990906
1215
246
200
image/png
Image
https://mno.teenax.com/m/4/4/i/r-QklSZd05FkuntaFPw.jpg
h2
498.03199991584
529.47700000368
16974
15972
200
image/jpeg
Image
https://ghi.teenax.com/g/Y/q/q/tjyjk7lsQ1dz6-jFtdg.jpg
h2
498.66100004874
523.16899993457
23509
22503
200
image/jpeg
Image
https://ghi.teenax.com/h/3/G/G/1DqKpO_nO8Hw4cKjaEw.jpg
h2
498.784000054
525.82799992524
16195
15189
200
image/jpeg
Image
https://jkl.teenax.com/l/B/B/L/9dhZBLj76sxmpBIxITg.jpg
h2
499.09000005573
524.63399991393
19035
18027
200
image/jpeg
Image
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)
216.485
14.07
299.468
14.523
318.731
12.445
331.208
60.569
391.936
60.961
456.319
66.544
522.921
13.525
550.195
5.987
564.232
5.924
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.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 4.4 s
The time taken for the page to become fully interactive.

Audits

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

Other

Serve images in next-gen formats — Potential savings of 65 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://teenax.com/img/famfamfam-flags.png
76543
57051
https://ghi.teenax.com/g/Y/q/q/tjyjk7lsQ1dz6-jFtdg.jpg
22503
9431.7
Enable text compression — Potential savings of 62 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
97163
63370
Preload Largest Contentful Paint image — Potential savings of 780 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://mno.teenax.com/m/4/4/i/r-QklSZd05FkuntaFPw.jpg
780

Metrics

Largest Contentful Paint — 4.4 s
The timing of the largest text or image that is painted.

Other

Eliminate render-blocking resources — Potential savings of 1,550 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Teenax.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/themes/smoothness/jquery-ui.css
9491
780
Reduce unused JavaScript — Potential savings of 99 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://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js
69027
60035
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
98217
41266
Avoid an excessive DOM size — 3,831 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
3831
Maximum DOM Depth
10
Maximum Child Elements
120
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://fonts.gstatic.com/s/russoone/v14/Z9XUDmZRWg6M1LvRYsHOz8mJvLuL9A.woff2
4.333000164479
Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
First Contentful Paint (3G) — 5520 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
71

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
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.

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.

Names and labels

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

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.

Audio and video

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

Names and labels

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

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
442
412
42
558
205
444
94
469
140
455
912
167
629
108
708
552
948
341
438
163
636
270
701
889
255
956
819
637
655
289
47
656
626
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

Navigation

Heading elements are not 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.
Failing Elements
MOM

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
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 teenax.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
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.
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
1.12.4
jQuery UI
1.12.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://teenax.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 7 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium
3
High

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://mno.teenax.com/m/4/4/i/r-QklSZd05FkuntaFPw.jpg
353 x 265
265 x 199
706 x 530
77

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of teenax.com on mobile screens.
Document uses legible font sizes — 75.72% 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
.az ul li span
3.00%
10px
.header
0.42%
10px
20.87%
< 12px
75.72%
≥ 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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

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

Content Best Practices

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

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

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of teenax.com on mobile screens.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide 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 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.233.196
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: DANESCO TRADING LTD
Organization: DANESCO TRADING LTD.
Country: Cyprus
City: Limassol
State:
Post Code: 3026
Email: teenax.com@whoisprotectservice.net
Phone: +357.95713635
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Public Interest Registry 88.208.29.137
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: teenax.com
Issued By: WE1
Valid From: 30th August, 2024
Valid To: 28th November, 2024
Subject: CN = teenax.com
Hash: e10fef2c
Issuer: CN = WE1
O = Google Trust Services
S = US
Version: 2
Serial Number: 0x954213B162913B4F0D1B8F982C3120AD
Serial Number (Hex): 954213B162913B4F0D1B8F982C3120AD
Valid From: 30th August, 2024
Valid To: 28th November, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:90:77:92:35:67:C4:FF:A8:CC:A9:E6:7B:D9:80:79:7B:CC:93:F9:38
Extended Key Usage: TLS Web Server Authentication
CRL Distribution Points:
Full Name:
URI:http://c.pki.goog/we1/r1Lq4vMcD8c.crl

Certificate Policies: Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://o.pki.goog/s/we1/lUI
CA Issuers - URI:http://i.pki.goog/we1.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 : Aug 30 03:18:05.098 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:1B:2B:33:75:51:2B:64:1D:87:E8:0B:23:
16:EF:2C:0E:FA:48:36:43:E5:47:61:06:B5:DE:CA:70:
A7:57:17:76:02:20:50:27:85:15:40:DA:17:B5:FE:34:
B5:5B:96:C5:62:EA:6A:4B:69:59:C9:CA:7D:6E:B1:1B:
0B:A4:5F:AA:D5:BD
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
Timestamp : Aug 30 03:18:05.263 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:46:01:44:AD:CA:EC:84:1F:42:49:22:76:
4A:06:F9:B8:ED:75:E7:6F:C3:A3:E1:FD:4E:E7:51:28:
FE:08:47:17:02:20:79:04:A5:D2:D0:F5:B5:31:91:8C:
E1:C8:C7:94:FD:4C:88:33:F7:58:FB:90:48:3F:DE:A7:
1C:F5:DE:39:E8:08
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.teenax.com
DNS:teenax.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
teenax.com. 46.229.165.145 IN 3599

NS Records

Host Nameserver Class TTL
teenax.com. ns2.cjperl.com. IN 3599
teenax.com. ns1.cjperl.com. IN 3599
teenax.com. ns3.cjperl.com. IN 3599

MX Records

Priority Host Server Class TTL
10 teenax.com. relay.teenax.com. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
teenax.com. ns1.cjperl.com. webmaster.teenax.com. 3599

TXT Records

Host Value Class TTL
teenax.com. v=spf1 IN 3599

HTTP Response Headers

HTTP-Code: HTTP/2 200
date: 18th October, 2024
content-type: text/html; charset=utf-8
cache-control: public, max-age=14400, s-maxage=300, stale-while-revalidate=60, stale-if-error=60, immutable
server: cloudflare
content-language: en
cross-origin-opener-policy: same-origin
rating: RTA-5042-1996-1400-1577-RTA
x-robots-tag: notranslate
x-runtime: 0.004945
strict-transport-security: max-age=15552000; includeSubDomains; preload
x-frame-options: SAMEORIGIN
referrer-policy: unsafe-url
cf-cache-status: HIT
age: 0
last-modified: 18th October, 2024
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=x5GScW0Z0jOdgCfy1smYA6bPhfF%2Bd2ohdR5bBwNHRTxuy0anGQPSNO%2Fmu6aQdLjzJ8gXJX79RzTZ3rGZAsrXLB4MkbOF2YOGn8O4wiRIYpi2QfyNrTyd0ojTUzLf"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
cf-ray: 8d48ada9fb205a27-IAD
alt-svc: h3=":443"; ma=86400

Whois Lookup

Created: 21st July, 2002
Changed: 24th June, 2024
Expires: 21st July, 2025
Status: clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited
Nameservers: cora.ns.cloudflare.com
leland.ns.cloudflare.com
Owner Name: Statutory Masking for data privacy
Owner Organization: Statutory Masking for data privacy
Owner Street: Statutory Masking for data privacy
Owner Post Code: Statutory Masking for data privacy
Owner City: Statutory Masking for data privacy
Owner Country: Statutory Masking for data privacy
Owner Phone: Statutory Masking for data privacy
Owner Email: teenax.com@whoisprotectservice.net
Admin Name: Statutory Masking for data privacy
Admin Organization: Statutory Masking for data privacy
Admin Street: Statutory Masking for data privacy
Admin Post Code: Statutory Masking for data privacy
Admin City: Statutory Masking for data privacy
Admin Country: Statutory Masking for data privacy
Admin Phone: Statutory Masking for data privacy
Admin Email: teenax.com@whoisprotectservice.net
Tech Name: Statutory Masking for data privacy
Tech Organization: Statutory Masking for data privacy
Tech Street: Statutory Masking for data privacy
Tech Post Code: Statutory Masking for data privacy
Tech City: Statutory Masking for data privacy
Tech Country: Statutory Masking for data privacy
Tech Phone: Statutory Masking for data privacy
Tech Email: teenax.com@whoisprotectservice.net
Billing Name: Statutory Masking for data privacy
Billing Organization: Statutory Masking for data privacy
Billing Street: Statutory Masking for data privacy
Billing Post Code: Statutory Masking for data privacy
Billing City: Statutory Masking for data privacy
Billing Country: Statutory Masking for data privacy
Billing Phone: Statutory Masking for data privacy
Billing Fax: Statutory Masking for data privacy
Billing Email: teenax.com@whoisprotectservice.net
Full Whois:
Danesco Trading LLC shall not bear responsibility for consequences regarding
operations with or content of on-line resources available via the registered
domain name.

Danesco Trading LLC protects the WhoIs Data under the law or the Registrants’
requests using special notifications as follows “Statutory masking for data
privacy”. If you have a legitimate interest in viewing the redacted WHOIS
details, send us a request.

Domain Name: TEENAX.COM
Domain ID: 88597186_DOMAIN_COM-VRSN
Creation Date: 2002-07-21T16:51:47Z
Updated Date: 2024-06-24T09:48:45Z
Registry Expiry Date: 2025-07-21T16:51:47Z
Registrar Registration Expiration Date: 2025-07-21T16:51:47Z
Domain Status: clientDeleteProhibited
Domain Status: clientTransferProhibited
Domain Status: clientUpdateProhibited
Registrant ID: MI_5485626WP
Registrant Name: Statutory Masking for data privacy
Registrant Organization: Statutory Masking for data privacy
Registrant Street: Statutory Masking for data privacy
Registrant City: Statutory Masking for data privacy
Registrant Postal Code: Statutory Masking for data privacy
Registrant Country: Statutory Masking for data privacy
Registrant Phone: Statutory Masking for data privacy
Registrant Fax: Statutory Masking for data privacy
Registrant Email: teenax.com@whoisprotectservice.net
Admin ID: MI_5485626WP
Admin Name: Statutory Masking for data privacy
Admin Organization: Statutory Masking for data privacy
Admin Street: Statutory Masking for data privacy
Admin City: Statutory Masking for data privacy
Admin Postal Code: Statutory Masking for data privacy
Admin Country: Statutory Masking for data privacy
Admin Phone: Statutory Masking for data privacy
Admin Fax: Statutory Masking for data privacy
Admin Email: teenax.com@whoisprotectservice.net
Tech ID: MI_5485626WP
Tech Name: Statutory Masking for data privacy
Tech Organization: Statutory Masking for data privacy
Tech Street: Statutory Masking for data privacy
Tech City: Statutory Masking for data privacy
Tech Postal Code: Statutory Masking for data privacy
Tech Country: Statutory Masking for data privacy
Tech Phone: Statutory Masking for data privacy
Tech Fax: Statutory Masking for data privacy
Tech Email: teenax.com@whoisprotectservice.net
Billing ID: MI_5485626WP
Billing Name: Statutory Masking for data privacy
Billing Organization: Statutory Masking for data privacy
Billing Street: Statutory Masking for data privacy
Billing City: Statutory Masking for data privacy
Billing Postal Code: Statutory Masking for data privacy
Billing Country: Statutory Masking for data privacy
Billing Phone: Statutory Masking for data privacy
Billing Fax: Statutory Masking for data privacy
Billing Email: teenax.com@whoisprotectservice.net
Name Server: cora.ns.cloudflare.com
Name Server: leland.ns.cloudflare.com
DNSSEC: unsigned

URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-10-18T12:54:42Z <<<

Danesco Trading LLC acts as a Domain Name Registrar only, provides to
Registrants registration and related services, and complies with ICANN rules and
policies.

Danesco Trading LLC shall not bear any responsibility for any consequences
regarding operations with or content of on-line resources available via the
registered domain name unless otherwise provided by law.

The Registrant is solely responsible for compliance with the jurisdiction laws
for which his website, web resource, goods, services, or Content is available.

The WhoIs Data is provided for information purposes only. The fact that Danesco
Trading LLC displays such information does not provide any guarantee expressed
or implied on the purpose for which the database may be used, its accuracy or
usefulness. By submitting a WHOIS query, you agree that you will use this Data
only for lawful purposes. Danesco Trading LLC cannot guarantee the accuracy of
the data provided.

Danesco Trading LLC protects the WhoIs Data under the law or the Registrants’
requests using special notifications as follows “Statutory masking for data
privacy”. If you have a legitimate interest in viewing the redacted WHOIS
details, send your request to the Registrar's email with the reasons for your
request. We will review that request and may ask for supporting documentation
and explanation.

Please use the Registrar's email if you wish to raise a legal issue connected
with the Registrant, operations with or content of resources available via the
registered domain name. Danesco Trading LLC has the ability to contact the
Registrant with the requirement to investigate a legal issue.

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

Nameservers

Name IP Address
cora.ns.cloudflare.com 162.159.38.195
leland.ns.cloudflare.com 172.64.35.8
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$2,059 USD 2/5
$2,615 USD 2/5
0/5
$761 USD 1/5
$917 USD 1/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$435 USD 1/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$984 USD 1/5