wellhello.com

wellhello.com is SSL secured

Free website and domain report on wellhello.com

Last Updated: 26th March, 2023 Update Now
Overview

Snoop Summary for wellhello.com

This is a free and comprehensive report about wellhello.com. The domain wellhello.com is currently hosted on a server located in United States with the IP address 172.67.203.45, where the local currency is USD and English is the local language. Our records indicate that wellhello.com is owned/operated by Identity Protection Service. Wellhello.com has the potential to be earning an estimated $14 USD per day from advertising revenue. If wellhello.com was to be sold it would possibly be worth $10,396 USD (based on the daily revenue potential of the website over a 24 month period). Wellhello.com is quite popular with an estimated 4,992 daily unique visitors. This report was last updated 26th March, 2023.

About wellhello.com

Site Preview:
Title: icon_prefs
Description:
Keywords and Tags: adult content, dating, https wellhello com site user profile 732877, personals, tours 78 94 wellhello com login, well hello com, wellhello, wellhello com, wellhello com login, wellhello home, wellhello login, www wellhello com, www wellhello com login
Related Terms:
Fav Icon:
Age: Over 19 years old
Domain Created: 31st August, 2004
Domain Updated: 29th November, 2022
Domain Expires: 31st August, 2026
Review

Snoop Score

3/5 (Great!)

Valuation

$10,396 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 116,154
Alexa Reach:
SEMrush Rank (US): 270,435
SEMrush Authority Score: 57
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 116 0
Traffic: 5,071 0
Cost: $2,452 USD $0 USD
Traffic

Visitors

Daily Visitors: 4,992
Monthly Visitors: 151,941
Yearly Visitors: 1,822,080
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $14 USD
Monthly Revenue: $433 USD
Yearly Revenue: $5,193 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

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

Top New Follow Links

1
Source: https://k.digital2cloud.com/?abc=523e1ef37d5df776&acme=wid.19314&media=bot&xa=n
Target: http://go.wellhello.com/go.php?aid=115152&clickid=scmsj5e59523f1f091214259978&sid=wid.19314&t=20743

2
Source: https://k.digital2cloud.com/?abc=523e1ef37d5df776&acme=wid.19314&media=bot&xa=n
Target: http://go.wellhello.com/go.php?aid=115152&clickid=hifsw5e716eb591710038248306&sid=wid.19314&t=20743

3
Source: https://k.digital2cloud.com/?abc=523e1ef37d5df776&acme=wid.19314&media=bot&xa=n
Target: http://go.wellhello.com/go.php?aid=115152&clickid=rxzqv5e65a12a529d7195082529&sid=wid.19314&t=20743

4
Source: https://k.digital2cloud.com/?abc=523e1ef37d5df776&acme=wid.4325&media=display&xa=n
Target: http://go.wellhello.com/go.php?aid=115152&clickid=vjynm5e68cb7d8c921505183472&sid=wid.4325&t=20743

5
Source: https://k.digital2cloud.com/?abc=523e1ef37d5df776&acme=wid.4325&media=display&xa=n
Target: http://go.wellhello.com/go.php?aid=115152&clickid=rshpi5e5d2692d2784251437371&sid=wid.4325&t=20743

Top Ranking Keywords (US)

1
Keyword: wellhello
Ranked Page: https://wellhello.com/

2
Keyword: wellhello com
Ranked Page: https://wellhello.com/

3
Keyword: wellhello login
Ranked Page: https://wellhello.com/

4
Keyword: well hello com
Ranked Page: https://wellhello.com/

5
Keyword: https wellhello com site user profile 732877
Ranked Page: https://wellhello.com/site/user/profile/732877

Domain Analysis

Value Length
Domain: wellhello.com 13
Domain Name: wellhello 9
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 3.02 seconds
Load Time Comparison: Faster than 23% of sites

PageSpeed Insights

Avg. (All Categories) 76
Performance 91
Accessibility 74
Best Practices 83
SEO 64
PWA 67
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://wellhello.com/
Updated: 11th December, 2022

3.51 seconds
First Contentful Paint (FCP)
48%
25%
27%

0.00 seconds
First Input Delay (FID)
99%
0%
1%

91

Performance

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

Metrics

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

Audits

Max Potential First Input Delay — 90 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://wellhello.com/
http/1.1
0
105.03400000744
1089
0
301
text/html
https://wellhello.com/
h2
105.46699992847
321.01499999408
264003
672600
200
text/html
Document
https://static.wellhello.com/build/css/wellhello/main-spa.c5245fed13d66ca876d8.min.css
h2
336.11000003293
464.30799993686
57655
314951
200
text/css
Stylesheet
https://static.wellhello.com/build/images/loading/wellhello.gif
h2
336.52699994855
398.9199999487
66045
65547
200
image/gif
Image
https://static.wellhello.com/build/js/ads.11c6cc038444d3733ffb.min.js
h2
343.86599995196
446.8329999363
1117
1333
200
application/javascript
Script
https://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
h2
344.12200003862
444.32100001723
508551
1759104
200
application/javascript
Script
data
371.04500003625
373.02699999418
0
61224
200
image/png
Image
data
373.58399992809
374.22600004356
0
18094
200
image/png
Image
data
375.05100003909
375.92799996492
0
26854
200
image/png
Image
https://static.wellhello.com/build/fonts/rubik/RubikRegular.woff2
h2
507.92400003411
526.14400000311
51575
51076
200
font/woff2
Font
https://wellhello.com/v2/api/profile/viewer/promousers
h2
710.05699993111
877.77499994263
4330
14214
200
application/json
XHR
https://wellhello.com/v2/api/registration
h2
716.41200000886
805.32000004314
2004
2735
200
application/json
XHR
https://static.wellhello.com/build/images/logo.png
h2
736.08199995942
780.25499999058
1899
1403
200
image/png
Image
https://static.wellhello.com/build/images/rainbow.png
h2
739.35099993832
799.79299998377
723
228
200
image/png
Image
https://static.wellhello.com/build/images/sprite_main.png
h2
739.47599995881
756.72599999234
21584
21086
200
image/png
Image
https://secure.authbill.com/join/tracking/track_in_overwatch.gif?track_type=prejoin&tour_id=20239&affiliate_id=104474&subid=
http/1.1
836.02799999062
1061.9269999443
340
0
200
text/html
Image
https://static.wellhello.com/build/images/sprite.png
h2
837.47799997218
984.3679999467
27869
27372
200
image/png
Image
https://static.wellhello.com/img/topusers/100/avatar144.jpg
h2
904.23799993005
965.89999995194
4469
3972
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/68/avatar144.jpg
h2
904.4340000255
971.96999995504
3845
3347
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/99/avatar288.jpg
h2
904.70900002401
967.80799992848
36382
35884
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/62/avatar288.jpg
h2
904.95799994096
939.56199998502
11420
10922
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/73/avatar144.jpg
h2
905.19199997652
966.88800002448
6458
5961
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/77/avatar144.jpg
h2
905.47400002833
972.76299993973
8007
7509
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/97/avatar288.jpg
h2
905.72299994528
974.34900002554
33081
32582
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/74/avatar144.jpg
h2
906.00099996664
975.00500001479
7215
6717
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/88/avatar144.jpg
h2
906.22100001201
997.90700001176
8678
8180
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/79/avatar144.jpg
h2
906.43600001931
967.45899994858
4691
4194
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/71/avatar144.jpg
h2
906.68399992865
1000.1530000009
37313
36815
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/60/avatar144.jpg
h2
907.03799994662
973.20499992929
7986
7488
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/61/avatar144.jpg
h2
907.40899997763
968.10599998571
9289
8792
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/66/avatar144.jpg
h2
907.72799996193
968.34899997339
4541
4044
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/59/avatar144.jpg
h2
908.12299994286
958.16899999045
7694
7196
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/90/avatar144.jpg
h2
908.48500002176
972.54400001839
5384
4886
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/64/avatar144.jpg
h2
908.69299997576
972.15599997435
4380
3882
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/69/avatar288.jpg
h2
908.89900003094
974.03000004124
23006
22508
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/78/avatar144.jpg
h2
909.18399998918
999.76199993398
5711
5214
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/108/avatar144.jpg
h2
909.38199998345
989.98499999288
8688
8191
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/70/avatar288.jpg
h2
909.76299997419
975.39399995003
20149
19651
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/89/avatar288.jpg
h2
909.96600000653
966.27999993507
20649
20151
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/91/avatar144.jpg
h2
910.18300002906
965.59499995783
5070
4572
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/92/avatar144.jpg
h2
910.5119999731
968.97799998987
5779
5282
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/107/avatar288.jpg
h2
910.77800001949
966.54399996623
16794
16295
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/58/avatar144.jpg
h2
911.16000001784
968.7429999467
6391
5894
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/98/avatar144.jpg
h2
911.44099994563
979.40499999095
25941
25442
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/76/avatar144.jpg
h2
911.67199995834
973.49200001918
5160
4662
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/65/avatar144.jpg
h2
911.91100003198
975.19299993291
5931
5433
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/81/avatar288.jpg
h2
912.11199993268
979.83199998271
26776
26278
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/75/avatar144.jpg
h2
912.37799997907
985.22699996829
8438
7940
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/67/avatar144.jpg
h2
912.61100000702
986.3980000373
8398
7901
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/63/avatar144.jpg
h2
913.13599993009
1005.2099999739
6913
6416
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/105/avatar144.jpg
h2
913.37800002657
995.94699998852
12016
11518
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/57/avatar144.jpg
h2
913.60500000883
969.29599996656
4791
4294
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/89/avatar.jpg
h2
913.79399993457
969.56799994223
19773
19275
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/91/avatar.jpg
h2
914.03799992986
970.09800001979
19928
19430
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/92/avatar.jpg
h2
914.27399998065
972.96199994162
16994
16495
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/107/avatar.jpg
h2
914.48499995749
981.34699999355
16424
15926
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/58/avatar126.jpg
h2
914.78500002995
1005.6509999558
5250
4753
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/98/avatar.jpg
h2
914.98000000138
984.91999995895
39407
38908
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/76/avatar126.jpg
h2
915.27500003576
972.37500001211
4292
3794
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/65/avatar126.jpg
h2
915.46599997673
970.37400002591
4978
4481
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/81/avatar.jpg
h2
915.84799997509
982.359000016
27422
26924
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/75/avatar.jpg
h2
916.06299998239
988.13800001517
16033
15535
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/67/avatar.jpg
h2
916.30699997768
971.70100000221
17027
16529
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/63/avatar126.jpg
h2
916.62399994675
995.01800001599
5721
5223
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/105/avatar.jpg
h2
916.97899997234
998.53899993468
33564
33066
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/57/avatar126.jpg
h2
917.28099994361
1020.0379999587
4000
3503
200
image/jpeg
Image
https://wellhello.com/img/topusers/63/avatar126.jpg
h2
967.3349999357
1050.6289999466
6347
5223
200
image/jpeg
Image
https://wellhello.com/img/topusers/105/avatar.jpg
h2
980.81800004002
1070.7920000423
34191
33066
200
image/jpeg
Image
https://wellhello.com/img/topusers/57/avatar.jpg
h2
980.89400003664
1076.1720000301
24239
23112
200
image/jpeg
Image
https://mad-collective.apm.us-east-1.aws.found.io/intake/v2/rum/events
h2
1393.0189999519
1437.9320000298
503
0
200
Preflight
https://mad-collective.apm.us-east-1.aws.found.io/intake/v2/rum/events
h2
1438.4689999279
1509.5919999294
414
74
400
application/json
XHR
https://wellhello.com/v2/api/login
h2
1823.5090000089
1887.4969999306
1573
1072
200
application/json
XHR
https://mad-collective.apm.us-east-1.aws.found.io/intake/v2/rum/events
h2
2396.1549999658
2452.1229999373
414
74
400
application/json
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
325.534
17.778
353.418
27.671
466.168
10.885
477.649
42.962
520.682
21.6
547.295
28.501
578.724
176.161
754.944
5.01
769.931
6.415
792.803
25.367
818.723
18.017
836.891
7.16
844.143
8.527
879.385
46.751
926.193
18.193
945.139
5.788
1889.273
5.218
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images — Potential savings of 160 KiB
Images can slow down the page's load time. Wellhello.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://static.wellhello.com/img/topusers/98/avatar.jpg
38908
31480
https://static.wellhello.com/img/topusers/105/avatar.jpg
33066
26753
https://static.wellhello.com/img/topusers/81/avatar.jpg
26924
21784
https://static.wellhello.com/img/topusers/91/avatar.jpg
19430
15721
https://static.wellhello.com/img/topusers/89/avatar.jpg
19275
15595
https://static.wellhello.com/img/topusers/67/avatar.jpg
16529
13373
https://static.wellhello.com/img/topusers/92/avatar.jpg
16495
13346
https://static.wellhello.com/img/topusers/107/avatar.jpg
15926
12886
https://static.wellhello.com/img/topusers/75/avatar.jpg
15535
12569
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Wellhello.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Wellhello.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Wellhello.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 52 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Wellhello.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://static.wellhello.com/build/css/wellhello/main-spa.c5245fed13d66ca876d8.min.css
57655
53517
Efficiently encode images — Potential savings of 107 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://static.wellhello.com/img/topusers/71/avatar144.jpg
36815
28062
https://static.wellhello.com/img/topusers/99/avatar288.jpg
35884
19267
https://static.wellhello.com/img/topusers/97/avatar288.jpg
32582
19250
https://static.wellhello.com/img/topusers/98/avatar144.jpg
25442
17421
https://static.wellhello.com/img/topusers/98/avatar.jpg
38908
14369
https://static.wellhello.com/img/topusers/105/avatar.jpg
33066
5752
https://wellhello.com/img/topusers/105/avatar.jpg
33066
5752
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 220 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://wellhello.com/
216.543
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Wellhello.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://wellhello.com/
190
https://wellhello.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Wellhello.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 6 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://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
5945
Avoids enormous network payloads — Total size was 1,684 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
508551
https://wellhello.com/
264003
https://static.wellhello.com/build/images/loading/wellhello.gif
66045
https://static.wellhello.com/build/css/wellhello/main-spa.c5245fed13d66ca876d8.min.css
57655
https://static.wellhello.com/build/fonts/rubik/RubikRegular.woff2
51575
https://static.wellhello.com/img/topusers/98/avatar.jpg
39407
https://static.wellhello.com/img/topusers/71/avatar144.jpg
37313
https://static.wellhello.com/img/topusers/99/avatar288.jpg
36382
https://wellhello.com/img/topusers/105/avatar.jpg
34191
https://static.wellhello.com/img/topusers/105/avatar.jpg
33564
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Wellhello.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.3 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://wellhello.com/
484.779
10.02
1.394
https://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
280.888
229.056
27.849
Unattributable
82.771
4.026
0
Minimizes main-thread work — 0.9 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
300.828
Script Evaluation
243.73
Style & Layout
149.932
Rendering
102.103
Parse HTML & CSS
34.259
Script Parsing & Compilation
29.347
Keep request counts low and transfer sizes small — 70 requests • 1,684 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
70
1724712
Image
58
831484
Script
2
509668
Document
1
264003
Stylesheet
1
57655
Font
1
51575
Other
7
10327
Media
0
0
Third-party
4
1671
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.046070921985816
0.041481481481481
0.00079614985219945
0.00067790977514012
0.00043354694921752
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task 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://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
1559
88
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
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 wellhello.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Metrics

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

Other

Eliminate render-blocking resources — Potential savings of 330 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Wellhello.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://static.wellhello.com/build/css/wellhello/main-spa.c5245fed13d66ca876d8.min.css
57655
310
Reduce unused JavaScript — Potential savings of 357 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
508551
365706
Serve images in next-gen formats — Potential savings of 304 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://static.wellhello.com/img/topusers/71/avatar144.jpg
36815
31562.75
61224
28336.2
https://static.wellhello.com/img/topusers/99/avatar288.jpg
35884
27660.95
https://static.wellhello.com/img/topusers/98/avatar.jpg
38908
26146.05
https://static.wellhello.com/img/topusers/97/avatar288.jpg
32582
25989.8
https://static.wellhello.com/img/topusers/98/avatar144.jpg
25442
21247.95
https://static.wellhello.com/img/topusers/105/avatar.jpg
33066
20451.1
https://wellhello.com/img/topusers/105/avatar.jpg
33066
20451.1
https://static.wellhello.com/img/topusers/81/avatar.jpg
26924
13519.45
https://static.wellhello.com/img/topusers/81/avatar288.jpg
26278
13341.2
https://static.wellhello.com/img/topusers/69/avatar288.jpg
22508
11871.35
https://wellhello.com/img/topusers/57/avatar.jpg
23112
11240.85
26854
11230.5
https://static.wellhello.com/img/topusers/70/avatar288.jpg
19651
10730.65
https://static.wellhello.com/img/topusers/89/avatar288.jpg
20151
10305.85
18094
9528.45
https://static.wellhello.com/img/topusers/89/avatar.jpg
19275
9204.1
https://static.wellhello.com/build/images/sprite.png
27372
8787.25
Preload Largest Contentful Paint image — Potential savings of 240 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://static.wellhello.com/img/topusers/89/avatar288.jpg
240

Other

Serve static assets with an efficient cache policy — 4 resources found
Wellhello.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://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
0
508551
https://static.wellhello.com/build/css/wellhello/main-spa.c5245fed13d66ca876d8.min.css
0
57655
https://static.wellhello.com/build/js/ads.11c6cc038444d3733ffb.min.js
0
1117
https://secure.authbill.com/join/tracking/track_in_overwatch.gif?track_type=prejoin&tour_id=20239&affiliate_id=104474&subid=
0
340
Avoid an excessive DOM size — 1,595 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
1595
Maximum DOM Depth
13
Maximum Child Elements
126
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://static.wellhello.com/build/fonts/rubik/RubikRegular.woff2
18.219999969006
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://static.wellhello.com/img/topusers/89/avatar.jpg
https://static.wellhello.com/img/topusers/91/avatar.jpg
https://static.wellhello.com/img/topusers/92/avatar.jpg
https://static.wellhello.com/img/topusers/107/avatar.jpg
https://static.wellhello.com/img/topusers/98/avatar.jpg
https://static.wellhello.com/img/topusers/81/avatar.jpg
https://static.wellhello.com/img/topusers/75/avatar.jpg
https://static.wellhello.com/img/topusers/67/avatar.jpg
https://static.wellhello.com/img/topusers/105/avatar.jpg
https://static.wellhello.com/img/topusers/58/avatar126.jpg
https://static.wellhello.com/img/topusers/76/avatar126.jpg
https://static.wellhello.com/img/topusers/65/avatar126.jpg
https://static.wellhello.com/img/topusers/63/avatar126.jpg
https://static.wellhello.com/img/topusers/57/avatar126.jpg
https://static.wellhello.com/build/images/logo.png
https://static.wellhello.com/build/images/logo.png
74

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of wellhello.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.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

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

Names and labels

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

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Contrast

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

Names and labels

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

Best practices

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

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Vue
core-js
core-js-global@3.6.5
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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://wellhello.com/
Allowed

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 400 (Bad Request)
Failed to load resource: the server responded with a status of 400 (Bad Request)
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
64

SEO

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

Crawling and Indexing

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

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Crawling and Indexing

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

Manual Checks

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

PWA

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

Installable

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

PWA Optimized

Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wellhello.com on mobile screens.

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.
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) 68
Performance 50
Accessibility 74
Best Practices 75
SEO 69
PWA 70
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://wellhello.com/
Updated: 11th December, 2022

5.86 seconds
First Contentful Paint (FCP)
23%
20%
57%

0.02 seconds
First Input Delay (FID)
91%
6%
3%

50

Performance

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

Metrics

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

Other

Properly size images — Potential savings of 16 KiB
Images can slow down the page's load time. Wellhello.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://static.wellhello.com/img/topusers/98/avatar.jpg
38908
6467
https://static.wellhello.com/img/topusers/105/avatar.jpg
33066
5496
https://static.wellhello.com/img/topusers/81/avatar.jpg
26924
4475
Defer offscreen images — Potential savings of 7 KiB
Time to Interactive can be slowed down by resources on the page. Wellhello.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://static.wellhello.com/img/topusers/100/avatar144.jpg
3972
3972
https://static.wellhello.com/img/topusers/68/avatar144.jpg
3347
3347
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Wellhello.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Wellhello.com should consider minifying JS files.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 370 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://wellhello.com/
365.259
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Wellhello.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://wellhello.com/
630
https://wellhello.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Wellhello.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.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 1,687 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
508551
https://wellhello.com/
263622
https://static.wellhello.com/build/images/loading/wellhello.gif
66044
https://static.wellhello.com/build/css/wellhello/main-spa.c5245fed13d66ca876d8.min.css
57655
https://static.wellhello.com/build/fonts/rubik/RubikRegular.woff2
51574
https://static.wellhello.com/img/topusers/98/avatar.jpg
39406
https://static.wellhello.com/img/topusers/71/avatar144.jpg
37313
https://wellhello.com/img/topusers/105/avatar.jpg
34193
https://static.wellhello.com/img/topusers/105/avatar.jpg
33564
https://static.wellhello.com/build/images/sprite.png
27869
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Wellhello.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.
Keep request counts low and transfer sizes small — 70 requests • 1,687 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
70
1727063
Image
58
834183
Script
2
509668
Document
1
263622
Stylesheet
1
57655
Font
1
51574
Other
7
10361
Media
0
0
Third-party
4
1671
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 4 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.078125
0.0077017670737372
0.0042188023461236
0.0026980712678697
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 9 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://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
7445
438
https://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
7883
188
https://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
7290
155
https://wellhello.com/
2694
127
https://wellhello.com/
2821
110
Unattributable
645
106
https://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
8071
100
https://wellhello.com/
2610
84
https://wellhello.com/
2931
56
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
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 wellhello.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://wellhello.com/
http/1.1
0
190.92100020498
1101
0
301
text/html
https://wellhello.com/
h2
191.28699973226
555.55299948901
263622
672600
200
text/html
Document
https://static.wellhello.com/build/css/wellhello/main-spa.c5245fed13d66ca876d8.min.css
h2
576.36099960655
619.66199986637
57655
314951
200
text/css
Stylesheet
https://static.wellhello.com/build/images/loading/wellhello.gif
h2
576.6319995746
610.55599991232
66044
65547
200
image/gif
Image
https://static.wellhello.com/build/js/ads.11c6cc038444d3733ffb.min.js
h2
582.66100008041
601.91399976611
1117
1333
200
application/javascript
Script
https://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
h2
583.17799959332
630.69000001997
508551
1759104
200
application/javascript
Script
data
613.66300005466
616.58000014722
0
61224
200
image/png
Image
data
617.27599985898
617.93099995703
0
18094
200
image/png
Image
data
618.82799956948
619.98599953949
0
26854
200
image/png
Image
https://static.wellhello.com/build/fonts/rubik/RubikRegular.woff2
h2
675.35400018096
688.99799976498
51574
51076
200
font/woff2
Font
https://wellhello.com/v2/api/profile/viewer/promousers
h2
1008.4560001269
1210.539999418
4343
14216
200
application/json
XHR
https://wellhello.com/v2/api/registration
h2
1016.1600001156
1226.6969997436
2005
2735
200
application/json
XHR
https://static.wellhello.com/build/images/logo.png
h2
1040.4650000855
1045.3249998391
1899
1403
200
image/png
Image
https://static.wellhello.com/build/images/rainbow.png
h2
1044.2629996687
1073.6369993538
723
228
200
image/png
Image
https://static.wellhello.com/build/images/sprite_main.png
h2
1044.4799996912
1086.1229998991
21583
21086
200
image/png
Image
https://static.wellhello.com/img/topusers/100/avatar144.jpg
h2
1231.9620000198
1237.0069995522
4469
3972
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/68/avatar144.jpg
h2
1232.3309993371
1243.1410001591
3844
3347
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/99/avatar144.jpg
h2
1232.506999746
1238.0649996921
21862
21364
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/62/avatar144.jpg
h2
1232.7069994062
1237.6699997112
5503
5006
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/73/avatar144.jpg
h2
1233.1739999354
1322.8159993887
6458
5961
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/77/avatar144.jpg
h2
1233.61299932
1275.8630001917
8006
7509
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/97/avatar144.jpg
h2
1233.9319996536
1245.0899994001
26835
26337
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/74/avatar144.jpg
h2
1234.1909995303
1261.9650000706
7214
6717
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/88/avatar144.jpg
h2
1234.6999999136
1261.6059994325
8677
8180
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/79/avatar144.jpg
h2
1235.425000079
1262.2109996155
4691
4194
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/71/avatar144.jpg
h2
1235.6219999492
1322.4189998582
37313
36815
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/60/avatar144.jpg
h2
1235.8559994027
1245.4679999501
7985
7488
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/61/avatar288.jpg
h2
1236.2709995359
1334.0320000425
26482
25984
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/66/avatar144.jpg
h2
1236.762999557
1262.4549996108
4541
4044
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/59/avatar144.jpg
h2
1237.4249994755
1325.8679993451
7693
7196
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/90/avatar144.jpg
h2
1238.4500000626
1267.5470001996
5383
4886
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/64/avatar144.jpg
h2
1238.6569995433
1244.6200000122
4379
3882
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/69/avatar288.jpg
h2
1238.7760002166
1257.7289994806
23006
22508
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/78/avatar144.jpg
h2
1239.017999731
1256.5299998969
5711
5214
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/108/avatar144.jpg
h2
1239.6129993722
1326.3240000233
8688
8191
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/70/avatar288.jpg
h2
1239.8729994893
1269.1970001906
20149
19651
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/89/avatar288.jpg
h2
1240.0310002267
1245.9410000592
20649
20151
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/91/avatar144.jpg
h2
1240.2119999751
1291.2010001019
5069
4572
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/92/avatar144.jpg
h2
1240.9979999065
1269.5189993829
5779
5282
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/107/avatar288.jpg
h2
1241.0929994658
1323.996999301
16793
16295
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/58/avatar144.jpg
h2
1241.1850001663
1334.6680002287
6391
5894
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/98/avatar144.jpg
h2
1241.4139993489
1248.3649998903
25940
25442
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/76/avatar144.jpg
h2
1241.6139999405
1246.9509998336
5159
4662
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/65/avatar144.jpg
h2
1242.0619996265
1321.6659994796
5930
5433
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/81/avatar288.jpg
h2
1242.1889994293
1247.3169993609
26776
26278
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/75/avatar288.jpg
h2
1242.7989998832
1271.8230001628
20642
20144
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/67/avatar144.jpg
h2
1242.9659999907
1292.1649999917
8398
7901
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/63/avatar144.jpg
h2
1243.5079999268
1292.8379997611
6913
6416
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/105/avatar144.jpg
h2
1243.6629999429
1249.8289998621
12016
11518
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/57/avatar144.jpg
h2
1243.8049996272
1255.2729994059
4791
4294
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/89/avatar.jpg
h2
1243.92899964
1265.7389994711
19773
19275
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/91/avatar.jpg
h2
1244.3570001051
1321.2500000373
19928
19430
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/92/avatar.jpg
h2
1245.7849998027
1272.1569994465
16993
16495
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/107/avatar.jpg
h2
1246.5279996395
1292.4899999052
16424
15926
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/58/avatar126.jpg
h2
1246.639999561
1272.4519995973
5250
4753
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/98/avatar.jpg
h2
1246.7510001734
1291.7050002143
39406
38908
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/76/avatar126.jpg
h2
1246.8759994954
1278.2669998705
4291
3794
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/65/avatar126.jpg
h2
1247.8789994493
1302.1989995614
4978
4481
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/81/avatar.jpg
h2
1247.9989994317
1320.8069996908
27422
26924
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/75/avatar.jpg
h2
1248.2249997556
1324.8439999297
16033
15535
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/67/avatar.jpg
h2
1249.3829997256
1323.6159998924
17027
16529
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/63/avatar126.jpg
h2
1249.5809998363
1325.6120001897
5720
5223
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/105/avatar.jpg
h2
1249.7429996729
1323.2279997319
33564
33066
200
image/jpeg
Image
https://static.wellhello.com/img/topusers/57/avatar126.jpg
h2
1250.3619994968
1324.3329999968
4000
3503
200
image/jpeg
Image
https://wellhello.com/img/topusers/63/avatar126.jpg
h2
1322.1049997956
1460.5879997835
6353
5223
200
image/jpeg
Image
https://wellhello.com/img/topusers/105/avatar.jpg
h2
1343.6099998653
1489.175000228
34193
33066
200
image/jpeg
Image
https://wellhello.com/img/topusers/57/avatar.jpg
h2
1343.7289996073
1601.6889996827
24235
23112
200
image/jpeg
Image
https://secure.authbill.com/join/tracking/track_in_overwatch.gif?track_type=prejoin&tour_id=20239&affiliate_id=104474&subid=
http/1.1
1343.8470000401
1629.1109994054
340
0
200
text/html
Image
https://static.wellhello.com/build/images/sprite.png
h2
1343.979999423
1366.3179995492
27869
27372
200
image/png
Image
https://mad-collective.apm.us-east-1.aws.found.io/intake/v2/rum/events
h2
1795.5470001325
1872.0959993079
503
0
200
Preflight
https://mad-collective.apm.us-east-1.aws.found.io/intake/v2/rum/events
h2
1872.5889995694
1941.4179995656
414
74
400
application/json
XHR
https://wellhello.com/v2/api/login
h2
2292.3649996519
2447.2089996561
1581
1072
200
application/json
XHR
https://mad-collective.apm.us-east-1.aws.found.io/intake/v2/rum/events
h2
2955.0289995968
3012.0459999889
414
74
400
application/json
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
561.151
20.883
594.027
31.723
627.712
11.939
639.947
54.821
700.632
5.219
779.81
26.549
806.421
38.839
845.282
219.003
1064.335
5.394
1101.007
28.14
1212.487
46.903
1259.461
15.564
1275.051
7.864
1282.924
25.119
1321.374
11.837
2449.034
5.777
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Speed Index — 4.5 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 380 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Audits

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

Other

Reduce unused CSS — Potential savings of 53 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Wellhello.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://static.wellhello.com/build/css/wellhello/main-spa.c5245fed13d66ca876d8.min.css
57655
53945
Efficiently encode images — Potential savings of 104 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://static.wellhello.com/img/topusers/71/avatar144.jpg
36815
28062
https://static.wellhello.com/img/topusers/97/avatar144.jpg
26337
20473
https://static.wellhello.com/img/topusers/98/avatar144.jpg
25442
17421
https://static.wellhello.com/img/topusers/99/avatar144.jpg
21364
15175
https://static.wellhello.com/img/topusers/98/avatar.jpg
38908
14369
https://static.wellhello.com/img/topusers/105/avatar.jpg
33066
5752
https://wellhello.com/img/topusers/105/avatar.jpg
33066
5752
Avoid serving legacy JavaScript to modern browsers — Potential savings of 6 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://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
5945
Reduce JavaScript execution time — 1.3 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://wellhello.com/
2277.58
50.352
6.26
https://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
1358.18
1090.104
152.336
Unattributable
404.532
15.084
0

Metrics

First Contentful Paint — 3.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 7.8 s
The time taken for the page to become fully interactive.
Largest Contentful Paint — 6.9 s
The timing of the largest text or image that is painted.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 1,270 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Wellhello.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://static.wellhello.com/build/css/wellhello/main-spa.c5245fed13d66ca876d8.min.css
57655
1080
Reduce unused JavaScript — Potential savings of 357 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
508551
365706
Serve images in next-gen formats — Potential savings of 314 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://static.wellhello.com/img/topusers/71/avatar144.jpg
36815
31562.75
61224
28336.2
https://static.wellhello.com/img/topusers/98/avatar.jpg
38908
26146.05
https://static.wellhello.com/img/topusers/97/avatar144.jpg
26337
23423
https://static.wellhello.com/img/topusers/98/avatar144.jpg
25442
21247.95
https://static.wellhello.com/img/topusers/105/avatar.jpg
33066
20451.1
https://wellhello.com/img/topusers/105/avatar.jpg
33066
20451.1
https://static.wellhello.com/img/topusers/99/avatar144.jpg
21364
18231.15
https://static.wellhello.com/img/topusers/81/avatar.jpg
26924
13519.45
https://static.wellhello.com/img/topusers/81/avatar288.jpg
26278
13341.2
https://static.wellhello.com/img/topusers/61/avatar288.jpg
25984
12610.3
https://static.wellhello.com/img/topusers/69/avatar288.jpg
22508
11871.35
https://wellhello.com/img/topusers/57/avatar.jpg
23112
11240.85
26854
11230.5
https://static.wellhello.com/img/topusers/70/avatar288.jpg
19651
10730.65
https://static.wellhello.com/img/topusers/89/avatar288.jpg
20151
10305.85
18094
9528.45
https://static.wellhello.com/img/topusers/89/avatar.jpg
19275
9204.1
https://static.wellhello.com/img/topusers/75/avatar288.jpg
20144
8859.65
https://static.wellhello.com/build/images/sprite.png
27372
8787.25
Serve static assets with an efficient cache policy — 4 resources found
Wellhello.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://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
0
508551
https://static.wellhello.com/build/css/wellhello/main-spa.c5245fed13d66ca876d8.min.css
0
57655
https://static.wellhello.com/build/js/ads.11c6cc038444d3733ffb.min.js
0
1117
https://secure.authbill.com/join/tracking/track_in_overwatch.gif?track_type=prejoin&tour_id=20239&affiliate_id=104474&subid=
0
340
Avoid an excessive DOM size — 1,595 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
1595
Maximum DOM Depth
13
Maximum Child Elements
126
Minimize main-thread work — 4.1 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
1442.256
Script Evaluation
1159.272
Style & Layout
707.888
Rendering
437.756
Script Parsing & Compilation
159.264
Parse HTML & CSS
155.668
Garbage Collection
31.12
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://static.wellhello.com/build/fonts/rubik/RubikRegular.woff2
13.643999584019
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://static.wellhello.com/img/topusers/89/avatar.jpg
https://static.wellhello.com/img/topusers/91/avatar.jpg
https://static.wellhello.com/img/topusers/92/avatar.jpg
https://static.wellhello.com/img/topusers/107/avatar.jpg
https://static.wellhello.com/img/topusers/98/avatar.jpg
https://static.wellhello.com/img/topusers/81/avatar.jpg
https://static.wellhello.com/img/topusers/75/avatar.jpg
https://static.wellhello.com/img/topusers/67/avatar.jpg
https://static.wellhello.com/img/topusers/105/avatar.jpg
https://static.wellhello.com/img/topusers/58/avatar126.jpg
https://static.wellhello.com/img/topusers/76/avatar126.jpg
https://static.wellhello.com/img/topusers/65/avatar126.jpg
https://static.wellhello.com/img/topusers/63/avatar126.jpg
https://static.wellhello.com/img/topusers/57/avatar126.jpg
https://static.wellhello.com/build/images/logo.png
https://static.wellhello.com/build/images/logo.png
First Contentful Paint (3G) — 7890 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
74

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of wellhello.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.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

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

Names and labels

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

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Contrast

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

Names and labels

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

Best practices

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

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
75

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Vue
core-js
core-js-global@3.6.5
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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://wellhello.com/
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://static.wellhello.com/build/images/logo.png
196 x 40
196 x 40
392 x 80

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 400 (Bad Request)
Failed to load resource: the server responded with a status of 400 (Bad Request)
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://static.wellhello.com/build/js/wellhello/main-spa.c5245fed13d66ca876d8.min.js
69

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for wellhello.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 wellhello.com on mobile screens.
Document uses legible font sizes — 96.89% 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
.form--registration .bottom-wrapper .terms
3.09%
10px
html
0.02%
10px
0.00%
10px
96.89%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

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

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Crawling and Indexing

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

Manual Checks

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

PWA

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

Installable

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

PWA Optimized

Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wellhello.com on mobile screens.

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

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: No
Name: On behalf of wellhello.com owner
Organization: Identity Protection Service
Country: GB
City: Hayes
State: Middlesex
Post Code: UB3 9TR
Email: b60f2800-fac6-4a86-9f69-80369752e00f@identity-protect.org
Phone: +44.1483307527
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Amazon Registrar, Inc. 3.162.3.75
Security

Visitor Safety

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

SSL/TLS Certificate

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

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

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

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : Oct 1 01:56:35.285 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:25:6A:F0:DC:CB:C1:09:E2:F6:1D:0A:F6:
D7:73:73:59:4B:D5:60:97:59:A9:5F:3A:12:E7:5A:F9:
1C:89:8F:7F:02:20:2F:78:19:59:75:23:DA:89:80:63:
CB:DA:56:F8:B2:BC:5B:64:20:82:B7:FF:49:F5:58:35:
55:88:42:07:BB:36
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B3:73:77:07:E1:84:50:F8:63:86:D6:05:A9:DC:11:09:
4A:79:2D:B1:67:0C:0B:87:DC:F0:03:0E:79:36:A5:9A
Timestamp : Oct 1 01:56:35.311 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:35:71:1F:1A:84:3E:55:64:66:D9:51:88:
1D:B1:26:FF:BE:A3:72:0B:63:11:38:F6:B9:69:F3:96:
F7:CC:52:86:02:21:00:92:6A:90:D7:77:78:BD:33:3E:
F0:F8:6E:BD:D0:3F:3C:95:EB:EA:54:0C:AC:B6:E7:EA:
6B:78:4F:78:A6:1F:1A
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
Timestamp : Oct 1 01:56:35.277 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:7E:0B:F5:60:33:ED:C7:83:EB:07:5B:D3:
E7:8E:50:C7:EF:41:A4:6A:76:84:41:6A:8C:B0:55:32:
60:80:08:FB:02:21:00:90:B0:C3:01:94:44:7C:BD:5C:
51:5E:60:E8:8C:15:E6:9D:B2:E9:02:15:FA:49:AD:E3:
34:22:86:9B:E5:2C:71
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:sni.cloudflaressl.com
DNS:wellhello.com
DNS:*.wellhello.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
wellhello.com. 54.227.234.29 IN 59
wellhello.com. 52.207.55.27 IN 59
wellhello.com. 35.168.189.106 IN 59

NS Records

Host Nameserver Class TTL
wellhello.com. ns-1071.awsdns-05.org. IN 21599
wellhello.com. ns-1627.awsdns-11.co.uk. IN 21599
wellhello.com. ns-246.awsdns-30.com. IN 21599
wellhello.com. ns-865.awsdns-44.net. IN 21599

MX Records

Priority Host Server Class TTL
1 wellhello.com. aspmx.l.google.com. IN 3599
10 wellhello.com. aspmx2.googlemail.com. IN 3599
10 wellhello.com. aspmx3.googlemail.com. IN 3599
5 wellhello.com. alt1.aspmx.l.google.com. IN 3599
5 wellhello.com. alt2.aspmx.l.google.com. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
wellhello.com. ns-865.awsdns-44.net. awsdns-hostmaster.amazon.com. 899

TXT Records

Host Value Class TTL
wellhello.com. google-site-verification=9Q-FWEtnY1GBVyUP03KbPmEcUxZcRaYocmpLZKAwGVo IN 299
wellhello.com. google-site-verification=BKKwzWQM10-eWjvPYwCoQVBdF9doULBRd9RoWZMUgeA IN 299
wellhello.com. google-site-verification=E1fp5EO6eMK-bGJ9sy8dVfBldBT3YM8GoezsE7kudIM IN 299
wellhello.com. google-site-verification=OoLeH9EFnEwEOEuD0MwLY2yo8GAfDs4WX4_UW2bfy-Q IN 299
wellhello.com. google-site-verification=dbugvklyvHsv7RnJT3KxTGrdhl2Xqoms3OXYX1UHYDU IN 299
wellhello.com. google-site-verification=mSTCmgCiwEBWohQPhJQ96eQbK2poAD1lehwphRv8Xl8 IN 299
wellhello.com. google-site-verification=wlNVPBhvhP8D5wzr4oYgEU0j3t7jsXBPeERT0SQRL2Q IN 299
wellhello.com. v=spf1 IN 299

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 26th March, 2023
Content-Type: text/html; charset=UTF-8
expires: 19th November, 1981
Cache-Control: no-cache, private
Server: cloudflare
Connection: keep-alive
set-cookie: *
pragma: no-cache
request-id: 332129e3-a67b-4c7a-8476-0ea3ab0dec89
request-time: 1679857638
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=xHRqOwoG0ogfjY0qcmRSg37ZhqKlpIhSIp7P0D5QAjl7FmZQZuiFPnfeDsisLwtjDqaehji3O%2BKQdM1Hjk%2FcwEuXmVAxyiDaYAkQJYtzFOrsXEsF3M9taIOPhJiVCXu9"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 7ae1acfebcd28c7b-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 31st August, 2004
Changed: 29th November, 2022
Expires: 31st August, 2026
Registrar: Amazon Registrar, Inc.
Status: clientUpdateProhibited
clientTransferProhibited
clientDeleteProhibited
Nameservers: derek.ns.cloudflare.com
ligia.ns.cloudflare.com
Owner Name: On behalf of wellhello.com owner
Owner Organization: Identity Protection Service
Owner Street: PO Box 786
Owner Post Code: UB3 9TR
Owner City: Hayes
Owner State: Middlesex
Owner Country: GB
Owner Phone: +44.1483307527
Owner Email: b60f2800-fac6-4a86-9f69-80369752e00f@identity-protect.org
Admin Name: On behalf of wellhello.com owner
Admin Organization: Identity Protection Service
Admin Street: PO Box 786
Admin Post Code: UB3 9TR
Admin City: Hayes
Admin State: Middlesex
Admin Country: GB
Admin Phone: +44.1483307527
Admin Email: b60f2800-fac6-4a86-9f69-80369752e00f@identity-protect.org
Tech Name: On behalf of wellhello.com owner
Tech Organization: Identity Protection Service
Tech Street: PO Box 786
Tech Post Code: UB3 9TR
Tech City: Hayes
Tech State: Middlesex
Tech Country: GB
Tech Phone: +44.1483307527
Tech Email: b60f2800-fac6-4a86-9f69-80369752e00f@identity-protect.org
Full Whois: Domain Name: wellhello.com
Registry Domain ID: 128844942_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrar.amazon.com
Registrar URL: https://registrar.amazon.com
Updated Date: 2022-11-29T17:13:49Z
Creation Date: 2004-08-31T18:29:20Z
Registrar Registration Expiration Date: 2026-08-31T18:29:20Z
Registrar: Amazon Registrar, Inc.
Registrar IANA ID: 468
Registrar Abuse Contact Email: abuse@amazonaws.com
Registrar Abuse Contact Phone: +1.2067406200
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: On behalf of wellhello.com owner
Registrant Organization: Identity Protection Service
Registrant Street: PO Box 786
Registrant City: Hayes
Registrant State/Province: Middlesex
Registrant Postal Code: UB3 9TR
Registrant Country: GB
Registrant Phone: +44.1483307527
Registrant Phone Ext:
Registrant Fax: +44.1483304031
Registrant Fax Ext:
Registrant Email: b60f2800-fac6-4a86-9f69-80369752e00f@identity-protect.org
Registry Admin ID: Not Available From Registry
Admin Name: On behalf of wellhello.com owner
Admin Organization: Identity Protection Service
Admin Street: PO Box 786
Admin City: Hayes
Admin State/Province: Middlesex
Admin Postal Code: UB3 9TR
Admin Country: GB
Admin Phone: +44.1483307527
Admin Phone Ext:
Admin Fax: +44.1483304031
Admin Fax Ext:
Admin Email: b60f2800-fac6-4a86-9f69-80369752e00f@identity-protect.org
Registry Tech ID: Not Available From Registry
Tech Name: On behalf of wellhello.com owner
Tech Organization: Identity Protection Service
Tech Street: PO Box 786
Tech City: Hayes
Tech State/Province: Middlesex
Tech Postal Code: UB3 9TR
Tech Country: GB
Tech Phone: +44.1483307527
Tech Phone Ext:
Tech Fax: +44.1483304031
Tech Fax Ext:
Tech Email: b60f2800-fac6-4a86-9f69-80369752e00f@identity-protect.org
Name Server: DEREK.NS.CLOUDFLARE.COM
Name Server: LIGIA.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-03-26T20:07:20Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

By submitting a query to the Amazon Registrar, Inc. WHOIS database, you
agree to abide by the following terms. The data in Amazon Registrar, Inc.'s
WHOIS database is provided by Amazon Registrar, Inc. for the sole purpose of
assisting you in obtaining information about domain name accuracy. You agree
to use this data only for lawful purposes and further agree not to use this
data for any unlawful purpose or to: (1) enable, allow, or otherwise support
the transmission by email, telephone, or facsimile of commercial advertising
or unsolicited bulk email, or (2) enable high volume, automated, electronic
processes to collect or compile this data for any purpose, including mining
this data for your own personal or commercial purposes. Amazon Registrar, Inc.
reserves the right to restrict or terminate your access to the data if you fail
to abide by these terms of use. Amazon Registrar, Inc. reserves the right
to modify these terms at any time.

Visit Amazon Registrar, Inc. at https://registrar.amazon.com

Contact information available here:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-contact-support.html

© 2020, Amazon.com, Inc., or its affiliates

Nameservers

Name IP Address
derek.ns.cloudflare.com 172.64.33.154
ligia.ns.cloudflare.com 172.64.34.4
Related

Subdomains

Domain Subdomain
go
tours
tours-78-94

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address