passion.com

passion.com is SSL secured

Free website and domain report on passion.com

Last Updated: 1st July, 2023 Update Now
Overview

Snoop Summary for passion.com

This is a free and comprehensive report about passion.com. The domain passion.com is currently hosted on a server located in San Jose, California in United States with the IP address 69.165.107.69, where the local currency is USD and English is the local language. Our records indicate that passion.com is owned/operated by Various, Inc. Passion.com has the potential to be earning an estimated $8 USD per day from advertising revenue. If passion.com was to be sold it would possibly be worth $6,168 USD (based on the daily revenue potential of the website over a 24 month period). Passion.com receives an estimated 2,960 unique visitors every day - a large amount of traffic! This report was last updated 1st July, 2023.

About passion.com

Site Preview:
Title: Welcome to Passion.com - the leading personals network for dating, romance, marriage, and fun!
Description: Passion.com is a free online dating site where you can find hot singles for romantic experiences. Sign up to meet local singles that are passionate about online dating.
Keywords and Tags: adult content, couples personals, date women, dating, find singles, free online dating, gay personals, hot personals, lesbian personals, local meetups, local personals site, local singles, meet singles, online dating, personal sites, personals, profile videos, sexual materials, single women
Related Terms: call of passion, lesson of passion, passion, passion dolls, passion dolls uk, passion fruits, passion hd, passion ru, sharmis passion, trail passion
Fav Icon:
Age: Over 28 years old
Domain Created: 20th April, 1995
Domain Updated: 22nd April, 2021
Domain Expires: 21st April, 2022
Review

Snoop Score

3/5 (Great!)

Valuation

$6,168 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 198,180
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: 2,960
Monthly Visitors: 90,093
Yearly Visitors: 1,080,400
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $8 USD
Monthly Revenue: $257 USD
Yearly Revenue: $3,079 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: passion.com 11
Domain Name: passion 7
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 4.11 seconds
Load Time Comparison: Faster than 12% of sites

PageSpeed Insights

Avg. (All Categories) 70
Performance 97
Accessibility 84
Best Practices 62
SEO 83
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://passion.com/
Updated: 21st February, 2022

1.92 seconds
First Contentful Paint (FCP)
72%
13%
15%

0.03 seconds
First Input Delay (FID)
96%
2%
2%

97

Performance

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

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.4 s
The time taken for the page to become fully interactive.
Total Blocking Time — 30 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 — 0.8 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 — 100 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.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://passion.com/
http/1.1
0
147.77400001185
435
0
301
text/html
https://passion.com/
http/1.1
148.20500000496
732.485000015
9699
27809
200
text/html
Document
https://passion.com/images/ffadult/css/header.css
http/1.1
743.99300001096
1196.1290000181
466
0
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Istok+Web|Josefin+Sans
h2
744.42200001795
756.50899999891
1395
2399
200
text/css
Stylesheet
https://secureimage.securedataimages.com/css/live_cd/ffadult/english/1/secure/passion_cover-1637109513.css
h2
744.70999999903
786.73800002434
3422
14066
200
text/css
Stylesheet
https://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js
h2
745.06500002462
750.07800001185
21004
57254
200
text/javascript
Script
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/jquery.infieldlabel.min.js
h2
745.41500001214
786.37300000992
1164
1736
200
application/x-javascript
Script
https://www.google.com/recaptcha/enterprise.js?render=6Le39tEaAAAAAMMkCDMgcFqH-bd48PekQZWZSphp
h2
745.90200002422
751.73500002711
1212
974
200
text/javascript
Script
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/close_btn.png
h2
788.89700002037
829.85500001814
1470
1129
200
image/png
Image
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/cover_logo3.png
h2
831.28100002068
846.5520000027
4445
4103
200
image/png
Image
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/bg_img.jpg
h2
1209.6730000048
1310.261000006
168970
168592
200
image/jpeg
Image
https://fonts.gstatic.com/s/istokweb/v18/3qTvojGmgSyUukBzKslpBmt_1EEYaA.woff2
h2
1210.6310000236
1214.1310000152
12192
11252
200
font/woff2
Font
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
h2
1215.2690000075
1225.9960000229
144166
362767
200
text/javascript
Script
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/form_bg.png
h2
1219.6320000221
1261.3780000247
1273
933
200
image/png
Image
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/cover_sprites.png
h2
1220.0850000081
1262.4000000069
25841
25499
200
image/png
Image
https://fonts.gstatic.com/s/josefinsans/v23/Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKSbpUVzEEQ.woff
h2
1221.8290000164
1228.4849999996
14751
13824
200
font/woff
Font
https://passion.com/qz/phone/info
http/1.1
1237.237000023
1458.0850000202
826
646
200
application/json
XHR
https://www.google.com/recaptcha/enterprise/anchor?ar=1&k=6Le39tEaAAAAAMMkCDMgcFqH-bd48PekQZWZSphp&co=aHR0cHM6Ly9wYXNzaW9uLmNvbTo0NDM.&hl=en&v=1B_yv3CBEV10KtI2HJ6eEXhJ&size=invisible&cb=h8pyyfq3sy6o
h2
1516.8510000221
1570.9870000137
22094
41513
200
text/html
Document
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/styles__ltr.css
h2
1582.9660000163
1591.5770000138
25159
52582
200
text/css
Stylesheet
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
h2
1583.5220000008
1595.0670000166
144166
362767
200
text/javascript
Script
https://www.gstatic.com/recaptcha/api2/logo_48.png
h2
1696.0860000108
1699.2750000209
3100
2228
200
image/png
Image
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
1696.8679999991
1700.4810000071
11688
10748
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
h2
1697.4310000078
1700.2020000073
11714
10788
200
font/woff2
Font
https://www.google.com/recaptcha/enterprise/webworker.js?hl=en&v=1B_yv3CBEV10KtI2HJ6eEXhJ
h2
1736.0510000144
1742.0630000124
832
102
200
text/javascript
Other
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)
777.954
6.763
1239.62
11.584
1260.923
7.072
1268.037
6.097
1277.232
234.952
1517.298
42.794
1564.75
22.289
1616.728
7.122
1666.489
100.434
1766.956
6.086
1786.894
47.409
1837.368
21.945
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. Passion.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Passion.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Passion.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Passion.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 23 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Passion.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/styles__ltr.css
25159
23708
Efficiently encode images — Potential savings of 7 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/bg_img.jpg
168592
7532
Serve images in next-gen formats — Potential savings of 128 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/bg_img.jpg
168592
109640.6
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/cover_sprites.png
25499
21126.2
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 590 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://passion.com/
585.274
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Passion.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://passion.com/
190
https://passion.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Passion.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 617 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/bg_img.jpg
168970
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
144166
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
144166
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/cover_sprites.png
25841
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/styles__ltr.css
25159
https://www.google.com/recaptcha/enterprise/anchor?ar=1&k=6Le39tEaAAAAAMMkCDMgcFqH-bd48PekQZWZSphp&co=aHR0cHM6Ly9wYXNzaW9uLmNvbTo0NDM.&hl=en&v=1B_yv3CBEV10KtI2HJ6eEXhJ&size=invisible&cb=h8pyyfq3sy6o
22094
https://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js
21004
https://fonts.gstatic.com/s/josefinsans/v23/Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKSbpUVzEEQ.woff
14751
https://fonts.gstatic.com/s/istokweb/v18/3qTvojGmgSyUukBzKslpBmt_1EEYaA.woff2
12192
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
11714
Uses efficient cache policy on static assets — 9 resources found
Passion.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://passion.com/images/ffadult/css/header.css
0
466
https://www.gstatic.com/recaptcha/api2/logo_48.png
604800000
3100
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/bg_img.jpg
2592000000
168970
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/cover_sprites.png
2592000000
25841
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/cover_logo3.png
2592000000
4445
https://secureimage.securedataimages.com/css/live_cd/ffadult/english/1/secure/passion_cover-1637109513.css
2592000000
3422
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/close_btn.png
2592000000
1470
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/form_bg.png
2592000000
1273
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/jquery.infieldlabel.min.js
2592000000
1164
Avoids an excessive DOM size — 177 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
177
Maximum DOM Depth
Man
9
Maximum Child Elements
13
Avoid chaining critical requests — 7 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Passion.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)
https://passion.com/
284.277
232.27
2.345
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
143.824
117.214
15.017
https://www.google.com/recaptcha/enterprise/anchor?ar=1&k=6Le39tEaAAAAAMMkCDMgcFqH-bd48PekQZWZSphp&co=aHR0cHM6Ly9wYXNzaW9uLmNvbTo0NDM.&hl=en&v=1B_yv3CBEV10KtI2HJ6eEXhJ&size=invisible&cb=h8pyyfq3sy6o
91.183
75.393
2.401
Minimizes main-thread work — 0.6 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
438.446
Other
52.97
Style & Layout
29.497
Rendering
28.314
Script Parsing & Compilation
21.336
Parse HTML & CSS
10.042
Keep request counts low and transfer sizes small — 24 requests • 617 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
24
631484
Script
5
311712
Image
6
205099
Font
4
50345
Document
2
31793
Stylesheet
4
30442
Other
3
2093
Media
0
0
Third-party
20
620058
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)
337595
0
51740
0
24138
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 — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
8.7343198202142E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 2 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://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js
656
117
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
1400
100
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of passion.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 — 1.4 s
The time taken for the page contents to be visibly populated.

Other

Eliminate render-blocking resources — Potential savings of 270 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Passion.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://passion.com/images/ffadult/css/header.css
466
70
https://fonts.googleapis.com/css?family=Istok+Web|Josefin+Sans
1395
230
https://secureimage.securedataimages.com/css/live_cd/ffadult/english/1/secure/passion_cover-1637109513.css
3422
230
https://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js
21004
310
Reduce unused JavaScript — Potential savings of 76 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://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
144166
77338

Other

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/istokweb/v18/3qTvojGmgSyUukBzKslpBmt_1EEYaA.woff2
3.4999999916181
https://fonts.gstatic.com/s/josefinsans/v23/Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKSbpUVzEEQ.woff
6.6559999831952
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
3.6130000080448
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
2.770999999484
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/cover_logo3.png
84

Accessibility

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

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
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.
62

Best Practices

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

Audits

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

Audits

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

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

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

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://passion.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 6 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
6
Medium

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
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for passion.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 passion.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.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is not valid — 11 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
62
Disallow: http://personals.sfgate.com/p/member.cgi?site=ffadult&dcb=personals.sfgate.com&fromPage=&mid=150167076_53766
Pattern should either be empty, start with "/" or "*"
63
Disallow: http://profile.xmatch.com/p/member.cgi?dcb=xmatch&fromPage=&mid=150167076_53766
Pattern should either be empty, start with "/" or "*"
64
Disallow: http://passion.com/view/TT2483?pid=p38260&override=1
Pattern should either be empty, start with "/" or "*"
65
Disallow: http://passion.com/view/2xfun1970?pid=p38260&override=1
Pattern should either be empty, start with "/" or "*"
66
Disallow: http://profile.adultfriendfinder.com/p/member.cgi?fromPage=&mid=55829490_97842
Pattern should either be empty, start with "/" or "*"
67
Disallow: http://profile.adultfriendfinder.com/view/25489010_14893.html?pid=g899570-pct.subtitlelink&pg=0
Pattern should either be empty, start with "/" or "*"
68
Disallow: http://personals.ugo.com/p/member.cgi?site=ffadult&dcb=personals.ugo.com&fromPage=magazine&mid=115767602_37139
Pattern should either be empty, start with "/" or "*"
69
Disallow: http://profile.passion.com/p/member.cgi?dcb=passion&fromPage=&mid=51936284_65515
Pattern should either be empty, start with "/" or "*"
70
Disallow: http://profile.passion.com/p/member.cgi?dcb=passion&mid=148374312_84991
Pattern should either be empty, start with "/" or "*"
71
Disallow: http://profile.xmatch.com/p/member.cgi?site=ffadult&dcb=xmatch&mid=132898470_36898&askmeforaphoto=1
Pattern should either be empty, start with "/" or "*"
72
Disallow: http://personals.nwsource.com/p/member.cgi?site=ffadult&dcb=personals.nwsource.com&fromPage=&mid=148641326_62004
Pattern should either be empty, start with "/" or "*"

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 passion.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 passion.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) 65
Performance 66
Accessibility 87
Best Practices 62
SEO 80
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://passion.com/
Updated: 21st February, 2022

2.06 seconds
First Contentful Paint (FCP)
69%
21%
10%

0.02 seconds
First Input Delay (FID)
94%
5%
1%

66

Performance

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

Metrics

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

Other

Properly size images
Images can slow down the page's load time. Passion.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Passion.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Passion.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Passion.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Passion.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://passion.com/
630
https://passion.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Passion.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 422 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
144166
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
144166
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/styles__ltr.css
25159
https://www.google.com/recaptcha/enterprise/anchor?ar=1&k=6Le39tEaAAAAAMMkCDMgcFqH-bd48PekQZWZSphp&co=aHR0cHM6Ly9wYXNzaW9uLmNvbTo0NDM.&hl=en&v=1B_yv3CBEV10KtI2HJ6eEXhJ&size=invisible&cb=vm2mqwfu13bs
22379
https://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js
21005
https://fonts.gstatic.com/s/istokweb/v18/3qTvojGmgSyUukBzKslpBmt_1EEYaA.woff2
12192
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
11728
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
11688
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/mobile_imgs/bg_img.jpg
11098
https://passion.com/
10591
Uses efficient cache policy on static assets — 6 resources found
Passion.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.gstatic.com/recaptcha/api2/logo_48.png
604800000
3100
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/mobile_imgs/bg_img.jpg
2592000000
11098
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/cover_logo3.png
2592000000
4445
https://secureimage.securedataimages.com/css/live_cd/ffadult/english/1/secure/passion_cover-1637109513.css
2592000000
3422
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/close_btn.png
2592000000
1470
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/jquery.infieldlabel.min.js
2592000000
1164
Avoids an excessive DOM size — 187 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
187
Maximum DOM Depth
Man
9
Maximum Child Elements
13
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Passion.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Keep request counts low and transfer sizes small — 20 requests • 422 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
20
432465
Script
5
311713
Font
3
35608
Document
2
32970
Stylesheet
3
29967
Image
4
20113
Other
3
2094
Media
0
0
Third-party
17
420612
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 — 5 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://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js
2340
940
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
5370
432
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
5802
118
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
1114
87
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
5920
50
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of passion.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.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://passion.com/
http/1.1
0
157.43799973279
435
0
301
text/html
https://passion.com/
http/1.1
157.73799968883
771.10499981791
10591
29306
200
text/html
Document
https://fonts.googleapis.com/css?family=Istok+Web|Josefin+Sans
h2
784.66699970886
791.86199977994
1386
2398
200
text/css
Stylesheet
https://secureimage.securedataimages.com/css/live_cd/ffadult/english/1/secure/passion_cover-1637109513.css
h2
784.99299986288
796.69099999592
3422
14066
200
text/css
Stylesheet
https://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js
h2
785.56999983266
790.91799957678
21005
57254
200
text/javascript
Script
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/jquery.infieldlabel.min.js
h2
785.81999987364
797.52099979669
1164
1736
200
application/x-javascript
Script
https://www.google.com/recaptcha/enterprise.js?render=6Le39tEaAAAAAMMkCDMgcFqH-bd48PekQZWZSphp
h2
786.41899954528
804.66699972749
1212
974
200
text/javascript
Script
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/close_btn.png
h2
789.25899975002
800.34899991006
1470
1129
200
image/png
Image
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/cover_logo3.png
h2
789.64099986479
801.31699983031
4445
4103
200
image/png
Image
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/mobile_imgs/bg_img.jpg
h2
813.60699981451
824.81299992651
11098
10722
200
image/jpeg
Image
https://fonts.gstatic.com/s/istokweb/v18/3qTvojGmgSyUukBzKslpBmt_1EEYaA.woff2
h2
814.01299964637
818.16499959677
12192
11252
200
font/woff2
Font
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
h2
818.742999807
830.67899988964
144166
362767
200
text/javascript
Script
https://passion.com/qz/phone/info
http/1.1
838.26899994165
1281.4729996026
827
646
200
application/json
XHR
https://www.google.com/recaptcha/enterprise/anchor?ar=1&k=6Le39tEaAAAAAMMkCDMgcFqH-bd48PekQZWZSphp&co=aHR0cHM6Ly9wYXNzaW9uLmNvbTo0NDM.&hl=en&v=1B_yv3CBEV10KtI2HJ6eEXhJ&size=invisible&cb=vm2mqwfu13bs
h2
1385.9049999155
1422.3749996163
22379
43263
200
text/html
Document
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/styles__ltr.css
h2
1433.720999863
1441.8829996139
25159
52582
200
text/css
Stylesheet
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
h2
1433.9979998767
1447.0689999871
144166
362767
200
text/javascript
Script
https://www.gstatic.com/recaptcha/api2/logo_48.png
h2
1548.4819998965
1551.5459999442
3100
2228
200
image/png
Image
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
1550.0429999083
1553.5229998641
11688
10748
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
h2
1551.3009997085
1554.8159996979
11728
10788
200
font/woff2
Font
https://www.google.com/recaptcha/enterprise/webworker.js?hl=en&v=1B_yv3CBEV10KtI2HJ6eEXhJ
h2
1592.7699999884
1603.8709999993
832
102
200
text/javascript
Other
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)
818.123
8.442
844.337
9.698
871.219
8.327
879.567
470.041
1386.573
43.722
1468.48
6.852
1515.462
108.103
1623.591
5.173
1628.802
5.554
1639.868
6.29
1648.125
59.134
1709.68
25.126
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

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

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 630 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Passion.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Istok+Web|Josefin+Sans
1386
780
https://secureimage.securedataimages.com/css/live_cd/ffadult/english/1/secure/passion_cover-1637109513.css
3422
780
Reduce unused CSS — Potential savings of 23 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Passion.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/styles__ltr.css
25159
23708
Reduce JavaScript execution time — 2.8 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://passion.com/
1948.96
1813.24
8.58
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
657.3
541.2
59.304
https://www.google.com/recaptcha/enterprise/anchor?ar=1&k=6Le39tEaAAAAAMMkCDMgcFqH-bd48PekQZWZSphp&co=aHR0cHM6Ly9wYXNzaW9uLmNvbTo0NDM.&hl=en&v=1B_yv3CBEV10KtI2HJ6eEXhJ&size=invisible&cb=vm2mqwfu13bs
392.752
333.648
8.78
https://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js
138.892
45.548
5.228
Unattributable
122.588
10.18
0.644
Minimize main-thread work — 3.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
2747.22
Other
206.228
Style & Layout
173.788
Script Parsing & Compilation
83.452
Parse HTML & CSS
39.444
Rendering
30.96

Metrics

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

Audits

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

Other

Reduce unused JavaScript — Potential savings of 75 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/1B_yv3CBEV10KtI2HJ6eEXhJ/recaptcha__en.js
144166
77297
Reduce initial server response time — Root document took 610 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://passion.com/
614.36
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/istokweb/v18/3qTvojGmgSyUukBzKslpBmt_1EEYaA.woff2
4.1519999504089
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
3.4799999557436
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
3.5149999894202
Reduce the impact of third-party code — Third-party code blocked the main thread for 420 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)
337596
236.16
24423
183.064
36994
0
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://secureimage.securedataimages.com/images/ffadult/passion/cover2/cover_logo3.png
First Contentful Paint (3G) — 5520 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
87

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of passion.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"]`
Passion.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.
62

Best Practices

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

Audits

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

Audits

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

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

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

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://passion.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 6 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
6
Medium

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
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
80

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for passion.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 passion.com on mobile screens.
Document uses legible font sizes — 83.88% 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
#logo a
10.99%
10.0008px
.rc-anchor-normal .rc-anchor-pt, .rc-anchor-invisible .rc-anchor-pt, .rc-anchor-compact .rc-anchor-pt
5.13%
8px
83.88%
≥ 12px

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is not valid — 11 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
62
Disallow: http://personals.sfgate.com/p/member.cgi?site=ffadult&dcb=personals.sfgate.com&fromPage=&mid=150167076_53766
Pattern should either be empty, start with "/" or "*"
63
Disallow: http://profile.xmatch.com/p/member.cgi?dcb=xmatch&fromPage=&mid=150167076_53766
Pattern should either be empty, start with "/" or "*"
64
Disallow: http://passion.com/view/TT2483?pid=p38260&override=1
Pattern should either be empty, start with "/" or "*"
65
Disallow: http://passion.com/view/2xfun1970?pid=p38260&override=1
Pattern should either be empty, start with "/" or "*"
66
Disallow: http://profile.adultfriendfinder.com/p/member.cgi?fromPage=&mid=55829490_97842
Pattern should either be empty, start with "/" or "*"
67
Disallow: http://profile.adultfriendfinder.com/view/25489010_14893.html?pid=g899570-pct.subtitlelink&pg=0
Pattern should either be empty, start with "/" or "*"
68
Disallow: http://personals.ugo.com/p/member.cgi?site=ffadult&dcb=personals.ugo.com&fromPage=magazine&mid=115767602_37139
Pattern should either be empty, start with "/" or "*"
69
Disallow: http://profile.passion.com/p/member.cgi?dcb=passion&fromPage=&mid=51936284_65515
Pattern should either be empty, start with "/" or "*"
70
Disallow: http://profile.passion.com/p/member.cgi?dcb=passion&mid=148374312_84991
Pattern should either be empty, start with "/" or "*"
71
Disallow: http://profile.xmatch.com/p/member.cgi?site=ffadult&dcb=xmatch&mid=132898470_36898&askmeforaphoto=1
Pattern should either be empty, start with "/" or "*"
72
Disallow: http://personals.nwsource.com/p/member.cgi?site=ffadult&dcb=personals.nwsource.com&fromPage=&mid=148641326_62004
Pattern should either be empty, start with "/" or "*"

Mobile Friendly

Tap targets are not sized appropriately — 39% 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.
Tap Target Size Overlapping Target
24x14
24x14
115x16
38x14
43x14
54x14
24x14

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 passion.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 passion.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: 69.165.107.69
Continent: North America
Country: United States
United States Flag
Region: California
City: San Jose
Longitude: -121.8208
Latitude: 37.3692
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
FriendFinder Networks Inc
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
GoDaddy.com, LLC 104.104.70.214
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: *.passion.com
Issued By: R3
Valid From: 21st December, 2021
Valid To: 21st March, 2022
Subject: CN = *.passion.com
Hash: c7d4de46
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03A3E260DB80626549FE6D61024BF025B4D7
Serial Number (Hex): 03A3E260DB80626549FE6D61024BF025B4D7
Valid From: 21st December, 2024
Valid To: 21st March, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: 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 : Dec 21 19:39:39.195 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:77:15:3E:D2:D3:DD:41:94:9A:93:11:DA:
31:68:AB:8C:07:FC:30:9F:1B:0C:9F:3B:F9:B8:D7:28:
90:9F:7E:EF:02:20:65:87:58:9F:E0:43:10:17:CD:FA:
87:7F:33:E8:30:CB:B4:AC:F2:48:22:FF:F0:6C:D6:CD:
27:02:DC:5F:74:B0
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 : Dec 21 19:39:39.192 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:DC:EA:2F:A5:84:E1:B9:65:B2:14:99:
1E:9E:4F:7A:11:3A:7C:44:3D:DB:2D:14:74:D2:2A:C8:
54:17:A7:CD:BC:02:20:59:D7:59:5F:B6:21:C0:D3:BE:
A4:2A:43:4C:49:91:5C:A2:51:43:DC:FB:84:93:96:3B:
62:F5:BD:E3:20:9B:52
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:passion.com
DNS:*.passion.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
passion.com. 69.165.107.69 IN 299

NS Records

Host Nameserver Class TTL
passion.com. pdns4.ultradns.org. IN 3599
passion.com. pdns5.ultradns.info. IN 3599
passion.com. pdns1.ultradns.net. IN 3599
passion.com. pdns2.ultradns.net. IN 3599
passion.com. pdns3.ultradns.org. IN 3599
passion.com. pdns6.ultradns.co.uk. IN 3599

MX Records

Priority Host Server Class TTL
20 passion.com. mx2.friendfinder.com. IN 3599
20 passion.com. mx1.friendfinder.com. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
passion.com. ii53-30.friendfinderinc.com. ops.friendfinderinc.com. 3599

TXT Records

Host Value Class TTL
passion.com. v=spf1 IN 499

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 21st February, 2022
Server: Apache
Content-Type: text/html;charset=UTF-8
Set-Cookie: *
X-PERF: 0.110503,0.022195,TS_22_0.0177740,TM_25_0.0171860,DB_11_0.0047690,CD_35_0.0041390,FS_19_0.0057210,PK_3_0.0000710,CE_44_0.0386480
Strict-Transport-Security: max-age=300; includeSubDomains
X-Frame-Options: SAMEORIGIN
ETag: TESTBED
P3P: CP="DSP LAW"
Content-Length: 27830
X-ApacheServer: si108-253.friendfinderinc.com
Vary: Accept-Encoding

Whois Lookup

Created: 20th April, 1995
Changed: 22nd April, 2021
Expires: 21st April, 2022
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: pdns1.ultradns.net
pdns2.ultradns.net
pdns3.ultradns.org
pdns4.ultradns.org
pdns5.ultradns.info
pdns6.ultradns.co.uk
Owner Organization: Various, Inc
Owner State: California
Owner Country: US
Owner Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=PASSION.COM
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=PASSION.COM
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=PASSION.COM
Full Whois: Domain Name: PASSION.COM
Registry Domain ID: 311517_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2021-04-22T09:27:52Z
Creation Date: 1995-04-20T23:00:00Z
Registrar Registration Expiration Date: 2022-04-21T23:00:00Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registrant Organization: Various, Inc
Registrant State/Province: California
Registrant Country: US
Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=PASSION.COM
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=PASSION.COM
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=PASSION.COM
Name Server: PDNS3.ULTRADNS.ORG
Name Server: PDNS2.ULTRADNS.NET
Name Server: PDNS5.ULTRADNS.INFO
Name Server: PDNS6.ULTRADNS.CO.UK
Name Server: PDNS1.ULTRADNS.NET
Name Server: PDNS4.ULTRADNS.ORG
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-02-21T18:23:18Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

Nameservers

Name IP Address
pdns1.ultradns.net 204.74.108.1
pdns2.ultradns.net 204.74.109.1
pdns3.ultradns.org 199.7.68.1
pdns4.ultradns.org 199.7.69.1
pdns5.ultradns.info 204.74.114.1
pdns6.ultradns.co.uk 204.74.115.1
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$8,126 USD 3/5
$998 USD 2/5
$9,387 USD 3/5
0/5
$684 USD 1/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
$345,517 USD 3/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$724 USD 2/5
$11,158,831 USD 5/5
$412 USD 1/5
$738 USD 2/5
$672 USD 1/5