dating.com
Free website and domain report on dating.com
Last Updated: 9th November, 2024
Overview
Snoop Summary for dating.com
This is a free and comprehensive report about dating.com. Our records indicate that dating.com is privately registered by Privacy protection service - whoisproxy.ru. Dating.com is expected to earn an estimated $113 USD per day from advertising revenue. The sale of dating.com would possibly be worth $82,188 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Dating.com receives an estimated 26,620 unique visitors every day - a massive amount of traffic! This report was last updated 9th November, 2024.
About dating.com
| Site Preview: |   |
| Title: | Dating.com™ Official Site – Dating, Love & Match Online |
| Description: | Dating.com is the Finest Dating Website With Over 10 Million Great Members. Connect With Singles And Start Your Online Dating Adventure! Enjoy Dating with Thrilling Online Chats And More |
| Keywords and Tags: | brazilian men, date com member search, dating, dating app, dating com, dating com free credits, dating girls, dating site, dating website, dating.com, italian guys, italian men, online chat, online dating, paid dating, personals, popular, rich men dating sites, swedish guys, swedish men, sweedish men, www dating com, www dating com app |
| Related Terms: | dating big personals, dating web site, hiv dating classifieds, internet dating services, online hiv dating, overweight dating, site dating |
| Fav Icon: | |
| Age: | Over 26 years old |
| Domain Created: | 23rd February, 1998 |
| Domain Updated: | 9th April, 2018 |
| Domain Expires: | 21st February, 2025 |
Review
Snoop Score
3/5 (Great!)
Valuation
$82,188 USD
Note: All valuation figures are estimates.
Popularity
High
Note: Popularity is estimated.
Rank, Reach and Authority
| Alexa Rank: | 29,453 |
| Alexa Reach: | |
| SEMrush Rank (US): | 89,686 |
| SEMrush Authority Score: | 48 |
| Moz Domain Authority: | 0 |
| Moz Page Authority: | 0 |
Organic vs Paid (Google Ads)
| Organic | Paid | |
|---|---|---|
| Keywords: | 4,779 | 155 |
| Traffic: | 20,723 | 2,615 |
| Cost: | $131,788 USD | $37,304 USD |
Traffic
Visitors
| Daily Visitors: | 26,620 |
| Monthly Visitors: | 810,229 |
| Yearly Visitors: | 9,716,300 |
Note: All visitors figures are estimates.
Visitors By Country
Revenue
Revenue
| Daily Revenue: | $113 USD |
| Monthly Revenue: | $3,426 USD |
| Yearly Revenue: | $41,089 USD |
Note: All revenue figures are estimates.
Revenue By Country
SEO
Backlinks Analysis (SEMrush)
| Backlinks: | 24,591 |
| Referring Domains: | 1,805 |
| Referring IPs: | 1,787 |
Dating.com has 24,591 backlinks according to SEMrush. 77% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve dating.com's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of dating.com's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.
Top New Follow Links
1
Source: https://www.elitedaily.com/p/if-you-didnt-feel-physical-attraction-on-a-first-date-should-you-go-on-a-second-22586894
Target: https://www.dating.com/
2
Source: https://www.sitejabber.com/categories/dating?page=6&sort=rating
Target: http://dating.com/
3
Source: https://www.sitejabber.com/categories/dating?page=6
Target: http://dating.com/
4
Source: http://www.techadre.com/aggregator/2009/03/2009/04/16/www.crunchbase.com/person/decarloj@gtlaw.com?page=148
Target: http://dating.com/
5
Source: http://www.techadre.com/aggregator/sources/5/pepperdecks.com?page=147
Target: http://dating.com/
Top Ranking Keywords (US)
1
Keyword: dating com
Ranked Page: https://www.dating.com/
2
Keyword: swedish men
Ranked Page: https://www.dating.com/best-advice-on-dating-swedish-men/
3
Keyword: dating
Ranked Page: https://www.dating.com/
4
Keyword: swedish guys
Ranked Page: https://www.dating.com/best-advice-on-dating-swedish-men/
5
Keyword: www dating com
Ranked Page: https://www.dating.com/
Domain Analysis
| Value | Length | |
|---|---|---|
| Domain: | dating.com | 10 |
| Domain Name: | dating | 6 |
| Extension (TLD): | com | 3 |
| Expiry Check: | |
Page Speed Analysis
| Average Load Time: | 2.26 seconds |
| Load Time Comparison: | Faster than 37% of sites |
PageSpeed Insights
Avg. (All Categories)
Performance
Accessibility
Best Practices
SEO
Progressive Web App
0–49 (Fail) 50–89 (Average) 90–100 (Pass) 
URL: https://www.dating.com/
Updated: 12th February, 2021
1.54 seconds
First Contentful Paint (FCP)
0.04 seconds
First Input Delay (FID) Simulate loading on desktop
Performance
Indicates how well the page is performing and highlights opportunities where performance may be improved for dating.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.
Speed Index — 0.6 s The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 0.7 s The timing of the largest text or image that is painted.
Time to Interactive — 0.6 s The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.007 Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data
Other
First CPU Idle — 0.6 s The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 40 ms Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.6 s The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive dating.com as laggy when the latency is higher than 0.05 seconds.
Network Requests Below is a list of network requests that were made during page load.
| URL | Start Time (Ms) | End Time (Ms) | Transfer Size (Bytes) | Resource Size (Bytes) | Status Code | MIME Type | Resource Type |
|---|---|---|---|---|---|---|---|
| http://dating.com/ | 0 | 46.811000007438 | 284 | 0 | 301 | ||
| https://dating.com/ | 47.256999998353 | 122.49600001087 | 314 | 0 | 301 | ||
| https://www.dating.com/ | 122.87900000229 | 222.53400000045 | 18843 | 89548 | 200 | text/html | Document |
| https://www.dating.com/terra-assets/images/intro/1920x600-72259d22f9-3.jpg | 231.83099999733 | 327.75399999809 | 27321 | 26663 | 200 | image/jpeg | Image |
| 249.22700000752 | 249.26300000516 | 0 | 298 | 200 | image/svg+xml | Image | |
| 275.76699999918 | 275.79700000933 | 0 | 164 | 200 | image/svg+xml | Image | |
| https://www.dating.com/terra-assets/images/people/Ralph-79f74dd901-3.jpg | 276.92899999965 | 352.49699999986 | 5342 | 4690 | 200 | image/jpeg | Image |
| https://www.dating.com/terra-assets/images/people/Giselle-24842720dc-3.jpg | 277.15300000273 | 357.52499999944 | 6400 | 5748 | 200 | image/jpeg | Image |
| https://www.dating.com/terra-assets/images/people/Mellisa-b07e2b738f-3.jpg | 277.39800000563 | 371.91700001131 | 5692 | 5040 | 200 | image/jpeg | Image |
| https://www.dating.com/terra-assets/images/people/Ben-5a980f05de-3.jpg | 277.76100000483 | 389.05300000624 | 5797 | 5145 | 200 | image/jpeg | Image |
| https://www.dating.com/terra-assets/images/people/Julian-4b89e35e6f-3.jpg | 278.11199999996 | 374.14900001022 | 9039 | 8387 | 200 | image/jpeg | Image |
| https://www.dating.com/terra-assets/images/people/Ivonne-2027a81dd5-3.jpg | 278.33600000304 | 367.8990000044 | 5795 | 5143 | 200 | image/jpeg | Image |
| https://www.dating.com/terra-assets/styles/defer-a05931cd8c-3.css | 391.13299999735 | 520.85000000079 | 4362 | 10944 | 200 | text/css | XHR |
| https://data.clickocean.io/px/bac89543cab84ebd99fed75791d44cbf.js | 391.62799999758 | 531.23900000355 | 4136 | 7947 | 200 | application/javascript | Script |
| https://www.datadoghq-browser-agent.com/datadog-rum.js | 391.8890000059 | 411.67300000961 | 20437 | 59111 | 200 | application/javascript | Script |
| https://www.dating.com/terra-assets/bundle-0406739b9f-3.js | 392.33600000443 | 449.69100000162 | 43332 | 181455 | 200 | application/javascript | Script |
| https://storage.communicationservicesplatform.com/app/xdls/d3d3LmRhdGluZy5jb20= | 489.87699999998 | 646.35300000373 | 4214 | 10909 | 200 | text/html | Document |
| https://connect.facebook.net/en_US/sdk.js | 492.9140000022 | 506.22400001157 | 2901 | 3224 | 200 | application/x-javascript | Script |
| https://connect.facebook.net/en_US/sdk.js?hash=748b4ec44a4e24d51252ff6834560e41&ua=modern_es6 | 509.42300001043 | 534.94700000738 | 62087 | 203060 | 200 | application/x-javascript | Script |
| 525.94800000952 | 525.99000000919 | 0 | 787 | 200 | image/svg+xml | Image | |
| 527.32200000901 | 527.35899999971 | 0 | 1227 | 200 | image/svg+xml | Image | |
| 528.74700000393 | 528.80100000766 | 0 | 2964 | 200 | image/svg+xml | Image | |
| https://www.dating.com/terra-assets/images/comments/1-608b2a0191-3.jpg | 529.68099999998 | 625.73900001007 | 4027 | 3374 | 200 | image/jpeg | Image |
| https://www.dating.com/terra-assets/images/comments/2-6a5abf8e8a-3.jpg | 529.94000000763 | 588.60899999854 | 4182 | 3529 | 200 | image/jpeg | Image |
| https://www.dating.com/terra-assets/images/comments/3-56fa70dff0-3.jpg | 530.23800000665 | 586.45100001013 | 3933 | 3280 | 200 | image/jpeg | Image |
| https://www.dating.com/terra-assets/images/about/1920x540-0682dfd0bb-3.jpg | 530.42200001073 | 576.47400000133 | 11548 | 10890 | 200 | image/jpeg | Image |
| https://data.clickocean.io/actions/views | 540.43100000126 | 584.38300000853 | 926 | 0 | 204 | Other | |
| https://data.clickocean.io/actions/views | 584.7960000101 | 687.42600000405 | 1114 | 0 | 204 | text/plain | XHR |
Network Round Trip Times — 0 ms High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks Below is a list of the top-level main thread tasks that executed during page load.
| Start Time (Ms) | End Time (Ms) |
|---|---|
| 251.932 | 8.787 |
| 263.868 | 8.536 |
| 272.417 | 24.417 |
| 299.801 | 23.237 |
| 323.055 | 10.59 |
| 442.387 | 16.723 |
| 484.314 | 35.269 |
| 550.644 | 9.894 |
| 578.87 | 16.582 |
| 675.665 | 8.203 |
Opportunities
Eliminate render-blocking resources Resources, such as JavaScript and style sheets, can block the first paint of the page. Dating.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. Dating.com should consider serving more appropriate-sized images.
Defer offscreen images Time to Interactive can be slowed down by resources on the page. Dating.com should consider lazy-loading offscreen and hidden images.
Minify CSS Cascading Style Sheets (CSS) files can contribute to network payload sizes. Dating.com should consider minifying CSS files.
Minify JavaScript JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Dating.com should consider minifying JS files.
Remove unused CSS Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Dating.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript — Potential savings of 44 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://connect.facebook.net/en_US/sdk.js?hash=748b4ec44a4e24d51252ff6834560e41&ua=modern_es6 | 62087 | 45015 |
Efficiently encode images Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
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 100 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.dating.com/ | 100.652 |
Preload key requests Key requests can be preloaded by using '<link rel=preload>'. Dating.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 11 KiB Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
| URL | Potential Savings (Bytes) |
|---|---|
| https://www.dating.com/terra-assets/bundle-0406739b9f-3.js | 10876 |
Diagnostics
Avoids enormous network payloads — Total size was 246 KiB Large network payloads can cost users money and are linked to long load times.
| URL | Transfer Size (Bytes) |
|---|---|
| https://connect.facebook.net/en_US/sdk.js?hash=748b4ec44a4e24d51252ff6834560e41&ua=modern_es6 | 62087 |
| https://www.dating.com/terra-assets/bundle-0406739b9f-3.js | 43332 |
| https://www.dating.com/terra-assets/images/intro/1920x600-72259d22f9-3.jpg | 27321 |
| https://www.datadoghq-browser-agent.com/datadog-rum.js | 20437 |
| https://www.dating.com/ | 18843 |
| https://www.dating.com/terra-assets/images/about/1920x540-0682dfd0bb-3.jpg | 11548 |
| https://www.dating.com/terra-assets/images/people/Julian-4b89e35e6f-3.jpg | 9039 |
| https://www.dating.com/terra-assets/images/people/Giselle-24842720dc-3.jpg | 6400 |
| https://www.dating.com/terra-assets/images/people/Ben-5a980f05de-3.jpg | 5797 |
| https://www.dating.com/terra-assets/images/people/Ivonne-2027a81dd5-3.jpg | 5795 |
Avoids an excessive DOM size — 384 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 | 384 | |
| Maximum DOM Depth | 23 | |
| Maximum Child Elements | 14 |
Avoid chaining critical requests — 1 chain found Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Dating.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
| URL | Total CPU Time (Ms) | Script Evaluation (Ms) | Script Parse (Ms) |
|---|---|---|---|
| https://www.dating.com/ | 101.553 | 16.407 | 2.273 |
Minimizes main-thread work — 0.2 s Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
| Category | Time Spent (Ms) |
|---|---|
| Script Evaluation | 87.479 |
| Style & Layout | 48.205 |
| Other | 46.713 |
| Rendering | 15.949 |
| Script Parsing & Compilation | 14.795 |
| Parse HTML & CSS | 8.958 |
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 — 23 requests • 246 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 | 23 | 252026 |
| Script | 5 | 132893 |
| Image | 11 | 89076 |
| Document | 2 | 23057 |
| Other | 5 | 7000 |
| Stylesheet | 0 | 0 |
| Media | 0 | 0 |
| Font | 0 | 0 |
| Third-party | 7 | 95815 |
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) |
|---|---|---|
| 64988 | 0 |
Largest Contentful Paint element — 1 element found The element which was identified as the Largest Contentful Paint.
| Element |
|---|
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 |
|---|---|
| 0.0067440946851763 | |
| 0.00011568992212603 |
Uses passive listeners to improve scrolling performance Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
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.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.
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.
Opportunities
Avoid multiple page redirects — Potential savings of 340 ms Redirects can cause additional delays before the page can begin loading. Dating.com should avoid multiple or unnecessary page redirects.
| URL | Time Spent (Ms) |
|---|---|
| http://dating.com/ | 190 |
| https://dating.com/ | 150 |
| https://www.dating.com/ | 0 |
Diagnostics
Serve static assets with an efficient cache policy — 14 resources found Dating.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://www.datadoghq-browser-agent.com/datadog-rum.js | 900000 | 20437 |
| https://connect.facebook.net/en_US/sdk.js | 1200000 | 2901 |
| https://www.dating.com/terra-assets/bundle-0406739b9f-3.js | 2592000000 | 43332 |
| https://www.dating.com/terra-assets/images/intro/1920x600-72259d22f9-3.jpg | 2592000000 | 27321 |
| https://www.dating.com/terra-assets/images/about/1920x540-0682dfd0bb-3.jpg | 2592000000 | 11548 |
| https://www.dating.com/terra-assets/images/people/Julian-4b89e35e6f-3.jpg | 2592000000 | 9039 |
| https://www.dating.com/terra-assets/images/people/Giselle-24842720dc-3.jpg | 2592000000 | 6400 |
| https://www.dating.com/terra-assets/images/people/Ben-5a980f05de-3.jpg | 2592000000 | 5797 |
| https://www.dating.com/terra-assets/images/people/Ivonne-2027a81dd5-3.jpg | 2592000000 | 5795 |
| https://www.dating.com/terra-assets/images/people/Mellisa-b07e2b738f-3.jpg | 2592000000 | 5692 |
| https://www.dating.com/terra-assets/images/people/Ralph-79f74dd901-3.jpg | 2592000000 | 5342 |
| https://www.dating.com/terra-assets/images/comments/2-6a5abf8e8a-3.jpg | 2592000000 | 4182 |
| https://www.dating.com/terra-assets/images/comments/1-608b2a0191-3.jpg | 2592000000 | 4027 |
| https://www.dating.com/terra-assets/images/comments/3-56fa70dff0-3.jpg | 2592000000 | 3933 |
Diagnostics
Avoid `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.
| URL | Location |
|---|---|
| https://www.dating.com/ | line: 0 |
Accessibility
Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of dating.com. This includes details about various page attributes that can be optimized.Navigation
`[accesskey]` values are unique Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
ARIA
`[aria-*]` attributes match their roles Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[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.
`[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-*]` 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.
| Failing Elements |
|---|
`<frame>` or `<iframe>` elements have a title Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute. It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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"]` Dating.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]` Dating.com may provide relevant information that dialogue cannot, by using audio descriptions.
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 |
|---|
Navigation
Heading elements are not in a sequentially-descending order Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
| Failing Elements |
|---|
Names and labels
Form elements do not have associated labels Screen readers and other assistive technologies rely on labels to properly announce form controls.
| Failing Elements |
|---|
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.
Best Practices
Indicates the recommended, best practices currently in place on the page and highlights the best practices that dating.com should incorporate. This includes practices such as protecting pages with HTTPS.Audits
Links to cross-origin destinations are safe Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.
Audits
Allows users to paste into password fields Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded It is recommended that optional fonts are preloaded.
Audits
Page has the HTML doctype Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.
Audits
Avoids `unload` event listeners The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries Below is a list of all front-end JavaScript libraries that were detected on the page.
| Name | Version |
|---|---|
| core-js | 3.6.5: global |
Avoids deprecated APIs Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps Consider deploying source maps for added benefits such as the ability to debug while in production.
Audits
Does not use HTTPS — 1 insecure request found Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
| Insecure URL |
|---|
| http://dating.com/ |
SEO
Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for dating.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 dating.com on mobile screens.
Document uses legible font sizes Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Content Best Practices
Document has a `<title>` element Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang` Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical` Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.
Crawling and Indexing
Page has successful HTTP status code Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Manual Checks
Structured data is valid Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
Progressive Web App
Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of dating.com. This includes details about web app manifests.Fast and reliable
Page load is fast enough on mobile networks Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.
PWA Optimized
Redirects HTTP traffic to HTTPS It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale` It is advised to use a '<meta name="viewport">' tag for the optimization of dating.com on mobile screens.
Contains some content when JavaScript is not available Apps should display alternative content for when JavaScript is disabled.
Fast and reliable
Current page does not respond with a 200 when offline In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.
Installable
Does not use HTTPS — 1 insecure request found Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
| Insecure URL |
|---|
| http://dating.com/ |
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.
Web app manifest does not 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.
View Data
PWA Optimized
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)
Performance
Accessibility
Best Practices
SEO
Progressive Web App
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.dating.com/
Updated: 12th February, 2021
2.31 seconds
First Contentful Paint (FCP)
0.18 seconds
First Input Delay (FID) Simulate loading on mobile
Performance
Indicates how well the page is performing and highlights opportunities where performance may be improved for dating.com. This includes details about optimizing page load times which can result in a better user experience.Metrics
First Contentful Paint — 2.1 s The time taken for the first image or text on the page to be rendered.
Speed Index — 2.1 s The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.1 s The timing of the largest text or image that is painted.
Total Blocking Time — 180 ms The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.024 Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data
Other
First Meaningful Paint — 2.2 s The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive dating.com as laggy when the latency is higher than 0.05 seconds.
Network Requests Below is a list of network requests that were made during page load.
| URL | Start Time (Ms) | End Time (Ms) | Transfer Size (Bytes) | Resource Size (Bytes) | Status Code | MIME Type | Resource Type |
|---|---|---|---|---|---|---|---|
| http://dating.com/ | 0 | 128.04700003471 | 284 | 0 | 301 | ||
| https://dating.com/ | 128.63600003766 | 144.77400004398 | 292 | 0 | 301 | ||
| https://www.dating.com/ | 145.34700004151 | 213.78700004425 | 18926 | 89548 | 200 | text/html | Document |
| https://www.dating.com/terra-assets/images/intro/712x500-01b621fdc9-3.jpg | 225.14900000533 | 270.28900000732 | 13552 | 12894 | 200 | image/jpeg | Image |
| 246.97800003923 | 247.01400002232 | 0 | 298 | 200 | image/svg+xml | Image | |
| 296.56300001079 | 296.60400003195 | 0 | 164 | 200 | image/svg+xml | Image | |
| https://www.dating.com/terra-assets/images/people/Ralph-79f74dd901-3.jpg | 298.26200002572 | 356.53900000034 | 5342 | 4690 | 200 | image/jpeg | Image |
| https://www.dating.com/terra-assets/images/people/Giselle-24842720dc-3.jpg | 298.65200002678 | 342.64200000325 | 6400 | 5748 | 200 | image/jpeg | Image |
| https://www.dating.com/terra-assets/styles/defer-a05931cd8c-3.css | 359.49500004062 | 431.94999999832 | 4355 | 10944 | 200 | text/css | XHR |
| https://data.clickocean.io/px/bac89543cab84ebd99fed75791d44cbf.js | 360.55400001351 | 434.81200002134 | 4136 | 7947 | 200 | application/javascript | Script |
| https://www.datadoghq-browser-agent.com/datadog-rum.js | 360.8940000413 | 408.84600003483 | 20450 | 59111 | 200 | application/javascript | Script |
| https://www.dating.com/terra-assets/bundle-0406739b9f-3.js | 361.59000004409 | 478.50100003416 | 43041 | 181455 | 200 | application/javascript | Script |
| https://data.clickocean.io/actions/views | 453.78600002732 | 519.69300000928 | 926 | 0 | 204 | Other | |
| 443.37300001644 | 443.41800000984 | 0 | 787 | 200 | image/svg+xml | Image | |
| 445.10200002696 | 445.15400001546 | 0 | 1227 | 200 | image/svg+xml | Image | |
| 447.04200001433 | 447.10500002839 | 0 | 2964 | 200 | image/svg+xml | Image | |
| https://www.dating.com/terra-assets/images/comments/1-608b2a0191-3.jpg | 448.23800004087 | 502.04799999483 | 4027 | 3374 | 200 | image/jpeg | Image |
| https://www.dating.com/terra-assets/images/comments/2-6a5abf8e8a-3.jpg | 448.73400003416 | 525.60500003165 | 4182 | 3529 | 200 | image/jpeg | Image |
| https://www.dating.com/terra-assets/images/comments/3-56fa70dff0-3.jpg | 449.20600001933 | 512.06199999433 | 3933 | 3280 | 200 | image/jpeg | Image |
| https://www.dating.com/terra-assets/images/about/712x540-7bd1c94d10-3.jpg | 449.81100002769 | 535.87200003676 | 8756 | 8099 | 200 | image/jpeg | Image |
| https://data.clickocean.io/actions/views | 520.37500002189 | 597.91000001132 | 1114 | 0 | 204 | text/plain | XHR |
| https://storage.communicationservicesplatform.com/app/xdls/d3d3LmRhdGluZy5jb20= | 530.80800001044 | 918.61400002381 | 4214 | 10909 | 200 | text/html | Document |
| https://connect.facebook.net/en_US/sdk.js | 534.42400001222 | 548.40100003639 | 2901 | 3224 | 200 | application/x-javascript | Script |
| https://connect.facebook.net/en_US/sdk.js?hash=748b4ec44a4e24d51252ff6834560e41&ua=modern_es6 | 553.4200000111 | 581.51600003475 | 62087 | 203060 | 200 | application/x-javascript | Script |
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) |
|---|---|
| 247.363 | 11.249 |
| 262.245 | 10.606 |
| 272.867 | 31.857 |
| 312.391 | 19.337 |
| 336.878 | 21.235 |
| 444.56 | 21.08 |
| 470.004 | 14.315 |
| 520.154 | 44.726 |
| 627.905 | 23.245 |
| 952.59 | 8.765 |
Opportunities
Eliminate render-blocking resources Resources, such as JavaScript and style sheets, can block the first paint of the page. Dating.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. Dating.com should consider serving more appropriate-sized images.
Defer offscreen images Time to Interactive can be slowed down by resources on the page. Dating.com should consider lazy-loading offscreen and hidden images.
Minify CSS Cascading Style Sheets (CSS) files can contribute to network payload sizes. Dating.com should consider minifying CSS files.
Minify JavaScript JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Dating.com should consider minifying JS files.
Remove unused CSS Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Dating.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
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 70 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.dating.com/ | 69.437 |
Preload key requests Key requests can be preloaded by using '<link rel=preload>'. Dating.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.
Diagnostics
Avoids enormous network payloads — Total size was 204 KiB Large network payloads can cost users money and are linked to long load times.
| URL | Transfer Size (Bytes) |
|---|---|
| https://connect.facebook.net/en_US/sdk.js?hash=748b4ec44a4e24d51252ff6834560e41&ua=modern_es6 | 62087 |
| https://www.dating.com/terra-assets/bundle-0406739b9f-3.js | 43041 |
| https://www.datadoghq-browser-agent.com/datadog-rum.js | 20450 |
| https://www.dating.com/ | 18926 |
| https://www.dating.com/terra-assets/images/intro/712x500-01b621fdc9-3.jpg | 13552 |
| https://www.dating.com/terra-assets/images/about/712x540-7bd1c94d10-3.jpg | 8756 |
| https://www.dating.com/terra-assets/images/people/Giselle-24842720dc-3.jpg | 6400 |
| https://www.dating.com/terra-assets/images/people/Ralph-79f74dd901-3.jpg | 5342 |
| https://www.dating.com/terra-assets/styles/defer-a05931cd8c-3.css | 4355 |
| https://storage.communicationservicesplatform.com/app/xdls/d3d3LmRhdGluZy5jb20= | 4214 |
Uses efficient cache policy on static assets — 10 resources found Dating.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://www.datadoghq-browser-agent.com/datadog-rum.js | 900000 | 20450 |
| https://connect.facebook.net/en_US/sdk.js | 1200000 | 2901 |
| https://www.dating.com/terra-assets/bundle-0406739b9f-3.js | 2592000000 | 43041 |
| https://www.dating.com/terra-assets/images/intro/712x500-01b621fdc9-3.jpg | 2592000000 | 13552 |
| https://www.dating.com/terra-assets/images/about/712x540-7bd1c94d10-3.jpg | 2592000000 | 8756 |
| https://www.dating.com/terra-assets/images/people/Giselle-24842720dc-3.jpg | 2592000000 | 6400 |
| https://www.dating.com/terra-assets/images/people/Ralph-79f74dd901-3.jpg | 2592000000 | 5342 |
| https://www.dating.com/terra-assets/images/comments/2-6a5abf8e8a-3.jpg | 2592000000 | 4182 |
| https://www.dating.com/terra-assets/images/comments/1-608b2a0191-3.jpg | 2592000000 | 4027 |
| https://www.dating.com/terra-assets/images/comments/3-56fa70dff0-3.jpg | 2592000000 | 3933 |
Avoids an excessive DOM size — 384 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 | 384 | |
| Maximum DOM Depth | 23 | |
| Maximum Child Elements | 14 |
Avoid chaining critical requests — 1 chain found Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Dating.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.5 s JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
| URL | Total CPU Time (Ms) | Script Evaluation (Ms) | Script Parse (Ms) |
|---|---|---|---|
| https://www.dating.com/ | 467.656 | 79.728 | 11.884 |
| https://www.dating.com/terra-assets/bundle-0406739b9f-3.js | 181.36 | 152.476 | 15.052 |
| Unattributable | 114.904 | 4.676 | 0.732 |
| https://www.datadoghq-browser-agent.com/datadog-rum.js | 107.176 | 90.412 | 5.024 |
| https://connect.facebook.net/en_US/sdk.js?hash=748b4ec44a4e24d51252ff6834560e41&ua=modern_es6 | 96.78 | 61.9 | 28.608 |
| https://data.clickocean.io/px/bac89543cab84ebd99fed75791d44cbf.js | 60.356 | 17.672 | 3.448 |
| https://storage.communicationservicesplatform.com/app/xdls/d3d3LmRhdGluZy5jb20= | 57.884 | 19.26 | 10.024 |
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 | 432.052 |
| Style & Layout | 240.672 |
| Other | 216.232 |
| Rendering | 82.776 |
| Script Parsing & Compilation | 77.012 |
| Parse HTML & CSS | 46.368 |
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 — 19 requests • 204 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 | 19 | 208918 |
| Script | 5 | 132615 |
| Image | 7 | 46192 |
| Document | 2 | 23140 |
| Other | 5 | 6971 |
| Stylesheet | 0 | 0 |
| Media | 0 | 0 |
| Font | 0 | 0 |
| Third-party | 7 | 95828 |
Minimize third-party usage — Third-party code blocked the main thread for 10 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) |
|---|---|---|
| 64988 | 6.78 |
Largest Contentful Paint element — 1 element found The element which was identified as the Largest Contentful Paint.
| Element |
|---|
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 |
|---|---|
| 0.022860495881849 | |
| 0.0012154318525258 |
Uses passive listeners to improve scrolling performance Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
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) |
|---|---|---|
| https://www.dating.com/terra-assets/bundle-0406739b9f-3.js | 3690 | 179 |
| https://connect.facebook.net/en_US/sdk.js?hash=748b4ec44a4e24d51252ff6834560e41&ua=modern_es6 | 5100 | 93 |
| https://www.datadoghq-browser-agent.com/datadog-rum.js | 3270 | 84 |
| https://www.dating.com/ | 2127 | 64 |
Avoid non-composited animations It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.
Budgets
Performance budget It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget It is advised to set a timing budget to monitor the performance of your site.
Metrics
Time to Interactive — 4.8 s The time taken for the page to become fully interactive.
Other
First CPU Idle — 4.5 s The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 180 ms Users could experience a delay when interacting with the page.
First Contentful Paint (3G) — 4096 ms The time taken for the first image or text on the page to be rendered while on a 3G network.
Opportunities
Remove unused JavaScript — Potential savings of 44 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://connect.facebook.net/en_US/sdk.js?hash=748b4ec44a4e24d51252ff6834560e41&ua=modern_es6 | 62087 | 45050 |
Avoid serving legacy JavaScript to modern browsers — Potential savings of 11 KiB Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
| URL | Potential Savings (Bytes) |
|---|---|
| https://www.dating.com/terra-assets/bundle-0406739b9f-3.js | 10803 |
Opportunities
Avoid multiple page redirects — Potential savings of 1,110 ms Redirects can cause additional delays before the page can begin loading. Dating.com should avoid multiple or unnecessary page redirects.
| URL | Time Spent (Ms) |
|---|---|
| http://dating.com/ | 630 |
| https://dating.com/ | 480 |
| https://www.dating.com/ | 0 |
Diagnostics
Avoid `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.
| URL | Location |
|---|---|
| https://www.dating.com/ | line: 0 |
Accessibility
Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of dating.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.
ARIA
`[aria-*]` attributes match their roles Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[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.
`[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-*]` 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.
| Failing Elements |
|---|
`<frame>` or `<iframe>` elements have a title Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute. It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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"]` Dating.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]` Dating.com may provide relevant information that dialogue cannot, by using audio descriptions.
Contrast
Background and foreground colors do not have a sufficient contrast ratio. Many (if not most) users find low-contrast text difficult or impossible to read.
| Failing Elements |
|---|
Names and labels
Form elements do not have associated labels Screen readers and other assistive technologies rely on labels to properly announce form controls.
| Failing Elements |
|---|
Links do not have a discernible name In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
| 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 |
|---|
Navigation
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.
Best Practices
Indicates the recommended, best practices currently in place on the page and highlights the best practices that dating.com should incorporate. This includes practices such as protecting pages with HTTPS.Audits
Links to cross-origin destinations are safe Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.
Audits
Allows users to paste into password fields Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded It is recommended that optional fonts are preloaded.
Audits
Page has the HTML doctype Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.
Audits
Avoids `unload` event listeners The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries Below is a list of all front-end JavaScript libraries that were detected on the page.
| Name | Version |
|---|---|
| core-js | 3.6.5: global |
Avoids deprecated APIs Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps Consider deploying source maps for added benefits such as the ability to debug while in production.
Audits
Does not use HTTPS — 1 insecure request found Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
| Insecure URL |
|---|
| http://dating.com/ |
SEO
Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for dating.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 dating.com on mobile screens.
Document uses legible font sizes — 95.48% 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 |
|---|---|---|---|
| #gdpr-agreement-wrapper | 4.17% | 11px | |
| .note | 0.33% | 11px | |
| #application-placeholder | 0.01% | 0px | |
| footer .appendix | 0.00% | 0px | |
| 95.48% | ≥ 12px |
Tap targets are sized appropriately — 100% appropriately sized tap targets Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Content Best Practices
Document has a `<title>` element Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang` Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical` Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.
Crawling and Indexing
Page has successful HTTP status code Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Manual Checks
Structured data is valid Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
Progressive Web App
Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of dating.com. This includes details about web app manifests.Fast and reliable
Page load is fast enough on mobile networks Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.
PWA Optimized
Redirects HTTP traffic to HTTPS It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale` It is advised to use a '<meta name="viewport">' tag for the optimization of dating.com on mobile screens.
Contains some content when JavaScript is not available Apps should display alternative content for when JavaScript is disabled.
Fast and reliable
Current page does not respond with a 200 when offline In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.
Installable
Does not use HTTPS — 1 insecure request found Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
| Insecure URL |
|---|
| http://dating.com/ |
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.
Web app manifest does not 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.
View Data
PWA Optimized
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: | 23.221.137.78 |
| Continent: | |
| Country: | |
| Region: | |
| City: | |
| Longitude: | |
| Latitude: | |
| Currencies: | |
| Languages: |
Web Hosting Provider
| Name | IP Address |
|---|---|
| Akamai Technologies, Inc. |
Registration
Domain Registrant
| Private Registration: | Yes |
| Name: | Privacy protection service - whoisproxy.ru |
| Organization: | Privacy protection service - whoisproxy.ru |
| Country: | RU |
| City: | Moscow |
| State: | Moscow |
| Post Code: | 123308 |
| Email: | dating.com@whoisproxy.ru |
| Phone: | +7.4957856536 |
Note: Registration information is derived from various sources and may be inaccurate.
Domain Registrar
| Name | IP Address |
|---|---|
| Name.com, Inc. | 104.18.7.161 |
Security
Visitor Safety
| Mature Content: | Not Likely |
| McAfee WebAdvisor Rating: | Unknown |
| WOT Rating: | 2.5/5 (10 reviews) |
| WOT Trustworthiness: | 50/100 |
| WOT Child Safety: | 23/100 |
Note: Safety information is not guaranteed.
SSL/TLS Certificate
| Issued To: | *.dating.com |
| Issued By: | Sectigo RSA Domain Validation Secure Server CA |
| Valid From: | 30th April, 2020 |
| Valid To: | 15th May, 2022 |
| Subject: | CN = *.dating.com |
| Hash: | ede6c534 |
| Issuer: | CN = Sectigo RSA Domain Validation Secure Server CA O = Sectigo Limited S = GB |
| Version: | 2 |
| Serial Number: | 89181980548013195526067532579144224325 |
| Serial Number (Hex): | 4317D31E78DDC0F92EB809312F004E45 |
| Valid From: | 30th April, 2024 |
| Valid To: | 15th May, 2024 |
| Signature Algorithm (Short Name): | RSA-SHA256 |
| Signature Algorithm (Long Name): | sha256WithRSAEncryption |
| Authority Key Identifier: | keyid:8D:8C:5E:C4:54:AD:8A:E1:77:E9:9B:F9:9B:05:E1:B8:01:8D:61:E1 |
| Extended Key Usage: | TLS Web Server Authentication, TLS Web Client Authentication |
| Certificate Policies: | Policy: 1.3.6.1.4.1.6449.1.2.2.7 CPS: https://sectigo.com/CPS Policy: 2.23.140.1.2.1 |
| Authority Information Access: | CA Issuers - URI:http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt OCSP - URI:http://ocsp.sectigo.com |
| SCT List: | Signed Certificate Timestamp: Version : v1 (0x0) Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D: 11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47 Timestamp : Apr 30 14:46:15.591 2020 GMT Extensions: none Signature : ecdsa-with-SHA256 30:46:02:21:00:B2:5C:EE:88:9E:DA:4E:68:AD:22:10: 07:35:85:E9:A5:A5:DD:83:04:24:73:E9:55:1D:B8:40: A3:6F:9F:62:61:02:21:00:99:4A:C3:EE:34:68:F3:17: 7B:F6:C4:16:F5:1B:B7:AA:7A:EC:AA:4E:4E:C9:56:C9: 21:9C:41:8A:ED:1C:4A:43 Signed Certificate Timestamp: Version : v1 (0x0) Log ID : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A: EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73 Timestamp : Apr 30 14:46:15.631 2020 GMT Extensions: none Signature : ecdsa-with-SHA256 30:45:02:20:34:10:EA:89:85:2C:62:94:F2:E3:1A:7A: F5:D5:E4:25:DE:87:09:05:4A:1F:15:F7:70:F3:04:1C: 9C:9D:5C:DA:02:21:00:D2:10:53:92:C9:78:18:1A:F0: 47:74:DC:06:6F:81:C0:87:DB:98:B8:A1:4E:8D:A0:E5: 94:FC:CA:BA:B5:F7:67 Signed Certificate Timestamp: Version : v1 (0x0) Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77: 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13 Timestamp : Apr 30 14:46:15.583 2020 GMT Extensions: none Signature : ecdsa-with-SHA256 30:45:02:20:66:E6:A0:9B:CB:5E:B2:CC:D0:C4:53:C3: 4E:02:86:77:EB:E1:68:04:6F:39:47:CE:7F:7A:37:4C: D0:DE:10:B6:02:21:00:8A:79:FE:BE:B4:ED:D9:0B:DB: 98:23:C5:31:9E:72:57:C3:BA:1E:30:87:C1:17:AF:CA: 7A:C0:42:33:3D:0F:CB |
| Key Usage: | Digital Signature, Key Encipherment |
| Basic Constraints: | CA:FALSE |
| Subject Alternative Name: | DNS:dating.com DNS:*.dating.com |
Technical
DNS Lookup
A Records
| Host | IP Address | Class | TTL |
|---|---|---|---|
| dating.com. | 104.82.16.220 | IN | 19 |
NS Records
| Host | Nameserver | Class | TTL |
|---|---|---|---|
| dating.com. | ns4-65.akam.net. | IN | 21599 |
| dating.com. | ns5-64.akam.net. | IN | 21599 |
| dating.com. | ns1-105.akam.net. | IN | 21599 |
| dating.com. | ns7-65.akam.net. | IN | 21599 |
MX Records
| Priority | Host | Server | Class | TTL |
|---|---|---|---|---|
| 5 | dating.com. | ormx.smtpsending.com. | IN | 3599 |
| 5 | dating.com. | ohmx.smtpsending.com. | IN | 3599 |
SOA Records
| Domain Name | Primary NS | Responsible Email | TTL |
|---|---|---|---|
| dating.com. | ns4-65.akam.net. | hostmaster.akamai.com. | 21599 |
TXT Records
| Host | Value | Class | TTL |
|---|---|---|---|
| dating.com. | google-site-verification=ACrR7_IvgkkQQm3koY_UsfgaKkBEN3aTofO-cyOgoCk | IN | 3599 |
| dating.com. | globalsign-domain-verification=ViNxjJsl6FQPtkDgw0kkDe5AhUz8l4nJzGfXB2oXi4 | IN | 3599 |
| dating.com. | v=spf1 | IN | 3599 |
HTTP Response Headers
| HTTP-Code: | HTTP/1.1 200 OK |
| Date: | 12th February, 2021 |
| Content-Type: | text/html; charset=UTF-8 |
| Cache-Control: | max-age=60, stale-while-revalidate=604800, stale-if-error=604800 |
| Server: | cloudflare |
| Connection: | keep-alive |
| Set-Cookie: | * |
| CF-Ray: | 6209e5008e1feff9-EWR |
| Age: | 27 |
| Content-Language: | en-US |
| Link: | <https://www.dating.com/amp/>; rel="amphtml", </terra-assets/images/intro/1920x600-72259d22f9-3.jpg>; rel=preload; as=image |
| Vary: | Accept-Encoding |
| CF-Cache-Status: | HIT |
| cf-request-id: | 083a0d74530000eff9aba6d000000001 |
| Content-Security-Policy: | frame-ancestors 'self' |
| Expect-CT: | max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" |
| alt-svc: | h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400 |
Whois Lookup
| Created: | 23rd February, 1998 |
| Changed: | 9th April, 2018 |
| Expires: | 21st February, 2025 |
| Registrar: | Regional Network Information Center, JSC dba RU-CENTER |
| Status: | clientTransferProhibited |
| Nameservers: | ns1-105.akam.net ns4-65.akam.net ns5-64.akam.net ns7-65.akam.net |
| Owner Name: | Privacy protection service - whoisproxy.ru |
| Owner Organization: | Privacy protection service - whoisproxy.ru |
| Owner Street: | PO box 99, whoisproxy.ru |
| Owner Post Code: | 123308 |
| Owner City: | Moscow |
| Owner State: | Moscow |
| Owner Country: | RU |
| Owner Phone: | +7.4957856536 |
| Owner Email: | dating.com@whoisproxy.ru |
| Admin Name: | Privacy protection service - whoisproxy.ru |
| Admin Organization: | Privacy protection service - whoisproxy.ru |
| Admin Street: | PO box 99, whoisproxy.ru |
| Admin Post Code: | 123308 |
| Admin City: | Moscow |
| Admin State: | Moscow |
| Admin Country: | RU |
| Admin Phone: | +7.4957856536 |
| Admin Email: | dating.com@whoisproxy.ru |
| Tech Name: | Privacy protection service - whoisproxy.ru |
| Tech Organization: | Privacy protection service - whoisproxy.ru |
| Tech Street: | PO box 99, whoisproxy.ru |
| Tech Post Code: | 123308 |
| Tech City: | Moscow |
| Tech State: | Moscow |
| Tech Country: | RU |
| Tech Phone: | +7.4957856536 |
| Tech Email: | dating.com@whoisproxy.ru |
| Full Whois: | Domain Name: DATING.COM
Registry Domain ID: 1572000_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.nic.ru Registrar URL: http://www.nic.ru Updated Date: 2018-04-09T08:11:35Z Creation Date: 1998-02-23T05:00:00Z Registrar Registration Expiration Date: 2025-02-21T21:00:00Z Registrar: Regional Network Information Center, JSC dba RU-CENTER Registrar IANA ID: 463 Registrar Abuse Contact Email: tld-abuse@nic.ru Registrar Abuse Contact Phone: +7.4959944601 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: Registrant Name: Privacy protection service - whoisproxy.ru Registrant Organization: Privacy protection service - whoisproxy.ru Registrant Street: PO box 99, whoisproxy.ru Registrant City: Moscow Registrant State/Province: Moscow Registrant Postal Code: 123308 Registrant Country: RU Registrant Phone: +7.4957856536 Registrant Phone Ext: Registrant Email: dating.com@whoisproxy.ru Registry Admin ID: Admin Name: Privacy protection service - whoisproxy.ru Admin Organization: Privacy protection service - whoisproxy.ru Admin Street: PO box 99, whoisproxy.ru Admin City: Moscow Admin State/Province: Moscow Admin Postal Code: 123308 Admin Country: RU Admin Phone: +7.4957856536 Admin Phone Ext: Admin Email: dating.com@whoisproxy.ru Registry Tech ID: Tech Name: Privacy protection service - whoisproxy.ru Tech Organization: Privacy protection service - whoisproxy.ru Tech Street: PO box 99, whoisproxy.ru Tech City: Moscow Tech State/Province: Moscow Tech Postal Code: 123308 Tech Country: RU Tech Phone: +7.4957856536 Tech Phone Ext: Tech Email: dating.com@whoisproxy.ru Name Server: ns1-105.akam.net Name Server: ns4-65.akam.net Name Server: ns5-64.akam.net Name Server: ns7-65.akam.net DNSSEC: unsigned URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/ For more information on Whois status codes, please visit: https://icann.org/epp >>> Last update of WHOIS database: 2021.02.13T01:54:50Z <<< |
Nameservers
| Name | IP Address |
|---|---|
| ns1-105.akam.net | 193.108.91.105 |
| ns4-65.akam.net | 84.53.139.65 |
| ns5-64.akam.net | 184.85.248.64 |
| ns7-65.akam.net | 96.7.49.65 |
Related
Subdomains
| Domain | Subdomain |
|---|---|
| onelyhearts |
Similar Sites
| Domain | Valuation | Snoop Score |
|---|---|---|
| $7,714 USD | 3/5 | |
| $3,373 USD | 3/5 | |
| 0/5 | ||
| $257,909 USD | 4/5 | |
| $9,387 USD | 3/5 |
Organic Search (US) Competitors
Backlink Competitors
Sites with the same domain name
| Domain | Valuation | Snoop Score |
|---|---|---|
| 0/5 | ||
| 0/5 |
Sites hosted on the same IP address
Love W3 Snoop?
Share This 