findmedateme.com

findmedateme.com may not be SSL secured

Free website and domain report on findmedateme.com

Last Updated: 16th April, 2024
Overview

Snoop Summary for findmedateme.com

This is a free and comprehensive report about findmedateme.com. Our records indicate that findmedateme.com is privately registered by Privacy Protect, LLC (PrivacyProtect.org). Findmedateme.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If findmedateme.com was to be sold it would possibly be worth $821 USD (based on the daily revenue potential of the website over a 24 month period). Findmedateme.com receives an estimated 390 unique visitors every day - a decent amount of traffic! This report was last updated 16th April, 2024.

About findmedateme.com

Site Preview: findmedateme.com findmedateme.com
Title:
Description:
Keywords and Tags: dating, personals
Related Terms:
Fav Icon:
Age: Over 13 years old
Domain Created: 9th July, 2010
Domain Updated: 13th December, 2023
Domain Expires: 9th July, 2025
Review

Snoop Score

1/5

Valuation

$821 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,030,728
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: 390
Monthly Visitors: 11,870
Yearly Visitors: 142,350
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $34 USD
Yearly Revenue: $406 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: findmedateme.com 16
Domain Name: findmedateme 12
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 68
Performance 94
Accessibility 64
Best Practices 69
SEO 90
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
94

Performance

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

Metrics

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

Audits

Max Potential First Input Delay — 110 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://findmedateme.com/
http/1.1
0
718.94899988547
7684
26048
200
text/html
Document
http://findmedateme.com/px.js?ch=1
http/1.1
734.71699981019
985.06599990651
628
346
200
application/javascript
Script
http://findmedateme.com/px.js?ch=2
http/1.1
734.98499998823
3038.5979996063
628
346
200
application/javascript
Script
http://i4.cdn-image.com/__media__/js/min.js?v2.3
http/1.1
735.46199966222
787.1799999848
3421
8435
200
application/javascript
Script
https://wp.webpushonline.com/script/fsub_ad632cba003c1a14778cdc91344cf33f.js
h2
736.46100005135
830.82899963483
20419
78081
200
application/javascript
Script
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUGR5N0J
http/1.1
3045.3209998086
3081.9319998845
400
0
301
text/html
http://i4.cdn-image.com/__media__/pics/12471/bodybg.png
http/1.1
3057.6889999211
3083.7439997122
97502
97189
200
image/png
Image
http://i4.cdn-image.com/__media__/pics/12471/logo.png
http/1.1
3058.2339996472
3105.877999682
4266
3956
200
image/png
Image
http://i4.cdn-image.com/__media__/pics/12471/kwbg.jpg
http/1.1
3058.7479998358
3085.7689999975
37532
37219
200
image/jpeg
Image
http://i4.cdn-image.com/__media__/pics/12471/libg.png
http/1.1
3059.1249996796
3083.0129999667
1402
1092
200
image/png
Image
http://i4.cdn-image.com/__media__/pics/12471/arrow.png
http/1.1
3059.6859999932
3082.3619998991
1370
1060
200
image/png
Image
http://i4.cdn-image.com/__media__/fonts/ubuntu-r/ubuntu-r.woff
http/1.1
3060.6279997155
3087.3449998908
37430
37152
200
application/font-woff
Font
http://i4.cdn-image.com/__media__/fonts/ubuntu-b/ubuntu-b.woff
http/1.1
3060.9979997389
3084.4609998167
38206
37928
200
application/font-woff
Font
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUGR5N0J
http/1.1
3082.8970000148
3132.176999934
31425
94509
200
text/javascript
Script
https://pxlgnpgecom-a.akamaihd.net/javascripts/bfp_ssn.js?templateId=10
http/1.1
3210.6469999999
3288.9459999278
4129
11922
200
text/html
Document
https://dt.gnpge.com/ptmdP
3345.8859999664
3367.5139998086
0
0
-1
Ping
https://dt.gnpge.com/cenw.js?identifier=bafp
h2
3351.255999878
3444.3969996646
469
36
200
text/html
XHR
https://dt6.gnpge.com/ptmdDual?t=%7B%22gh%22%3A%221639581517005101565409339%22%2C%22za%22%3A1%2C%22gcd%22%3A1639581517143%2C%22al%22%3A10%2C%22bcnd%22%3A1%7D
h2
3353.964000009
3443.9399996772
408
70
200
image/gif
Image
https://dt.gnpge.com/cenw.js
h2
3444.7449999861
3557.1459997445
469
36
200
text/html
XHR
https://dt.gnpge.com/ptmd?t=1639581517005101565409339_N4IgtgniBcDasEYA0AWAHAViWgbFgTAAwCcS+OAzALpKz6qbZ5kDsFSF+LNs76WuLBQosOxBDxQMBzFIWQoMGHln5NVzDAmI8c09Ugz5SGNNVqi1gw8XY4U3WmkMkklUi0LOW5HqRye2PhYnt6+tAiE2Bh6xLhIoQm+NCAA7gCOMLApkABOWSkAdgCGWSjGKMQB5FIIFHJonhQmFIRe6K1FxQDOMMZIIACWxWBZhCnDvdDOIAAeAGYwIACmAMYAJujLCPho66sYLMXFLMTLrSgHq82rq2hoJCADCwAuS-PE18vEKDt1IgAjYQIVbEAHFZbfeZ3HDEYpcJ4gADWpWgIBQOGKcnmxUIAFoMOtwXiEAg1njin88Sh5ixaQDyPUMADEUiWdBkCBVgA3JbAAA6IAANgB7VbFIUAfW6LxFuWKAHNloLoIKMVjCDj8YTiaTyZT8AhqbT6YzFADBUhBd1lt1uoMRYVpbL5UqVWrMdjcQSicUSWTVhSqTS6SwGZRzZbBasRSKkYNlpL1sUXsV3ejPZrvTq-XrAwajSHTRHmYKAL6IhUvRZwKJRZB1lJVqawOtIevtlIylttjvjAZrF6jNGcCiI5azJaERHdGNLBDuUwILQ4SXEXbL2EYYjEDAzmM1zmzkVvNEL5pLldrjcxXc7jCSgGRVbfS7zYxghdhlgoYqwlAoMshAQqCmz7ieh4DMeLzrPOi5oMuC7Xght7brukoLgCDgsNuyw6gCAKfDguxYiwywAqs+AUESpKLFBMYwZBKwoksGJYcurQ+rqAZ4kCODrHi4g4vgvwYBQoJ0cx7KcjyUwgAKwpihKzpyoqyowB67Fidqvr+uSfECUJ8KieJxDzFGIA2naDpOjKqluhpGZaZxOZ6YGBmCQgwkmRJFkxnGCZJimaaOWxJk6dx+kUPxnneRxvkgBWAyDLy0CEAAdFglmpi8ACuLbIP0rRIKQVFINoKQAF6opyAAOCpLLyAwKgAFnBF4oQgniEFo8gxBgci2M0iLcnJODpRlihjgMEowJEAzQjAJIDi8gztbunU4DOLwNWlUFIutl5IeuKFbve46DLVSwBOlRAYOldQsA9CIDNyyz5GitW5CKsEDrlNUDLla17Ss3JCgUAy1aNEOWUKMqHZtu4oIiQpMas+UvJKgywWixAAMIAKoAOIAEoYAAcoQABSI2DFjOMgDsVGNDsLCkig9ToFU+CVqsc3wYhLCwlEIDpMsc0LcD+BlkAA
h2
3911.3119998947
3940.6369999051
408
70
200
image/gif
Image
https://dt.gnpge.com/ptmd?t=1639581517005101565409339_N4IgZghiBcDaDMB2AHPATI+A2ZAGANAIy4AsyArMjvgbTfcZoiYcmifevudsorgE429cuzTJk+NDhLxyJcliJLcAXXzgIAZxhKQAC30xYaAmkL54C9eDAw0GgK6OYigRrAA3GCBAaAlt7QDiBaAC4QYY46cGjkRAI2AF5Q0BYgAA4A5j7eGllG0CCEWPAClITkhPy4VbiVWPKC8GV+IJ4xIFgAdLjdCvBtEAA2MMQeAMYwALTpAKZh-j4lZRVVWG3hOdAEoQDWy6XlyJUlAPoC4g3lAuVtc-4ZPliI3abk3YRInxhtnnMAJx8GQBAHsACb3RypdKOJY7DRzTyjOA2DIdYwgXAAAne5GxhBANi0w3Ch1WJ3W5RIbWGdjSGgm0TCZ38kKKAgAwgBVADiACVyAA5XAAKT+-lZ7OKaDQ8D4hAwhEIshIZAEWDQbSyUzSRzWhAElXiIAAjnMxh54fAAL5AA
h2
5376.3019996695
5401.9479998387
408
70
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
772.859
9.522
3093.639
18.06
3111.717
19.175
3191.305
211.01
3408.134
9.082
3419.816
6.218
3426.047
39.303
3465.369
6.959
3479.809
15.24
3499.834
37.368
3541.007
26.703
3569.224
27.738
3602.081
22.474
3629.07
19.176
3650.473
19.955
3672.685
18.307
3693.612
23.923
3720.679
19.253
3741.283
19.456
3761.987
19.07
3785.667
24.36
3811.095
26.36
3838.923
20.714
3863.68
22.06
3888.104
21.092
3911.194
20.051
3931.26
29.454
3963.394
25.661
3990.994
23.254
4017.573
35.128
4054.087
29.278
4084.431
20.818
4106.364
21.715
4129.083
24.767
4154.722
10.453
5397.01
28.876
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 — Potential savings of 120 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Findmedateme.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://findmedateme.com/px.js?ch=1
628
70
http://findmedateme.com/px.js?ch=2
628
110
http://i4.cdn-image.com/__media__/js/min.js?v2.3
3421
190
Properly size images
Images can slow down the page's load time. Findmedateme.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Findmedateme.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Findmedateme.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Findmedateme.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Findmedateme.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 31 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUGR5N0J
94509
31776
Efficiently encode images — Potential savings of 21 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://i4.cdn-image.com/__media__/pics/12471/kwbg.jpg
37219
21609
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Findmedateme.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Findmedateme.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 282 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://i4.cdn-image.com/__media__/pics/12471/bodybg.png
97502
http://i4.cdn-image.com/__media__/fonts/ubuntu-b/ubuntu-b.woff
38206
http://i4.cdn-image.com/__media__/pics/12471/kwbg.jpg
37532
http://i4.cdn-image.com/__media__/fonts/ubuntu-r/ubuntu-r.woff
37430
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUGR5N0J
31425
https://wp.webpushonline.com/script/fsub_ad632cba003c1a14778cdc91344cf33f.js
20419
http://findmedateme.com/
7684
http://i4.cdn-image.com/__media__/pics/12471/logo.png
4266
https://pxlgnpgecom-a.akamaihd.net/javascripts/bfp_ssn.js?templateId=10
4129
http://i4.cdn-image.com/__media__/js/min.js?v2.3
3421
Avoids an excessive DOM size — 63 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
63
Maximum DOM Depth
7
Maximum Child Elements
13
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Findmedateme.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.4 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)
http://findmedateme.com/
990.128
427.707
2.992
Minimizes main-thread work — 1.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
475.372
Style & Layout
464.316
Other
66.082
Parse HTML & CSS
57.374
Rendering
22.743
Script Parsing & Compilation
10.259
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 21 requests • 282 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
21
288604
Image
8
143296
Font
2
75636
Script
5
56521
Document
2
11813
Other
4
1338
Stylesheet
0
0
Media
0
0
Third-party
18
279664
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)
35954
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
2.7948515891778E-5
2.7948515891778E-5
2.7948515891778E-5
2.7948515891778E-5
2.7948515891778E-5
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUGR5N0J
668
106
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 findmedateme.com on mobile screens.

Budgets

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

Metrics

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

Other

Serve images in next-gen formats — Potential savings of 77 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://i4.cdn-image.com/__media__/pics/12471/bodybg.png
97189
47261.25
http://i4.cdn-image.com/__media__/pics/12471/kwbg.jpg
37219
31840.5

Other

Reduce initial server response time — Root document took 720 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)
http://findmedateme.com/
719.941
Serve static assets with an efficient cache policy — 15 resources found
Findmedateme.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)
http://i4.cdn-image.com/__media__/fonts/ubuntu-b/ubuntu-b.woff
0
38206
http://i4.cdn-image.com/__media__/fonts/ubuntu-r/ubuntu-r.woff
0
37430
http://findmedateme.com/px.js?ch=1
0
628
http://findmedateme.com/px.js?ch=2
0
628
https://dt.gnpge.com/ptmd?t=1639581517005101565409339_N4IgtgniBcDasEYA0AWAHAViWgbFgTAAwCcS+OAzALpKz6qbZ5kDsFSF+LNs76WuLBQosOxBDxQMBzFIWQoMGHln5NVzDAmI8c09Ugz5SGNNVqi1gw8XY4U3WmkMkklUi0LOW5HqRye2PhYnt6+tAiE2Bh6xLhIoQm+NCAA7gCOMLApkABOWSkAdgCGWSjGKMQB5FIIFHJonhQmFIRe6K1FxQDOMMZIIACWxWBZhCnDvdDOIAAeAGYwIACmAMYAJujLCPho66sYLMXFLMTLrSgHq82rq2hoJCADCwAuS-PE18vEKDt1IgAjYQIVbEAHFZbfeZ3HDEYpcJ4gADWpWgIBQOGKcnmxUIAFoMOtwXiEAg1njin88Sh5ixaQDyPUMADEUiWdBkCBVgA3JbAAA6IAANgB7VbFIUAfW6LxFuWKAHNloLoIKMVjCDj8YTiaTyZT8AhqbT6YzFADBUhBd1lt1uoMRYVpbL5UqVWrMdjcQSicUSWTVhSqTS6SwGZRzZbBasRSKkYNlpL1sUXsV3ejPZrvTq-XrAwajSHTRHmYKAL6IhUvRZwKJRZB1lJVqawOtIevtlIylttjvjAZrF6jNGcCiI5azJaERHdGNLBDuUwILQ4SXEXbL2EYYjEDAzmM1zmzkVvNEL5pLldrjcxXc7jCSgGRVbfS7zYxghdhlgoYqwlAoMshAQqCmz7ieh4DMeLzrPOi5oMuC7Xght7brukoLgCDgsNuyw6gCAKfDguxYiwywAqs+AUESpKLFBMYwZBKwoksGJYcurQ+rqAZ4kCODrHi4g4vgvwYBQoJ0cx7KcjyUwgAKwpihKzpyoqyowB67Fidqvr+uSfECUJ8KieJxDzFGIA2naDpOjKqluhpGZaZxOZ6YGBmCQgwkmRJFkxnGCZJimaaOWxJk6dx+kUPxnneRxvkgBWAyDLy0CEAAdFglmpi8ACuLbIP0rRIKQVFINoKQAF6opyAAOCpLLyAwKgAFnBF4oQgniEFo8gxBgci2M0iLcnJODpRlihjgMEowJEAzQjAJIDi8gztbunU4DOLwNWlUFIutl5IeuKFbve46DLVSwBOlRAYOldQsA9CIDNyyz5GitW5CKsEDrlNUDLla17Ss3JCgUAy1aNEOWUKMqHZtu4oIiQpMas+UvJKgywWixAAMIAKoAOIAEoYAAcoQABSI2DFjOMgDsVGNDsLCkig9ToFU+CVqsc3wYhLCwlEIDpMsc0LcD+BlkAA
0
408
https://dt.gnpge.com/ptmd?t=1639581517005101565409339_N4IgZghiBcDaDMB2AHPATI+A2ZAGANAIy4AsyArMjvgbTfcZoiYcmifevudsorgE429cuzTJk+NDhLxyJcliJLcAXXzgIAZxhKQAC30xYaAmkL54C9eDAw0GgK6OYigRrAA3GCBAaAlt7QDiBaAC4QYY46cGjkRAI2AF5Q0BYgAA4A5j7eGllG0CCEWPAClITkhPy4VbiVWPKC8GV+IJ4xIFgAdLjdCvBtEAA2MMQeAMYwALTpAKZh-j4lZRVVWG3hOdAEoQDWy6XlyJUlAPoC4g3lAuVtc-4ZPliI3abk3YRInxhtnnMAJx8GQBAHsACb3RypdKOJY7DRzTyjOA2DIdYwgXAAAne5GxhBANi0w3Ch1WJ3W5RIbWGdjSGgm0TCZ38kKKAgAwgBVADiACVyAA5XAAKT+-lZ7OKaDQ8D4hAwhEIshIZAEWDQbSyUzSRzWhAElXiIAAjnMxh54fAAL5AA
0
408
https://dt6.gnpge.com/ptmdDual?t=%7B%22gh%22%3A%221639581517005101565409339%22%2C%22za%22%3A1%2C%22gcd%22%3A1639581517143%2C%22al%22%3A10%2C%22bcnd%22%3A1%7D
0
408
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUGR5N0J
1800000
31425
https://wp.webpushonline.com/script/fsub_ad632cba003c1a14778cdc91344cf33f.js
14400000
20419
http://i4.cdn-image.com/__media__/pics/12471/kwbg.jpg
25982000
37532
http://i4.cdn-image.com/__media__/pics/12471/arrow.png
25983000
1370
http://i4.cdn-image.com/__media__/pics/12471/logo.png
59003000
4266
http://i4.cdn-image.com/__media__/js/min.js?v2.3
59004000
3421
http://i4.cdn-image.com/__media__/pics/12471/libg.png
68285000
1402
http://i4.cdn-image.com/__media__/pics/12471/bodybg.png
85580000
97502
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
64

Accessibility

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

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 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"]`
Findmedateme.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Best practices

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

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 12 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://findmedateme.com/
Allowed
http://findmedateme.com/px.js?ch=1
Allowed
http://findmedateme.com/px.js?ch=2
Allowed
http://i4.cdn-image.com/__media__/js/min.js?v2.3
Allowed
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUGR5N0J
Allowed
http://i4.cdn-image.com/__media__/pics/12471/bodybg.png
Allowed
http://i4.cdn-image.com/__media__/pics/12471/logo.png
Allowed
http://i4.cdn-image.com/__media__/pics/12471/kwbg.jpg
Allowed
http://i4.cdn-image.com/__media__/pics/12471/libg.png
Allowed
http://i4.cdn-image.com/__media__/pics/12471/arrow.png
Allowed
http://i4.cdn-image.com/__media__/fonts/ubuntu-r/ubuntu-r.woff
Allowed
http://i4.cdn-image.com/__media__/fonts/ubuntu-b/ubuntu-b.woff
Allowed

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Audits

Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
RTP data channels are no longer supported. The "RtpDataChannels" constraint is currently ignored, and may cause an error at a later date.
90

SEO

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

Crawling and Indexing

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

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

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

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

PWA Optimized

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

Installable

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

PWA Optimized

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

Manual Checks

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

Performance

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

Metrics

Time to Interactive — 3.2 s
The time taken for the page to become fully interactive.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 1.8 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://findmedateme.com/
http/1.1
0
734.7679999657
7626
25912
200
text/html
Document
http://findmedateme.com/px.js?ch=1
http/1.1
747.28599982336
1250.5259998143
628
346
200
application/javascript
Script
http://findmedateme.com/px.js?ch=2
http/1.1
747.87699989974
1218.7649998814
628
346
200
application/javascript
Script
http://i3.cdn-image.com/__media__/js/min.js?v2.3
http/1.1
748.15999995917
829.19199997559
3421
8435
200
application/javascript
Script
https://wp.webpushonline.com/script/fsub_ad632cba003c1a14778cdc91344cf33f.js
h2
748.68399975821
819.61699994281
20421
78081
200
application/javascript
Script
http://i3.cdn-image.com/__media__/pics/12471/bodybg.png
http/1.1
1256.021999754
1325.5050000735
97502
97189
200
image/png
Image
http://i3.cdn-image.com/__media__/pics/12471/logo.png
http/1.1
1256.6229999065
1445.5289999023
4266
3956
200
image/png
Image
http://i3.cdn-image.com/__media__/pics/12471/kwbg.jpg
http/1.1
1257.0849996991
1316.0210000351
37532
37219
200
image/jpeg
Image
http://i3.cdn-image.com/__media__/pics/12471/libg.png
http/1.1
1257.3139998131
1273.8049998879
1402
1092
200
image/png
Image
http://i3.cdn-image.com/__media__/pics/12471/arrow.png
http/1.1
1257.545999717
1400.1229996793
1370
1060
200
image/png
Image
http://i3.cdn-image.com/__media__/fonts/ubuntu-r/ubuntu-r.woff
http/1.1
1258.4850001149
1274.1649998352
37430
37152
200
application/font-woff
Font
http://i3.cdn-image.com/__media__/fonts/ubuntu-b/ubuntu-b.woff
http/1.1
1258.6729996838
1286.2390000373
38206
37928
200
application/font-woff
Font
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUGR5N0J
http/1.1
1271.9149999321
1333.5929997265
403
0
301
text/html
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUGR5N0J
http/1.1
1334.0719998814
1546.1339997128
31427
94513
200
text/javascript
Script
https://pxlgnpgecom-a.akamaihd.net/javascripts/bfp_ssn.js?templateId=10
http/1.1
1587.0690001175
1749.0329998545
4129
11922
200
text/html
Document
https://dt.gnpge.com/ptmdP
1655.7219997048
1663.3049999364
0
0
-1
Ping
https://dt.gnpge.com/cenw.js?identifier=bafp
h2
1660.0089999847
1728.8079997525
469
36
200
text/html
XHR
https://dt6.gnpge.com/ptmdDual?t=%7B%22gh%22%3A%221639581531842103922376172%22%2C%22za%22%3A1%2C%22gcd%22%3A1639581531917%2C%22al%22%3A10%2C%22bcnd%22%3A1%7D
h2
1660.7149997726
1716.9880000874
408
70
200
image/gif
Image
https://dt.gnpge.com/cenw.js
h2
1830.3569997661
1907.0069999434
469
36
200
text/html
XHR
https://dt.gnpge.com/ptmd?t=1639581531842103922376172_N4IgtgniBcDasEYA0BmAbKgTAViQgHAJxKYAsCAukrJqhijidvQAz5Wwp1a4NcoB2bB1LcGvQiySlSmDr3qNS2AUmwtCHeotzYyagWg6r0PNYWRpSKDvjGM02OwIQsOxU+KQDGAvx1d7XAFCWnwZCioQAHcARxhYKMgAJwSogDsAQwTZQlJCNB8rPBRSNgEWFGJsFBY2UnxajMyAZxhMYhAAS0ywBLI3JG7WmDsQAA8AMxgQAFMAYwATBtmETHxF+ZVMzJDZ2tIt+ar5+fx8DRAhqYAXGcnCY9m8tYQUQQAjd4R5wg-M2bPSZnNCETKYARXEAAa2y0BApEmaEWjTqAFpsIt-miEAgFmiPthMh8cR9XJNSI5ZpgqlDoR8YMgQPMAG4zYAAHRAABsAPbzTLcgD6LRuvOSmQA5rMudAuYjkaiWBisZkcXj5gSiSSEGSWBSqTTCFykFyWrMWi0urz0iKxRLpbL5UiUbVlZjsbj8YTiaTyZTsNSqiaufNebzoV1ZkLFpkbpknQiXUqVZ6NVrfbr-YbgyAAL5QyU3aZwZBSctIQYgIttOAVst4KKi2uweuVytRBY3Prw2qYKGzcYzFhQlphmYINBVJwIGoIIVoKyYBCUgqhNCjsMlplj3l3eGT6f4WcoeeL2Qr0GgzBoIV6+bPQ6TDp-ScCD4CUiZUEyWYsAG-Msm57tuQy7jciwTlOhAznOC5Lpea43kKk4fKQfjYIQsweh8HyPGg6yZOhswfPMNJYri0xgWGEGgXMsIzIiRCzF+7qquq+KZK8aKIgIkzvjepTYAyQyzPSjJDKytYgJyPL8oKdrilKMowM6zGsamapepqXHLjx-H8R8gnKB8IYgOalrWraopKY6qlJupmRsWmnHcbxhnGcJZlhhGUYxnGCb2UxWEaR6WnprpCD6XxAlTiZXIFkMXRstALAAHS4OZ8Y3AAri2yAdKgUjEDSeCaEMABecJMgADpKMxskMkoABZQUeJ4EBelShDShgID4UIstJaBpelygoFCgqMlIIDAjAOKiTcXRtTBx5zqONz1alYHQitsGnvBF6rteG6iV0NUzIUaWYCw2BpW8Aj3RCg2zKk8I1ckvKQaJOXVUMOXLdtcwstyaRDDVQ1g+Z3Kinta2nvg6xQtydHzHlNxCl0kHwoQADCACqADiABK2AAHIsAAUoNXSY9jIBrDS+AuBCbxsDUmFI018yMtB+1kDeQyxLMEmzYDmB5kAA
h2
2186.3019997254
2244.2679996602
408
70
200
image/gif
Image
https://dt.gnpge.com/ptmd?t=1639581531842103922376172_N4IgZghiBcDaDMB2AHPATI+A2ZAGANAIy4AsyArMjvgbTfcZoiYcmifevudsorgE429cuzTJk+NDhLxyJcliJLcAXXzgIAZxhKQAC30xYhKeXXgwMAiACutmCVw2wANxggQGgJbvoaDS0AFwgg2x04NHIiAQsALyhoUxAABwBzD3cNNKNoEEIseAFKQh5WEjRiIrQ0JCxCRDQvEFcIkCwAOlwOhXhmiAAbGGINMABjGABaZIBTIO8PAqKSsubgjOgbLQBrRcLi5FL4QgB9LCwKwhIsARvpZpnvFI8sRA60XHIOwiRvjGbXDMAE4eFJAgD2ABMHrZEslbAtNhoZq4hnALClWsYQLgAAQfVi4wggCxaAbBPbLQ5lNjIZoDKxJDRjcJBE7eaF5AQAYQAqgBxABK5AAcrgAFIA7zszn5GrwPiEDA-XAUOQCcTNNITJL7Fbwap6ACOM2Go0R8AAvkA
h2
3681.4939999022
3699.6979997493
408
70
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
779.251
7.734
1296.452
14.989
1311.571
12.121
1596.885
105.502
1711.706
26.596
1761.305
17.51
1781.942
17.435
1800.44
6.379
1808.745
17.545
1827.764
15.132
1846.147
13.75
1862.338
10.16
1872.526
15.261
1889.408
14.422
1905.634
15.157
1921.668
14.986
1941.317
14.48
1961.289
19.082
1981.686
17.677
2002.921
21.267
2025.121
17.121
2046.597
16.184
2063.513
17.432
2081.976
13.956
2101.611
24.334
2127.032
13.69
2141.474
15.169
2161.693
14.721
2181.276
13.939
2198.629
28.826
2227.486
18.445
2246.954
20.215
2268.507
6.524
3698.546
24.273
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Findmedateme.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Findmedateme.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Findmedateme.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Findmedateme.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Findmedateme.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 31 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUGR5N0J
94513
31776
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Findmedateme.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Findmedateme.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 282 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://i3.cdn-image.com/__media__/pics/12471/bodybg.png
97502
http://i3.cdn-image.com/__media__/fonts/ubuntu-b/ubuntu-b.woff
38206
http://i3.cdn-image.com/__media__/pics/12471/kwbg.jpg
37532
http://i3.cdn-image.com/__media__/fonts/ubuntu-r/ubuntu-r.woff
37430
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUGR5N0J
31427
https://wp.webpushonline.com/script/fsub_ad632cba003c1a14778cdc91344cf33f.js
20421
http://findmedateme.com/
7626
http://i3.cdn-image.com/__media__/pics/12471/logo.png
4266
https://pxlgnpgecom-a.akamaihd.net/javascripts/bfp_ssn.js?templateId=10
4129
http://i3.cdn-image.com/__media__/js/min.js?v2.3
3421
Avoids an excessive DOM size — 63 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
63
Maximum DOM Depth
7
Maximum Child Elements
15
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Findmedateme.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 1.2 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)
http://findmedateme.com/
2667.372
1065.596
10.976
https://pxlgnpgecom-a.akamaihd.net/javascripts/bfp_ssn.js?templateId=10
130.544
87.696
10.392
Unattributable
123.012
14.324
0.892
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 21 requests • 282 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
21
288553
Image
8
143296
Font
2
75636
Script
5
56525
Document
2
11755
Other
4
1341
Stylesheet
0
0
Media
0
0
Third-party
18
279671
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)
35959
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 4 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)
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUGR5N0J
2238
211
http://findmedateme.com/
3289
115
http://findmedateme.com/
2449
106
http://findmedateme.com/
3481
97
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 findmedateme.com on mobile screens.

Budgets

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

Metrics

First Contentful Paint — 1.8 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 3.5 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 250 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 3.2 s
The timing of the largest text or image that is painted.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 330 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Findmedateme.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://findmedateme.com/px.js?ch=1
628
180
http://findmedateme.com/px.js?ch=2
628
330
http://i3.cdn-image.com/__media__/js/min.js?v2.3
3421
630
Efficiently encode images — Potential savings of 21 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://i3.cdn-image.com/__media__/pics/12471/kwbg.jpg
37219
21609
Serve images in next-gen formats — Potential savings of 77 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://i3.cdn-image.com/__media__/pics/12471/bodybg.png
97189
47261.25
http://i3.cdn-image.com/__media__/pics/12471/kwbg.jpg
37219
31840.5
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)
Style & Layout
1325.32
Script Evaluation
1200.276
Other
215.548
Parse HTML & CSS
147.64
Rendering
64.808
Script Parsing & Compilation
35.616
First Contentful Paint (3G) — 3549 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Other

Reduce initial server response time — Root document took 740 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)
http://findmedateme.com/
735.761
Serve static assets with an efficient cache policy — 15 resources found
Findmedateme.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)
http://i3.cdn-image.com/__media__/fonts/ubuntu-b/ubuntu-b.woff
0
38206
http://i3.cdn-image.com/__media__/fonts/ubuntu-r/ubuntu-r.woff
0
37430
http://findmedateme.com/px.js?ch=1
0
628
http://findmedateme.com/px.js?ch=2
0
628
https://dt.gnpge.com/ptmd?t=1639581531842103922376172_N4IgtgniBcDasEYA0BmAbKgTAViQgHAJxKYAsCAukrJqhijidvQAz5Wwp1a4NcoB2bB1LcGvQiySlSmDr3qNS2AUmwtCHeotzYyagWg6r0PNYWRpSKDvjGM02OwIQsOxU+KQDGAvx1d7XAFCWnwZCioQAHcARxhYKMgAJwSogDsAQwTZQlJCNB8rPBRSNgEWFGJsFBY2UnxajMyAZxhMYhAAS0ywBLI3JG7WmDsQAA8AMxgQAFMAYwATBtmETHxF+ZVMzJDZ2tIt+ar5+fx8DRAhqYAXGcnCY9m8tYQUQQAjd4R5wg-M2bPSZnNCETKYARXEAAa2y0BApEmaEWjTqAFpsIt-miEAgFmiPthMh8cR9XJNSI5ZpgqlDoR8YMgQPMAG4zYAAHRAABsAPbzTLcgD6LRuvOSmQA5rMudAuYjkaiWBisZkcXj5gSiSSEGSWBSqTTCFykFyWrMWi0urz0iKxRLpbL5UiUbVlZjsbj8YTiaTyZTsNSqiaufNebzoV1ZkLFpkbpknQiXUqVZ6NVrfbr-YbgyAAL5QyU3aZwZBSctIQYgIttOAVst4KKi2uweuVytRBY3Prw2qYKGzcYzFhQlphmYINBVJwIGoIIVoKyYBCUgqhNCjsMlplj3l3eGT6f4WcoeeL2Qr0GgzBoIV6+bPQ6TDp-ScCD4CUiZUEyWYsAG-Msm57tuQy7jciwTlOhAznOC5Lpea43kKk4fKQfjYIQsweh8HyPGg6yZOhswfPMNJYri0xgWGEGgXMsIzIiRCzF+7qquq+KZK8aKIgIkzvjepTYAyQyzPSjJDKytYgJyPL8oKdrilKMowM6zGsamapepqXHLjx-H8R8gnKB8IYgOalrWraopKY6qlJupmRsWmnHcbxhnGcJZlhhGUYxnGCb2UxWEaR6WnprpCD6XxAlTiZXIFkMXRstALAAHS4OZ8Y3AAri2yAdKgUjEDSeCaEMABecJMgADpKMxskMkoABZQUeJ4EBelShDShgID4UIstJaBpelygoFCgqMlIIDAjAOKiTcXRtTBx5zqONz1alYHQitsGnvBF6rteG6iV0NUzIUaWYCw2BpW8Aj3RCg2zKk8I1ckvKQaJOXVUMOXLdtcwstyaRDDVQ1g+Z3Kinta2nvg6xQtydHzHlNxCl0kHwoQADCACqADiABK2AAHIsAAUoNXSY9jIBrDS+AuBCbxsDUmFI018yMtB+1kDeQyxLMEmzYDmB5kAA
0
408
https://dt.gnpge.com/ptmd?t=1639581531842103922376172_N4IgZghiBcDaDMB2AHPATI+A2ZAGANAIy4AsyArMjvgbTfcZoiYcmifevudsorgE429cuzTJk+NDhLxyJcliJLcAXXzgIAZxhKQAC30xYhKeXXgwMAiACutmCVw2wANxggQGgJbvoaDS0AFwgg2x04NHIiAQsALyhoUxAABwBzD3cNNKNoEEIseAFKQh5WEjRiIrQ0JCxCRDQvEFcIkCwAOlwOhXhmiAAbGGINMABjGABaZIBTIO8PAqKSsubgjOgbLQBrRcLi5FL4QgB9LCwKwhIsARvpZpnvFI8sRA60XHIOwiRvjGbXDMAE4eFJAgD2ABMHrZEslbAtNhoZq4hnALClWsYQLgAAQfVi4wggCxaAbBPbLQ5lNjIZoDKxJDRjcJBE7eaF5AQAYQAqgBxABK5AAcrgAFIA7zszn5GrwPiEDA-XAUOQCcTNNITJL7Fbwap6ACOM2Go0R8AAvkA
0
408
https://dt6.gnpge.com/ptmdDual?t=%7B%22gh%22%3A%221639581531842103922376172%22%2C%22za%22%3A1%2C%22gcd%22%3A1639581531917%2C%22al%22%3A10%2C%22bcnd%22%3A1%7D
0
408
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUGR5N0J
1800000
31427
https://wp.webpushonline.com/script/fsub_ad632cba003c1a14778cdc91344cf33f.js
14400000
20421
http://i3.cdn-image.com/__media__/pics/12471/arrow.png
15376000
1370
http://i3.cdn-image.com/__media__/pics/12471/bodybg.png
23958000
97502
http://i3.cdn-image.com/__media__/pics/12471/logo.png
34869000
4266
http://i3.cdn-image.com/__media__/pics/12471/kwbg.jpg
42059000
37532
http://i3.cdn-image.com/__media__/pics/12471/libg.png
60280000
1402
http://i3.cdn-image.com/__media__/js/min.js?v2.3
85945000
3421
70

Accessibility

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

Contrast

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

Tables and lists

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

Internationalization and localization

`<html>` element has a 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"]`
Findmedateme.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Best practices

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

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 12 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://findmedateme.com/
Allowed
http://findmedateme.com/px.js?ch=1
Allowed
http://findmedateme.com/px.js?ch=2
Allowed
http://i3.cdn-image.com/__media__/js/min.js?v2.3
Allowed
http://i3.cdn-image.com/__media__/pics/12471/bodybg.png
Allowed
http://i3.cdn-image.com/__media__/pics/12471/logo.png
Allowed
http://i3.cdn-image.com/__media__/pics/12471/kwbg.jpg
Allowed
http://i3.cdn-image.com/__media__/pics/12471/libg.png
Allowed
http://i3.cdn-image.com/__media__/pics/12471/arrow.png
Allowed
http://i3.cdn-image.com/__media__/fonts/ubuntu-r/ubuntu-r.woff
Allowed
http://i3.cdn-image.com/__media__/fonts/ubuntu-b/ubuntu-b.woff
Allowed
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUGR5N0J
Allowed

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Audits

Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
RTP data channels are no longer supported. The "RtpDataChannels" constraint is currently ignored, and may cause an error at a later date.
92

SEO

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

Content Best Practices

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

Crawling and Indexing

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

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Manual Checks

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

PWA

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

PWA Optimized

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

Installable

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

PWA Optimized

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

Manual Checks

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

Server Location

Server IP Address: 64.190.63.222
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Confluence Networks Inc
Registration

Domain Registrant

Private Registration: Yes
Name: Domain Admin
Organization: Privacy Protect, LLC (PrivacyProtect.org)
Country: US
City: Burlington
State: MA
Post Code: 01803
Email: contact@privacyprotect.org
Phone: +1.8022274003
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
PDR Ltd. d/b/a PublicDomainRegistry.com 104.16.181.120
Security

Visitor Safety

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

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
findmedateme.com. 64.190.63.222 IN 300

NS Records

Host Nameserver Class TTL
findmedateme.com. ns1.sedoparking.com. IN 21600
findmedateme.com. ns2.sedoparking.com. IN 21600

MX Records

Priority Host Server Class TTL
0 findmedateme.com. localhost. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
findmedateme.com. ns1.sedoparking.com. hostmaster.sedo.de. 21600

TXT Records

Host Value Class TTL
findmedateme.com. v=spf1 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 405 Not Allowed
date: 16th April, 2024
content-type: text/html
server: NginX
content-length: 556

Whois Lookup

Created: 9th July, 2010
Changed: 13th December, 2023
Expires: 9th July, 2025
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com
Status: clientTransferProhibited
Nameservers: ns1.sedoparking.com
ns2.sedoparking.com
Owner Name: Domain Admin
Owner Organization: Privacy Protect, LLC (PrivacyProtect.org)
Owner Street: 10 Corporate Drive
Owner Post Code: 01803
Owner City: Burlington
Owner State: MA
Owner Country: US
Owner Phone: +1.8022274003
Owner Email: contact@privacyprotect.org
Admin Name: Domain Admin
Admin Organization: Privacy Protect, LLC (PrivacyProtect.org)
Admin Street: 10 Corporate Drive
Admin Post Code: 01803
Admin City: Burlington
Admin State: MA
Admin Country: US
Admin Phone: +1.8022274003
Admin Email: contact@privacyprotect.org
Tech Name: Domain Admin
Tech Organization: Privacy Protect, LLC (PrivacyProtect.org)
Tech Street: 10 Corporate Drive
Tech Post Code: 01803
Tech City: Burlington
Tech State: MA
Tech Country: US
Tech Phone: +1.8022274003
Tech Email: contact@privacyprotect.org
Full Whois: Domain Name: FINDMEDATEME.COM
Registry Domain ID: 1605774402_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.publicdomainregistry.com
Registrar URL: www.publicdomainregistry.com
Updated Date: 2023-12-13T11:37:56Z
Creation Date: 2010-07-09T19:00:17Z
Registrar Registration Expiration Date: 2025-07-09T19:00:17Z
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID: 303
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Domain Admin
Registrant Organization: Privacy Protect, LLC (PrivacyProtect.org)
Registrant Street: 10 Corporate Drive
Registrant City: Burlington
Registrant State/Province: MA
Registrant Postal Code: 01803
Registrant Country: US
Registrant Phone: +1.8022274003
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: contact@privacyprotect.org
Registry Admin ID: Not Available From Registry
Admin Name: Domain Admin
Admin Organization: Privacy Protect, LLC (PrivacyProtect.org)
Admin Street: 10 Corporate Drive
Admin City: Burlington
Admin State/Province: MA
Admin Postal Code: 01803
Admin Country: US
Admin Phone: +1.8022274003
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: contact@privacyprotect.org
Registry Tech ID: Not Available From Registry
Tech Name: Domain Admin
Tech Organization: Privacy Protect, LLC (PrivacyProtect.org)
Tech Street: 10 Corporate Drive
Tech City: Burlington
Tech State/Province: MA
Tech Postal Code: 01803
Tech Country: US
Tech Phone: +1.8022274003
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: contact@privacyprotect.org
Name Server: ns1.sedoparking.com
Name Server: ns2.sedoparking.com
DNSSEC: Unsigned
Registrar Abuse Contact Email: abuse-contact@publicdomainregistry.com
Registrar Abuse Contact Phone: +1.2013775952
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-04-16T06:25:47Z <<<

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

Registration Service Provided By: WQRM HOLDINGS INC

PRIVACYPROTECT.ORG is providing privacy protection services to this domain name to
protect the owner from spam and phishing attacks. PrivacyProtect.org is not
responsible for any of the activities associated with this domain name. If you wish
to report any abuse concerning the usage of this domain name, you may do so at
http://privacyprotect.org/contact. We have a stringent abuse policy and any
complaint will be actioned within a short period of time.

The data in this whois database is provided to you for information purposes
only, that is, to assist you in obtaining information about or related to a
domain name registration record. We make this information available "as is",
and do not guarantee its accuracy. By submitting a whois query, you agree
that you will use this data only for lawful purposes and that, under no
circumstances will you use this data to:
(1) enable high volume, automated, electronic processes that stress or load
this whois database system providing you this information; or
(2) allow, enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic mail, or
by telephone.
The compilation, repackaging, dissemination or other use of this data is
expressly prohibited without prior written consent from us. The Registrar of
record is PDR Ltd. d/b/a PublicDomainRegistry.com.
We reserve the right to modify these terms at any time.
By submitting this query, you agree to abide by these terms.


Nameservers

Name IP Address
ns1.sedoparking.com 3.130.216.63
ns2.sedoparking.com 34.211.188.210
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
0/5
0/5
0/5
$875 USD 1/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
$945 USD 1/5
$10 USD 1/5
$640 USD 1/5
0/5