18boyz.com

18boyz.com is SSL secured

Free website and domain report on 18boyz.com

Last Updated: 21st August, 2024 Update Now
Overview

Snoop Summary for 18boyz.com

This is a free and comprehensive report about 18boyz.com. 18boyz.com is hosted in Canada on a server with an IP address of 198.50.193.57, where CAD is the local currency and the local language is English. Our records indicate that 18boyz.com is privately registered by See PrivacyGuardian.org. 18boyz.com has the potential to be earning an estimated $4 USD per day from advertising revenue. If 18boyz.com was to be sold it would possibly be worth $3,139 USD (based on the daily revenue potential of the website over a 24 month period). 18boyz.com receives an estimated 1,504 unique visitors every day - a large amount of traffic! This report was last updated 21st August, 2024.

About 18boyz.com

Site Preview:
Title:
Description: Naughty twink boys and their gay boyfriends are up for a big show that involves sweet anal sex and incredibile blowjob by handsome and sexy men.
Keywords and Tags: adult content, pornography, teen gay porn, twinks gay sex, young gay
Related Terms: boyfriends, ex boyfriends, jawga boyz
Fav Icon:
Age: Over 20 years old
Domain Created: 8th September, 2004
Domain Updated: 9th August, 2024
Domain Expires: 8th September, 2024
Review

Snoop Score

2/5

Valuation

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

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 546,503
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,504
Monthly Visitors: 45,777
Yearly Visitors: 548,960
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $4 USD
Monthly Revenue: $130 USD
Yearly Revenue: $1,565 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: 18boyz.com 10
Domain Name: 18boyz 6
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.39 seconds
Load Time Comparison: Faster than 96% of sites

PageSpeed Insights

Avg. (All Categories) 69
Performance 100
Accessibility 39
Best Practices 83
SEO 92
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://18boyz.com/
Updated: 3rd November, 2022

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

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

100

Performance

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

Metrics

First Contentful Paint — 0.4 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.4 s
The time taken for the page to become fully interactive.
Speed Index — 0.7 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 0.4 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.06
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.4 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://18boyz.com/
http/1.1
0
167.84400003962
272
0
301
text/html
https://18boyz.com/
http/1.1
168.14800002612
570.19800000126
18031
97897
200
text/html
Document
https://18boyz.com/images/logo.png
http/1.1
577.93500000844
719.51700001955
12926
12594
200
image/png
Image
https://cdn.18boyz.com/pics/gl.png
http/1.1
578.08900001692
866.60300003132
2087
1757
200
image/png
Image
https://cdn.18boyz.com/pics/bpp.png
http/1.1
586.57600003062
884.68800002011
1712
1382
200
image/png
Image
https://cdn.18boyz.com/pics/cam.png
http/1.1
586.77799999714
889.83400003053
1699
1369
200
image/png
Image
https://cdn.18boyz.com/pics/dating.png
http/1.1
587.00600004522
865.99600000773
1850
1520
200
image/png
Image
https://cdn.18boyz.com/pics/girl.png
http/1.1
587.22500002477
859.32000004686
3889
3559
200
image/png
Image
https://18boyz.com/images/bg.jpg
http/1.1
588.83500000229
935.12100004591
905
575
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/ah/416776.jpg
http/1.1
598.39300002204
910.30899999896
61668
61335
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Xe/309494.jpg
http/1.1
598.86299999198
884.36600001296
15503
15170
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/ah/416055.jpg
http/1.1
599.19300000183
952.30100001208
62311
61978
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Vg/411652.jpg
http/1.1
599.34000001522
925.15700001968
54561
54228
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Pf/353590.jpg
http/1.1
599.71999999834
857.58300003363
9998
9666
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Te/305154.jpg
http/1.1
600.03900004085
917.54200001014
17004
16671
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/af/312700.jpg
http/1.1
600.213000027
901.95200004382
14430
14097
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Zf/363870.jpg
http/1.1
600.4430000321
994.9079999933
10151
9819
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Ug/410010.jpg
http/1.1
600.83200002555
936.23500003014
39952
39619
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/fg/369914.jpg
http/1.1
601.03399999207
891.61200000672
15213
14880
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Eg/394444.jpg
http/1.1
601.21799999615
860.0640000077
11166
10833
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/fg/369216.jpg
http/1.1
601.40899999533
889.22800001455
10463
10130
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Te/305080.jpg
http/1.1
601.8360000453
882.42800004082
12118
11785
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Ve/307763.jpg
http/1.1
611.40200000955
904.51600000961
20344
20011
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Zf/363926.jpg
http/1.1
611.55100003816
901.22100000735
13227
12894
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Eg/394159.jpg
http/1.1
611.87500000233
936.76700000651
14351
14018
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/qh/432172.jpg
http/1.1
612.23900003824
947.40200001979
61304
60971
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Xf/361835.jpg
http/1.1
612.57100000512
909.97500001686
18720
18387
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Fg/395798.jpg
http/1.1
612.96600004425
868.84100001771
10898
10565
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Ue/306799.jpg
http/1.1
613.34600002738
946.01800001692
22945
22612
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/De/289241.jpg
http/1.1
613.57800004771
854.93100003805
13892
13559
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/239/239712.jpg
http/1.1
613.83099999512
889.49500001036
9900
9568
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Yg/414905.jpg
http/1.1
614.00500003947
945.63299999572
63772
63439
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Hh/449471.jpg
http/1.1
614.12800004473
913.90099999262
59244
58911
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/238/238552.jpg
http/1.1
614.43700001109
915.52100004628
20157
19824
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/De/289966.jpg
http/1.1
614.70700002974
939.99300000723
21586
21253
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Zg/415981.jpg
http/1.1
614.89299999084
946.45000004675
55899
55566
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Fh/447968.jpg
http/1.1
615.3640000266
917.12200001348
80314
79980
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Se/304013.jpg
http/1.1
615.71300000651
858.75300003681
12784
12451
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Se/304571.jpg
http/1.1
615.96900003497
856.57000000356
9430
9098
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/We/308073.jpg
http/1.1
616.23600003077
904.81999999611
16191
15858
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Ye/310244.jpg
http/1.1
616.39999999898
858.02099999273
9857
9525
200
image/jpeg
Image
https://cdn.18boyz.com/gals/chatur/bcam7.jpg
http/1.1
616.70200002845
920.03600002499
19169
18836
200
image/jpeg
Image
https://cdn.18boyz.com/gals/engbo19.jpg
http/1.1
617.02599999262
913.3359999978
21551
21218
200
image/jpeg
Image
https://18boyz.com/tmb/dat1.jpg
http/1.1
617.23800003529
852.1330000367
15841
15508
200
image/jpeg
Image
https://cdn.18boyz.com/gals/alexb11.jpg
http/1.1
617.40300001111
893.30500003416
29156
28823
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Xg/413567.jpg
http/1.1
619.21700002858
924.48899999727
62757
62424
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Xf/361474.jpg
http/1.1
619.31999999797
914.31200003717
14121
13788
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Gh/448930.jpg
http/1.1
620.09899999248
928.12600004254
58997
58664
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Hf/345085.jpg
http/1.1
679.62400004035
902.6250000461
13484
13151
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/bf/313585.jpg
http/1.1
680.09199999506
891.24600001378
18168
17835
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Ve/307462.jpg
http/1.1
680.38800003706
875.86100003682
13320
12987
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Qe/302947.jpg
http/1.1
680.57300004875
880.53500000387
13418
13085
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Yg/414090.jpg
http/1.1
680.74300000444
934.63000003248
52642
52309
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/197/197429.jpg
http/1.1
680.93100003898
904.085999995
17932
17599
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Wg/412008.jpg
http/1.1
681.17900000652
919.64100004407
45423
45090
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Ee/290361.jpg
http/1.1
681.33500003023
905.97500000149
16717
16384
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/dg/367466.jpg
http/1.1
681.78899999475
902.31100004166
8393
8061
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Qf/354939.jpg
http/1.1
681.97800003691
905.44699999737
15780
15447
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Xg/413729.jpg
http/1.1
682.14400002034
928.82700002519
45249
44916
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Vf/359092.jpg
http/1.1
682.56800004747
906.24199999729
14845
14512
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/217/217318.jpg
http/1.1
682.79799999436
934.08100004308
15052
14719
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/fg/369805.jpg
http/1.1
682.95700004091
995.26500003412
12432
12099
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Hh/449187.jpg
http/1.1
683.20200004382
926.87700001989
50359
50026
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Zg/415130.jpg
http/1.1
683.37500002235
935.51500001922
62678
62345
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Ug/410847.jpg
http/1.1
683.78800002392
953.74399999855
63316
62983
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/De/289665.jpg
http/1.1
683.92400001176
1017.6600000123
17031
16698
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Tg/409823.jpg
http/1.1
684.07300004037
998.39600000996
58427
58094
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Ee/290654.jpg
http/1.1
684.22100000316
1019.8830000008
17367
17034
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Vg/411058.jpg
http/1.1
684.3640000443
1153.2400000142
43945
43612
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Wg/412919.jpg
http/1.1
684.50600001961
999.0070000058
36040
35707
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Eh/446736.jpg
http/1.1
684.98600000748
1045.4460000037
45993
45660
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Zf/363880.jpg
http/1.1
685.12199999532
996.72100000316
11979
11646
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Wg/412720.jpg
http/1.1
685.232000018
1020.3709999914
49909
49576
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Vg/411390.jpg
http/1.1
685.40000001667
1142.5990000134
58108
57775
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Uf/358619.jpg
http/1.1
685.52600004477
1022.6390000316
11011
10678
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Ee/290444.jpg
http/1.1
685.65100000706
997.85500002326
16054
15721
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Fh/447159.jpg
http/1.1
685.74700003956
1046.7650000355
55662
55329
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Dh/445029.jpg
http/1.1
686.136000033
1047.2600000212
67623
67289
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Xe/309816.jpg
http/1.1
686.30300002405
1021.1850000196
16019
15686
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Wg/412385.jpg
http/1.1
686.49100000039
1021.5460000327
68987
68653
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Wg/412471.jpg
http/1.1
686.63300003391
1043.3910000138
54700
54367
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/af/312618.jpg
http/1.1
686.81800004561
1017.0750000398
21047
20714
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/195/195706.jpg
http/1.1
686.97100004647
1017.9810000118
13448
13115
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Ve/307990.jpg
http/1.1
687.08599999081
1020.8200000343
13650
13317
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Ue/306824.jpg
http/1.1
687.21599999117
1017.4209999968
10959
10626
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/216/216008.jpg
http/1.1
687.38000001758
1016.6000000318
13089
12756
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/xh/439401.jpg
http/1.1
690.30400004704
999.44300000789
53830
53497
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Yg/414950.jpg
http/1.1
692.30600004084
997.27500003064
41172
40839
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/ah/416240.jpg
http/1.1
692.40100000752
1044.9789999984
54016
53683
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/237/237260.jpg
http/1.1
692.5400000182
995.90999999782
9061
8729
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/De/289609.jpg
http/1.1
692.65400001314
1146.911000018
22079
21746
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Xg/413111.jpg
http/1.1
692.76400003582
1023.3590000425
42698
42365
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Tg/409828.jpg
http/1.1
692.84500001231
1043.8089999952
51520
51187
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)
574.296
10.365
589.18
14.056
606.128
12.183
620.335
22.085
642.596
46.358
883.017
8.062
907.781
8.203
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
Resources, such as JavaScript and style sheets, can block the first paint of the page. 18boyz.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 11 KiB
Images can slow down the page's load time. 18boyz.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://18boyz.com/images/logo.png
12594
6522
https://cdn.18boyz.com/gals/chatur/bcam7.jpg
18836
4302
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. 18boyz.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 18boyz.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 18boyz.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 18boyz.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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 400 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://18boyz.com/
403.045
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. 18boyz.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://18boyz.com/
190
https://18boyz.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. 18boyz.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 2,528 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://cdn.18boyz.com/sr/thumbs/Fh/447968.jpg
80314
https://cdn.18boyz.com/sr/thumbs/Wg/412385.jpg
68987
https://cdn.18boyz.com/sr/thumbs/Dh/445029.jpg
67623
https://cdn.18boyz.com/sr/thumbs/Yg/414905.jpg
63772
https://cdn.18boyz.com/sr/thumbs/Ug/410847.jpg
63316
https://cdn.18boyz.com/sr/thumbs/Xg/413567.jpg
62757
https://cdn.18boyz.com/sr/thumbs/Zg/415130.jpg
62678
https://cdn.18boyz.com/sr/thumbs/ah/416055.jpg
62311
https://cdn.18boyz.com/sr/thumbs/ah/416776.jpg
61668
https://cdn.18boyz.com/sr/thumbs/qh/432172.jpg
61304
Uses efficient cache policy on static assets — 0 resources found
18boyz.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 — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. 18boyz.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.0 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://18boyz.com/
157.412
10.787
1.429
Unattributable
55.59
2.008
0
Minimizes main-thread work — 0.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)
Other
70.607
Rendering
63.718
Style & Layout
56.059
Script Evaluation
12.795
Parse HTML & CSS
8.394
Script Parsing & Compilation
1.429
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 — 93 requests • 2,528 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
93
2588948
Image
91
2570645
Document
1
18031
Other
1
272
Stylesheet
0
0
Media
0
0
Font
0
0
Script
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 — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.039195606178016
0.021199546610706
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of 18boyz.com 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

Efficiently encode images — Potential savings of 1,211 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn.18boyz.com/sr/thumbs/Fh/447968.jpg
79980
56784
https://cdn.18boyz.com/sr/thumbs/Wg/412385.jpg
68653
47732
https://cdn.18boyz.com/sr/thumbs/Dh/445029.jpg
67289
46465
https://cdn.18boyz.com/sr/thumbs/ah/416055.jpg
61978
44393
https://cdn.18boyz.com/sr/thumbs/Ug/410847.jpg
62983
43931
https://cdn.18boyz.com/sr/thumbs/Zg/415130.jpg
62345
43351
https://cdn.18boyz.com/sr/thumbs/Xg/413567.jpg
62424
43347
https://cdn.18boyz.com/sr/thumbs/ah/416776.jpg
61335
43264
https://cdn.18boyz.com/sr/thumbs/Yg/414905.jpg
63439
42796
https://cdn.18boyz.com/sr/thumbs/qh/432172.jpg
60971
42628
https://cdn.18boyz.com/sr/thumbs/Tg/409823.jpg
58094
41092
https://cdn.18boyz.com/sr/thumbs/Gh/448930.jpg
58664
40833
https://cdn.18boyz.com/sr/thumbs/Hh/449471.jpg
58911
40572
https://cdn.18boyz.com/sr/thumbs/Vg/411390.jpg
57775
40528
https://cdn.18boyz.com/sr/thumbs/Zg/415981.jpg
55566
40203
https://cdn.18boyz.com/sr/thumbs/Vg/411652.jpg
54228
38705
https://cdn.18boyz.com/sr/thumbs/Fh/447159.jpg
55329
38356
https://cdn.18boyz.com/sr/thumbs/xh/439401.jpg
53497
38240
https://cdn.18boyz.com/sr/thumbs/ah/416240.jpg
53683
38138
https://cdn.18boyz.com/sr/thumbs/Wg/412471.jpg
54367
37885
https://cdn.18boyz.com/sr/thumbs/Yg/414090.jpg
52309
37472
https://cdn.18boyz.com/sr/thumbs/Hh/449187.jpg
50026
36451
https://cdn.18boyz.com/sr/thumbs/Wg/412720.jpg
49576
35452
https://cdn.18boyz.com/sr/thumbs/Tg/409828.jpg
51187
35445
https://cdn.18boyz.com/sr/thumbs/Eh/446736.jpg
45660
34151
https://cdn.18boyz.com/sr/thumbs/Xg/413729.jpg
44916
33087
https://cdn.18boyz.com/sr/thumbs/Wg/412008.jpg
45090
32856
https://cdn.18boyz.com/sr/thumbs/Vg/411058.jpg
43612
30801
https://cdn.18boyz.com/sr/thumbs/Yg/414950.jpg
40839
30256
https://cdn.18boyz.com/sr/thumbs/Xg/413111.jpg
42365
30053
https://cdn.18boyz.com/sr/thumbs/Ug/410010.jpg
39619
28726
https://cdn.18boyz.com/sr/thumbs/Wg/412919.jpg
35707
26419
Serve images in next-gen formats — Potential savings of 1,507 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://cdn.18boyz.com/sr/thumbs/Fh/447968.jpg
79980
68268.2
https://cdn.18boyz.com/sr/thumbs/Wg/412385.jpg
68653
57911.55
https://cdn.18boyz.com/sr/thumbs/Dh/445029.jpg
67289
57103.8
https://cdn.18boyz.com/sr/thumbs/Ug/410847.jpg
62983
53731.2
https://cdn.18boyz.com/sr/thumbs/ah/416055.jpg
61978
53372.95
https://cdn.18boyz.com/sr/thumbs/Xg/413567.jpg
62424
53137.95
https://cdn.18boyz.com/sr/thumbs/Yg/414905.jpg
63439
52941.45
https://cdn.18boyz.com/sr/thumbs/Zg/415130.jpg
62345
52929.3
https://cdn.18boyz.com/sr/thumbs/ah/416776.jpg
61335
52124.45
https://cdn.18boyz.com/sr/thumbs/qh/432172.jpg
60971
52074.85
https://cdn.18boyz.com/sr/thumbs/Hh/449471.jpg
58911
50003.85
https://cdn.18boyz.com/sr/thumbs/Gh/448930.jpg
58664
49868.65
https://cdn.18boyz.com/sr/thumbs/Tg/409823.jpg
58094
49766.7
https://cdn.18boyz.com/sr/thumbs/Vg/411390.jpg
57775
49426.45
https://cdn.18boyz.com/sr/thumbs/Zg/415981.jpg
55566
48322.05
https://cdn.18boyz.com/sr/thumbs/Fh/447159.jpg
55329
47093.75
https://cdn.18boyz.com/sr/thumbs/Vg/411652.jpg
54228
47002.45
https://cdn.18boyz.com/sr/thumbs/Wg/412471.jpg
54367
46574.5
https://cdn.18boyz.com/sr/thumbs/ah/416240.jpg
53683
46471.15
https://cdn.18boyz.com/sr/thumbs/xh/439401.jpg
53497
46404.35
https://cdn.18boyz.com/sr/thumbs/Yg/414090.jpg
52309
45373.35
https://cdn.18boyz.com/sr/thumbs/Hh/449187.jpg
50026
43949.05
https://cdn.18boyz.com/sr/thumbs/Tg/409828.jpg
51187
43743.5
https://cdn.18boyz.com/sr/thumbs/Wg/412720.jpg
49576
43125
https://cdn.18boyz.com/sr/thumbs/Eh/446736.jpg
45660
40448.35
https://cdn.18boyz.com/sr/thumbs/Xg/413729.jpg
44916
39541.95
https://cdn.18boyz.com/sr/thumbs/Wg/412008.jpg
45090
39529.1
https://cdn.18boyz.com/sr/thumbs/Vg/411058.jpg
43612
37847.65
https://cdn.18boyz.com/sr/thumbs/Xg/413111.jpg
42365
36679.8
https://cdn.18boyz.com/sr/thumbs/Yg/414950.jpg
40839
36242.05
https://cdn.18boyz.com/sr/thumbs/Ug/410010.jpg
39619
34918.15
https://cdn.18boyz.com/sr/thumbs/Wg/412919.jpg
35707
31615.4
https://cdn.18boyz.com/gals/alexb11.jpg
28823
14276.45
https://cdn.18boyz.com/gals/engbo19.jpg
21218
11304.45
https://cdn.18boyz.com/gals/chatur/bcam7.jpg
18836
10022.25
Avoid an excessive DOM size — 1,500 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
1500
Maximum DOM Depth
9
Maximum Child Elements
100
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://cdn.18boyz.com/gals/engbo19.jpg
https://cdn.18boyz.com/gals/alexb11.jpg
https://cdn.18boyz.com/pics/gl.png
https://cdn.18boyz.com/pics/bpp.png
https://cdn.18boyz.com/pics/cam.png
https://cdn.18boyz.com/pics/dating.png
https://cdn.18boyz.com/pics/girl.png
39

Accessibility

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

Names and labels

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

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
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 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"]`
18boyz.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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

Internationalization and localization

`<html>` element does not have 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.
Failing Elements

Names and labels

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

Tables and lists

List items (`<li>`) are not 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.
Failing Elements

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 18boyz.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

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

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
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.
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://18boyz.com/
Allowed

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
https://cdn.18boyz.com/gals/chatur/bcam7.jpg
300 x 250 (1.20)
360 x 270 (1.33)
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for 18boyz.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 18boyz.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

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

Content Best Practices

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

Manual Checks

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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of 18boyz.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 18boyz.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

1.07 seconds
First Contentful Paint (FCP)
85%
9%
6%

0.02 seconds
First Input Delay (FID)
95%
5%
0%

90

Performance

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

Metrics

First Contentful Paint — 1.3 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.4 s
The time taken for the page to become fully interactive.
Speed Index — 1.3 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 20 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 90 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.3 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://18boyz.com/
http/1.1
0
56.66400003247
272
0
301
text/html
https://18boyz.com/
http/1.1
57.029000017792
314.28599986248
18042
97912
200
text/html
Document
https://18boyz.com/images/logo.png
http/1.1
324.03999986127
466.30600001663
12926
12594
200
image/png
Image
https://cdn.18boyz.com/pics/gl.png
http/1.1
324.26099991426
464.23799986951
2087
1757
200
image/png
Image
https://cdn.18boyz.com/pics/bpp.png
http/1.1
331.2979999464
472.31799992733
1712
1382
200
image/png
Image
https://cdn.18boyz.com/pics/cam.png
http/1.1
331.44599990919
469.15100002661
1699
1369
200
image/png
Image
https://cdn.18boyz.com/pics/dating.png
http/1.1
331.61800005473
468.55599991977
1850
1520
200
image/png
Image
https://cdn.18boyz.com/pics/girl.png
http/1.1
331.79700002074
468.89099990949
3889
3559
200
image/png
Image
https://18boyz.com/images/bg.jpg
http/1.1
334.21500003897
475.73499986902
905
575
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/ah/416776.jpg
http/1.1
341.76400001161
521.38399984688
61668
61335
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Xe/309494.jpg
http/1.1
341.91600000486
490.27099995874
15503
15170
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/ah/416055.jpg
http/1.1
342.08099986427
522.78700005263
62311
61978
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Vg/411652.jpg
http/1.1
342.40299998783
521.95900003426
54561
54228
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Pf/353590.jpg
http/1.1
342.70099992864
463.97399995476
9998
9666
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Te/305154.jpg
http/1.1
343.29900005832
494.5590000134
17004
16671
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/af/312700.jpg
http/1.1
343.53800001554
494.13100001402
14430
14097
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Zf/363870.jpg
http/1.1
343.76799990423
463.73099996708
10151
9819
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Ug/410010.jpg
http/1.1
344.30800005794
489.38799998723
39952
39619
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/fg/369914.jpg
http/1.1
344.55799986608
489.93299994618
15213
14880
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Eg/394444.jpg
http/1.1
344.71999993548
463.34400004707
11166
10833
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/fg/369216.jpg
http/1.1
345.04300006665
462.86899992265
10463
10130
200
image/jpeg
Image
https://cdn.18boyz.com/sr/thumbs/Te/305080.jpg
http/1.1
345.26699990965
474.02099985629
12118
11785
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)
318.055
10.562
328.833
5.53
334.373
12.256
349.653
6.306
358.427
22.712
381.309
33.363
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
Resources, such as JavaScript and style sheets, can block the first paint of the page. 18boyz.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. 18boyz.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. 18boyz.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 18boyz.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 18boyz.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 18boyz.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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 260 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://18boyz.com/
258.251
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. 18boyz.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://18boyz.com/
630
https://18boyz.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. 18boyz.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://cdn.18boyz.com/sr/thumbs/ah/416776.jpg
0
Avoids enormous network payloads — Total size was 369 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://cdn.18boyz.com/sr/thumbs/ah/416055.jpg
62311
https://cdn.18boyz.com/sr/thumbs/ah/416776.jpg
61668
https://cdn.18boyz.com/sr/thumbs/Vg/411652.jpg
54561
https://cdn.18boyz.com/sr/thumbs/Ug/410010.jpg
39952
https://18boyz.com/
18042
https://cdn.18boyz.com/sr/thumbs/Te/305154.jpg
17004
https://cdn.18boyz.com/sr/thumbs/Xe/309494.jpg
15503
https://cdn.18boyz.com/sr/thumbs/fg/369914.jpg
15213
https://cdn.18boyz.com/sr/thumbs/af/312700.jpg
14430
https://18boyz.com/images/logo.png
12926
Uses efficient cache policy on static assets — 0 resources found
18boyz.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 — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. 18boyz.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://18boyz.com/
426.152
51.284
6.272
Unattributable
75
7.036
0
Minimizes main-thread work — 0.5 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
200.764
Other
120.14
Rendering
77.048
Script Evaluation
58.32
Parse HTML & CSS
38.608
Script Parsing & Compilation
6.272
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 — 22 requests • 369 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
22
377920
Image
20
359606
Document
1
18042
Other
1
272
Stylesheet
0
0
Media
0
0
Font
0
0
Script
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
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://18boyz.com/
1349
91
https://18boyz.com/
630
67
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of 18boyz.com 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.
First Contentful Paint (3G) — 2507 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

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

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

Other

Efficiently encode images — Potential savings of 151 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn.18boyz.com/sr/thumbs/ah/416055.jpg
61978
44393
https://cdn.18boyz.com/sr/thumbs/ah/416776.jpg
61335
43264
https://cdn.18boyz.com/sr/thumbs/Vg/411652.jpg
54228
38705
https://cdn.18boyz.com/sr/thumbs/Ug/410010.jpg
39619
28726
Serve images in next-gen formats — Potential savings of 183 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://cdn.18boyz.com/sr/thumbs/ah/416055.jpg
61978
53372.95
https://cdn.18boyz.com/sr/thumbs/ah/416776.jpg
61335
52124.45
https://cdn.18boyz.com/sr/thumbs/Vg/411652.jpg
54228
47002.45
https://cdn.18boyz.com/sr/thumbs/Ug/410010.jpg
39619
34918.15
Avoid an excessive DOM size — 1,500 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
1500
Maximum DOM Depth
9
Maximum Child Elements
100
Largest Contentful Paint image was lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://cdn.18boyz.com/pics/gl.png
https://cdn.18boyz.com/pics/bpp.png
https://cdn.18boyz.com/pics/cam.png
https://cdn.18boyz.com/pics/dating.png
https://cdn.18boyz.com/pics/girl.png
39

Accessibility

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

Names and labels

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

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
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 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"]`
18boyz.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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

Internationalization and localization

`<html>` element does not have 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.
Failing Elements

Names and labels

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

Tables and lists

List items (`<li>`) are not 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.
Failing Elements

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 18boyz.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

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

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
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.
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://18boyz.com/
Allowed

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://cdn.18boyz.com/sr/thumbs/Xe/309494.jpg
190 x 245
190 x 245
380 x 490
https://cdn.18boyz.com/sr/thumbs/ah/416776.jpg
190 x 245
190 x 245
380 x 490
https://18boyz.com/images/logo.png
159 x 50
229 x 72
318 x 100
92

SEO

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

Content Best Practices

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

Crawling and Indexing

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

Mobile Friendly

Tap targets are not sized appropriately — 94% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
300x19
300x19
300x19
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
72x26
310x36

Content Best Practices

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

Manual Checks

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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of 18boyz.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 18boyz.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

Server Location

Server IP Address: 198.50.193.57
Continent: North America
Country: Canada
Canada Flag
Region:
City:
Longitude: -79.3716
Latitude: 43.6319
Currencies: CAD
Languages: English
French

Web Hosting Provider

Name IP Address
OVH Hosting, Inc.
Registration

Domain Registrant

Private Registration: Yes
Name: REDACTED FOR PRIVACY
Organization: See PrivacyGuardian.org
Country: US
City: Phoenix
State: AZ
Post Code: 85016
Email: [email protected]
Phone: +1.3478717726
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
NameSilo, LLC 104.18.31.76
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: 18boyz.com
Issued By: R3
Valid From: 4th October, 2022
Valid To: 2nd January, 2023
Subject: CN = 18boyz.com
Hash: aad3138c
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x04948E7CBED19191D06335A5A8535F3B16C4
Serial Number (Hex): 04948E7CBED19191D06335A5A8535F3B16C4
Valid From: 4th October, 2025
Valid To: 2nd January, 2025
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Oct 4 03:07:53.198 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:14:2F:65:BA:9E:DD:90:6C:AF:C8:64:7F:
9E:7D:80:71:C4:30:1A:16:A6:92:64:6A:D4:0B:AF:A4:
A8:15:E2:8B:02:20:35:BF:1D:CC:C6:DE:FC:39:78:C3:
BC:18:87:0A:32:40:E5:0B:4E:8C:62:BD:EB:E5:13:85:
DC:36:3C:1A:52:4B
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Oct 4 03:07:53.127 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:76:B1:43:DA:D2:C6:3E:D3:41:7D:22:AE:
F7:C9:6C:91:17:37:0B:71:24:A5:C8:29:B9:AF:20:44:
A1:A5:76:5E:02:20:7F:56:A2:AE:9B:67:18:F2:2B:F1:
84:59:5F:63:F8:B0:15:92:3E:0E:33:8B:B3:FA:BD:E9:
B3:55:B2:04:16:F7
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.18boyz.com
DNS:18boyz.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
18boyz.com. 198.50.193.57 IN 7200

NS Records

Host Nameserver Class TTL
18boyz.com. ns1.topdns.me. IN 7200
18boyz.com. ns2.topdns.me. IN 7200
18boyz.com. ns3.topdns.me. IN 7200

SOA Records

Domain Name Primary NS Responsible Email TTL
18boyz.com. ns1.topdns.me. hostmaster.18boyz.com. 7200

TXT Records

Host Value Class TTL
18boyz.com. google-site-verification=fPesbOP2tiP5EgT_OoNCxunbQD5LrIn5TBddDx4CQpw IN 7200

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 3rd November, 2022
Content-Type: text/html; charset=UTF-8
Cache-Control: private, must-revalidate
Expires: 3rd November, 2022
Connection: keep-alive
Keep-Alive: timeout=60
Vary: Accept-Encoding
X-Powered-By: PHP/7.4.27

Whois Lookup

Created: 8th September, 2004
Changed: 9th August, 2024
Expires: 8th September, 2024
Registrar: NameSilo, LLC
Status: clientTransferProhibited
Nameservers: ns1.dnsowl.com
ns2.dnsowl.com
ns3.dnsowl.com
Owner Name: Domain Administrator
Owner Organization: See PrivacyGuardian.org
Owner Street: 1928 E. Highland Ave. Ste F104 PMB# 255
Owner Post Code: 85016
Owner City: Phoenix
Owner State: AZ
Owner Country: US
Owner Phone: +1.3478717726
Owner Email: [email protected]
Admin Name: Domain Administrator
Admin Organization: See PrivacyGuardian.org
Admin Street: 1928 E. Highland Ave. Ste F104 PMB# 255
Admin Post Code: 85016
Admin City: Phoenix
Admin State: AZ
Admin Country: US
Admin Phone: +1.3478717726
Admin Email: [email protected]
Tech Name: Domain Administrator
Tech Organization: See PrivacyGuardian.org
Tech Street: 1928 E. Highland Ave. Ste F104 PMB# 255
Tech Post Code: 85016
Tech City: Phoenix
Tech State: AZ
Tech Country: US
Tech Phone: +1.3478717726
Tech Email: [email protected]
Full Whois: Domain Name: 18boyz.com
Registry Domain ID: 129537994_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namesilo.com
Registrar URL: https://www.namesilo.com/
Updated Date: 2024-08-09T07:00:00Z
Creation Date: 2004-09-08T07:00:00Z
Registrar Registration Expiration Date: 2024-09-08T07:00:00Z
Registrar: NameSilo, LLC
Registrar IANA ID: 1479
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.4805240066
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: Domain Administrator
Registrant Organization: See PrivacyGuardian.org
Registrant Street: 1928 E. Highland Ave. Ste F104 PMB# 255
Registrant City: Phoenix
Registrant State/Province: AZ
Registrant Postal Code: 85016
Registrant Country: US
Registrant Phone: +1.3478717726
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: [email protected]
Registry Admin ID:
Admin Name: Domain Administrator
Admin Organization: See PrivacyGuardian.org
Admin Street: 1928 E. Highland Ave. Ste F104 PMB# 255
Admin City: Phoenix
Admin State/Province: AZ
Admin Postal Code: 85016
Admin Country: US
Admin Phone: +1.3478717726
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: [email protected]
Registry Tech ID:
Tech Name: Domain Administrator
Tech Organization: See PrivacyGuardian.org
Tech Street: 1928 E. Highland Ave. Ste F104 PMB# 255
Tech City: Phoenix
Tech State/Province: AZ
Tech Postal Code: 85016
Tech Country: US
Tech Phone: +1.3478717726
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: [email protected]
Name Server: NS1.DNSOWL.COM
Name Server: NS2.DNSOWL.COM
Name Server: NS3.DNSOWL.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/

>>> Last update of WHOIS database: 2024-08-21T07:00:00Z <<<

For more information on Whois status codes, please visit https://icann.org/epp
NOTICE AND TERMS OF USE: You are not authorized to access or query our WHOIS
database through the use of high-volume, automated, electronic processes. The
Data in our WHOIS database is provided for information purposes only, and to
assist persons in obtaining information about or related to a domain name
registration record. We do not guarantee its accuracy. By submitting a WHOIS
query, you agree to abide by the following terms of use: You agree that you may
use this Data only for lawful purposes and that under no circumstances will you
use this Data to: (1) allow, enable, or otherwise support the transmission of
mass unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes that
apply to us (or our computer systems). The compilation, repackaging,
dissemination or other use of this Data is expressly prohibited without our
prior written consent. We reserve the right to terminate your access to the
WHOIS database at our sole discretion, including without limitation, for
excessive querying of the WHOIS database or for failure to otherwise abide by
this policy. We reserve the right to modify these terms at any time.

Domains - cheap, easy, and secure at NameSilo.com

https://www.namesilo.com

Register your domain now at www.NameSilo.com - Domains. Cheap, Fast and Secure

Nameservers

Name IP Address
ns1.dnsowl.com 162.159.27.173
ns2.dnsowl.com 162.159.27.130
ns3.dnsowl.com 162.159.27.98
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
0/5
0/5
$603 USD
0/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5

Sites hosted on the same IP address

Love W3 Snoop?

18boyz.com Infographic

18boyz.com by the numbers infographic