Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

meetme.com

meetme.com is SSL secured

Free website and domain report on meetme.com

Last Updated: 25th March, 2024
Overview

Snoop Summary for meetme.com

This is a free and comprehensive report about meetme.com. Meetme.com is hosted in United States on a server with an IP address of 204.145.125.82, where the local currency is USD and English is the local language. Our records indicate that meetme.com is owned/operated by MeetMe. Meetme.com is expected to earn an estimated $119 USD per day from advertising revenue. The sale of meetme.com would possibly be worth $86,760 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Meetme.com is wildly popular with an estimated 28,101 daily unique visitors. This report was last updated 25th March, 2024.

About meetme.com

Site Preview: meetme.com meetme.com
Title: MeetMe - Chat and Meet New People
Description: MeetMe helps you find new people nearby who share your interests and want to chat now! It’s fun, friendly, and free! Join 100+ MILLION PEOPLE chatting and making new friends. It’s for all ages, all nationalities, all backgrounds — EVERYONE! So what are you waiting for? Join the best site for finding new friends to chat with!
Keywords and Tags: college, dating, free online dating, high school, meet new people, popular, social networking
Related Terms: all ages, all ages chat, join over 100, list of people nearby, meetme, meetme.com brandee popovich, new friends, to find new friends, to meet new friends
Fav Icon:
Age: Over 28 years old
Domain Created: 5th September, 1995
Domain Updated: 3rd August, 2023
Domain Expires: 4th September, 2024
Review

Snoop Score

3/5 (Great!)

Valuation

$86,760 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 27,952
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 28,101
Monthly Visitors: 855,306
Yearly Visitors: 10,256,865
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $119 USD
Monthly Revenue: $3,617 USD
Yearly Revenue: $43,375 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

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

Page Speed Analysis

Average Load Time: 0.96 seconds
Load Time Comparison: Faster than 73% of sites

PageSpeed Insights

Avg. (All Categories) 71
Performance 76
Accessibility 67
Best Practices 75
SEO 82
PWA 56
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.meetme.com/
Updated: 12th November, 2022

2.10 seconds
First Contentful Paint (FCP)
70%
16%
14%

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

Simulate loading on desktop
76

Performance

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

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.5 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).

Audits

Max Potential First Input Delay — 40 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://meetme.com/
http/1.1
0
41.005000006407
476
0
302
text/html
https://meetme.com/
http/1.1
41.387000121176
159.67500000261
502
0
301
text/html
http://www.meetme.com/
http/1.1
160.07099999115
218.32900005393
480
0
302
text/html
https://www.meetme.com/
http/1.1
218.67100009695
366.39600014314
2583
5609
200
text/html
Document
https://beta.meetme.com/bower_components/requirejs/require.js?1659377197738
h2
382.79900001362
475.7250000257
21602
85921
200
application/javascript
Script
https://beta.meetme.com/css/phoenix.css?1659377197738
h2
383.12699995004
524.81900015846
77761
588946
200
text/css
Stylesheet
https://beta.meetme.com/js/app/main.js?1659377197738
h2
490.27299997397
506.71799993142
3156
7579
200
application/javascript
Script
https://beta.meetme.com/bower_components/jquery/dist/jquery.min.js?cb=1659377197738
h2
515.17800008878
621.3080000598
30200
84380
200
application/javascript
Script
https://beta.meetme.com/fonts/fontawesome-webfont.woff2?v=4.3.0
h2
560.0310000591
620.62199995853
57025
56780
200
font/woff2
Font
https://beta.meetme.com/fonts/lato-v11-latin_latin-ext-regular.woff2
h2
564.46000002325
581.08699996956
28137
27892
200
font/woff2
Font
https://beta.meetme.com/bower_components/bootstrap/dist/js/bootstrap.min.js?cb=1659377197738
h2
760.59300010093
836.43399993889
11546
39680
200
application/javascript
Script
https://beta.meetme.com/js/lib/phoenix.js?cb=1659377197738
h2
845.55199998431
931.95899995044
247707
1275798
200
application/javascript
Script
https://beta.meetme.com/bower_components/lodash/lodash.min.js?cb=1659377197738
h2
1027.8280000202
1101.1179999914
19120
50543
200
application/javascript
Script
https://beta.meetme.com/bower_components/sanitize.js/lib/sanitize.js?cb=1659377197738
h2
1029.841999989
1100.231999997
3437
9001
200
application/javascript
Script
https://beta.meetme.com/js/app/strings.js?cb=1659377197738
h2
1031.0560001526
1070.3529999591
27500
68025
200
application/javascript
Script
https://beta.meetme.com/bower_components/node-uuid/uuid.js?cb=1659377197738
h2
1032.773999963
1121.7120001093
3560
8013
200
application/javascript
Script
https://beta.meetme.com/bower_components/simpleStorage/simpleStorage.js?cb=1659377197738
h2
1033.6450000759
1101.5280000865
3090
11395
200
application/javascript
Script
https://beta.meetme.com/bower_components/ua-parser-js/dist/ua-parser.min.js?cb=1659377197738
h2
1034.7560001537
1101.8459999468
8091
19701
200
application/javascript
Script
https://beta.meetme.com/bower_components/moment/min/moment.min.js?cb=1659377197738
h2
1036.9520001113
1086.830999935
12189
33783
200
application/javascript
Script
https://beta.meetme.com/templates/compiled.js?cb=1659377197738
h2
1040.3229999356
1091.1199999973
67122
753898
200
application/javascript
Script
https://beta.meetme.com/bower_components/handlebars-helpers/src/helpers.js?cb=1659377197738
h2
1042.8160000592
1112.4340000097
1456
3051
200
application/javascript
Script
https://beta.meetme.com/bower_components/numeral/min/numeral.min.js?cb=1659377197738
h2
1043.3209999464
1077.016999945
4635
11444
200
application/javascript
Script
https://beta.meetme.com/bower_components/Autolinker.js/dist/Autolinker.min.js?cb=1659377197738
h2
1058.8609999977
1092.5670000724
4933
10437
200
application/javascript
Script
https://beta.meetme.com/bower_components/handlebars/handlebars.min.js?cb=1659377197738
h2
1062.5430000946
1129.3460000306
24772
80288
200
application/javascript
Script
https://beta.meetme.com/bower_components/backbone/backbone.js?cb=1659377197738
h2
1119.752000086
1195.7290000282
18074
60997
200
application/javascript
Script
https://api.meetme.com/mobile/settings
h2
1264.7590001579
1385.9200000297
896
0
200
application/json
Preflight
https://api.meetme.com/mobile/settings
h2
1386.4740000572
1500.9900000878
6071
27038
200
application/json
XHR
https://profile.meetme.com/mobile/member/v2/?peek=1
http/1.1
1522.4940001499
1674.4640001561
811
0
200
application/json
Preflight
https://profile.meetme.com/mobile/member/v2/?peek=1
http/1.1
1675.2039999701
1769.806999946
674
88
200
application/json
XHR
https://api.meetme.com/mobile/counts
h2
1541.727000149
1673.5440001357
896
0
200
application/json
Preflight
https://profile.meetme.com/mobile/membersettings
http/1.1
1545.4590001609
1674.9080000445
811
0
200
application/json
Preflight
https://api.meetme.com/mobile/counts
h2
1673.9640000742
1760.2880001068
758
88
200
application/json
XHR
https://profile.meetme.com/mobile/membersettings
http/1.1
1675.6629999727
1765.325000044
674
88
200
application/json
XHR
https://beta.meetme.com/js/app/SmartBanner.js?cb=1659377197738
h2
1546.0910000838
1565.952999983
1351
752
200
application/javascript
Script
https://beta.meetme.com/bower_components/jquery.smartbanner/jquery.smartbanner.js?cb=1659377197738
h2
1576.7250000499
1593.0820000358
4943
14903
200
application/javascript
Script
https://beta.meetme.com/node_modules/web-live-sdk/dist/web-live-sdk.js?cb=1659377197738
h2
1636.3260000944
1654.9349999987
16311
52740
200
application/javascript
Script
https://beta.meetme.com/bower_components/seiyria-bootstrap-slider/dist/bootstrap-slider.min.js?cb=1659377197738
h2
1643.6900000554
1661.558000138
6087
20975
200
application/javascript
Script
https://api.meetme.com/mobile/mobilerequestgeodata
h2
1757.8710000962
1858.2359999418
736
50
200
application/json
XHR
https://api.meetme.com/mobile/mobilerequestgeodata
h2
1648.6289999448
1757.5660001021
896
0
200
application/json
Preflight
https://beta.meetme.com/img/menu/ic_filter_caret_down.png
h2
1787.4829999637
1804.5789999887
903
317
200
image/png
Image
https://beta.meetme.com/fonts/meetme-icons.woff?92030772
h2
1790.9679999575
1806.7509999964
14244
14000
200
font/woff
Font
https://beta.meetme.com/img/backgrounds/energetic-youth.jpg
h2
1820.0310000684
1848.2890001033
89100
88509
200
image/jpeg
Image
data
1824.9660001602
1825.2050001174
0
483
200
image/svg+xml
Image
data
1834.5719999634
1834.7710000817
0
1508
200
image/svg+xml
Image
data
1837.2939999681
1837.5339999329
0
2590
200
image/svg+xml
Image
data
1839.510000078
1839.6700001322
0
675
200
image/svg+xml
Image
https://beta.meetme.com/fonts/lato-v11-latin-ext_latin-700.woff2
h2
1841.7009999976
1859.3520000577
27901
27656
200
font/woff2
Font
https://beta.meetme.com/img/logo_long.png
h2
1850.8520000614
1867.1830000822
5376
4788
200
image/png
Image
https://connect.facebook.net/en_US/sdk.js?cb=1659377197738
h2
1860.2780001238
1876.1279999744
2640
3097
200
application/x-javascript
Script
data
1867.8190000355
1868.080999935
0
2956
200
image/svg+xml
Image
data
1870.6499999389
1870.8590001334
0
1354
200
image/svg+xml
Image
https://api.meetme.com/mobile/languages
h2
1887.3779999558
1988.7600000948
896
0
200
application/json
Preflight
https://api.meetme.com/mobile/languages
h2
1989.1870000865
2081.033000024
949
631
200
application/json
XHR
https://connect.facebook.net/en_US/sdk.js?hash=27e09e85a6354c818ce53cd1733e4a7b
h2
1927.8700000141
1950.3120000008
87854
307557
200
application/x-javascript
Script
https://www.facebook.com/x/oauth/status?client_id=109674171476&input_token&origin=1&redirect_uri=https%3A%2F%2Fwww.meetme.com%2F%23home&sdk=joey&wants_cookie_data=false
h2
1998.6010000575
2028.7949999329
2321
0
200
text/plain
Fetch
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)
371.047
9.001
386.575
5.216
527.548
23.377
551.212
16.863
568.602
38.613
622.513
5.16
633.685
12.279
975.5
17.017
992.558
30.891
1027.371
19.798
1108.927
12.255
1121.243
19.932
1141.719
12.123
1155.867
17.293
1176.336
15.434
1191.782
7.278
1202.051
36.241
1239.705
13.909
1257.597
8.464
1502.955
21.507
1533.97
18.528
1596.748
10.887
1608.806
9.435
1622.643
11.09
1635.583
11.097
1660.381
5.206
1667.237
18.691
1768.496
20.283
1789.877
5.712
1809.214
43.457
1865.55
15.645
1902.408
5.202
1908.229
16.604
1971.918
21.113
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Meetme.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Meetme.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Meetme.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Meetme.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 27 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Meetme.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://beta.meetme.com/bower_components/requirejs/require.js?1659377197738
21602
15121
https://beta.meetme.com/bower_components/backbone/backbone.js?cb=1659377197738
18074
10188
https://beta.meetme.com/bower_components/jquery.smartbanner/jquery.smartbanner.js?cb=1659377197738
4943
2062
Reduce unused CSS — Potential savings of 72 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Meetme.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://beta.meetme.com/css/phoenix.css?1659377197738
77761
73584
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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 150 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.meetme.com/
148.72
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Meetme.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 931 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://beta.meetme.com/js/lib/phoenix.js?cb=1659377197738
247707
https://beta.meetme.com/img/backgrounds/energetic-youth.jpg
89100
https://connect.facebook.net/en_US/sdk.js?hash=27e09e85a6354c818ce53cd1733e4a7b
87854
https://beta.meetme.com/css/phoenix.css?1659377197738
77761
https://beta.meetme.com/templates/compiled.js?cb=1659377197738
67122
https://beta.meetme.com/fonts/fontawesome-webfont.woff2?v=4.3.0
57025
https://beta.meetme.com/bower_components/jquery/dist/jquery.min.js?cb=1659377197738
30200
https://beta.meetme.com/fonts/lato-v11-latin_latin-ext-regular.woff2
28137
https://beta.meetme.com/fonts/lato-v11-latin-ext_latin-700.woff2
27901
https://beta.meetme.com/js/app/strings.js?cb=1659377197738
27500
Avoids an excessive DOM size — 110 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
110
Maximum DOM Depth
div#home-content-header > p > a.btn > br
15
Maximum Child Elements
body.site-responsive
10
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Meetme.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://beta.meetme.com/bower_components/requirejs/require.js?1659377197738
378.968
305.863
1.33
https://www.meetme.com/
120.948
5.865
1.901
Unattributable
101.938
2.907
0
Minimizes main-thread work — 0.8 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)
Script Evaluation
389.274
Other
168.034
Style & Layout
79.407
Script Parsing & Compilation
58.987
Parse HTML & CSS
30.435
Rendering
27.372
Garbage Collection
7.194
Keep request counts low and transfer sizes small — 49 requests • 931 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
49
953253
Script
24
631376
Font
4
127307
Image
3
95379
Stylesheet
1
77761
Other
16
18847
Document
1
2583
Media
0
0
Third-party
3
92815
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)
SHOW DETAILS
92815
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
Meet, chat, and have fun with new people — free!
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
Meet, chat, and have fun with new people — free! Get it for ANDROID Get it for…
0.25957826226542
About Us Press Careers Social Theater FAQs Suggestions?
8.5672591425152E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
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.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of meetme.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Metrics

Speed Index — 2.0 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.3 s
The timing of the largest text or image that is painted.

Audits

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

Other

Reduce unused JavaScript — Potential savings of 323 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://beta.meetme.com/js/lib/phoenix.js?cb=1659377197738
247707
208155
https://beta.meetme.com/templates/compiled.js?cb=1659377197738
67122
63518
https://connect.facebook.net/en_US/sdk.js?hash=27e09e85a6354c818ce53cd1733e4a7b
87854
59278
Avoid multiple page redirects — Potential savings of 530 ms
Redirects can cause additional delays before the page can begin loading. Meetme.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://meetme.com/
190
https://meetme.com/
150
http://www.meetme.com/
190
https://www.meetme.com/
0

Metrics

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

Other

Serve static assets with an efficient cache policy — 30 resources found
Meetme.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://beta.meetme.com/js/lib/phoenix.js?cb=1659377197738
0
247707
https://beta.meetme.com/img/backgrounds/energetic-youth.jpg
0
89100
https://beta.meetme.com/css/phoenix.css?1659377197738
0
77761
https://beta.meetme.com/templates/compiled.js?cb=1659377197738
0
67122
https://beta.meetme.com/fonts/fontawesome-webfont.woff2?v=4.3.0
0
57025
https://beta.meetme.com/bower_components/jquery/dist/jquery.min.js?cb=1659377197738
0
30200
https://beta.meetme.com/fonts/lato-v11-latin_latin-ext-regular.woff2
0
28137
https://beta.meetme.com/fonts/lato-v11-latin-ext_latin-700.woff2
0
27901
https://beta.meetme.com/js/app/strings.js?cb=1659377197738
0
27500
https://beta.meetme.com/bower_components/handlebars/handlebars.min.js?cb=1659377197738
0
24772
https://beta.meetme.com/bower_components/requirejs/require.js?1659377197738
0
21602
https://beta.meetme.com/bower_components/lodash/lodash.min.js?cb=1659377197738
0
19120
https://beta.meetme.com/bower_components/backbone/backbone.js?cb=1659377197738
0
18074
https://beta.meetme.com/node_modules/web-live-sdk/dist/web-live-sdk.js?cb=1659377197738
0
16311
https://beta.meetme.com/fonts/meetme-icons.woff?92030772
0
14244
https://beta.meetme.com/bower_components/moment/min/moment.min.js?cb=1659377197738
0
12189
https://beta.meetme.com/bower_components/bootstrap/dist/js/bootstrap.min.js?cb=1659377197738
0
11546
https://beta.meetme.com/bower_components/ua-parser-js/dist/ua-parser.min.js?cb=1659377197738
0
8091
https://beta.meetme.com/bower_components/seiyria-bootstrap-slider/dist/bootstrap-slider.min.js?cb=1659377197738
0
6087
https://beta.meetme.com/img/logo_long.png
0
5376
https://beta.meetme.com/bower_components/jquery.smartbanner/jquery.smartbanner.js?cb=1659377197738
0
4943
https://beta.meetme.com/bower_components/Autolinker.js/dist/Autolinker.min.js?cb=1659377197738
0
4933
https://beta.meetme.com/bower_components/numeral/min/numeral.min.js?cb=1659377197738
0
4635
https://beta.meetme.com/bower_components/node-uuid/uuid.js?cb=1659377197738
0
3560
https://beta.meetme.com/bower_components/sanitize.js/lib/sanitize.js?cb=1659377197738
0
3437
https://beta.meetme.com/js/app/main.js?1659377197738
0
3156
https://beta.meetme.com/bower_components/simpleStorage/simpleStorage.js?cb=1659377197738
0
3090
https://beta.meetme.com/bower_components/handlebars-helpers/src/helpers.js?cb=1659377197738
0
1456
https://beta.meetme.com/js/app/SmartBanner.js?cb=1659377197738
0
1351
https://beta.meetme.com/img/menu/ic_filter_caret_down.png
0
903
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://beta.meetme.com/fonts/fontawesome-webfont.woff2?v=4.3.0
60.590999899432
https://beta.meetme.com/fonts/lato-v11-latin_latin-ext-regular.woff2
16.626999946311
https://beta.meetme.com/fonts/meetme-icons.woff?92030772
15.783000038937
https://beta.meetme.com/fonts/lato-v11-latin-ext_latin-700.woff2
17.651000060141
67

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

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

Names and labels

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

Contrast

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

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Names and labels

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

Best practices

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

Manual Checks

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
3.4.1
jQuery
2.1.4
Backbone
1.1.2
Lo-Dash
3.10.1
RequireJS
2.1.22
Moment.js
2.8.4
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.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 2 insecure requests 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://meetme.com/
Allowed
http://www.meetme.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 16 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
SHOW DETAILS
4
Medium
SHOW DETAILS
8
High
SHOW DETAILS
4
High

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.
SHOW DETAILS
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://beta.meetme.com/templates/compiled.js?cb=1659377197738
https://beta.meetme.com/js/lib/phoenix.js?cb=1659377197738
https://beta.meetme.com/bower_components/jquery/dist/jquery.min.js?cb=1659377197738
https://beta.meetme.com/bower_components/jquery/dist/jquery.min.map
82

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Crawling and Indexing

robots.txt is not valid — 2 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
3
Noarchive: /
Unknown directive
6
Noarchive: /
Unknown directive

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div.container > div.row > h2.col-sm-6 > img

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

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

Installable

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

PWA Optimized

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 meetme.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

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

Manual Checks

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

1.71 seconds
First Contentful Paint (FCP)
77%
12%
11%

0.03 seconds
First Input Delay (FID)
89%
8%
3%

Simulate loading on mobile
38

Performance

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

Metrics

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

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Meetme.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Meetme.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Meetme.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Meetme.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 27 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Meetme.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://beta.meetme.com/bower_components/requirejs/require.js?1659377197738
21602
15121
https://beta.meetme.com/bower_components/backbone/backbone.js?cb=1659377197738
18074
10188
https://beta.meetme.com/bower_components/jquery.smartbanner/jquery.smartbanner.js?cb=1659377197738
4943
2062
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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 90 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://beta.meetme.com/
92.666
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Meetme.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 934 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://beta.meetme.com/js/lib/phoenix.js?cb=1659377197738
247707
https://beta.meetme.com/img/backgrounds/energetic-youth.jpg
89100
https://connect.facebook.net/en_US/sdk.js?hash=27e09e85a6354c818ce53cd1733e4a7b
87854
https://beta.meetme.com/css/phoenix.css?1659377197738
77761
https://beta.meetme.com/templates/compiled.js?cb=1659377197738
67122
https://beta.meetme.com/fonts/fontawesome-webfont.woff2?v=4.3.0
57025
https://beta.meetme.com/bower_components/jquery/dist/jquery.min.js?cb=1659377197738
30200
https://beta.meetme.com/fonts/lato-v11-latin_latin-ext-regular.woff2
28137
https://beta.meetme.com/fonts/lato-v11-latin-ext_latin-700.woff2
27901
https://beta.meetme.com/js/app/strings.js?cb=1659377197738
27500
Avoids an excessive DOM size — 100 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
100
Maximum DOM Depth
div#home-content-header > p > a.btn > br
15
Maximum Child Elements
body.site-responsive
10
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Meetme.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Keep request counts low and transfer sizes small — 54 requests • 934 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
54
956465
Script
24
631376
Font
4
127307
Image
3
95379
Stylesheet
1
77761
Other
21
22242
Document
1
2400
Media
0
0
Third-party
3
92812
Minimize third-party usage — Third-party code blocked the main thread for 30 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)
SHOW DETAILS
92812
32.012
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
Meet, chat, and have fun with new people — free!
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 — 16 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://beta.meetme.com/bower_components/backbone/backbone.js?cb=1659377197738
9524
157
https://beta.meetme.com/
4167
147
https://beta.meetme.com/js/lib/phoenix.js?cb=1659377197738
7928
134
https://connect.facebook.net/en_US/sdk.js?hash=27e09e85a6354c818ce53cd1733e4a7b
11734
104
https://beta.meetme.com/bower_components/requirejs/require.js?1659377197738
9681
83
https://beta.meetme.com/bower_components/requirejs/require.js?1659377197738
9767
79
https://beta.meetme.com/css/phoenix.css?1659377197738
4710
75
https://beta.meetme.com/templates/compiled.js?cb=1659377197738
9184
73
https://beta.meetme.com/bower_components/requirejs/require.js?1659377197738
8062
72
https://beta.meetme.com/bower_components/jquery/dist/jquery.min.js?cb=1659377197738
6660
66
https://beta.meetme.com/bower_components/jquery.smartbanner/jquery.smartbanner.js?cb=1659377197738
9864
61
Unattributable
630
59
https://beta.meetme.com/bower_components/requirejs/require.js?1659377197738
10439
58
https://beta.meetme.com/bower_components/requirejs/require.js?1659377197738
9990
53
https://beta.meetme.com/bower_components/lodash/lodash.min.js?cb=1659377197738
8284
52
https://beta.meetme.com/bower_components/ua-parser-js/dist/ua-parser.min.js?cb=1659377197738
8584
51
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of meetme.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://meetme.com/
http/1.1
0
61.60999997519
476
0
302
text/html
https://meetme.com/
http/1.1
62.103999953251
218.51899998728
502
0
301
text/html
http://www.meetme.com/
http/1.1
219.05999997398
287.09999995772
480
0
302
text/html
https://www.meetme.com/
http/1.1
287.58599999128
432.4599999818
790
0
302
text/html
http://m.meetme.com/
http/1.1
432.78799997643
499.03899995843
293
0
302
text/html
https://m.meetme.com/
http/1.1
499.38099994324
645.81499999622
494
0
302
text/html
https://beta.meetme.com/
h2
646.24199998798
737.91399999755
2400
5609
200
text/html
Document
https://beta.meetme.com/bower_components/requirejs/require.js?1659377197738
h2
754.44399996195
903.27199996682
21602
85921
200
application/javascript
Script
https://beta.meetme.com/css/phoenix.css?1659377197738
h2
754.95699996827
936.88699998893
77761
588946
200
text/css
Stylesheet
https://beta.meetme.com/js/app/main.js?1659377197738
h2
918.2579999906
2989.9229999864
3156
7579
200
application/javascript
Script
https://beta.meetme.com/fonts/fontawesome-webfont.woff2?v=4.3.0
h2
966.01999999257
1060.8679999714
57025
56780
200
font/woff2
Font
https://beta.meetme.com/fonts/lato-v11-latin_latin-ext-regular.woff2
h2
970.32499994384
1077.4919999531
28137
27892
200
font/woff2
Font
https://beta.meetme.com/bower_components/jquery/dist/jquery.min.js?cb=1659377197738
h2
2999.6009999886
3116.7709999718
30200
84380
200
application/javascript
Script
https://beta.meetme.com/bower_components/bootstrap/dist/js/bootstrap.min.js?cb=1659377197738
h2
3256.9219999714
3331.8959999597
11546
39680
200
application/javascript
Script
https://beta.meetme.com/js/lib/phoenix.js?cb=1659377197738
h2
3341.7869999539
3444.9610000011
247707
1275798
200
application/javascript
Script
https://beta.meetme.com/bower_components/lodash/lodash.min.js?cb=1659377197738
h2
3535.2739999653
3642.5209999434
19120
50543
200
application/javascript
Script
https://beta.meetme.com/bower_components/sanitize.js/lib/sanitize.js?cb=1659377197738
h2
3536.8099999614
3564.1979999491
3437
9001
200
application/javascript
Script
https://beta.meetme.com/js/app/strings.js?cb=1659377197738
h2
3537.7169999992
3612.5069999835
27500
68025
200
application/javascript
Script
https://beta.meetme.com/bower_components/node-uuid/uuid.js?cb=1659377197738
h2
3539.1669999808
3608.0659999861
3560
8013
200
application/javascript
Script
https://beta.meetme.com/bower_components/simpleStorage/simpleStorage.js?cb=1659377197738
h2
3539.7899999516
3564.682999975
3090
11395
200
application/javascript
Script
https://beta.meetme.com/bower_components/ua-parser-js/dist/ua-parser.min.js?cb=1659377197738
h2
3540.8459999599
3582.4609999545
8091
19701
200
application/javascript
Script
https://beta.meetme.com/bower_components/moment/min/moment.min.js?cb=1659377197738
h2
3542.8989999928
3583.033999952
12189
33783
200
application/javascript
Script
https://beta.meetme.com/templates/compiled.js?cb=1659377197738
h2
3545.8919999655
3640.4739999562
67122
753898
200
application/javascript
Script
https://beta.meetme.com/bower_components/handlebars-helpers/src/helpers.js?cb=1659377197738
h2
3547.8479999583
3586.8069999851
1456
3051
200
application/javascript
Script
https://beta.meetme.com/bower_components/numeral/min/numeral.min.js?cb=1659377197738
h2
3548.7779999967
3586.0579999862
4635
11444
200
application/javascript
Script
https://beta.meetme.com/bower_components/Autolinker.js/dist/Autolinker.min.js?cb=1659377197738
h2
3561.5479999688
3586.4529999672
4933
10437
200
application/javascript
Script
https://beta.meetme.com/bower_components/handlebars/handlebars.min.js?cb=1659377197738
h2
3565.2809999883
3600.2829999779
24772
80288
200
application/javascript
Script
https://beta.meetme.com/bower_components/backbone/backbone.js?cb=1659377197738
h2
3662.8139999812
3689.3639999907
18074
60997
200
application/javascript
Script
https://api.meetme.com/mobile/settings
h2
3752.7919999557
3828.6629999639
897
0
200
application/json
Preflight
https://api.meetme.com/mobile/settings
h2
3829.1549999849
3918.2149999542
6072
27038
200
application/json
XHR
https://profile.meetme.com/mobile/member/v2/?peek=1
http/1.1
3939.3469999777
4094.6409999742
812
0
200
application/json
Preflight
https://profile.meetme.com/mobile/member/v2/?peek=1
http/1.1
4095.1379999751
4207.1979999891
674
88
200
application/json
XHR
https://api.meetme.com/mobile/counts
h2
3959.5369999879
4042.32399998
897
0
200
application/json
Preflight
https://profile.meetme.com/mobile/membersettings
http/1.1
3962.9639999475
4120.3959999839
812
0
200
application/json
Preflight
https://api.meetme.com/mobile/counts
h2
4042.7869999548
4104.4169999659
759
88
200
application/json
XHR
https://profile.meetme.com/mobile/membersettings
http/1.1
4120.7819999545
4274.8859999701
675
88
200
application/json
XHR
https://beta.meetme.com/js/app/SmartBanner.js?cb=1659377197738
h2
3963.8849999756
3985.178999952
1351
752
200
application/javascript
Script
https://beta.meetme.com/bower_components/jquery.smartbanner/jquery.smartbanner.js?cb=1659377197738
h2
3993.9109999686
4014.2149999738
4943
14903
200
application/javascript
Script
https://api.meetme.com/mobile/smartBannerConfig
h2
4022.8599999682
4081.4999999711
897
0
200
application/json
Preflight
https://api.meetme.com/mobile/smartBannerConfig
h2
4082.2569999727
4140.241999994
913
333
200
application/json
XHR
https://beta.meetme.com/node_modules/web-live-sdk/dist/web-live-sdk.js?cb=1659377197738
h2
4063.4999999893
4155.7719999691
16311
52740
200
application/javascript
Script
https://beta.meetme.com/bower_components/seiyria-bootstrap-slider/dist/bootstrap-slider.min.js?cb=1659377197738
h2
4072.7299999562
4093.5829999507
6087
20975
200
application/javascript
Script
https://api.meetme.com/mobile/mobilerequestgeodata
h2
4130.7410000009
4188.09099996
737
50
200
application/json
XHR
https://api.meetme.com/mobile/mobilerequestgeodata
h2
4079.1629999876
4130.3339999868
897
0
200
application/json
Preflight
https://beta.meetme.com/img/menu/ic_filter_caret_down.png
h2
4194.2509999499
4232.7489999589
903
317
200
image/png
Image
https://beta.meetme.com/fonts/meetme-icons.woff?92030772
h2
4198.0579999508
4233.3279999439
14244
14000
200
font/woff
Font
https://beta.meetme.com/img/backgrounds/energetic-youth.jpg
h2
4235.4739999864
4271.510999999
89100
88509
200
image/jpeg
Image
data
4238.5009999853
4238.8039999641
0
483
200
image/svg+xml
Image
https://beta.meetme.com/img/logo_long.png
h2
4252.0169999916
4294.9509999598
5376
4788
200
image/png
Image
https://connect.facebook.net/en_US/sdk.js?cb=1659377197738
h2
4258.3469999954
4264.4529999816
2640
3097
200
application/x-javascript
Script
data
4266.1009999574
4266.3289999473
0
2956
200
image/svg+xml
Image
data
4268.6859999667
4268.9049999462
0
1354
200
image/svg+xml
Image
https://beta.meetme.com/fonts/lato-v11-latin-ext_latin-700.woff2
h2
4271.0579999839
4340.5429999693
27901
27656
200
font/woff2
Font
https://api.meetme.com/mobile/languages
h2
4286.9099999662
4346.4939999976
897
0
200
application/json
Preflight
https://api.meetme.com/mobile/languages
h2
4346.9379999442
4395.8269999712
950
631
200
application/json
XHR
https://connect.facebook.net/en_US/sdk.js?hash=27e09e85a6354c818ce53cd1733e4a7b
h2
4299.7909999685
4309.6269999514
87854
307557
200
application/x-javascript
Script
https://www.facebook.com/x/oauth/status?client_id=109674171476&input_token&origin=2&redirect_uri=https%3A%2F%2Fbeta.meetme.com%2F%23home&sdk=joey&wants_cookie_data=false
h2
4372.4399999483
4395.3629999887
2318
0
200
text/plain
Fetch
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)
742.647
9.765
939.692
18.653
958.412
16.349
981.607
36.854
3125.391
16.531
3337.879
5.35
3483.208
14.69
3497.952
33.534
3535.335
18.085
3588.98
12.649
3614.76
10.063
3625.791
5.29
3651.556
12.993
3664.567
9.44
3674.431
18.27
3695.609
39.222
3736.407
6.698
3746.456
7.765
3920.664
20.685
3951.167
19.841
4018.058
15.211
4034.936
9.102
4049.772
12.179
4063.3
13.175
4162.46
19.562
4184.074
11.734
4196.144
6.12
4202.298
7.252
4224.239
28.926
4264.045
18.046
4313.481
9.707
4332.465
26.075
4365.394
6.846
4398.017
5.921
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Total Blocking Time — 440 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Audits

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

Other

Reduce unused CSS — Potential savings of 73 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Meetme.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://beta.meetme.com/css/phoenix.css?1659377197738
77761
74922
Reduce JavaScript execution time — 1.7 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://beta.meetme.com/bower_components/requirejs/require.js?1659377197738
1536.724
1280.348
5.544
https://beta.meetme.com/
436.792
24.408
6.008
Unattributable
375.76
16.292
0
https://connect.facebook.net/en_US/sdk.js?hash=27e09e85a6354c818ce53cd1733e4a7b
135.088
112.8
20.756
https://beta.meetme.com/js/lib/phoenix.js?cb=1659377197738
93.968
14.344
77.988
https://beta.meetme.com/bower_components/jquery/dist/jquery.min.js?cb=1659377197738
75.604
65.176
6.848
https://beta.meetme.com/css/phoenix.css?1659377197738
74.612
0
0
https://beta.meetme.com/templates/compiled.js?cb=1659377197738
52.092
1.068
50.46
Minimize main-thread work — 3.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)
Script Evaluation
1654.572
Other
643.468
Style & Layout
253.864
Script Parsing & Compilation
212.828
Parse HTML & CSS
102.28
Rendering
90.9
Garbage Collection
20.816

Metrics

First Contentful Paint — 4.4 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 11.2 s
The time taken for the page to become fully interactive.
Speed Index — 11.4 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 10.9 s
The timing of the largest text or image that is painted.

Audits

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

Other

Reduce unused JavaScript — Potential savings of 324 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://beta.meetme.com/js/lib/phoenix.js?cb=1659377197738
247707
208799
https://beta.meetme.com/templates/compiled.js?cb=1659377197738
67122
63530
https://connect.facebook.net/en_US/sdk.js?hash=27e09e85a6354c818ce53cd1733e4a7b
87854
59309
Avoid multiple page redirects — Potential savings of 3,330 ms
Redirects can cause additional delays before the page can begin loading. Meetme.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://meetme.com/
630
https://meetme.com/
480
http://www.meetme.com/
630
https://www.meetme.com/
480
http://m.meetme.com/
630
https://m.meetme.com/
480
https://beta.meetme.com/
0
Serve static assets with an efficient cache policy — 30 resources found
Meetme.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://beta.meetme.com/js/lib/phoenix.js?cb=1659377197738
0
247707
https://beta.meetme.com/img/backgrounds/energetic-youth.jpg
0
89100
https://beta.meetme.com/css/phoenix.css?1659377197738
0
77761
https://beta.meetme.com/templates/compiled.js?cb=1659377197738
0
67122
https://beta.meetme.com/fonts/fontawesome-webfont.woff2?v=4.3.0
0
57025
https://beta.meetme.com/bower_components/jquery/dist/jquery.min.js?cb=1659377197738
0
30200
https://beta.meetme.com/fonts/lato-v11-latin_latin-ext-regular.woff2
0
28137
https://beta.meetme.com/fonts/lato-v11-latin-ext_latin-700.woff2
0
27901
https://beta.meetme.com/js/app/strings.js?cb=1659377197738
0
27500
https://beta.meetme.com/bower_components/handlebars/handlebars.min.js?cb=1659377197738
0
24772
https://beta.meetme.com/bower_components/requirejs/require.js?1659377197738
0
21602
https://beta.meetme.com/bower_components/lodash/lodash.min.js?cb=1659377197738
0
19120
https://beta.meetme.com/bower_components/backbone/backbone.js?cb=1659377197738
0
18074
https://beta.meetme.com/node_modules/web-live-sdk/dist/web-live-sdk.js?cb=1659377197738
0
16311
https://beta.meetme.com/fonts/meetme-icons.woff?92030772
0
14244
https://beta.meetme.com/bower_components/moment/min/moment.min.js?cb=1659377197738
0
12189
https://beta.meetme.com/bower_components/bootstrap/dist/js/bootstrap.min.js?cb=1659377197738
0
11546
https://beta.meetme.com/bower_components/ua-parser-js/dist/ua-parser.min.js?cb=1659377197738
0
8091
https://beta.meetme.com/bower_components/seiyria-bootstrap-slider/dist/bootstrap-slider.min.js?cb=1659377197738
0
6087
https://beta.meetme.com/img/logo_long.png
0
5376
https://beta.meetme.com/bower_components/jquery.smartbanner/jquery.smartbanner.js?cb=1659377197738
0
4943
https://beta.meetme.com/bower_components/Autolinker.js/dist/Autolinker.min.js?cb=1659377197738
0
4933
https://beta.meetme.com/bower_components/numeral/min/numeral.min.js?cb=1659377197738
0
4635
https://beta.meetme.com/bower_components/node-uuid/uuid.js?cb=1659377197738
0
3560
https://beta.meetme.com/bower_components/sanitize.js/lib/sanitize.js?cb=1659377197738
0
3437
https://beta.meetme.com/js/app/main.js?1659377197738
0
3156
https://beta.meetme.com/bower_components/simpleStorage/simpleStorage.js?cb=1659377197738
0
3090
https://beta.meetme.com/bower_components/handlebars-helpers/src/helpers.js?cb=1659377197738
0
1456
https://beta.meetme.com/js/app/SmartBanner.js?cb=1659377197738
0
1351
https://beta.meetme.com/img/menu/ic_filter_caret_down.png
0
903
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://beta.meetme.com/fonts/fontawesome-webfont.woff2?v=4.3.0
94.847999978811
https://beta.meetme.com/fonts/lato-v11-latin_latin-ext-regular.woff2
107.16700000921
https://beta.meetme.com/fonts/meetme-icons.woff?92030772
35.269999993034
https://beta.meetme.com/fonts/lato-v11-latin-ext_latin-700.woff2
69.484999985434
First Contentful Paint (3G) — 8622 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
67

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

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

Names and labels

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

Contrast

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

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div.container > div.row > h2.col-sm-6 > img

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
head > meta

Manual Checks

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-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.
Name Version
Bootstrap
3.4.1
jQuery
2.1.4
Backbone
1.1.2
Lo-Dash
3.10.1
RequireJS
2.1.22
Moment.js
2.8.4
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.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 3 insecure requests 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://meetme.com/
Allowed
http://www.meetme.com/
Allowed
http://m.meetme.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 16 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
SHOW DETAILS
4
Medium
SHOW DETAILS
8
High
SHOW DETAILS
4
High

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.
SHOW DETAILS
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://beta.meetme.com/templates/compiled.js?cb=1659377197738
https://beta.meetme.com/js/lib/phoenix.js?cb=1659377197738
https://beta.meetme.com/bower_components/jquery/dist/jquery.min.js?cb=1659377197738
https://beta.meetme.com/bower_components/jquery/dist/jquery.min.map
92

SEO

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

Crawling and Indexing

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

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div.container > div.row > h2.col-sm-6 > img

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

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

Installable

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

PWA Optimized

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 meetme.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

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

Manual Checks

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

Server Location

Server IP Address: 204.145.125.82
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
MeetMe, Inc.
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
MarkMonitor, Inc. 104.18.39.152
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: *.meetme.com
Issued By: Sectigo RSA Organization Validation Secure Server CA
Valid From: 23rd June, 2023
Valid To: 22nd June, 2024
Subject: CN = *.meetme.com
O = The Meet Group, Inc
S = US
Hash: 263fedcb
Issuer: CN = Sectigo RSA Organization Validation Secure Server CA
O = Sectigo Limited
S = GB
Version: 2
Serial Number: 0xE01372C097E28CE59478247D0B722639
Serial Number (Hex): E01372C097E28CE59478247D0B722639
Valid From: 23rd June, 2024
Valid To: 22nd June, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:17:D9:D6:25:27:67:F9:31:C2:49:43:D9:30:36:44:8C:6C:A9:4F:EB
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.sectigo.com/SectigoRSAOrganizationValidationSecureServerCA.crl
Certificate Policies: Policy: 1.3.6.1.4.1.6449.1.2.1.3.4
CPS: https://sectigo.com/CPS
Policy: 2.23.140.1.2.2
Authority Information Access: CA Issuers - URI:http://crt.sectigo.com/SectigoRSAOrganizationValidationSecureServerCA.crt
OCSP - URI:http://ocsp.sectigo.com
SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
Timestamp : Jun 23 09:22:48.233 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:8A:1F:25:EA:FE:C8:15:88:70:41:57:
56:42:DE:B7:E5:79:15:92:A1:9E:8B:69:59:DB:18:B2:
30:BE:A9:66:DB:02:21:00:B2:E6:0F:67:1C:D6:C8:C5:
5F:FF:28:0C:2F:3C:84:FE:5A:9D:71:94:A4:2B:29:BF:
FB:D5:CD:FE:E6:48:CA:A3
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DA:B6:BF:6B:3F:B5:B6:22:9F:9B:C2:BB:5C:6B:E8:70:
91:71:6C:BB:51:84:85:34:BD:A4:3D:30:48:D7:FB:AB
Timestamp : Jun 23 09:22:48.314 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:03:0C:90:90:A3:63:46:0D:94:B0:BA:0C:
72:26:DB:37:23:2F:7D:36:60:1B:0B:02:96:D0:6F:52:
AD:46:D0:E2:02:21:00:DA:18:0A:A9:C2:CB:4B:71:8D:
A6:CA:3B:53:78:46:98:B8:43:96:D1:CF:D0:E1:19:F3:
D1:60:05:75:88:25:F2
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
Timestamp : Jun 23 09:22:48.360 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:D1:AC:BA:2F:60:28:90:C7:51:AA:4A:
2F:6E:4E:77:F1:4F:C5:FB:9D:4D:B0:16:86:DC:BE:9B:
21:95:2A:A7:A1:02:20:16:48:DA:D5:7A:35:7E:E8:85:
85:7A:0C:74:E7:85:00:AA:DE:40:A4:85:7E:2D:A2:4A:
F7:D2:8C:F5:49:EA:01
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:meetme.com
DNS:*.meetme.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
meetme.com. 204.145.125.82 IN 300

NS Records

Host Nameserver Class TTL
meetme.com. ns-1084.awsdns-07.org. IN 3600
meetme.com. ns-1757.awsdns-27.co.uk. IN 3600
meetme.com. ns-278.awsdns-34.com. IN 3600
meetme.com. ns-982.awsdns-58.net. IN 3600

MX Records

Priority Host Server Class TTL
1 meetme.com. aspmx.l.google.com. IN 21600
10 meetme.com. alt3.aspmx.l.google.com. IN 21600
10 meetme.com. alt4.aspmx.l.google.com. IN 21600
5 meetme.com. alt1.aspmx.l.google.com. IN 21600
5 meetme.com. alt2.aspmx.l.google.com. IN 21600

SOA Records

Domain Name Primary NS Responsible Email TTL
meetme.com. ns-1757.awsdns-27.co.uk. awsdns-hostmaster.amazon.com. 900

TXT Records

Host Value Class TTL
meetme.com. google-site-verification=_Kln2-mS_IecJkIG8lnw6HfMCvEywgFyVdVv6OywRSU IN 30
meetme.com. stripe-verification=f8e3e0c26b8b7b5b1b7023b394c6d84ca3ada1f26916df703439ea9a977f66ef IN 30
meetme.com. v=spf1 IN 30

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 25th March, 2024
Server: Apache
Cache-Control: no-store, no-cache
Content-Type: text/html; charset=UTF-8;
Set-Cookie: *
Pragma: no-cache
Content-Length: 5599
Vary: Host,User-Agent,Origin
Access-Control-Allow-Credentials: true
Access-Control-Allow-Methods: POST, GET, OPTIONS, DELETE
Access-Control-Allow-Headers: x-device,x-supportedfeatures,xsrf

Whois Lookup

Created: 5th September, 1995
Changed: 3rd August, 2023
Expires: 4th September, 2024
Registrar: MarkMonitor, Inc.
Status: clientUpdateProhibited
clientTransferProhibited
clientDeleteProhibited
Nameservers: ns-1084.awsdns-07.org
ns-1757.awsdns-27.co.uk
ns-278.awsdns-34.com
ns-982.awsdns-58.net
Owner Organization: The Meet Group
Owner State: PA
Owner Country: US
Owner Email: Select Request Email Form at https://domains.markmonitor.com/whois/meetme.com
Admin Organization: The Meet Group
Admin State: PA
Admin Country: US
Admin Email: Select Request Email Form at https://domains.markmonitor.com/whois/meetme.com
Tech Organization: The Meet Group
Tech State: PA
Tech Country: US
Tech Email: Select Request Email Form at https://domains.markmonitor.com/whois/meetme.com
Full Whois: Domain Name: meetme.com
Registry Domain ID: 628081_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2023-08-03T09:18:19+0000
Creation Date: 1995-09-05T04:00:00+0000
Registrar Registration Expiration Date: 2024-09-04T00:00:00+0000
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2086851750
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Registrant Organization: The Meet Group
Registrant State/Province: PA
Registrant Country: US
Registrant Email: Select Request Email Form at https://domains.markmonitor.com/whois/meetme.com
Admin Organization: The Meet Group
Admin State/Province: PA
Admin Country: US
Admin Email: Select Request Email Form at https://domains.markmonitor.com/whois/meetme.com
Tech Organization: The Meet Group
Tech State/Province: PA
Tech Country: US
Tech Email: Select Request Email Form at https://domains.markmonitor.com/whois/meetme.com
Name Server: ns-278.awsdns-34.com
Name Server: ns-1757.awsdns-27.co.uk
Name Server: ns-1084.awsdns-07.org
Name Server: ns-982.awsdns-58.net
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-03-25T00:19:33+0000 <<<

For more information on WHOIS status codes, please visit:
https://www.icann.org/resources/pages/epp-status-codes

If you wish to contact this domain’s Registrant, Administrative, or Technical
contact, and such email address is not visible above, you may do so via our web
form, pursuant to ICANN’s Temporary Specification. To verify that you are not a
robot, please enter your email address to receive a link to a page that
facilitates email communication with the relevant contact(s).

Web-based WHOIS:
https://domains.markmonitor.com/whois

If you have a legitimate interest in viewing the non-public WHOIS details, send
your request and the reasons for your request to whoisrequest@markmonitor.com
and specify the domain name in the subject line. We will review that request and
may ask for supporting documentation and explanation.

The data in MarkMonitor’s WHOIS database is provided for information purposes,
and to assist persons in obtaining information about or related to a domain
name’s registration record. While MarkMonitor believes the data to be accurate,
the data is provided "as is" with no guarantee or warranties regarding its
accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
(1) allow, enable, or otherwise support the transmission by email, telephone,
or facsimile of mass, unsolicited, commercial advertising, or spam; or
(2) enable high volume, automated, or electronic processes that send queries,
data, or email to MarkMonitor (or its systems) or the domain name contacts (or
its systems).

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

By submitting this query, you agree to abide by this policy.

MarkMonitor Domain Management(TM)
Protecting companies and consumers in a digital world.

Visit MarkMonitor at https://www.markmonitor.com
Contact us at +1.8007459229
In Europe, at +44.02032062220
View Raw Whois

Nameservers

Name IP Address
ns-1084.awsdns-07.org 205.251.196.60
ns-1757.awsdns-27.co.uk 205.251.198.221
ns-278.awsdns-34.com 205.251.193.22
ns-982.awsdns-58.net 205.251.195.214
Related

Subdomains

Domain Subdomain
m.meetme.com
m
touch.meetme.com
touch

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
meetme.biz
0/5
meetme.info
0/5
meetme.net
$10 USD
meetme.ru
$10 USD

Sites hosted on the same IP address

Love W3 Snoop?
Update Now

meetme.com Infographic

meetme.com by the numbers infographic

Recently Updated

novelpia.com
etersec.com
drive4kb.com
fayettevilleflyer.com
guddan.net
mydaddy.cc
gscpay.com
funhub.com.pk
google.com
hoichoi.tv

Recently Viewed

fancoshop.com
americascupnews.com
sinbolgroup.com
1stopmove.com
boyslatin.org
fame.ws
digitalsupercenter.com
perutou.org
velmicro.com
odisharoots.org