fuckbookmobile.com

fuckbookmobile.com is SSL secured

Free website and domain report on fuckbookmobile.com

Last Updated: 23rd October, 2024 Update Now
Overview

Snoop Summary for fuckbookmobile.com

This is a free and comprehensive report about fuckbookmobile.com. The domain fuckbookmobile.com is currently hosted on a server located in Virginia in United States with the IP address 35.184.135.239, where USD is the local currency and the local language is English. Our records indicate that fuckbookmobile.com is privately registered by REDACTED FOR PRIVACY. Fuckbookmobile.com is expected to earn an estimated $16 USD per day from advertising revenue. The sale of fuckbookmobile.com would possibly be worth $11,740 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Fuckbookmobile.com receives an estimated 5,638 unique visitors every day - a huge amount of traffic! This report was last updated 23rd October, 2024.

What is fuckbookmobile.com?

Fuckbookmobile.com is a hook-ups site where you can have online discussions and meet others for dates and hookups. We advise against visiting websites like fuckbookmobile.com due to their potentially risky nature.

About fuckbookmobile.com

Site Preview:
Title: Fuckbook - Are you looking for pleasure?
Description: Fuckbook is a one-of-a-kind platform that offers an exciting way to explore your deepest desires and fantasies. With a variety of free adult features, Fuckbook allows you to embark on thrilling erotic adventures and indulge in your wildest dreams.
Keywords and Tags: adult content, adult dating, booty call, casual dating, chat, free personals, fuckbook, hook up online, online dating, online hookups, personals, photo, popular, pornography, sex, singles, swinger
Related Terms: embark, embark portal, fuckbook app, fuckbook com, fuckbook login, fuckbook net, fuckbook search, fuckbookmobile, what is fuckbook, www fuckbook com
Fav Icon:
Age: Over 14 years old
Domain Created: 18th January, 2010
Domain Updated: 20th October, 2024
Domain Expires: 18th January, 2025
Review

Snoop Score

3/5 (Great!)

Valuation

$11,740 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 95,587
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: 5,638
Monthly Visitors: 171,603
Yearly Visitors: 2,057,870
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $16 USD
Monthly Revenue: $489 USD
Yearly Revenue: $5,865 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: fuckbookmobile.com 18
Domain Name: fuckbookmobile 14
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 4.78 seconds
Load Time Comparison: Faster than 8% of sites

PageSpeed Insights

Avg. (All Categories) 84
Performance 88
Accessibility 82
Best Practices 83
SEO 90
PWA 78
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.fuckbookdating.net/en/
Updated: 15th December, 2022

2.99 seconds
First Contentful Paint (FCP)
52%
27%
21%

0.01 seconds
First Input Delay (FID)
99%
1%
0%

88

Performance

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

Metrics

Time to Interactive — 1.9 s
The time taken for the page to become fully interactive.
Total Blocking Time — 70 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
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources — Potential savings of 60 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Fuckbookmobile.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://1118660075.rsc.cdn77.org/vendor-css/en/375/1671087908/all.css
6192
230
https://1118660075.rsc.cdn77.org/library-css/en/375/1671087908/all.css
44091
80
Properly size images
Images can slow down the page's load time. Fuckbookmobile.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Fuckbookmobile.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Fuckbookmobile.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Fuckbookmobile.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 41 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Fuckbookmobile.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://1118660075.rsc.cdn77.org/library-css/en/375/1671087908/all.css
44091
41661
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 20 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://1118660075.rsc.cdn77.org/layout/en/100/1671087908/img/index/version9/wallpaper.jpg
54312
20303.45
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 510 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.fuckbookdating.net/en/
509.628
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Fuckbookmobile.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 6 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://1118660075.rsc.cdn77.org/vendor-js/en/375/1671087908/after-body.js
5707
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://1118660075.rsc.cdn77.org/layout/en/100/1671087908/img/index/version9/wallpaper.jpg
0
Avoids enormous network payloads — Total size was 545 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://1118660075.rsc.cdn77.org/vendor-js/en/375/1671087908/after-body.js
224274
https://cdn.onesignal.com/sdks/OneSignalPageSDKES6.js?v=151514
69710
https://1118660075.rsc.cdn77.org/layout/en/100/1671087908/img/index/version9/wallpaper.jpg
54774
https://1118660075.rsc.cdn77.org/library-js/en/375/1671087908/library.js
48682
https://1118660075.rsc.cdn77.org/library-css/en/375/1671087908/all.css
44091
https://www.googletagmanager.com/gtm.js?id=GTM-TX583L
40446
https://1118660075.rsc.cdn77.org/static/font/icon-webfont.woff?1671087908
25224
https://www.google-analytics.com/analytics.js
20664
https://www.fuckbookdating.net/en/
9466
https://1118660075.rsc.cdn77.org/vendor-css/en/375/1671087908/all.css
6192
Avoids an excessive DOM size — 392 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
392
Maximum DOM Depth
18
Maximum Child Elements
84
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Fuckbookmobile.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.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.fuckbookdating.net/en/
180.336
15.481
2.649
https://1118660075.rsc.cdn77.org/vendor-js/en/375/1671087908/after-body.js
164.685
142.757
12.173
Minimizes main-thread work — 0.5 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
241.492
Other
90.178
Style & Layout
74.981
Parse HTML & CSS
39.402
Script Parsing & Compilation
27.069
Rendering
13.328
Keep request counts low and transfer sizes small — 22 requests • 545 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
22
558284
Script
8
413179
Image
4
57429
Stylesheet
2
50283
Font
1
25224
Document
1
9466
Other
6
2703
Media
0
0
Third-party
20
548450
Minimize third-party usage — Third-party code blocked the main thread for 40 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)
411281
37.487
73051
0
40446
0
21287
0
694
0
673
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://1118660075.rsc.cdn77.org/vendor-js/en/375/1671087908/after-body.js
1740
137
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of fuckbookmobile.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://fuckbookmobile.com/
http/1.1
0
106.54100007378
258
0
301
text/html
https://fuckbookmobile.com/
http/1.1
106.91700014286
374.43300010636
353
0
302
text/html
https://www.fuckbookmobile.com/en/
http/1.1
375.84200012498
866.85200012289
407
0
302
text/html
https://www.fuckbookdating.net/en/site-redirect?session=03c15d01b5e905a3836d2409a9c2c286
http/1.1
867.17400001362
1334.8720001522
368
0
302
text/html
https://www.fuckbookdating.net/en/
h2
1335.3540000971
1843.9910002053
9466
37017
200
text/html
Document
https://1118660075.rsc.cdn77.org/vendor-css/en/375/1671087908/all.css
h2
1854.6970000025
1913.4230001364
6192
26511
200
text/css
Stylesheet
https://1118660075.rsc.cdn77.org/library-css/en/375/1671087908/all.css
h2
1854.9409999978
1918.0080001242
44091
293188
200
text/css
Stylesheet
https://1118660075.rsc.cdn77.org/vendor-js/en/375/1671087908/before-body.js
h2
1855.1750001498
1891.4650001097
4337
10967
200
application/x-javascript
Script
https://1118660075.rsc.cdn77.org/vendor-js/en/375/1671087908/after-body.js
h2
1855.435000034
1912.1240000241
224274
804092
200
application/x-javascript
Script
https://1118660075.rsc.cdn77.org/library-js/en/375/1671087908/library.js
h2
1855.6860000826
1892.1270000283
48682
207749
200
application/x-javascript
Script
https://1118660075.rsc.cdn77.org/library-js/en/375/1671087908/translations/1590572550.js
h2
1855.9260000475
1877.329000039
1725
4098
200
application/x-javascript
Script
https://cdn.onesignal.com/sdks/OneSignalSDK.js
h2
1875.7470001001
1899.3810000829
3341
9138
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
1948.1300001498
1963.2490000222
20664
50230
200
text/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-TX583L
h2
1949.0420001093
1963.8870002236
40446
101631
200
application/javascript
Script
https://1118660075.rsc.cdn77.org/layout/en/100/1671087908/img/index/version9/wallpaper.jpg
h2
1964.4970002118
1976.1720001698
54774
54312
200
image/jpeg
Image
https://1118660075.rsc.cdn77.org/static/font/icon-webfont.woff?1671087908
h2
1991.60700012
2007.3430000339
25224
24768
200
application/octet-stream
Font
https://cdn.onesignal.com/sdks/OneSignalPageSDKES6.js?v=151514
h2
2185.7200001832
2214.0400002245
69710
289928
200
application/javascript
Script
https://1118660075.rsc.cdn77.org/layout/en/100/1671087908/img/checkbox.svg
h2
2225.1900001429
2284.6830000635
906
622
200
image/svg+xml
Image
https://1118660075.rsc.cdn77.org/layout/en/375/1671087908/img/flags/us.png
h2
2250.6710002199
2285.0620001554
1076
609
200
image/png
Image
https://www.google-analytics.com/j/collect?v=1&_v=j98&aip=1&a=1801486447&t=pageview&_s=1&dl=https%3A%2F%2Fwww.fuckbookdating.net%2Fen%2F&dp=%2F&ul=en-us&de=UTF-8&dt=Fuckbook%20-%20Are%20you%20looking%20for%20pleasure%3F&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAAABAAAAACAAI~&jid=1833840736&gjid=125778179&cid=1650073952.1671136219&tid=UA-1769378-2&_gid=1055857771.1671136219&_r=1&_slc=1&cd1=false&z=1481620360
h2
2277.6030001696
2281.0780000873
623
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j98&tid=UA-1769378-2&cid=1650073952.1671136219&jid=1833840736&gjid=125778179&_gid=1055857771.1671136219&_u=YEBAAAAAAAAAACAAI~&z=1353289845
h2
2326.4150000177
2331.6440000199
694
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j98&tid=UA-1769378-2&cid=1650073952.1671136219&jid=1833840736&_u=YEBAAAAAAAAAACAAI~&z=205288632
h2
2357.8210000414
2377.57900008
673
42
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1849.031
24.653
1920.102
8.897
1931.435
6.977
1938.544
19.976
1958.986
48.044
2015.602
18.043
2033.68
137.056
2170.973
6.516
2179.132
8.119
2187.277
65.862
2253.219
25.978
2279.224
24.934
2304.268
8.274
2334.905
21.613
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 — 1.2 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.8 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.6 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 140 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.6 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused JavaScript — Potential savings of 241 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://1118660075.rsc.cdn77.org/vendor-js/en/375/1671087908/after-body.js
224274
131173
https://cdn.onesignal.com/sdks/OneSignalPageSDKES6.js?v=151514
69710
61094
https://1118660075.rsc.cdn77.org/library-js/en/375/1671087908/library.js
48682
27977
https://www.googletagmanager.com/gtm.js?id=GTM-TX583L
40446
26894
Serve static assets with an efficient cache policy — 3 resources found
Fuckbookmobile.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.google-analytics.com/analytics.js
7200000
20664
https://cdn.onesignal.com/sdks/OneSignalPageSDKES6.js?v=151514
259200000
69710
https://cdn.onesignal.com/sdks/OneSignalSDK.js
259200000
3341

Other

Avoid multiple page redirects — Potential savings of 800 ms
Redirects can cause additional delays before the page can begin loading. Fuckbookmobile.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://fuckbookmobile.com/
190
https://fuckbookmobile.com/
150
https://www.fuckbookmobile.com/en/
230
https://www.fuckbookdating.net/en/site-redirect?session=03c15d01b5e905a3836d2409a9c2c286
230
https://www.fuckbookdating.net/en/
0
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://1118660075.rsc.cdn77.org/static/font/icon-webfont.woff?1671087908
15.735999913886
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
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
82

Accessibility

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

Navigation

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

ARIA

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

Tables and lists

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

Names and labels

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

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

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements

Contrast

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

Best practices

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

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
FlotCharts
0.8.3
jQuery
2.2.4
Modernizr
3.12.0
Backbone
1.1.2
Underscore
1.7.0
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.
URL Map URL
https://cdn.onesignal.com/sdks/OneSignalSDK.js
https://cdn.onesignal.com/sdks/OneSignalSDK.js.map
https://cdn.onesignal.com/sdks/OneSignalPageSDKES6.js?v=151514
https://cdn.onesignal.com/sdks/OneSignalPageSDKES6.js.map
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://fuckbookmobile.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 5 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
4
Medium
1
Medium
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for fuckbookmobile.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 fuckbookmobile.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.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Crawling and Indexing

Page is 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.
Blocking Directive Source

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

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

Installable

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

PWA Optimized

Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets 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
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 fuckbookmobile.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
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) 76
Performance 45
Accessibility 84
Best Practices 83
SEO 87
PWA 80
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.fuckbookdating.net/en/
Updated: 15th December, 2022

4.50 seconds
First Contentful Paint (FCP)
37%
25%
38%

0.02 seconds
First Input Delay (FID)
93%
5%
2%

45

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for fuckbookmobile.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. Fuckbookmobile.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Fuckbookmobile.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Fuckbookmobile.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Fuckbookmobile.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 290 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.fuckbookdating.net/en/
288.282
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Fuckbookmobile.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 6 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://1118660075.rsc.cdn77.org/vendor-js/en/375/1671087908/after-body.js
5707
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://1118660075.rsc.cdn77.org/layout/en/100/1671087908/img/index/version9/wallpaper.jpg
0
Avoids enormous network payloads — Total size was 545 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://1118660075.rsc.cdn77.org/vendor-js/en/375/1671087908/after-body.js
224275
https://cdn.onesignal.com/sdks/OneSignalPageSDKES6.js?v=151514
69710
https://1118660075.rsc.cdn77.org/layout/en/100/1671087908/img/index/version9/wallpaper.jpg
54776
https://1118660075.rsc.cdn77.org/library-js/en/375/1671087908/library.js
48683
https://1118660075.rsc.cdn77.org/library-css/en/375/1671087908/all.css
44093
https://www.googletagmanager.com/gtm.js?id=GTM-TX583L
40447
https://1118660075.rsc.cdn77.org/static/font/icon-webfont.woff?1671087908
25226
https://www.google-analytics.com/analytics.js
20664
https://www.fuckbookdating.net/en/
9440
https://1118660075.rsc.cdn77.org/vendor-css/en/375/1671087908/all.css
6194
Avoids an excessive DOM size — 392 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
392
Maximum DOM Depth
18
Maximum Child Elements
84
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Fuckbookmobile.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 1.1 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://1118660075.rsc.cdn77.org/vendor-js/en/375/1671087908/after-body.js
675.308
578.912
61.176
https://www.fuckbookdating.net/en/
525.572
26.728
14.548
Unattributable
195.476
8.144
0
https://www.google-analytics.com/analytics.js
166.392
149.5
6.168
https://1118660075.rsc.cdn77.org/library-js/en/375/1671087908/library.js
98.932
80.396
17.856
https://cdn.onesignal.com/sdks/OneSignalPageSDKES6.js?v=151514
75.82
53.548
21.42
https://www.googletagmanager.com/gtm.js?id=GTM-TX583L
67.672
52.04
9.944
https://1118660075.rsc.cdn77.org/library-css/en/375/1671087908/all.css
52.46
0
0
Minimizes main-thread work — 1.9 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
975.5
Other
382.904
Style & Layout
250.604
Script Parsing & Compilation
134.62
Parse HTML & CSS
100.664
Rendering
54.592
Keep request counts low and transfer sizes small — 22 requests • 545 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
22
558289
Script
8
413186
Image
4
57435
Stylesheet
2
50287
Font
1
25226
Document
1
9440
Other
6
2715
Media
0
0
Third-party
20
548482
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.
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 — 8 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://1118660075.rsc.cdn77.org/vendor-js/en/375/1671087908/after-body.js
6330
394
https://www.google-analytics.com/analytics.js
3930
146
https://www.googletagmanager.com/gtm.js?id=GTM-TX583L
6724
146
https://1118660075.rsc.cdn77.org/library-js/en/375/1671087908/library.js
6930
123
https://www.fuckbookdating.net/en/
2908
79
https://cdn.onesignal.com/sdks/OneSignalPageSDKES6.js?v=151514
5176
76
https://www.fuckbookdating.net/en/
683
58
https://1118660075.rsc.cdn77.org/library-css/en/375/1671087908/all.css
4680
52
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of fuckbookmobile.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://fuckbookmobile.com/
http/1.1
0
83.046999759972
243
0
301
text/html
https://fuckbookmobile.com/
http/1.1
83.53800047189
319.08799987286
367
0
302
text/html
https://www.fuckbookmobile.com/en/
http/1.1
319.42300032824
632.14300014079
421
0
302
text/html
https://www.fuckbookdating.net/en/site-redirect?session=8ae0aaa673ec48c701f4c1e05145c1c1
http/1.1
632.58500024676
947.78999965638
367
0
302
text/html
https://www.fuckbookdating.net/en/
h2
948.19799996912
1235.4840002954
9440
37017
200
text/html
Document
https://1118660075.rsc.cdn77.org/vendor-css/en/375/1671087908/all.css
h2
1244.8120005429
1321.27400022
6194
26511
200
text/css
Stylesheet
https://1118660075.rsc.cdn77.org/library-css/en/375/1671087908/all.css
h2
1245.0390001759
1357.7920002863
44093
293188
200
text/css
Stylesheet
https://1118660075.rsc.cdn77.org/vendor-js/en/375/1671087908/before-body.js
h2
1245.4340001568
1305.0969997421
4339
10967
200
application/x-javascript
Script
https://1118660075.rsc.cdn77.org/vendor-js/en/375/1671087908/after-body.js
h2
1245.7530004904
1388.6360004544
224275
804092
200
application/x-javascript
Script
https://1118660075.rsc.cdn77.org/library-js/en/375/1671087908/library.js
h2
1246.0270002484
1343.9899999648
48683
207749
200
application/x-javascript
Script
https://1118660075.rsc.cdn77.org/library-js/en/375/1671087908/translations/1590572550.js
h2
1246.305000037
1314.9890005589
1727
4098
200
application/x-javascript
Script
https://cdn.onesignal.com/sdks/OneSignalSDK.js
h2
1251.7769997939
1287.5490002334
3341
9138
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
1381.9289999083
1391.7209999636
20664
50230
200
text/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-TX583L
h2
1383.7870005518
1400.4889996722
40447
101631
200
application/javascript
Script
https://1118660075.rsc.cdn77.org/layout/en/100/1671087908/img/index/version9/wallpaper.jpg
h2
1391.4769999683
1443.4409998357
54776
54312
200
image/jpeg
Image
https://1118660075.rsc.cdn77.org/static/font/icon-webfont.woff?1671087908
h2
1404.6740001068
1440.6359996647
25226
24768
200
application/octet-stream
Font
https://www.google-analytics.com/j/collect?v=1&_v=j98&aip=1&a=572020954&t=pageview&_s=1&dl=https%3A%2F%2Fwww.fuckbookdating.net%2Fen%2F&dp=%2F&ul=en-us&de=UTF-8&dt=Fuckbook%20-%20Are%20you%20looking%20for%20pleasure%3F&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAAABAAAAACAAI~&jid=179488406&gjid=2121515949&cid=677544036.1671136251&tid=UA-1769378-2&_gid=1729813584.1671136251&_r=1&_slc=1&cd1=false&z=326388492
h2
1491.054000333
1495.4280005768
623
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j98&tid=UA-1769378-2&cid=677544036.1671136251&jid=179488406&gjid=2121515949&_gid=1729813584.1671136251&_u=YEBAAAAAAAAAACAAI~&z=1385687884
h2
1619.2380003631
1627.1210005507
694
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j98&tid=UA-1769378-2&cid=677544036.1671136251&jid=179488406&_u=YEBAAAAAAAAAACAAI~&z=1880096697
h2
1657.5170001015
1678.883000277
673
42
200
image/gif
Image
https://cdn.onesignal.com/sdks/OneSignalPageSDKES6.js?v=151514
h2
1662.5850005075
1705.8950001374
69710
289928
200
application/javascript
Script
https://1118660075.rsc.cdn77.org/layout/en/100/1671087908/img/checkbox.svg
h2
1705.2710000426
1727.3519998416
908
622
200
image/svg+xml
Image
https://1118660075.rsc.cdn77.org/layout/en/375/1671087908/img/flags/us.png
h2
1734.7729997709
1755.3369998932
1078
609
200
image/png
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1239.901
11.62
1360.286
13.115
1373.615
6.103
1381.205
5.356
1386.741
39.41
1433.544
9.936
1448.461
7.936
1456.474
36.416
1494.144
10.103
1504.651
11.913
1516.582
98.454
1623.535
30.692
1658.162
6.111
1664.322
72.766
1738.875
28.952
1789.848
18.955
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

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

Other

Eliminate render-blocking resources — Potential savings of 250 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Fuckbookmobile.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://1118660075.rsc.cdn77.org/vendor-css/en/375/1671087908/all.css
6194
780
https://1118660075.rsc.cdn77.org/library-css/en/375/1671087908/all.css
44093
300
Reduce unused CSS — Potential savings of 41 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Fuckbookmobile.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://1118660075.rsc.cdn77.org/library-css/en/375/1671087908/all.css
44093
41857
Serve images in next-gen formats — Potential savings of 20 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://1118660075.rsc.cdn77.org/layout/en/100/1671087908/img/index/version9/wallpaper.jpg
54312
20303.45
Serve static assets with an efficient cache policy — 3 resources found
Fuckbookmobile.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.google-analytics.com/analytics.js
7200000
20664
https://cdn.onesignal.com/sdks/OneSignalPageSDKES6.js?v=151514
259200000
69710
https://cdn.onesignal.com/sdks/OneSignalSDK.js
259200000
3341

Metrics

First Contentful Paint — 3.9 s
The time taken for the first image or text on the page to be rendered.
Total Blocking Time — 610 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 — 7.1 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 390 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 4.1 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused JavaScript — Potential savings of 241 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://1118660075.rsc.cdn77.org/vendor-js/en/375/1671087908/after-body.js
224275
131173
https://cdn.onesignal.com/sdks/OneSignalPageSDKES6.js?v=151514
69710
61094
https://1118660075.rsc.cdn77.org/library-js/en/375/1671087908/library.js
48683
27978
https://www.googletagmanager.com/gtm.js?id=GTM-TX583L
40447
26895
Avoid multiple page redirects — Potential savings of 2,670 ms
Redirects can cause additional delays before the page can begin loading. Fuckbookmobile.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://fuckbookmobile.com/
630
https://fuckbookmobile.com/
480
https://www.fuckbookmobile.com/en/
780
https://www.fuckbookdating.net/en/site-redirect?session=8ae0aaa673ec48c701f4c1e05145c1c1
780
https://www.fuckbookdating.net/en/
0
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://1118660075.rsc.cdn77.org/static/font/icon-webfont.woff?1671087908
35.961999557912
Reduce the impact of third-party code — Third-party code blocked the main thread for 580 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)
411299
494.984
21287
85.964
73051
2.948
40447
0
694
0
673
0
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
First Contentful Paint (3G) — 7680 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
84

Accessibility

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

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.

Names and labels

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

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

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
FlotCharts
0.8.3
jQuery
2.2.4
Modernizr
3.12.0
Backbone
1.1.2
Underscore
1.7.0
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.
URL Map URL
https://cdn.onesignal.com/sdks/OneSignalSDK.js
https://cdn.onesignal.com/sdks/OneSignalSDK.js.map
https://cdn.onesignal.com/sdks/OneSignalPageSDKES6.js?v=151514
https://cdn.onesignal.com/sdks/OneSignalPageSDKES6.js.map
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://fuckbookmobile.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 5 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
4
Medium
1
Medium
87

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for fuckbookmobile.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 fuckbookmobile.com on mobile screens.
Document uses legible font sizes — 99.55% 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
.fancySelect .fancySelect-select .labelPrefix
0.45%
10px
99.55%
≥ 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.
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.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Crawling and Indexing

Page is 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.
Blocking Directive Source

Mobile Friendly

Tap targets are not sized appropriately — 46% 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
38x38
28x16
60x16
57x16
48x16
48x16
37x16
38x16
37x16
44x16
52x16
45x16

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

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

Installable

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

PWA Optimized

Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets 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
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 fuckbookmobile.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
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: 35.184.135.239
Continent: North America
Country: United States
United States Flag
Region: Virginia
City:
Longitude: -77.2497
Latitude: 38.6582
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Google LLC
Registration

Domain Registrant

Private Registration: Yes
Name: REDACTED FOR PRIVACY
Organization:
Country: FR
City: Paris
State: Paris
Post Code: 75013
Email: 4060b1770db0197b83b1f589320b1431-3609191@contact.gandi.net
Phone: +33.170377666
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Gandi SAS 146.75.29.103
Security

Visitor Safety

Mature Content: Yes
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 80/100
WOT Child Safety: 10/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.fuckbookmobile.com
Issued By: R11
Valid From: 11th August, 2024
Valid To: 9th November, 2024
Subject: CN = *.fuckbookmobile.com
Hash: 76042ddc
Issuer: CN = R11
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x046EA042341D44D30776811B07DC72158098
Serial Number (Hex): 046EA042341D44D30776811B07DC72158098
Valid From: 11th August, 2024
Valid To: 9th November, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
Timestamp : Aug 11 21:33:52.252 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:44:AD:C6:6B:8C:5D:94:FC:B5:05:EA:C3:
6D:44:94:FE:A0:A7:D0:95:A7:47:3D:FF:89:D2:70:0D:
CA:48:F7:EA:02:20:23:43:25:46:D5:98:AE:79:39:BE:
63:4C:69:5F:B8:C6:D8:43:A1:18:20:97:83:7F:CE:30:
D9:5A:B7:19:1A:49
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
Timestamp : Aug 11 21:33:52.258 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:C0:8D:C7:35:F5:8D:E6:1B:65:7B:AF:
12:FB:60:44:C8:92:FD:82:EF:9E:9D:FB:6A:8B:AE:CB:
7A:6F:4E:58:88:02:20:71:4F:98:C1:59:3D:16:21:11:
0E:58:EE:28:39:8F:45:B7:71:02:D0:AE:6C:64:F2:43:
9F:90:93:90:6A:BE:DE
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:fuckbookmobile.com
DNS:*.fuckbookmobile.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
fuckbookmobile.com. 35.184.135.239 IN 3600

NS Records

Host Nameserver Class TTL
fuckbookmobile.com. ns-1215.awsdns-23.org. IN 21600
fuckbookmobile.com. ns-1783.awsdns-30.co.uk. IN 21600
fuckbookmobile.com. ns-322.awsdns-40.com. IN 21600
fuckbookmobile.com. ns-801.awsdns-36.net. IN 21600

MX Records

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

SOA Records

Domain Name Primary NS Responsible Email TTL
fuckbookmobile.com. ns-801.awsdns-36.net. awsdns-hostmaster.amazon.com. 900

TXT Records

Host Value Class TTL
fuckbookmobile.com. v=spf1 IN 3600
fuckbookmobile.com. google-site-verification=yABOsbClFKlDJnm5lGFNlevdAcBGSwWIWDwk-TrH1uw IN 3600
fuckbookmobile.com. google-site-verification=NxspEZ2qD7xAaisvh3vY81JNeLShsazoKf75s5RQCA8 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/2 302
server: nginx
date: 23rd October, 2024
content-type: text/html; charset=UTF-8
cache-control: no-store, must-revalidate
location: https://www.fuckbookmobile.com/en/
set-cookie: *
strict-transport-security: max-age=31536000;

Whois Lookup

Created: 18th January, 2010
Changed: 20th October, 2024
Expires: 18th January, 2025
Registrar: GANDI SAS
Status: clientTransferProhibited
Nameservers: ns-1215.awsdns-23.org
ns-1783.awsdns-30.co.uk
ns-322.awsdns-40.com
ns-801.awsdns-36.net
Owner Name: REDACTED FOR PRIVACY
Owner Street: 63-65 boulevard Massena
Owner Post Code: 75013
Owner City: Paris
Owner State: Paris
Owner Country: FR
Owner Phone: +33.170377666
Owner Email: 4060b1770db0197b83b1f589320b1431-3609191@contact.gandi.net
Admin Name: REDACTED FOR PRIVACY
Admin Street: 63-65 boulevard Massena
Admin Post Code: 75013
Admin City: Paris
Admin State: Paris
Admin Country: FR
Admin Phone: +33.170377666
Admin Email: 4060b1770db0197b83b1f589320b1431-3609191@contact.gandi.net
Tech Name: REDACTED FOR PRIVACY
Tech Street: 63-65 boulevard Massena
Tech Post Code: 75013
Tech City: Paris
Tech State: Paris
Tech Country: FR
Tech Phone: +33.170377666
Tech Email: 4060b1770db0197b83b1f589320b1431-3609191@contact.gandi.net
Full Whois: Domain Name: fuckbookmobile.com
Registry Domain ID: 1582254322_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.gandi.net
Registrar URL: http://www.gandi.net
Updated Date: 2024-10-20T14:07:06Z
Creation Date: 2010-01-18T15:00:56Z
Registrar Registration Expiration Date: 2025-01-18T16:00:56Z
Registrar: GANDI SAS
Registrar IANA ID: 81
Registrar Abuse Contact Email: abuse@support.gandi.net
Registrar Abuse Contact Phone: +33.170377661
Reseller: Amazon Registrar, Inc.
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status:
Domain Status:
Domain Status:
Domain Status:
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization:
Registrant Street: 63-65 boulevard Massena
Registrant City: Paris
Registrant State/Province: Paris
Registrant Postal Code: 75013
Registrant Country: FR
Registrant Phone: +33.170377666
Registrant Phone Ext:
Registrant Fax: +33.143730576
Registrant Fax Ext:
Registrant Email: 4060b1770db0197b83b1f589320b1431-3609191@contact.gandi.net
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization:
Admin Street: 63-65 boulevard Massena
Admin City: Paris
Admin State/Province: Paris
Admin Postal Code: 75013
Admin Country: FR
Admin Phone: +33.170377666
Admin Phone Ext:
Admin Fax: +33.143730576
Admin Fax Ext:
Admin Email: 4060b1770db0197b83b1f589320b1431-3609191@contact.gandi.net
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization:
Tech Street: 63-65 boulevard Massena
Tech City: Paris
Tech State/Province: Paris
Tech Postal Code: 75013
Tech Country: FR
Tech Phone: +33.170377666
Tech Phone Ext:
Tech Fax: +33.143730576
Tech Fax Ext:
Tech Email: 4060b1770db0197b83b1f589320b1431-3609191@contact.gandi.net
Name Server: NS-1783.AWSDNS-30.CO.UK
Name Server: NS-801.AWSDNS-36.NET
Name Server: NS-1215.AWSDNS-23.ORG
Name Server: NS-322.AWSDNS-40.COM
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
DNSSEC: Unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-10-23T07:15:11Z <<<

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

Reseller Email:
Reseller URL:

Personal data access and use are governed by French law, any use for the purpose of unsolicited mass commercial advertising as well as any mass or automated inquiries (for any intent other than the registration or modification of a domain name) are strictly forbidden. Copy of whole or part of our database without Gandi's endorsement is strictly forbidden.
A dispute over the ownership of a domain name may be subject to the alternate procedure established by the Registry in question or brought before the courts.
For additional information, please contact us via the following form:
https://www.gandi.net/support/contacter/mail/

Nameservers

Name IP Address
ns-1215.awsdns-23.org 205.251.196.191
ns-1783.awsdns-30.co.uk 205.251.198.247
ns-322.awsdns-40.com 205.251.193.66
ns-801.awsdns-36.net 205.251.195.33
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$3,711 USD 3/5
$4,531 USD 3/5
$2,835 USD 2/5
$3,197 USD 2/5
0/5