messenger.com

messenger.com is SSL secured

Free website and domain report on messenger.com

Last Updated: 17th October, 2023 Update Now
Overview

Snoop Summary for messenger.com

This is a free and comprehensive report about messenger.com. The domain messenger.com is currently hosted on a server located in Ireland with the IP address 31.13.71.1, where the local currency is EUR and English is the local language. Our records indicate that messenger.com is owned/operated by Meta Platforms, Inc.. Messenger.com is expected to earn an estimated $97,055 USD per day from advertising revenue. The sale of messenger.com would possibly be worth $70,849,881 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Messenger.com is unbelievably popular with an estimated 10,423,797 daily unique visitors. This report was last updated 17th October, 2023.

About messenger.com

Site Preview: messenger.com messenger.com
Title: Messenger
Description: Hang out anytime, anywhere—Messenger makes it easy and fun to stay close to your favorite people
Keywords and Tags: facebook, facebook com, facebook log in, facebook messenger, facebook sign in, instant messaging, messenger, messenger app, messenger login, open messenger, popular, web phone, www facebook com
Related Terms: angel messenger, anytime, como cerrar sesion en messenger, flock messenger, instant messenger plugin, invisible yahoo messenger, messenger bag, messenger plus, mingo messenger, whatsapp messenger
Fav Icon:
Age: Over 25 years old
Domain Created: 4th November, 1998
Domain Updated: 26th January, 2022
Domain Expires: 3rd November, 2031
Review

Snoop Score

5/5 (Perfect!)

Valuation

$70,849,881 USD
Note: All valuation figures are estimates.

Popularity

Worldwide Sensation
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 224
Alexa Reach:
SEMrush Rank (US): 905
SEMrush Authority Score: 79
Moz Domain Authority: 92
Moz Page Authority: 67

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 23,426 0
Traffic: 3,905,081 0
Cost: $3,182,740 USD $0 USD
Traffic

Visitors

Daily Visitors: 10,423,797
Monthly Visitors: 317,267,545
Yearly Visitors: 3,804,685,905
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $97,055 USD
Monthly Revenue: $2,954,037 USD
Yearly Revenue: $35,424,936 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 44,149,274
Referring Domains: 51,086
Referring IPs: 56,167
Messenger.com has 44,149,274 backlinks according to SEMrush. 81% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve messenger.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 messenger.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://sonsuanha.com.vn/
Target: https://www.messenger.com/t/2658012747548950

2
Source: https://wishlist.ge/%E1%83%AD%E1%83%A3%E1%83%A0%E1%83%AD%E1%83%94%E1%83%9A%E1%83%98-%E1%83%93%E1%83%90-%E1%83%A1%E1%83%90%E1%83%9B%E1%83%96%E1%83%90%E1%83%A0%E1%83%94%E1%83%A3%E1%83%9A%E1%83%9D%E1%83%A1-%E1%83%90%E1%83%A5%E1%83%A1%E1%83%94%E1%83%A1%E1%83%A3%E1%83%90%E1%83%A0%E1%83%94%E1%83%91%E1%83%98/%E1%83%A2%E1%83%90%E1%83%A4%E1%83%94%E1%83%91%E1%83%98-%E1%83%A5%E1%83%95%E1%83%90%E1%83%91%E1%83%94%E1%83%91%E1%83%98-%E1%83%99%E1%83%9D%E1%83%9B%E1%83%9E%E1%83%9A%E1%83%94%E1%83%A5%E1%83%A2%E1%83%94%E1%83%91%E1%83%98/
Target: https://www.messenger.com/login.php?next=https%3A%2F%2Fwww.messenger.com%2Ft%2F1565226030384402%2F%3Fmessaging_source%3Dsource%253Apages%253Amessage_shortlink

3
Source: https://set.com.vn/
Target: https://www.messenger.com/t/2658012747548950

4
Source: https://www.top4marketing.com.au/packages/
Target: https://www.messenger.com/login.php?next=https%3A%2F%2Fwww.messenger.com%2Ft%2F1475123402809025%2F%3Fmessaging_source%3Dsource%253Apages%253Amessage_shortlink

5
Source: https://www.crisistextline.org/
Target: https://www.messenger.com/login.php?next=https%3A%2F%2Fwww.messenger.com%2Ft%2F204427966369963%2F%3Fmessaging_source%3Dsource%253Apages%253Amessage_shortlink

Top Ranking Keywords (US)

1
Keyword: facebook
Ranked Page: https://www.messenger.com/login.php

2
Keyword: messenger
Ranked Page: https://www.messenger.com/

3
Keyword: facebook messenger
Ranked Page: https://www.messenger.com/

4
Keyword: facebook log in
Ranked Page: https://www.messenger.com/login.php

5
Keyword: messenger login
Ranked Page: https://www.messenger.com/

Domain Analysis

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

Page Speed Analysis

Average Load Time: 2.26 seconds
Load Time Comparison: Faster than 28% of sites

PageSpeed Insights

Avg. (All Categories) 71
Performance 82
Accessibility 88
Best Practices 92
SEO 91
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.messenger.com/
Updated: 16th December, 2022

4.41 seconds
First Contentful Paint (FCP)
42%
17%
41%

0.02 seconds
First Input Delay (FID)
88%
5%
7%

Simulate loading on desktop
82

Performance

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

Metrics

Time to Interactive — 1.0 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.077
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
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://messenger.com/
http/1.1
0
40.92399997171
260
0
301
text/plain
https://messenger.com/
http/1.1
41.397999972105
123.86199997854
447
0
301
text/html
https://www.messenger.com/
h2
124.33199997758
300.45999999857
24692
80651
200
text/html
Document
https://static.xx.fbcdn.net/rsrc.php/v3/yG/l/0,cross/gRFRQL1b8BU.css?_nc_x=Ij3Wp8lg5Kz
h2
341.82899998268
358.1519999716
6142
23486
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yy/l/0,cross/pDani-foaNX.css?_nc_x=Ij3Wp8lg5Kz
h2
342.63299999293
357.66799998237
4731
17287
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yB/r/c3wqNgluzz7.js?_nc_x=Ij3Wp8lg5Kz
h2
342.74599998025
366.44899999374
95074
370261
200
application/x-javascript
Script
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/120009688_325579128711709_1736249742330805861_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=G8xpkcgC0OgAX_ShVWl&_nc_ht=scontent-atl3-1.xx&oh=00_AfAJqi378UhvCLwl_YCFQUHD6jFf8zXZomLfssQwQ6vpSA&oe=63A232BD
h2
443.40199997532
459.07399998396
11668
11159
200
image/png
Image
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/119597221_2801552506611915_4465041091818364564_n.svg?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=wNsxqXlCGXkAX9zFw6u&_nc_ht=scontent-atl3-1.xx&oh=00_AfDPaIWb3xu3RwtdHkEk0mFU32mbQjBl7Z8ooAGpmbCv7w&oe=63A0AEF5
h2
443.67499998771
459.46399998502
11377
10843
200
image/svg+xml
Image
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/119656338_326247688451849_3018195711400016354_n.svg?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=yeZkH4XY_eoAX8pms-_&_nc_ht=scontent-atl3-1.xx&oh=00_AfBI0ZRLLNDd3PH9s70nf3rqGlxDpiaHbSMCrfR2oVgLkA&oe=63A1BB94
h2
443.94800000009
460.23499997682
7823
7310
200
image/svg+xml
Image
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/120973513_338186077283942_8148888802958728934_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=oeFqMZ7OyhMAX-ISIiX&_nc_ht=scontent-atl3-1.xx&oh=00_AfDu30pkhXFoWxBxdn9feTlerOI3CQs7ufABMBVP6CJJ0Q&oe=63A1EBE7
h2
444.15699999081
497.939999972
1047993
1047459
200
image/png
Image
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/284131241_398860802255675_7090232386370085328_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=7ex5FyIjn24AX9kK8Zb&_nc_ht=scontent-atl3-1.xx&oh=00_AfCGKBN237zHkxn3VN8WN8GXXmLObye4T1qXhEkIvRFulw&oe=63A14D06
h2
444.39199997578
493.0469999963
1084254
1083720
200
image/png
Image
https://static.xx.fbcdn.net/rsrc.php/v3i7M54/y5/l/en_US/9IIhnT1bmCg.js?_nc_x=Ij3Wp8lg5Kz
h2
364.22699998366
381.04299997212
27841
101096
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yE/r/hC8CXfuCKpb.js?_nc_x=Ij3Wp8lg5Kz
h2
389.71899999888
404.32799997507
8660
25591
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yF/r/p55HfXW__mM.js?_nc_x=Ij3Wp8lg5Kz
h2
398.62499997253
412.98299998743
997
507
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3id3L4/ym/l/en_US/oKKfrxEGaeO.js?_nc_x=Ij3Wp8lg5Kz
h2
442.61399999959
458.55499999016
23474
80881
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y_/r/WcU0YItm9jS.js?_nc_x=Ij3Wp8lg5Kz
h2
442.89399997797
456.90599997761
964
614
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yz/r/86mSZGRYSHl.js?_nc_x=Ij3Wp8lg5Kz
h2
443.10499998392
464.4139999873
53426
357616
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/yN/r/rauSA04huJL.woff2
h2
455.43499998166
472.10999997333
31307
30635
200
font/woff2
Font
https://static.xx.fbcdn.net/rsrc.php/yT/r/HWVCvIuXDLN.woff2
h2
455.78099999693
470.85699997842
32136
31464
200
font/woff2
Font
https://static.xx.fbcdn.net/rsrc.php/ym/r/QPhdGXMkzKu.woff2
h2
456.18199999444
472.69499997492
32248
31576
200
font/woff2
Font
https://www.facebook.com/login/async_sso/messenger_dot_com/?__a=1
h2
3218.0389999994
3310.5439999781
1235
111
200
application/x-javascript
XHR
https://static.xx.fbcdn.net/rsrc.php/v3/yT/r/MEnuEFzOkJR.js?_nc_x=Ij3Wp8lg5Kz
h2
3222.3649999942
3239.1059999936
6357
17897
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yD/r/k-pmFTkhm40.js?_nc_x=Ij3Wp8lg5Kz
h2
3223.0529999943
3238.6609999812
4025
8561
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yv/r/i_MYL-kry8c.js?_nc_x=Ij3Wp8lg5Kz
h2
3224.9599999923
3239.9029999797
10869
33619
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iqES4/yQ/l/en_US/2iTHBHUS1ae.js?_nc_x=Ij3Wp8lg5Kz
h2
3225.5499999737
3241.1189999839
11894
35834
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y_/r/PQFVgR7hi7-.png
h2
3236.2389999907
3251.7439999792
2676
2044
200
image/png
Image
https://www.messenger.com/ajax/bz?__a=1&__ccg=EXCELLENT&__comet_req=0&__dyn=7xe6E5aQ1PyUbFuC1swgE98nwgU6C7UW3q327E3rw5ux60Vo1upE4W0OE2Wwce1xwEwt81sbzo5-16wf50Fwww6Dw5Uwdq0Ho2ewnE3fw6iw4vwbS1Lw4Cw&__hs=19342.BP%3Amessengerdotcom_pkg.2.0.0.0.0&__hsi=7177798269347646041&__jssesw=1&__req=2&__rev=1006751983&__s=64y0hr%3Azjmfk7%3A6jz0tj&__spin_b=trunk&__spin_r=1006751983&__spin_t=1671211391&__user=0&dpr=1&jazoest=2899&lsd=AVpvbn8-1GY
h2
5219.9449999898
5346.8509999802
2282
0
200
text/html
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)
306.695
7.093
343.088
6282.28
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

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Messenger.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Messenger.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Messenger.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Messenger.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 90 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.xx.fbcdn.net/rsrc.php/v3/yB/r/c3wqNgluzz7.js?_nc_x=Ij3Wp8lg5Kz
95074
51083
https://static.xx.fbcdn.net/rsrc.php/v3/yz/r/86mSZGRYSHl.js?_nc_x=Ij3Wp8lg5Kz
53426
41540
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 180 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.messenger.com/
177.123
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Messenger.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 13 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.xx.fbcdn.net/rsrc.php/v3/yB/r/c3wqNgluzz7.js?_nc_x=Ij3Wp8lg5Kz
13805
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 2,485 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/284131241_398860802255675_7090232386370085328_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=7ex5FyIjn24AX9kK8Zb&_nc_ht=scontent-atl3-1.xx&oh=00_AfCGKBN237zHkxn3VN8WN8GXXmLObye4T1qXhEkIvRFulw&oe=63A14D06
1084254
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/120973513_338186077283942_8148888802958728934_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=oeFqMZ7OyhMAX-ISIiX&_nc_ht=scontent-atl3-1.xx&oh=00_AfDu30pkhXFoWxBxdn9feTlerOI3CQs7ufABMBVP6CJJ0Q&oe=63A1EBE7
1047993
https://static.xx.fbcdn.net/rsrc.php/v3/yB/r/c3wqNgluzz7.js?_nc_x=Ij3Wp8lg5Kz
95074
https://static.xx.fbcdn.net/rsrc.php/v3/yz/r/86mSZGRYSHl.js?_nc_x=Ij3Wp8lg5Kz
53426
https://static.xx.fbcdn.net/rsrc.php/ym/r/QPhdGXMkzKu.woff2
32248
https://static.xx.fbcdn.net/rsrc.php/yT/r/HWVCvIuXDLN.woff2
32136
https://static.xx.fbcdn.net/rsrc.php/yN/r/rauSA04huJL.woff2
31307
https://static.xx.fbcdn.net/rsrc.php/v3i7M54/y5/l/en_US/9IIhnT1bmCg.js?_nc_x=Ij3Wp8lg5Kz
27841
https://www.messenger.com/
24692
https://static.xx.fbcdn.net/rsrc.php/v3id3L4/ym/l/en_US/oKKfrxEGaeO.js?_nc_x=Ij3Wp8lg5Kz
23474
Avoids an excessive DOM size — 215 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
215
Maximum DOM Depth
25
Maximum Child Elements
32
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Messenger.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
Unattributable
6293.197
0.035
0
Keep request counts low and transfer sizes small — 27 requests • 2,485 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
27
2544852
Image
6
2165791
Script
11
243581
Font
3
95691
Document
1
24692
Stylesheet
2
10873
Other
4
4224
Media
0
0
Third-party
23
2517171
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
2517171
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

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

Metrics

First Contentful Paint — 1.0 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 2.0 s
The timing of the largest text or image that is painted.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 430 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Messenger.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.xx.fbcdn.net/rsrc.php/v3/yG/l/0,cross/gRFRQL1b8BU.css?_nc_x=Ij3Wp8lg5Kz
6142
230
https://static.xx.fbcdn.net/rsrc.php/v3/yB/r/c3wqNgluzz7.js?_nc_x=Ij3Wp8lg5Kz
95074
80
Serve images in next-gen formats — Potential savings of 714 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://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/120973513_338186077283942_8148888802958728934_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=oeFqMZ7OyhMAX-ISIiX&_nc_ht=scontent-atl3-1.xx&oh=00_AfDu30pkhXFoWxBxdn9feTlerOI3CQs7ufABMBVP6CJJ0Q&oe=63A1EBE7
1047459
721487
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/120009688_325579128711709_1736249742330805861_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=G8xpkcgC0OgAX_ShVWl&_nc_ht=scontent-atl3-1.xx&oh=00_AfAJqi378UhvCLwl_YCFQUHD6jFf8zXZomLfssQwQ6vpSA&oe=63A232BD
11159
10092
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Messenger.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://messenger.com/
190
https://messenger.com/
150
https://www.messenger.com/
0

Metrics

Speed Index — 2.8 s
The time taken for the page contents to be visibly populated.

Other

Properly size images — Potential savings of 1,066 KiB
Images can slow down the page's load time. Messenger.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/284131241_398860802255675_7090232386370085328_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=7ex5FyIjn24AX9kK8Zb&_nc_ht=scontent-atl3-1.xx&oh=00_AfCGKBN237zHkxn3VN8WN8GXXmLObye4T1qXhEkIvRFulw&oe=63A14D06
1083720
1083659
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/120009688_325579128711709_1736249742330805861_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=G8xpkcgC0OgAX_ShVWl&_nc_ht=scontent-atl3-1.xx&oh=00_AfAJqi378UhvCLwl_YCFQUHD6jFf8zXZomLfssQwQ6vpSA&oe=63A232BD
11159
8369
Serve static assets with an efficient cache policy — 5 resources found
Messenger.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://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/284131241_398860802255675_7090232386370085328_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=7ex5FyIjn24AX9kK8Zb&_nc_ht=scontent-atl3-1.xx&oh=00_AfCGKBN237zHkxn3VN8WN8GXXmLObye4T1qXhEkIvRFulw&oe=63A14D06
1209600000
1084254
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/120973513_338186077283942_8148888802958728934_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=oeFqMZ7OyhMAX-ISIiX&_nc_ht=scontent-atl3-1.xx&oh=00_AfDu30pkhXFoWxBxdn9feTlerOI3CQs7ufABMBVP6CJJ0Q&oe=63A1EBE7
1209600000
1047993
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/120009688_325579128711709_1736249742330805861_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=G8xpkcgC0OgAX_ShVWl&_nc_ht=scontent-atl3-1.xx&oh=00_AfAJqi378UhvCLwl_YCFQUHD6jFf8zXZomLfssQwQ6vpSA&oe=63A232BD
1209600000
11668
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/119597221_2801552506611915_4465041091818364564_n.svg?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=wNsxqXlCGXkAX9zFw6u&_nc_ht=scontent-atl3-1.xx&oh=00_AfDPaIWb3xu3RwtdHkEk0mFU32mbQjBl7Z8ooAGpmbCv7w&oe=63A0AEF5
1209600000
11377
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/119656338_326247688451849_3018195711400016354_n.svg?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=yeZkH4XY_eoAX8pms-_&_nc_ht=scontent-atl3-1.xx&oh=00_AfBI0ZRLLNDd3PH9s70nf3rqGlxDpiaHbSMCrfR2oVgLkA&oe=63A1BB94
1209600000
7823
Minimize main-thread work — 6.3 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
6293.091
Rendering
0.071
Script Evaluation
0.035
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.xx.fbcdn.net/rsrc.php/yN/r/rauSA04huJL.woff2
16.674999991665
https://static.xx.fbcdn.net/rsrc.php/yT/r/HWVCvIuXDLN.woff2
15.075999981491
https://static.xx.fbcdn.net/rsrc.php/ym/r/QPhdGXMkzKu.woff2
16.512999980478
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://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/284131241_398860802255675_7090232386370085328_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=7ex5FyIjn24AX9kK8Zb&_nc_ht=scontent-atl3-1.xx&oh=00_AfCGKBN237zHkxn3VN8WN8GXXmLObye4T1qXhEkIvRFulw&oe=63A14D06
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/119656338_326247688451849_3018195711400016354_n.svg?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=yeZkH4XY_eoAX8pms-_&_nc_ht=scontent-atl3-1.xx&oh=00_AfBI0ZRLLNDd3PH9s70nf3rqGlxDpiaHbSMCrfR2oVgLkA&oe=63A1BB94
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/119597221_2801552506611915_4465041091818364564_n.svg?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=wNsxqXlCGXkAX9zFw6u&_nc_ht=scontent-atl3-1.xx&oh=00_AfDPaIWb3xu3RwtdHkEk0mFU32mbQjBl7Z8ooAGpmbCv7w&oe=63A0AEF5
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of messenger.com on mobile screens.
Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
88

Accessibility

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

Tables and lists

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

Names and labels

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

Internationalization and localization

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

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

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

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Contrast

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that messenger.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
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary.
script-src
High
'unsafe-inline' allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.
script-src
High
Avoid using plain URL schemes (data:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
script-src
High
Avoid using plain URL schemes (data:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
default-src
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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

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

SEO

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

Content Best Practices

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

Crawling and Indexing

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

Mobile Friendly

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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of messenger.com on mobile screens.

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

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of messenger.com on mobile screens.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

2.58 seconds
First Contentful Paint (FCP)
63%
17%
20%

0.04 seconds
First Input Delay (FID)
82%
7%
11%

Simulate loading on mobile
65

Performance

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

Metrics

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.008
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
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://messenger.com/
http/1.1
0
25.517000351101
260
0
301
text/plain
https://messenger.com/
http/1.1
25.857999920845
101.74900013953
421
0
301
text/html
https://www.messenger.com/
h2
102.04500006512
277.25800033659
19567
49249
200
text/html
Document
https://static.xx.fbcdn.net/rsrc.php/v3/yU/l/0,cross/NUzw1rwHmiU.css?_nc_x=Ij3Wp8lg5Kz
h2
313.84600000456
334.19599989429
15221
61447
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/ye/l/0,cross/ro5RHrQRpV0.css?_nc_x=Ij3Wp8lg5Kz
h2
314.00300003588
330.30900033191
4162
15143
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yN/l/0,cross/UfKc1JT6ecJ.css?_nc_x=Ij3Wp8lg5Kz
h2
314.39100019634
329.59800027311
4712
15199
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yM/r/QCOpWCaHOMR.js?_nc_x=Ij3Wp8lg5Kz
h2
314.59100032225
337.08900026977
79081
311105
200
application/x-javascript
Script
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/120009688_325579128711709_1736249742330805861_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=G8xpkcgC0OgAX_ShVWl&_nc_ht=scontent-atl3-1.xx&oh=00_AfAJqi378UhvCLwl_YCFQUHD6jFf8zXZomLfssQwQ6vpSA&oe=63A232BD
h2
375.43900031596
390.32900007442
11668
11159
200
image/png
Image
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/44751398_444218965982796_2611412198404128768_n.svg?_nc_cat=105&ccb=1-7&_nc_sid=6825c5&_nc_ohc=SI5yuOwI-poAX_OlDk4&_nc_ht=scontent-atl3-1.xx&oh=00_AfAxsJ7Npy2cgNwk6oZsbks22SaJHUC5bC1THnxyRlzQlg&oe=63A2798A
h2
375.54500019178
392.11199991405
9808
9295
200
image/svg+xml
Image
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/119597221_2801552506611915_4465041091818364564_n.svg?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=wNsxqXlCGXkAX9zFw6u&_nc_ht=scontent-atl3-1.xx&oh=00_AfDPaIWb3xu3RwtdHkEk0mFU32mbQjBl7Z8ooAGpmbCv7w&oe=63A0AEF5
h2
375.64000021666
391.809000168
11377
10843
200
image/svg+xml
Image
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/119656338_326247688451849_3018195711400016354_n.svg?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=yeZkH4XY_eoAX8pms-_&_nc_ht=scontent-atl3-1.xx&oh=00_AfBI0ZRLLNDd3PH9s70nf3rqGlxDpiaHbSMCrfR2oVgLkA&oe=63A1BB94
h2
375.77500008047
391.1120002158
7823
7310
200
image/svg+xml
Image
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/120973513_338186077283942_8148888802958728934_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=oeFqMZ7OyhMAX-ISIiX&_nc_ht=scontent-atl3-1.xx&oh=00_AfDu30pkhXFoWxBxdn9feTlerOI3CQs7ufABMBVP6CJJ0Q&oe=63A1EBE7
h2
375.89200027287
422.36900003627
1047993
1047459
200
image/png
Image
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/284131241_398860802255675_7090232386370085328_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=7ex5FyIjn24AX9kK8Zb&_nc_ht=scontent-atl3-1.xx&oh=00_AfCGKBN237zHkxn3VN8WN8GXXmLObye4T1qXhEkIvRFulw&oe=63A14D06
h2
376.04100024328
427.25700000301
1084254
1083720
200
image/png
Image
https://static.xx.fbcdn.net/rsrc.php/v3iZkm4/yB/l/en_US/Ozv8GA-bKfD.js?_nc_x=Ij3Wp8lg5Kz
h2
335.44200006872
353.67300035432
50950
181945
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y2/r/tttf5FDK7WA.js?_nc_x=Ij3Wp8lg5Kz
h2
359.42800017074
374.18900011107
13794
44468
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y4/r/BpNdGwXCWqa.js?_nc_x=Ij3Wp8lg5Kz
h2
371.54299998656
386.86600001529
11449
36100
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yG/r/LqXI6W_bsOb.js?_nc_x=Ij3Wp8lg5Kz
h2
375.16600033268
390.79699991271
9230
26709
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yP/l/0,cross/iUYvFYkFFzq.css?_nc_x=Ij3Wp8lg5Kz
h2
375.31900033355
391.46700035781
5963
26213
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/yN/r/rauSA04huJL.woff2
h2
384.40000033006
398.79800006747
31307
30635
200
font/woff2
Font
https://static.xx.fbcdn.net/rsrc.php/yT/r/HWVCvIuXDLN.woff2
h2
384.61000006646
400.10800026357
32136
31464
200
font/woff2
Font
https://static.xx.fbcdn.net/rsrc.php/ym/r/QPhdGXMkzKu.woff2
h2
384.76700009778
399.6140002273
32248
31576
200
font/woff2
Font
data
473.17099990323
473.39100018144
0
0
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yT/r/OQ2NlcQEZ4F.js?_nc_x=Ij3Wp8lg5Kz
h2
2528.8610002026
2544.0520001575
9096
27129
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iL7o4/y9/l/en_US/x7D1f1fiP_b.js?_nc_x=Ij3Wp8lg5Kz
h2
2529.4540002942
2544.6880003437
12408
35498
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y0/r/l6Rl_HBNMcj.js?_nc_x=Ij3Wp8lg5Kz
h2
2531.5539999865
2545.8450000733
1633
2405
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3ijfq4/yC/l/en_US/VUjON4sNvXj.js?_nc_x=Ij3Wp8lg5Kz
h2
2532.0390001871
2547.4630002864
10031
31554
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iLl54/yK/l/en_US/0D75Vw0sOuD.js?_nc_x=Ij3Wp8lg5Kz
h2
2532.55000012
2547.9150000028
3978
8771
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yg/r/GaT0-DQJdWD.js?_nc_x=Ij3Wp8lg5Kz
h2
2533.071000129
2547.1060001291
895
313
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y9/r/ie38mp0O07P.js?_nc_x=Ij3Wp8lg5Kz
h2
2533.5170002654
2548.3220000751
11113
25101
200
application/x-javascript
Script
https://scontent.xx.fbcdn.net/hads-ak-prn2/1487645_6012475414660_1439393861_n.png
h2
3365.45199994
3380.8699999936
384
79
200
image/png
Image
https://www.messenger.com/a/bz?fb_dtsg=NAcOkVrWbOcsz1MjzdfU2ubJpRUCfJeGXv2Lm9hZU2QdJ2ypucyWaNA%3A0%3A0&jazoest=25143&lsd=AVo5KFOulKc&__dyn=0wzpawlEaU4ifDg9ppk1swgE98nwgU2owpUuwcC4o1nEhwem0iy1gCwjE1xo33w2sbzo1MU88C0pS0ny0oi0zE1bE881so17U2ZwrU2pw8O&__csr=&__req=1&__a=AYl5AV8WHYh0loZXo_qEw-xYYXjByfvKxFtfNDj8pSgwAwJZePIlWwanJaItnudTw-qkokykwJKzOksJzj-Zehk0sq1ccov6zadMGk2unIcCCw&__user=0
h2
4372.3110002466
4456.8920000456
2668
249
200
text/html
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.
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

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Messenger.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Messenger.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Messenger.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 180 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.messenger.com/
176.207
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Messenger.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 13 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.xx.fbcdn.net/rsrc.php/v3/yM/r/QCOpWCaHOMR.js?_nc_x=Ij3Wp8lg5Kz
13666
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 2,476 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/284131241_398860802255675_7090232386370085328_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=7ex5FyIjn24AX9kK8Zb&_nc_ht=scontent-atl3-1.xx&oh=00_AfCGKBN237zHkxn3VN8WN8GXXmLObye4T1qXhEkIvRFulw&oe=63A14D06
1084254
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/120973513_338186077283942_8148888802958728934_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=oeFqMZ7OyhMAX-ISIiX&_nc_ht=scontent-atl3-1.xx&oh=00_AfDu30pkhXFoWxBxdn9feTlerOI3CQs7ufABMBVP6CJJ0Q&oe=63A1EBE7
1047993
https://static.xx.fbcdn.net/rsrc.php/v3/yM/r/QCOpWCaHOMR.js?_nc_x=Ij3Wp8lg5Kz
79081
https://static.xx.fbcdn.net/rsrc.php/v3iZkm4/yB/l/en_US/Ozv8GA-bKfD.js?_nc_x=Ij3Wp8lg5Kz
50950
https://static.xx.fbcdn.net/rsrc.php/ym/r/QPhdGXMkzKu.woff2
32248
https://static.xx.fbcdn.net/rsrc.php/yT/r/HWVCvIuXDLN.woff2
32136
https://static.xx.fbcdn.net/rsrc.php/yN/r/rauSA04huJL.woff2
31307
https://www.messenger.com/
19567
https://static.xx.fbcdn.net/rsrc.php/v3/yU/l/0,cross/NUzw1rwHmiU.css?_nc_x=Ij3Wp8lg5Kz
15221
https://static.xx.fbcdn.net/rsrc.php/v3/y2/r/tttf5FDK7WA.js?_nc_x=Ij3Wp8lg5Kz
13794
Avoids an excessive DOM size — 212 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
212
Maximum DOM Depth
20
Maximum Child Elements
32
Avoid chaining critical requests — 7 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Messenger.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
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.
Minimizes main-thread work — 0.0 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
29.272
Rendering
0.292
Script Evaluation
0.152
Keep request counts low and transfer sizes small — 30 requests • 2,476 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
30
2535630
Image
7
2173307
Script
12
213658
Font
3
95691
Stylesheet
4
30058
Document
1
19567
Other
3
3349
Media
0
0
Third-party
26
2512714
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
2512714
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of messenger.com on mobile screens.

Budgets

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

Metrics

Time to Interactive — 3.9 s
The time taken for the page to become fully interactive.
Speed Index — 3.9 s
The time taken for the page contents to be visibly populated.

Audits

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

Other

Reduce unused CSS — Potential savings of 15 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Messenger.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.xx.fbcdn.net/rsrc.php/v3/yU/l/0,cross/NUzw1rwHmiU.css?_nc_x=Ij3Wp8lg5Kz
15221
14849
Reduce unused JavaScript — Potential savings of 75 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.xx.fbcdn.net/rsrc.php/v3/yM/r/QCOpWCaHOMR.js?_nc_x=Ij3Wp8lg5Kz
79081
41878
https://static.xx.fbcdn.net/rsrc.php/v3iZkm4/yB/l/en_US/Ozv8GA-bKfD.js?_nc_x=Ij3Wp8lg5Kz
50950
34602

Metrics

First Contentful Paint — 3.9 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 9.9 s
The timing of the largest text or image that is painted.

Other

Eliminate render-blocking resources — Potential savings of 1,830 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Messenger.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.xx.fbcdn.net/rsrc.php/v3/yU/l/0,cross/NUzw1rwHmiU.css?_nc_x=Ij3Wp8lg5Kz
15221
930
https://static.xx.fbcdn.net/rsrc.php/v3/yM/r/QCOpWCaHOMR.js?_nc_x=Ij3Wp8lg5Kz
79081
450
Properly size images — Potential savings of 1,058 KiB
Images can slow down the page's load time. Messenger.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/284131241_398860802255675_7090232386370085328_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=7ex5FyIjn24AX9kK8Zb&_nc_ht=scontent-atl3-1.xx&oh=00_AfCGKBN237zHkxn3VN8WN8GXXmLObye4T1qXhEkIvRFulw&oe=63A14D06
1083720
1083636
Serve images in next-gen formats — Potential savings of 714 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://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/120973513_338186077283942_8148888802958728934_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=oeFqMZ7OyhMAX-ISIiX&_nc_ht=scontent-atl3-1.xx&oh=00_AfDu30pkhXFoWxBxdn9feTlerOI3CQs7ufABMBVP6CJJ0Q&oe=63A1EBE7
1047459
721487
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/120009688_325579128711709_1736249742330805861_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=G8xpkcgC0OgAX_ShVWl&_nc_ht=scontent-atl3-1.xx&oh=00_AfAJqi378UhvCLwl_YCFQUHD6jFf8zXZomLfssQwQ6vpSA&oe=63A232BD
11159
10092
Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Messenger.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://messenger.com/
630
https://messenger.com/
480
https://www.messenger.com/
0
Serve static assets with an efficient cache policy — 6 resources found
Messenger.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://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/284131241_398860802255675_7090232386370085328_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=7ex5FyIjn24AX9kK8Zb&_nc_ht=scontent-atl3-1.xx&oh=00_AfCGKBN237zHkxn3VN8WN8GXXmLObye4T1qXhEkIvRFulw&oe=63A14D06
1209600000
1084254
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/120973513_338186077283942_8148888802958728934_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=oeFqMZ7OyhMAX-ISIiX&_nc_ht=scontent-atl3-1.xx&oh=00_AfDu30pkhXFoWxBxdn9feTlerOI3CQs7ufABMBVP6CJJ0Q&oe=63A1EBE7
1209600000
1047993
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/120009688_325579128711709_1736249742330805861_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=G8xpkcgC0OgAX_ShVWl&_nc_ht=scontent-atl3-1.xx&oh=00_AfAJqi378UhvCLwl_YCFQUHD6jFf8zXZomLfssQwQ6vpSA&oe=63A232BD
1209600000
11668
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/119597221_2801552506611915_4465041091818364564_n.svg?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=wNsxqXlCGXkAX9zFw6u&_nc_ht=scontent-atl3-1.xx&oh=00_AfDPaIWb3xu3RwtdHkEk0mFU32mbQjBl7Z8ooAGpmbCv7w&oe=63A0AEF5
1209600000
11377
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/44751398_444218965982796_2611412198404128768_n.svg?_nc_cat=105&ccb=1-7&_nc_sid=6825c5&_nc_ohc=SI5yuOwI-poAX_OlDk4&_nc_ht=scontent-atl3-1.xx&oh=00_AfAxsJ7Npy2cgNwk6oZsbks22SaJHUC5bC1THnxyRlzQlg&oe=63A2798A
1209600000
9808
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/119656338_326247688451849_3018195711400016354_n.svg?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=yeZkH4XY_eoAX8pms-_&_nc_ht=scontent-atl3-1.xx&oh=00_AfBI0ZRLLNDd3PH9s70nf3rqGlxDpiaHbSMCrfR2oVgLkA&oe=63A1BB94
1209600000
7823
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.xx.fbcdn.net/rsrc.php/yN/r/rauSA04huJL.woff2
14.397999737412
https://static.xx.fbcdn.net/rsrc.php/yT/r/HWVCvIuXDLN.woff2
15.498000197113
https://static.xx.fbcdn.net/rsrc.php/ym/r/QPhdGXMkzKu.woff2
14.847000129521
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://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/284131241_398860802255675_7090232386370085328_n.png?_nc_cat=1&ccb=1-7&_nc_sid=6825c5&_nc_ohc=7ex5FyIjn24AX9kK8Zb&_nc_ht=scontent-atl3-1.xx&oh=00_AfCGKBN237zHkxn3VN8WN8GXXmLObye4T1qXhEkIvRFulw&oe=63A14D06
https://scontent-atl3-1.xx.fbcdn.net/v/t39.8562-6/44751398_444218965982796_2611412198404128768_n.svg?_nc_cat=105&ccb=1-7&_nc_sid=6825c5&_nc_ohc=SI5yuOwI-poAX_OlDk4&_nc_ht=scontent-atl3-1.xx&oh=00_AfAxsJ7Npy2cgNwk6oZsbks22SaJHUC5bC1THnxyRlzQlg&oe=63A2798A
Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
First Contentful Paint (3G) — 7920 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
78

Accessibility

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

Tables and lists

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

Names and labels

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Contrast

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that messenger.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
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary.
script-src
High
'unsafe-inline' allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.
script-src
High
Avoid using plain URL schemes (data:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
script-src
High
Avoid using plain URL schemes (data:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
default-src
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.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

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

Audits

Charset declaration is missing or occurs too late in the HTML
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

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Relaxing the same-origin policy by setting `document.domain` is deprecated, and will be disabled by default. To continue using this feature, please opt-out of origin-keyed agent clusters by sending an `Origin-Agent-Cluster: ?0` header along with the HTTP response for the document and frames. See https://developer.chrome.com/blog/immutable-document-domain/ for more details.
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: the server responded with a status of 404 (Not Found)
92

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
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.

Crawling and Indexing

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

Manual Checks

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

PWA

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

PWA Optimized

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

Installable

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

PWA Optimized

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

Manual Checks

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

Server Location

Server IP Address: 31.13.71.1
Continent: Europe
Country: Ireland
Ireland Flag
Region:
City:
Longitude: -6.2439
Latitude: 53.3472
Currencies: EUR
Languages: English
Irish

Web Hosting Provider

Name IP Address
Facebook, Inc.
Registration

Domain Registrant

Private Registration: No
Name: Domain Admin
Organization: Meta Platforms, Inc.
Country: US
City: Menlo Park
State: CA
Post Code: 94025
Email: domain@fb.com
Phone: +1.6505434800
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
RegistrarSafe, LLC 157.240.22.35
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: *.facebook.com
Issued By: DigiCert SHA2 High Assurance Server CA
Valid From: 21st January, 2023
Valid To: 21st April, 2023
Subject: CN = *.facebook.com
O = Meta Platforms, Inc.
L = Menlo Park
S = US
Hash: a5a6422f
Issuer: CN = DigiCert SHA2 High Assurance Server CA
OU = www.digicert.com
O = DigiCert Inc
S = US
Version: 2
Serial Number: 3818002613346050166873563494058769217
Serial Number (Hex): 02DF520FF694A570D19F987E40373B41
Valid From: 21st January, 2024
Valid To: 21st April, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:51:68:FF:90:AF:02:07:75:3C:CC:D9:65:64:62:A2:12:B8:59:72:3B
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/sha2-ha-server-g6.crl

Full Name:
URI:http://crl4.digicert.com/sha2-ha-server-g6.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/DigiCertSHA2HighAssuranceServerCA.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Jan 21 01:02:16.688 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:3A:33:55:46:14:43:9E:49:77:11:1F:9C:
44:38:8D:EA:9F:42:70:2A:37:C8:DD:BD:B5:A2:84:B4:
48:BF:DD:06:02:21:00:CE:33:24:37:A8:D1:74:F7:2D:
58:E0:1E:A2:46:EB:D2:60:D2:A8:BA:4B:39:E0:59:E7:
29:26:BB:B7:9F:C6:51
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 : Jan 21 01:02:16.807 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:3D:4F:79:8C:CC:88:D5:A2:79:9A:25:EC:
5A:41:80:0F:A0:E7:07:01:E9:11:49:6B:D6:EC:53:AD:
2D:11:F3:99:02:21:00:EA:BF:A4:AD:2D:4A:1F:CA:72:
E4:51:BE:CB:65:4B:EE:69:4C:96:AB:3A:E0:90:42:77:
01:E8:72:6E:94:09:5B
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 : Jan 21 01:02:16.740 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:F9:58:DA:83:89:17:18:83:8B:51:31:
18:EE:9C:A9:80:C3:BC:1F:5D:00:A2:49:2D:E2:4B:DE:
C5:6D:ED:F0:63:02:21:00:E5:0E:9D:13:63:8A:15:B2:
B0:28:9A:D2:75:89:5B:CE:B4:C3:47:41:7C:94:FA:2C:
D9:8C:20:21:1B:4A:AB:84
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.facebook.net
DNS:*.fbcdn.net
DNS:*.fbsbx.com
DNS:*.m.facebook.com
DNS:*.messenger.com
DNS:*.xx.fbcdn.net
DNS:*.xy.fbcdn.net
DNS:*.xz.fbcdn.net
DNS:facebook.com
DNS:messenger.com
DNS:*.facebook.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
messenger.com. 31.13.71.1 IN 300

NS Records

Host Nameserver Class TTL
messenger.com. b.ns.facebook.com. IN 21600
messenger.com. c.ns.facebook.com. IN 21600
messenger.com. d.ns.facebook.com. IN 21600
messenger.com. a.ns.facebook.com. IN 21600

AAAA Records

IP Address Class TTL
2a03:2880:f012:1:face:b00c:0:1 IN 300

CAA Records

Domain Flags Tag Class TTL
digicert.com 0 issue IN 3600

MX Records

Priority Host Server Class TTL
10 messenger.com. mxb-00082601.gslb.pphosted.com. IN 7200
10 messenger.com. mxa-00082601.gslb.pphosted.com. IN 7200

SOA Records

Domain Name Primary NS Responsible Email TTL
messenger.com. a.ns.facebook.com. dns.facebook.com. 3600

TXT Records

Host Value Class TTL
messenger.com. 6fd64222-f6ef-4766-87e8-34729703809a IN 3600
messenger.com. MS=ms57472615 IN 3600
messenger.com. fLEQ2Q8vdk4sDU0r7FqRc8XJoe7FYEj3ihT0KxCABfwuAbMel2204jpnNBjV+c1rfY71OeFf/cTMCKZpzJBPPw== IN 3600
messenger.com. google-site-verification=z9mNNADBbsCO2UKMxiu5UFnUz5SvavUmC2Jx-4Lw9RI IN 7200
messenger.com. google-site-verification=f68cxjENokmrbNLEilsjxlPqbiM3lTmXKGLJFg0OHr4 IN 7200
messenger.com. v=spf1 IN 7200

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Cache-Control: private, no-cache, no-store, must-revalidate
Expires: 1st January, 2000
Content-Type: text/html; charset="utf-8"
Date: 14th April, 2023
accept-ch-lifetime: 4838400
accept-ch: viewport-width,Sec-CH-Prefers-Color-Scheme
Pragma: no-cache
content-security-policy-report-only: default-src https
content-security-policy: default-src data
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 0
report-to: {"max_age":86400,"endpoints":[{"url":"https:\/\/www.facebook.com\/browser_reporting\/?minimize=0"}],"group":"coep_report"}, {"max_age":259200,"endpoints":[{"url":"https:\/\/www.messenger.com\/ajax\/messenger_error_reports\/?device_level=unknown"}]}
cross-origin-embedder-policy-report-only: require-corp;report-to="coep_report"
cross-origin-opener-policy: same-origin-allow-popups
Vary: Accept-Encoding
Strict-Transport-Security: max-age=15552000; preload; includeSubDomains
X-FB-Debug: H3Xhz2twSEI+NMNtveGrZhJpzWTXO/DzLZ5uxOUIrA8CernEUXs8MRk1aku+c4/CUyGmsesUNNz1lkpu09NHOA==
Transfer-Encoding: chunked
Alt-Svc: h3=":443"; ma=86400
Connection: keep-alive

Whois Lookup

Created: 4th November, 1998
Changed: 26th January, 2022
Expires: 3rd November, 2031
Registrar: RegistrarSafe, LLC
Status: clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited
serverDeleteProhibited
serverTransferProhibited
serverUpdateProhibited
Nameservers: a.ns.facebook.com
b.ns.facebook.com
c.ns.facebook.com
d.ns.facebook.com
Owner Name: Domain Admin
Owner Organization: Meta Platforms, Inc.
Owner Street: 1601 Willow Rd
Owner Post Code: 94025
Owner City: Menlo Park
Owner State: CA
Owner Country: US
Owner Phone: +1.6505434800
Owner Email: domain@fb.com
Admin Name: Domain Admin
Admin Organization: Meta Platforms, Inc.
Admin Street: 1601 Willow Rd
Admin Post Code: 94025
Admin City: Menlo Park
Admin State: CA
Admin Country: US
Admin Phone: +1.6505434800
Admin Email: domain@fb.com
Tech Name: Domain Admin
Tech Organization: Meta Platforms, Inc.
Tech Street: 1601 Willow Rd
Tech Post Code: 94025
Tech City: Menlo Park
Tech State: CA
Tech Country: US
Tech Phone: +1.6505434800
Tech Email: domain@fb.com
Full Whois: Domain Name: MESSENGER.COM
Registry Domain ID: 2341650_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrarsafe.com
Registrar URL: https://www.registrarsafe.com
Updated Date: 2022-01-26T17:28:50Z
Creation Date: 1998-11-04T05:00:00Z
Registrar Registration Expiration Date: 2031-11-03T05:00:00Z
Registrar: RegistrarSafe, LLC
Registrar IANA ID: 3237
Registrar Abuse Contact Email: abusecomplaints@registrarsafe.com
Registrar Abuse Contact Phone: +1.6503087004
Domain Status: clientDeleteProhibited https://www.icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://www.icann.org/epp#clientUpdateProhibited
Domain Status: serverDeleteProhibited https://www.icann.org/epp#serverDeleteProhibited
Domain Status: serverTransferProhibited https://www.icann.org/epp#serverTransferProhibited
Domain Status: serverUpdateProhibited https://www.icann.org/epp#serverUpdateProhibited
Registry Registrant ID:
Registrant Name: Domain Admin
Registrant Organization: Meta Platforms, Inc.
Registrant Street: 1601 Willow Rd
Registrant City: Menlo Park
Registrant State/Province: CA
Registrant Postal Code: 94025
Registrant Country: US
Registrant Phone: +1.6505434800
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: domain@fb.com
Registry Admin ID:
Admin Name: Domain Admin
Admin Organization: Meta Platforms, Inc.
Admin Street: 1601 Willow Rd
Admin City: Menlo Park
Admin State/Province: CA
Admin Postal Code: 94025
Admin Country: US
Admin Phone: +1.6505434800
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: domain@fb.com
Registry Tech ID:
Tech Name: Domain Admin
Tech Organization: Meta Platforms, Inc.
Tech Street: 1601 Willow Rd
Tech City: Menlo Park
Tech State/Province: CA
Tech Postal Code: 94025
Tech Country: US
Tech Phone: +1.6505434800
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: domain@fb.com
Name Server: D.NS.FACEBOOK.COM
Name Server: A.NS.FACEBOOK.COM
Name Server: B.NS.FACEBOOK.COM
Name Server: C.NS.FACEBOOK.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-04-14T11:55:00Z <<<

Search results obtained from the RegistrarSafe, LLC WHOIS database are
provided by RegistrarSafe, LLC for information purposes only, to assist
users in obtaining information concerning a domain name registration record.
The information contained therein is provided on an "as is" and "as available"
basis and RegistrarSafe, LLC does not guarantee the accuracy or completeness
of any information provided through the WHOIS database. By submitting a WHOIS query,
you agree to the following: (1) that you will use any information provided through
the WHOIS only for lawful purposes; (2) that you will comply with all ICANN rules
and regulations governing use of the WHOIS; (3) that you will not use any information
provided through the WHOIS to enable, or otherwise cause the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail (i.e., spam); or
(4) that you will not use the WHOIS to enable or otherwise utilize high volume,
automated, electronic processes that apply to or attach to RegistrarSafe, LLC or
its systems. RegistrarSafe, LLC reserves the right to modify these terms
at any time and to take any other appropriate actions, including but not limited to
restricting any access that violates these terms and conditions. By submitting this
query, you acknowledge and agree to abide by the foregoing terms, conditions and policies.

For more information on Whois status codes, please visit
https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en.

Nameservers

Name IP Address
a.ns.facebook.com 129.134.30.12
b.ns.facebook.com 129.134.31.12
c.ns.facebook.com 185.89.218.12
d.ns.facebook.com 185.89.219.12
Related

Similar Sites

Domain Valuation Snoop Score
$484 USD 1/5
0/5
$2,020 USD 2/5
$22,833 USD 3/5
$899 USD 1/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

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

Sites hosted on the same IP address

Domain Valuation Snoop Score
$763 USD 2/5
$1,000 USD 2/5
$959 USD 2/5
$873 USD 1/5
$4,498 USD 2/5