vanityteen.com

vanityteen.com is SSL secured

Free website and domain report on vanityteen.com

Last Updated: 1st July, 2021 Update Now
Overview

Snoop Summary for vanityteen.com

This is a free and comprehensive report about vanityteen.com. The domain vanityteen.com is currently hosted on a server located in London, England in United Kingdom with the IP address 35.214.93.23, where GBP is the local currency and the local language is English. Vanityteen.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If vanityteen.com was to be sold it would possibly be worth $1,090 USD (based on the daily revenue potential of the website over a 24 month period). Vanityteen.com receives an estimated 519 unique visitors every day - a decent amount of traffic! This report was last updated 1st July, 2021.

About vanityteen.com

Site Preview: vanityteen.com vanityteen.com
Title: Vanity Teen 虚荣青年 Menswear & New Faces Magazine 杂志
Description: VTEEN - 虚荣青年 杂志 Vanity Teen LLC Fashion, Lifestyle, Culture Digital & Biannual print menswear magazine, founded in 2008
Keywords and Tags: beauty, fashion
Related Terms: cottage vanity, designer menswear, haggar menswear, mainline menswear stockists of armani, menswear, menswear online, revista vanity fair, texwood menswear, vanity fair, vanity plates
Fav Icon:
Age: Over 15 years old
Domain Created: 6th April, 2008
Domain Updated: 2nd March, 2021
Domain Expires: 6th April, 2022
Review

Snoop Score

2/5

Valuation

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

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,059,361
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: 519
Monthly Visitors: 15,797
Yearly Visitors: 189,435
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $45 USD
Yearly Revenue: $540 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: vanityteen.com 14
Domain Name: vanityteen 10
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 2.64 seconds
Load Time Comparison: Faster than 27% of sites

PageSpeed Insights

Avg. (All Categories) 70
Performance 75
Accessibility 61
Best Practices 80
SEO 100
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.vanityteen.com/
Updated: 1st July, 2021

3.27 seconds
First Contentful Paint (FCP)
50%
22%
28%

0.00 seconds
First Input Delay (FID)
98%
1%
1%

Simulate loading on desktop
75

Performance

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

Metrics

Time to Interactive — 1.2 s
The time taken for the page to become fully interactive.
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).

Other

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
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://vanityteen.com/
http/1.1
0
318.18000017665
363
0
301
text/html
https://www.vanityteen.com/
h2
318.64200020209
1373.5640000086
24255
253499
200
text/html
Document
https://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/siteground-optimizer-combined-css-184175adc866a279db2930441d20097e.css
h2
1387.3460001778
1492.1560001094
46032
317873
200
text/css
Stylesheet
https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/themes/smoothness/jquery-ui.css?ver=6fa9f632ca4835ef907c5c56c1cc0b3c
h2
1387.693000026
1393.9420001116
9279
36536
200
text/css
Stylesheet
https://use.fontawesome.com/releases/v5.5.0/css/all.css?ver=6fa9f632ca4835ef907c5c56c1cc0b3c
h2
1387.9170001019
1407.1520001162
13256
51215
200
text/css
Stylesheet
https://use.fontawesome.com/releases/v5.12.1/css/all.css?ver=6fa9f632ca4835ef907c5c56c1cc0b3c
1387.6060000621
1395.4450001474
0
0
-1
Stylesheet
https://www.vanityteen.com/wp-content/themes/zoxpress/css/zox-media-queries.min.css
h2
1388.5000001173
1469.6750000585
10419
139066
200
text/css
Stylesheet
data
1392.0050000306
1392.061999999
0
37
200
image/gif
Image
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
h2
1407.7180000022
1426.5500002075
4945
12332
200
application/javascript
Script
https://static.cloudflareinsights.com/beacon.min.js
h2
1408.0110001378
1427.9910000041
5553
13614
200
text/javascript
Script
https://cdn.usefathom.com/script.js
h2
1433.702000184
1516.6120000649
2297
6192
200
application/javascript
Script
https://www.vanityteen.com/wp-includes/js/wp-embed.min.js
h2
1434.2030000407
1464.9500001688
1637
1426
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/q2w3-fixed-widget/js/q2w3-fixed-widget.min.js
h2
1434.8960001953
1470.1830002014
2238
4360
200
application/javascript
Script
https://www.vanityteen.com/wp-content/themes/zoxpress/js/lozad.min.js
h2
1435.0080001168
1489.7530002054
2113
3095
200
application/javascript
Script
https://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/zox-intersection-observer-polyfill.min.js
h2
1435.3540001903
1462.4300000723
3181
6893
200
application/javascript
Script
https://www.vanityteen.com/wp-includes/js/comment-reply.min.js
h2
1435.7790001668
1491.1670000292
2194
2984
200
application/javascript
Script
https://www.vanityteen.com/wp-content/themes/zoxpress/js/jquery.infinitescroll.min.js
h2
1436.1450001597
1472.0740001649
12574
21705
200
application/javascript
Script
https://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/zox-retina.min.js
h2
1436.5030000918
1490.9250000492
1674
1621
200
application/javascript
Script
https://www.vanityteen.com/wp-content/themes/zoxpress/js/scripts.js
h2
1436.8570002262
1501.6450001858
24475
113963
200
application/javascript
Script
https://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/zox-custom.min.js
h2
1437.3040001374
1459.2970001977
1001
0
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/wp-smush-pro/app/assets/js/smush-lazy-load.min.js
h2
1437.5930000097
1488.8750000391
4453
7918
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/zoxpress-plugin//scripts/jquery.waypoints.min.js
h2
1437.9670000635
1477.6600000914
3912
10478
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/zoxpress-plugin//scripts/jquery.sticky-kit.min.js
h2
1438.3070000913
1499.9610001687
2154
2798
200
application/javascript
Script
https://www.vanityteen.com/wp-includes/js/jquery/ui/core.min.js
h2
1438.6910002213
1461.8250001222
7505
20787
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/wp-user-avatar/assets/js/frontend.min.js
h2
1439.029000001
1482.9410000239
3073
9070
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/awb/awb.min.js
h2
1439.3980000168
1490.6690001953
4120
9278
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/vendor/object-fit-images/ofi.min.js
h2
1439.9050001521
1489.341000095
2270
3291
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/vendor/jarallax/jarallax-video.min.js
1439.7520001512
1444.0870000981
0
0
-1
Script
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/vendor/jarallax/jarallax.min.js
h2
1440.5030000489
1465.6660000328
5911
15450
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/wp-user-avatar/assets/select2/select2.min.js
h2
1440.955000231
1485.3160001803
19285
70851
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/wp-user-avatar/assets/flatpickr/flatpickr.min.js
h2
1441.3180002011
1490.1190001983
14238
48518
200
application/javascript
Script
https://www.vanityteen.com/wp-includes/js/jquery/jquery-migrate.min.js
h2
1441.679000156
1493.1290000677
4880
11224
200
application/javascript
Script
https://www.vanityteen.com/wp-includes/js/jquery/jquery.min.js
h2
1442.0360000804
1497.5210002158
31097
89496
200
application/javascript
Script
https://fonts.gstatic.com/s/nunitosans/v6/pe03MImSLYBIv1o4X1M8cc8WAc5tU1Q.ttf
h2
1462.2120000422
1467.9510002024
22023
37692
200
font/ttf
Font
https://use.fontawesome.com/releases/v5.5.0/webfonts/fa-brands-400.woff2
1461.9680000469
1467.7180000581
0
0
-1
Font
https://fonts.gstatic.com/s/nunitosans/v6/pe03MImSLYBIv1o4X1M8cc9iB85tU1Q.ttf
h2
1462.9370002076
1467.1230001841
22154
38208
200
font/ttf
Font
https://fonts.gstatic.com/s/nunitosans/v6/pe03MImSLYBIv1o4X1M8cc8GBs5tU1Q.ttf
h2
1463.3170000743
1466.5850000456
22300
38740
200
font/ttf
Font
https://use.fontawesome.com/releases/v5.5.0/webfonts/fa-solid-900.woff2
h2
1463.5640000924
1478.4440000076
74318
73852
200
font/woff2
Font
https://use.fontawesome.com/releases/v5.5.0/webfonts/fa-regular-400.woff2
h2
1464.8690000176
1479.084999999
15310
14844
200
font/woff2
Font
https://use.fontawesome.com/releases/v5.5.0/webfonts/fa-brands-400.woff
h2
1468.8740000129
1484.430000186
82089
81612
200
application/font-woff
Font
https://www.vanityteen.com/wp-content/themes/zoxpress-child/fonts/strawford/bold/strawford-bold-webfont.woff2
h2
1520.2440000139
1546.6790001374
17548
16548
200
font/woff2
Font
https://www.vanityteen.com/wp-content/themes/zoxpress-child/fonts/strawford/regular/strawford-regular-webfont.woff2
h2
1554.3220001273
1580.6810001377
17340
16340
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v20/mem5YaGs126MiZpBA-UN7rgOUuhs.ttf
h2
1558.7560001295
1566.945000086
19964
29028
200
font/ttf
Font
https://www.vanityteen.com/wp-includes/js/wp-emoji-release.min.js
h2
1743.1430001743
1771.2770001963
5320
14229
200
application/javascript
Script
https://fonts.gstatic.com/s/nunitosans/v6/pe0qMImSLYBIv1o4X1M8cce9I94.ttf
h2
1747.1850002185
1750.4070000723
22383
38640
200
font/ttf
Font
https://img3.usefathom.com/?p=%2F&h=https%3A%2F%2Fwww.vanityteen.com&r=&sid=ONRYTBOS&qs=%7B%7D
h2
2069.5360000245
2173.2620000839
164
0
200
text/html
Image
https://www.vanityteen.com/wp-content/uploads/2020/10/logo.png
h2
2168.6780001037
2192.9630001541
4859
3864
200
image/png
Image
https://www.vanityteen.com/wp-content/uploads/2021/06/demetra-2-1.jpg
h2
2169.4860002026
2213.2330001332
191736
190743
200
image/jpeg
Image
https://www.vanityteen.com/wp-content/uploads/2021/06/Behen-7-scaled-e1624886221275-1536x1019.jpg
h2
2169.5920000784
2752.1880001295
133013
132031
200
image/jpeg
Image
https://www.vanityteen.com/wp-content/uploads/2021/06/Vanity-Teen-Ret-17-1024x576.jpg
h2
2169.693000149
2203.7480000872
65886
64893
200
image/jpeg
Image
https://www.vanityteen.com/wp-content/uploads/2021/03/kust_march_2021-300x250.jpg
h2
2169.9080001563
2192.3390000593
10822
9833
200
image/jpeg
Image
data
2294.6700002067
2294.9220000301
0
7824
200
image/gif
Image
https://www.vanityteen.com/cdn-cgi/rum?req_id=667e8034a9d259b0
h2
2301.4150001109
2321.8220002018
413
0
200
text/plain
XHR
https://www.vanityteen.com/wp-content/uploads/2021/06/Paris-Fashion-Week-Day-06-1024x576.png
h2
2327.0920000505
2385.5940001085
293374
292376
200
image/png
Image
https://www.vanityteen.com/wp-content/uploads/2021/06/Paris-Fashion-Week-Day-05-2-1024x576.png
h2
2327.2160000633
2364.8690001573
246074
245077
200
image/png
Image
https://www.vanityteen.com/wp-content/uploads/2021/01/The-Trevor-Project-banner.jpg
h2
2327.4450001772
2355.7830001228
79996
78987
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)
1382.049
6.568
1391.44
6.118
1432.835
15.03
1449.619
21.629
1484.174
5.282
1502.412
10.361
1513.506
194.606
1714.781
52.372
1767.589
12.43
1780.483
15.489
1803.564
150.952
1956.955
57.283
2017.16
52.373
2074.288
11.588
2085.889
6.864
2092.836
10.688
2108.203
14.298
2129.692
12.758
2145.53
9.753
2158.151
14.734
2172.91
5.081
2179.936
6.659
2195.78
11.101
2211.646
12.456
2227.3
14.859
2244.269
10.022
2256.407
11.647
2268.971
6.206
2275.19
17.798
2293.487
7.261
2306.012
7.922
2329.859
6.029
2375.438
10.072
2492.233
9.951
2509.178
6.101
2525.902
5.257
2543.744
5.551
2580.916
5.409
2596.826
11.65
2627.056
6.674
2642.644
13.677
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.

Opportunities

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Vanityteen.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Vanityteen.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 8 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Vanityteen.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.vanityteen.com/wp-content/themes/zoxpress/js/scripts.js
24475
8044
Reduce unused CSS — Potential savings of 64 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Vanityteen.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/siteground-optimizer-combined-css-184175adc866a279db2930441d20097e.css
46032
42200
https://use.fontawesome.com/releases/v5.5.0/css/all.css?ver=6fa9f632ca4835ef907c5c56c1cc0b3c
13256
13085
https://www.vanityteen.com/wp-content/themes/zoxpress/css/zox-media-queries.min.css
10419
10419
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.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Vanityteen.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://vanityteen.com/
190
https://www.vanityteen.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Vanityteen.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 — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/vendor/jarallax/jarallax.min.js
64
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.vanityteen.com/wp-content/uploads/2021/06/Behen-7-scaled-e1624886221275-1536x1019.jpg
0

Diagnostics

Avoids enormous network payloads — Total size was 1,580 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.vanityteen.com/wp-content/uploads/2021/06/Paris-Fashion-Week-Day-06-1024x576.png
293374
https://www.vanityteen.com/wp-content/uploads/2021/06/Paris-Fashion-Week-Day-05-2-1024x576.png
246074
https://www.vanityteen.com/wp-content/uploads/2021/06/demetra-2-1.jpg
191736
https://www.vanityteen.com/wp-content/uploads/2021/06/Behen-7-scaled-e1624886221275-1536x1019.jpg
133013
https://use.fontawesome.com/releases/v5.5.0/webfonts/fa-brands-400.woff
82089
https://www.vanityteen.com/wp-content/uploads/2021/01/The-Trevor-Project-banner.jpg
79996
https://use.fontawesome.com/releases/v5.5.0/webfonts/fa-solid-900.woff2
74318
https://www.vanityteen.com/wp-content/uploads/2021/06/Vanity-Teen-Ret-17-1024x576.jpg
65886
https://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/siteground-optimizer-combined-css-184175adc866a279db2930441d20097e.css
46032
https://www.vanityteen.com/wp-includes/js/jquery/jquery.min.js
31097
Uses efficient cache policy on static assets — 3 resources found
Vanityteen.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://cdn.usefathom.com/script.js
0
2297
https://static.cloudflareinsights.com/beacon.min.js
86400000
5553
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
172800000
4945
Avoid chaining critical requests — 14 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Vanityteen.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://www.vanityteen.com/
779.42500000003
2.899
0.909
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
122.719
96.201
2.211
https://www.vanityteen.com/wp-content/plugins/wp-smush-pro/app/assets/js/smush-lazy-load.min.js
93.157
19.445
0.641
Unattributable
68.654
2.692
0.152
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
422.091
Other
296.809
Rendering
221.91900000004
Script Evaluation
168.194
Parse HTML & CSS
28.565
Script Parsing & Compilation
21.327
Garbage Collection
3.656
Keep request counts low and transfer sizes small — 54 requests • 1,580 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
54
1617470
Image
9
1025924
Font
11
315429
Script
26
172100
Stylesheet
5
78986
Document
1
24255
Other
2
776
Media
0
0
Third-party
16
316035
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
184973
0
108824
0
9279
0
4945
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
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://www.vanityteen.com/
466
97
https://www.vanityteen.com/
563
75
Avoid non-composited animations — 123 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
a
a
a
a
a
a
a
div
div
div

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

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

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 430 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Vanityteen.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://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/siteground-optimizer-combined-css-184175adc866a279db2930441d20097e.css
46032
240
https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/themes/smoothness/jquery-ui.css?ver=6fa9f632ca4835ef907c5c56c1cc0b3c
9279
270
https://use.fontawesome.com/releases/v5.5.0/css/all.css?ver=6fa9f632ca4835ef907c5c56c1cc0b3c
13256
270
https://use.fontawesome.com/releases/v5.12.1/css/all.css?ver=6fa9f632ca4835ef907c5c56c1cc0b3c
0
230
Properly size images — Potential savings of 481 KiB
Images can slow down the page's load time. Vanityteen.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.vanityteen.com/wp-content/uploads/2021/06/Paris-Fashion-Week-Day-06-1024x576.png
292376
204518
https://www.vanityteen.com/wp-content/uploads/2021/06/Paris-Fashion-Week-Day-05-2-1024x576.png
245077
171432
https://www.vanityteen.com/wp-content/uploads/2021/06/Behen-7-scaled-e1624886221275-1536x1019.jpg
132031
98231
https://www.vanityteen.com/wp-content/uploads/2021/06/Vanity-Teen-Ret-17-1024x576.jpg
64893
18493
Efficiently encode images — Potential savings of 196 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.vanityteen.com/wp-content/uploads/2021/06/demetra-2-1.jpg
190743
144411
https://www.vanityteen.com/wp-content/uploads/2021/01/The-Trevor-Project-banner.jpg
78987
56232
Serve images in next-gen formats — Potential savings of 594 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://www.vanityteen.com/wp-content/uploads/2021/06/demetra-2-1.jpg
190743
169745
https://www.vanityteen.com/wp-content/uploads/2021/06/Paris-Fashion-Week-Day-06-1024x576.png
292376
164972
https://www.vanityteen.com/wp-content/uploads/2021/06/Paris-Fashion-Week-Day-05-2-1024x576.png
245077
162389
https://www.vanityteen.com/wp-content/uploads/2021/01/The-Trevor-Project-banner.jpg
78987
67457
https://www.vanityteen.com/wp-content/uploads/2021/06/Behen-7-scaled-e1624886221275-1536x1019.jpg
132031
43867

Diagnostics

Avoid an excessive DOM size — 1,099 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
1099
Maximum DOM Depth
24
Maximum Child Elements
29

Metrics

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

Opportunities

Reduce initial server response time — Root document took 1,060 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.vanityteen.com/
1055.92

Diagnostics

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://use.fontawesome.com/releases/v5.5.0/webfonts/fa-brands-400.woff2
5.7500000111759
https://use.fontawesome.com/releases/v5.5.0/webfonts/fa-solid-900.woff2
14.879999915138
https://use.fontawesome.com/releases/v5.5.0/webfonts/fa-regular-400.woff2
14.215999981388
https://use.fontawesome.com/releases/v5.5.0/webfonts/fa-brands-400.woff
15.556000173092
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
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 Failing Elements
https://www.vanityteen.com/wp-content/uploads/2020/10/logo.png
https://www.vanityteen.com/wp-content/uploads/2020/10/logo.png
61

Accessibility

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

ARIA

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

Names and labels

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

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Vanityteen.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
Some elements have a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.
Failing Elements

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
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.

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that vanityteen.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.
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

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.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
jQuery UI
1.12.1
WordPress
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.vanityteen.com/wp-content/plugins/wp-smush-pro/app/assets/js/smush-lazy-load.min.js
https://www.vanityteen.com/wp-content/plugins/wp-smush-pro/app/assets/js/smush-lazy-load.min.js.map
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/vendor/jarallax/jarallax.min.js
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/vendor/jarallax/jarallax.min.js.map
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://vanityteen.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: net::ERR_ACCESS_DENIED
Failed to load resource: net::ERR_ACCESS_DENIED
Failed to load resource: net::ERR_ACCESS_DENIED
100

SEO

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

Crawling and Indexing

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

Manual Checks

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

Progressive Web App

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 vanityteen.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) 64
Performance 44
Accessibility 64
Best Practices 73
SEO 99
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.vanityteen.com/
Updated: 1st July, 2021

3.17 seconds
First Contentful Paint (FCP)
38%
36%
26%

0.04 seconds
First Input Delay (FID)
91%
8%
1%

Simulate loading on mobile
44

Performance

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

Metrics

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

Other

Max Potential First Input Delay — 80 ms
Users could experience a delay when interacting with the page.
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://vanityteen.com/
http/1.1
0
204.91299999412
366
0
301
text/html
https://www.vanityteen.com/
h2
205.51499992143
1096.1569999345
24206
253499
200
text/html
Document
https://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/siteground-optimizer-combined-css-184175adc866a279db2930441d20097e.css
h2
1117.6779998932
1176.9989999011
46034
317873
200
text/css
Stylesheet
https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/themes/smoothness/jquery-ui.css?ver=6fa9f632ca4835ef907c5c56c1cc0b3c
h2
1118.0609998992
1125.9439999703
9271
36536
200
text/css
Stylesheet
https://use.fontawesome.com/releases/v5.5.0/css/all.css?ver=6fa9f632ca4835ef907c5c56c1cc0b3c
h2
1118.2430000044
1142.1549998922
13256
51215
200
text/css
Stylesheet
https://use.fontawesome.com/releases/v5.12.1/css/all.css?ver=6fa9f632ca4835ef907c5c56c1cc0b3c
h2
1118.8339999644
1143.7379999552
14637
57333
200
text/css
Stylesheet
https://www.vanityteen.com/wp-content/themes/zoxpress/css/zox-media-queries.min.css
h2
1119.3319999147
1173.2029999839
10421
139066
200
text/css
Stylesheet
data
1124.4529999094
1124.5549999876
0
37
200
image/gif
Image
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
h2
1148.3439999865
1166.7080000043
5130
12332
200
application/javascript
Script
https://static.cloudflareinsights.com/beacon.min.js
h2
1148.9319999237
1171.9159999629
5553
13614
200
text/javascript
Script
https://cdn.usefathom.com/script.js
h2
1178.5499999532
1196.763999993
2297
6192
200
application/javascript
Script
https://www.vanityteen.com/wp-includes/js/wp-embed.min.js
h2
1179.1329999687
1210.0929999724
1641
1426
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/q2w3-fixed-widget/js/q2w3-fixed-widget.min.js
h2
1179.8369999742
1201.7559999367
2236
4360
200
application/javascript
Script
https://www.vanityteen.com/wp-content/themes/zoxpress/js/lozad.min.js
h2
1180.0839999923
1216.2259999895
2107
3095
200
application/javascript
Script
https://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/zox-intersection-observer-polyfill.min.js
h2
1180.5419999873
1210.5779999401
3177
6893
200
application/javascript
Script
https://www.vanityteen.com/wp-includes/js/comment-reply.min.js
h2
1181.3819999807
1836.0319999047
2190
2984
200
application/javascript
Script
https://www.vanityteen.com/wp-content/themes/zoxpress/js/jquery.infinitescroll.min.js
h2
1181.660000002
1208.3749999292
12566
21705
200
application/javascript
Script
https://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/zox-retina.min.js
h2
1182.267999975
1223.876999924
1672
1621
200
application/javascript
Script
https://www.vanityteen.com/wp-content/themes/zoxpress/js/scripts.js
h2
1182.8019999666
1219.9859999819
24479
113963
200
application/javascript
Script
https://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/zox-custom.min.js
h2
1183.7029999588
1204.3609999819
1011
0
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/wp-smush-pro/app/assets/js/smush-lazy-load.min.js
h2
1184.1119999299
1221.3769999798
4451
7918
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/zoxpress-plugin//scripts/jquery.waypoints.min.js
h2
1184.399999911
1219.3149999948
3906
10478
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/zoxpress-plugin//scripts/jquery.sticky-kit.min.js
h2
1188.4249999421
1235.503999982
2152
2798
200
application/javascript
Script
https://www.vanityteen.com/wp-includes/js/jquery/ui/core.min.js
h2
1188.8329999056
1220.6109999679
7493
20787
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/wp-user-avatar/assets/js/frontend.min.js
h2
1189.0219999477
1218.4209999396
3067
9070
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/awb/awb.min.js
h2
1189.3429999473
1221.0189999314
4118
9278
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/vendor/object-fit-images/ofi.min.js
h2
1189.5499998936
1218.8899999019
2258
3291
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/vendor/jarallax/jarallax-video.min.js
h2
1189.8059999803
1234.7129998961
6269
18445
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/vendor/jarallax/jarallax.min.js
h2
1190.111999982
1221.7849999433
5909
15450
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/wp-user-avatar/assets/select2/select2.min.js
h2
1190.3379999567
1223.3879999258
19299
70851
200
application/javascript
Script
https://www.vanityteen.com/wp-content/plugins/wp-user-avatar/assets/flatpickr/flatpickr.min.js
h2
1190.6799999997
1224.3079999462
14240
48518
200
application/javascript
Script
https://www.vanityteen.com/wp-includes/js/jquery/jquery-migrate.min.js
h2
1191.8619999196
1845.6509999232
4878
11224
200
application/javascript
Script
https://www.vanityteen.com/wp-includes/js/jquery/jquery.min.js
h2
1192.8809999954
1234.1189999133
31093
89496
200
application/javascript
Script
https://fonts.gstatic.com/s/nunitosans/v6/pe03MImSLYBIv1o4X1M8cc8WAc5tU1Q.ttf
h2
1225.5789999617
1231.9179999176
21851
37692
200
font/ttf
Font
https://use.fontawesome.com/releases/v5.12.1/webfonts/fa-brands-400.woff2
h2
1226.084999973
1242.4589999719
77014
76548
200
font/woff2
Font
https://fonts.gstatic.com/s/nunitosans/v6/pe03MImSLYBIv1o4X1M8cc9iB85tU1Q.ttf
h2
1226.8530000001
1232.6109999558
22326
38208
200
font/ttf
Font
https://fonts.gstatic.com/s/nunitosans/v6/pe03MImSLYBIv1o4X1M8cc8GBs5tU1Q.ttf
h2
1227.0729999291
1233.1569999224
22472
38740
200
font/ttf
Font
https://use.fontawesome.com/releases/v5.12.1/webfonts/fa-solid-900.woff2
h2
1228.3919999609
1244.8940000031
76586
76120
200
font/woff2
Font
https://use.fontawesome.com/releases/v5.12.1/webfonts/fa-regular-400.woff2
h2
1237.9109999165
1252.698999946
14066
13600
200
font/woff2
Font
https://www.vanityteen.com/wp-content/themes/zoxpress-child/fonts/strawford/bold/strawford-bold-webfont.woff2
h2
1293.6369999079
1320.5609999131
17538
16548
200
font/woff2
Font
https://www.vanityteen.com/wp-content/themes/zoxpress-child/fonts/strawford/regular/strawford-regular-webfont.woff2
h2
1336.6260000039
1360.1469999412
17338
16340
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v20/mem5YaGs126MiZpBA-UN7rgOUuhs.ttf
h2
1341.6609999258
1346.5809999034
19964
29028
200
font/ttf
Font
https://fonts.gstatic.com/s/nunitosans/v6/pe0qMImSLYBIv1o4X1M8cce9I94.ttf
h2
1517.3380000051
1521.7049999628
22383
38640
200
font/ttf
Font
https://www.vanityteen.com/wp-includes/js/wp-emoji-release.min.js
h2
1587.596999947
1610.6209999416
5312
14229
200
application/javascript
Script
https://img3.usefathom.com/?p=%2F&h=https%3A%2F%2Fwww.vanityteen.com&r=&sid=ONRYTBOS&qs=%7B%7D
h2
2117.7429999225
2218.4299998917
164
0
200
text/html
Image
https://www.vanityteen.com/wp-content/uploads/2020/10/logo.png
h2
2256.2049999833
2278.3399999607
4853
3864
200
image/png
Image
https://www.vanityteen.com/wp-content/uploads/2021/06/demetra-2-1-600x313.jpg
h2
2256.3799999189
2282.4519999558
22399
21399
200
image/jpeg
Image
https://www.vanityteen.com/wp-content/uploads/2021/06/Behen-7-scaled-e1624886221275-600x600.jpg
h2
2256.5440000035
2281.8129999796
51681
50689
200
image/jpeg
Image
https://www.vanityteen.com/wp-content/uploads/2020/10/logo@2x.png
h2
2317.8060000064
3073.7209999934
12765
65536
404
text/html
Image
data
2381.7890000064
2381.9829999702
0
7824
200
image/gif
Image
https://www.vanityteen.com/cdn-cgi/rum?req_id=667e80f3b9bd5b2f
h2
2389.6909999894
2422.9789999081
413
0
200
text/plain
XHR
https://www.vanityteen.com/wp-content/uploads/2021/06/Vanity-Teen-Ret-17-1024x576.jpg
h2
2452.428999939
2476.0109999916
65888
64893
200
image/jpeg
Image
https://www.vanityteen.com/wp-content/uploads/2021/06/Paris-Fashion-Week-Day-06-1024x576.png
h2
3382.0709999418
3409.152999986
293370
292376
200
image/png
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)
1110.486
10.457
1124.558
8.775
1176.603
21.879
1201.73
38.79
1240.734
6.902
1267.302
15.491
1283.384
194.277
1492.463
5.627
1498.191
50.823
1549.183
7.101
1557.824
43.002
1601.85
296.451
1898.486
19.715
1919.629
113.759
2037.061
7.173
2044.254
22.963
2068.929
23.58
2096.371
20.951
2124.769
25.009
2149.88
10.344
2165.444
6.873
2172.372
5.63
2183.096
24.983
2209.945
5.281
2215.275
12.441
2241.444
6.302
2251.741
13.543
2265.313
5.484
2278.742
5.482
2289.243
5.19
2303.193
21.952
2325.177
6.962
2339.396
10.227
2354.529
25.222
2380.685
10.178
2398.039
16.716
2414.828
10.301
2426.129
11.1
2441.802
6.859
2457.366
9.32
2471.552
6.003
2488.365
15.934
2521.835
5.27
2554.632
5.161
2571.41
5.162
2588.226
5.169
2604.698
5.806
2671.273
5.021
2871.666
6.637
2904.662
5.051
2987.918
5.911
3187.977
10.366
3204.713
5.805
3232.623
12.777
3388.108
6.23
3421.496
19.666
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.

Opportunities

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Vanityteen.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Vanityteen.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 8 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Vanityteen.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.vanityteen.com/wp-content/themes/zoxpress/js/scripts.js
24479
8045
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Vanityteen.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://vanityteen.com/
630
https://www.vanityteen.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Vanityteen.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 — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/vendor/jarallax/jarallax.min.js
64
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/vendor/jarallax/jarallax-video.min.js
57
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.vanityteen.com/wp-content/uploads/2021/06/demetra-2-1-600x313.jpg
0

Diagnostics

Avoids enormous network payloads — Total size was 1,035 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.vanityteen.com/wp-content/uploads/2021/06/Paris-Fashion-Week-Day-06-1024x576.png
293370
https://use.fontawesome.com/releases/v5.12.1/webfonts/fa-brands-400.woff2
77014
https://use.fontawesome.com/releases/v5.12.1/webfonts/fa-solid-900.woff2
76586
https://www.vanityteen.com/wp-content/uploads/2021/06/Vanity-Teen-Ret-17-1024x576.jpg
65888
https://www.vanityteen.com/wp-content/uploads/2021/06/Behen-7-scaled-e1624886221275-600x600.jpg
51681
https://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/siteground-optimizer-combined-css-184175adc866a279db2930441d20097e.css
46034
https://www.vanityteen.com/wp-includes/js/jquery/jquery.min.js
31093
https://www.vanityteen.com/wp-content/themes/zoxpress/js/scripts.js
24479
https://www.vanityteen.com/
24206
https://fonts.gstatic.com/s/nunitosans/v6/pe03MImSLYBIv1o4X1M8cc8GBs5tU1Q.ttf
22472
Uses efficient cache policy on static assets — 3 resources found
Vanityteen.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://cdn.usefathom.com/script.js
0
2297
https://static.cloudflareinsights.com/beacon.min.js
86400000
5553
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
172800000
5130
Avoid chaining critical requests — 13 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Vanityteen.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 — 1.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://www.vanityteen.com/
4041.9200000001
16.996
5.304
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
718.444
611.212
12.152
https://www.vanityteen.com/wp-includes/js/jquery/jquery.min.js
488.192
120.924
8.472
https://www.vanityteen.com/wp-content/plugins/wp-smush-pro/app/assets/js/smush-lazy-load.min.js
405.432
128.888
4.12
Unattributable
360.596
12.032
0.624
https://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/siteground-optimizer-combined-css-184175adc866a279db2930441d20097e.css
61.964
0
0
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/awb/awb.min.js
52.956
46.936
5.232
Keep request counts low and transfer sizes small — 51 requests • 1,035 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
51
1059766
Image
7
451120
Font
10
311538
Script
26
178504
Stylesheet
5
93619
Document
1
24206
Other
2
779
Media
0
0
Third-party
15
326970
Minimize third-party usage — Third-party code blocked the main thread for 130 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)
5130
133.052
195559
0
108996
0
9271
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
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.51893596460738
0.22718017535818
0.21406443111767
0.093816773887469
0.0028228759765625
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 — 14 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.vanityteen.com/
2128
593
https://www.vanityteen.com/
1637
389
https://www.vanityteen.com/
3050
228
https://static.cloudflareinsights.com/beacon.min.js
2809
155
https://www.vanityteen.com/
2026
102
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
2721
88
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
2964
86
https://www.vanityteen.com/wp-includes/js/jquery/jquery.min.js
6660
79
https://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/siteground-optimizer-combined-css-184175adc866a279db2930441d20097e.css
3278
62
https://www.vanityteen.com/wp-includes/js/jquery/jquery.min.js
6953
51
https://www.vanityteen.com/
3475
50
https://www.vanityteen.com/
3525
50
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/awb/awb.min.js
5610
50
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
6803
50
Avoid non-composited animations — 124 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
a
a
a
a
a
a
a
div
div

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

Time to Interactive — 5.7 s
The time taken for the page to become fully interactive.

Opportunities

Properly size images — Potential savings of 51 KiB
Images can slow down the page's load time. Vanityteen.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.vanityteen.com/wp-content/uploads/2021/06/Paris-Fashion-Week-Day-06-1024x576.png
292376
42758
https://www.vanityteen.com/wp-content/uploads/2021/06/Vanity-Teen-Ret-17-1024x576.jpg
64893
9490
Reduce unused CSS — Potential savings of 69 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Vanityteen.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/siteground-optimizer-combined-css-184175adc866a279db2930441d20097e.css
46034
42598
https://use.fontawesome.com/releases/v5.12.1/css/all.css?ver=6fa9f632ca4835ef907c5c56c1cc0b3c
14637
14470
https://use.fontawesome.com/releases/v5.5.0/css/all.css?ver=6fa9f632ca4835ef907c5c56c1cc0b3c
13256
13095

Diagnostics

Avoid an excessive DOM size — 1,100 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
1100
Maximum DOM Depth
24
Maximum Child Elements
30

Metrics

First Contentful Paint — 4.9 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 6.4 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 6.7 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 1.057
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First Meaningful Paint — 4.9 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 10290 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 1,650 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Vanityteen.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://www.vanityteen.com/wp-content/uploads/siteground-optimizer-assets/siteground-optimizer-combined-css-184175adc866a279db2930441d20097e.css
46034
1050
https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/themes/smoothness/jquery-ui.css?ver=6fa9f632ca4835ef907c5c56c1cc0b3c
9271
930
https://use.fontawesome.com/releases/v5.5.0/css/all.css?ver=6fa9f632ca4835ef907c5c56c1cc0b3c
13256
1080
https://use.fontawesome.com/releases/v5.12.1/css/all.css?ver=6fa9f632ca4835ef907c5c56c1cc0b3c
14637
300
https://www.vanityteen.com/wp-content/themes/zoxpress/css/zox-media-queries.min.css
10421
300
Serve images in next-gen formats — Potential savings of 170 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://www.vanityteen.com/wp-content/uploads/2021/06/Paris-Fashion-Week-Day-06-1024x576.png
292376
164972
https://www.vanityteen.com/wp-content/uploads/2021/06/Behen-7-scaled-e1624886221275-600x600.jpg
50689
8891
Reduce initial server response time — Root document took 890 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.vanityteen.com/
891.636

Diagnostics

Minimize main-thread work — 6.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)
Other
1985.904
Style & Layout
1956.556
Rendering
1139.2800000002
Script Evaluation
1112.64
Parse HTML & CSS
195.548
Script Parsing & Compilation
117.768
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://use.fontawesome.com/releases/v5.12.1/webfonts/fa-brands-400.woff2
16.373999998905
https://use.fontawesome.com/releases/v5.12.1/webfonts/fa-solid-900.woff2
16.502000042237
https://use.fontawesome.com/releases/v5.12.1/webfonts/fa-regular-400.woff2
14.788000029512
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
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 Failing Elements
https://www.vanityteen.com/wp-content/uploads/2020/10/logo.png
64

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of vanityteen.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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Vanityteen.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

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
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.

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that vanityteen.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

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.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
jQuery UI
1.12.1
WordPress
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.vanityteen.com/wp-content/plugins/wp-smush-pro/app/assets/js/smush-lazy-load.min.js
https://www.vanityteen.com/wp-content/plugins/wp-smush-pro/app/assets/js/smush-lazy-load.min.js.map
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/vendor/jarallax/jarallax.min.js
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/vendor/jarallax/jarallax.min.js.map
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/vendor/jarallax/jarallax-video.min.js
https://www.vanityteen.com/wp-content/plugins/advanced-backgrounds/assets/vendor/jarallax/jarallax-video.min.js.map
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://vanityteen.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

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://www.vanityteen.com/wp-content/uploads/2020/10/logo.png
150 x 37
203 x 50
300 x 74

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: the server responded with a status of 404 (Not Found)
99

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for vanityteen.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 vanityteen.com on mobile screens.
Document uses legible font sizes — 92.84% 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
.zox-s1 span.zox-s-cat, .zox-s2 span.zox-s-cat
5.97%
10px
h1.zox-logo-title, h2.zox-logo-title
0.90%
0px
span.zox-fly-soc-head
0.29%
11.2px
92.84%
≥ 12px

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
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 — 90% 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
67x15
83x15
98x15
48x15
50x15
49x15
48x15
91x15
83x15

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

Progressive Web App

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 vanityteen.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: 35.214.93.23
Continent: Europe
Country: United Kingdom
United Kingdom Flag
Region: England
City: London
Longitude: -0.093
Latitude: 51.5164
Currencies: GBP
Languages: English

Web Hosting Provider

Name IP Address
Google LLC
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
TUCOWS, INC. 199.16.172.52
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 22nd August, 2020
Valid To: 22nd August, 2021
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: 4d04c09a
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 16091505125875870915049678095789540458
Serial Number (Hex): 0C1B1C74CCAA3006D905BF21B5D3446A
Valid From: 22nd August, 2024
Valid To: 22nd August, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

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

Certificate Policies: Policy: 2.16.840.1.114412.1.1
CPS: https://www.digicert.com/CPS
Policy: 2.23.140.1.2.2

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Aug 22 11:46:33.001 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:0A:95:0F:65:E3:4F:AF:FE:AC:6F:37:61:
31:14:D4:E2:A0:04:C7:4B:86:57:DB:E2:30:19:84:F1:
0A:79:A3:B7:02:20:4B:BE:45:9B:64:FB:19:7C:D7:1C:
CF:CE:43:B3:16:82:F3:0E:D3:D7:1D:4B:84:34:BB:2D:
BF:FB:74:93:8D:AC
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
Timestamp : Aug 22 11:46:33.000 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:7B:3D:99:6D:87:46:32:AD:7D:36:ED:1F:
CF:A6:B7:C3:10:E3:E3:10:0E:42:44:E2:14:2B:41:3E:
7A:5F:AD:E7:02:21:00:C4:21:B6:57:E8:37:BB:AA:A6:
54:AC:4F:88:16:EC:3E:E3:ED:B5:A8:43:C9:E7:D9:61:
6A:FE:41:C9:53:74:33
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:sni.cloudflaressl.com
DNS:www.vanityteen.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
vanityteen.com. 35.214.93.23 IN 21599

NS Records

Host Nameserver Class TTL
vanityteen.com. ns1.c26599.sgvps.net. IN 21599
vanityteen.com. ns2.c26599.sgvps.net. IN 21599

MX Records

Priority Host Server Class TTL
1 vanityteen.com. aspmx.l.google.com. IN 14399
10 vanityteen.com. alt4.aspmx.l.google.com. IN 14399
5 vanityteen.com. alt2.aspmx.l.google.com. IN 14399
5 vanityteen.com. alt1.aspmx.l.google.com. IN 14399
20 vanityteen.com. mx20.mailspamprotection.com. IN 14399
10 vanityteen.com. alt3.aspmx.l.google.com. IN 14399
30 vanityteen.com. mx30.mailspamprotection.com. IN 14399

SOA Records

Domain Name Primary NS Responsible Email TTL
vanityteen.com. ns1.c26599.sgvps.net. root.c26599.sgvps.net. 21599

TXT Records

Host Value Class TTL
vanityteen.com. yandex-verification: IN 3599
vanityteen.com. google-site-verification=QlrgpvA8J381F4kpnr7cXCwU-pH5x779tBC7z75wVlo IN 3599
vanityteen.com. v=spf1 IN 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 1st July, 2021
Content-Type: text/html; charset=UTF-8
Expires: 19th November, 1981
Cache-Control: no-store, no-cache, must-revalidate
Server: cloudflare
Connection: keep-alive
Vary: Accept-Encoding
Pragma: no-cache
X-Cache-Enabled: True
Link: <https://www.vanityteen.com/wp-json/>; rel="https://api.w.org/", <https://www.vanityteen.com/wp-json/wp/v2/pages/97937>; rel="alternate"; type="application/json", <https://www.vanityteen.com/>; rel=shortlink
Set-Cookie: *
X-Httpd: 1
Host-Header: 8441280b0c35cbc1147f8ba998a563a7
X-Proxy-Cache-Info: DT:1
CF-Cache-Status: DYNAMIC
cf-request-id: 0b02ee587d00001a13aa07b000000001
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v2?s=ijSkb3f01XBYumXwM86%2BKg8LgikpNvKoLMmYUNQSSw6dgezfav0FwRm0INnSmLoG02BUywf%2FgSM7%2FGBpbkrgkWiH0u%2F2FofqPzfAi0rS04lWOG3WmcgQy0bpJM%2F9uV4J"}],"group":"cf-nel","max_age":604800}
NEL: {"report_to":"cf-nel","max_age":604800}
CF-RAY: 667e800728881a13-EWR
alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400, h3=":443"; ma=86400

Whois Lookup

Created: 6th April, 2008
Changed: 2nd March, 2021
Expires: 6th April, 2022
Registrar: TUCOWS, INC.
Status: ok
Nameservers: ns1.c26599.sgvps.net
ns2.c26599.sgvps.net
Owner Name: REDACTED FOR PRIVACY
Owner Organization: REDACTED FOR PRIVACY
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: DE
Owner Country: US
Owner Phone: REDACTED FOR PRIVACY
Owner Email: https://tieredaccess.com/contact/360a9055-abc7-4a5d-83e2-52b9dd794eb6
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: REDACTED FOR PRIVACY
Full Whois: Domain Name: VANITYTEEN.COM
Registry Domain ID: 1444003218_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://tucowsdomains.com
Updated Date: 2021-03-02T10:52:34
Creation Date: 2008-04-06T01:48:07
Registrar Registration Expiration Date: 2022-04-06T01:48:07
Registrar: TUCOWS, INC.
Registrar IANA ID: 69
Reseller: SiteGround Hosting Ltd.
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID:
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: DE
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext:
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext:
Registrant Email: https://tieredaccess.com/contact/360a9055-abc7-4a5d-83e2-52b9dd794eb6
Registry Admin ID:
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext:
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext:
Admin Email: REDACTED FOR PRIVACY
Registry Tech ID:
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext:
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext:
Tech Email: REDACTED FOR PRIVACY
Name Server: ns1.c26599.sgvps.net
Name Server: ns2.c26599.sgvps.net
DNSSEC: unsigned
Registrar Abuse Contact Email: domainabuse@tucows.com
Registrar Abuse Contact Phone: +1.4165350123
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-07-01T09:10:18Z <<<

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

Registration Service Provider:
SiteGround Hosting Ltd., tucows@domains.siteground.com
+44.8008620379
This company may be contacted for domain login/passwords,
DNS/Nameserver changes, and general domain support questions.

The Data in the Tucows Registrar WHOIS database is provided to you by Tucows
for information purposes only, and may be used to assist you in obtaining
information about or related to a domain name's registration record.

Tucows makes this information available "as is," and does not guarantee its
accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
a) allow, enable, or otherwise support the transmission by e-mail,
telephone, or facsimile of mass, unsolicited, commercial advertising or
solicitations to entities other than the data recipient's own existing
customers; or (b) enable high volume, automated, electronic processes that
send queries or data to the systems of any Registry Operator or
ICANN-Accredited registrar, except as reasonably necessary to register
domain names or modify existing registrations.

The compilation, repackaging, dissemination or other use of this Data is
expressly prohibited without the prior written consent of Tucows.

Tucows reserves the right to terminate your access to the Tucows WHOIS
database in its sole discretion, including without limitation, for excessive
querying of the WHOIS database or for failure to otherwise abide by this
policy.

Tucows reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by these terms.

NOTE: THE WHOIS DATABASE IS A CONTACT DATABASE ONLY. LACK OF A DOMAIN
RECORD DOES NOT SIGNIFY DOMAIN AVAILABILITY.

Nameservers

Name IP Address
ns1.c26599.sgvps.net 35.214.93.23
ns2.c26599.sgvps.net 35.214.93.23
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address