frndzcafe.net

frndzcafe.net is SSL secured

Free website and domain report on frndzcafe.net

Last Updated: 6th November, 2022 Update Now
Overview

Snoop Summary for frndzcafe.net

This is a free and comprehensive report about frndzcafe.net. The domain frndzcafe.net is currently hosted on a server located in United States with the IP address 206.233.165.165, where the local currency is USD and English is the local language. Our records indicate that frndzcafe.net is privately registered by Redacted for privacy. Frndzcafe.net has the potential to be earning an estimated $1 USD per day from advertising revenue. If frndzcafe.net was to be sold it would possibly be worth $855 USD (based on the daily revenue potential of the website over a 24 month period). Frndzcafe.net receives an estimated 406 unique visitors every day - a decent amount of traffic! This report was last updated 6th November, 2022.

About frndzcafe.net

Site Preview: frndzcafe.net frndzcafe.net
Title: OG真人注册-OG视讯真人注册
Description: OG真人注册是一家全球性的软件提供商,金融部门服务和增值数据.20多年了,OG真人注册一直在帮助其客户——资产管理公司,机构和另类资产管理公司,基金管理者和贷款和租赁机构,OG真人注册以创新和有效的解决方案迎接挑战.
Keywords and Tags: entertainment, og真人注册, og视讯真人注册
Related Terms:
Fav Icon:
Age: Over 2 years old
Domain Created: 5th September, 2021
Domain Updated: 5th September, 2022
Domain Expires: 5th September, 2023
Review

Snoop Score

1/5

Valuation

$855 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 2,757,256
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 11
Moz Page Authority: 33

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 406
Monthly Visitors: 12,357
Yearly Visitors: 148,190
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $35 USD
Yearly Revenue: $422 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: frndzcafe.net 13
Domain Name: frndzcafe 9
Extension (TLD): net 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 76
Performance 80
Accessibility 69
Best Practices 85
SEO 100
Progressive Web App 46
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
80

Performance

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

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
Time to Interactive — 0.9 s
The time taken for the page to become fully interactive.
First CPU Idle — 0.9 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive frndzcafe.net as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://frndzcafe.net/
0
921.16100003477
292
0
301
text/html
https://frndzcafe.net/
922.571000061
2322.5190000376
4569
4348
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=UA-139985968-1
2336.4600000205
2387.7920000814
30922
81746
200
application/javascript
Script
https://frndzcafe.net/themes/fonts.css
2336.66000003
3826.7240000423
581
329
200
text/css
Stylesheet
https://frndzcafe.net/themes/bootstrap/local.css
2336.8900000351
2641.5510000661
2214
9659
200
text/css
Stylesheet
https://frndzcafe.net/themes/audio.css
2337.1720000869
3537.9010000033
1218
6412
200
text/css
Stylesheet
https://frndzcafe.net/themes/styler.css
2337.4490001006
3870.3260000329
649
730
200
text/css
Stylesheet
https://frndzcafe.net/themes/Devilxxx.css
2338.2289999863
2954.0190000553
4144
24888
200
text/css
Stylesheet
https://frndzcafe.net/themes/fc_js.js
2338.4870000882
3840.4560000636
778
883
200
application/javascript
Script
https://frndzcafe.net/images/slogo.png
2338.5790000902
3548.3259999892
4715
4388
200
image/png
Image
https://frndzcafe.net/images/register_now.gif
2416.6250000708
3666.8690000661
4733
4406
200
image/gif
Image
https://images.dmca.com/Badges/_dmca_premi_badge_4.png?ID=521fda4a-7544-4e4c-bb11-8a8e35d0607f
3549.3940000888
3608.2370000659
4931
4535
200
image/png
Image
https://images.dmca.com/Badges/DMCABadgeHelper.min.js
2397.1140000504
2413.4410000406
778
465
200
application/javascript
Script
https://frndzcafe.net/images/copyright_proof.jpg
3609.3899999978
4214.7439999972
20011
19683
200
image/jpeg
Image
https://cdn.ywxi.net/js/1.js
3668.0990000023
3700.3750000149
4950
17366
200
text/javascript
Script
https://www.google-analytics.com/analytics.js
3702.1500000264
3707.2130000452
18767
45229
200
text/javascript
Script
https://www.google-analytics.com/r/collect?v=1&_v=j81&a=304809133&t=pageview&_s=1&dl=https%3A%2F%2Ffrndzcafe.net%2F&ul=en-us&de=UTF-8&dt=Mobile%20chat%2C%20Free%20chatrooms%2C%20Easy%20Text%20Dating&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUAB~&jid=1105937641&gjid=723745265&cid=1668468935.1588361998&tid=UA-139985968-1&_gid=669320104.1588361998&_r=1&gtm=2ou4m0&z=389476184
3738.70300001
3742.9860000266
553
35
200
image/gif
Image
https://s3-us-west-2.amazonaws.com/mfesecure-public/host/frndzcafe.net/client.json?source=jsmain
3890.0200000498
4255.7910000905
974
199
200
application/json
XHR
https://s3-us-west-2.amazonaws.com/mfesecure-public/host/frndzcafe.net/client.json?source=jsinline
3890.9880000865
4259.5730000176
974
199
200
application/json
XHR
https://www.trustedsite.com/rpc/ajax?do=tmjs-visit&host=frndzcafe.net&rand=1588361998969
4260.7150000986
4378.2080000965
689
6
200
text/javascript
Script
https://cdn.ywxi.net/meter/frndzcafe.net/205.svg?ts=1588321309280&l=en-US
4266.7020000517
4384.2690000311
7912
20606
200
image/svg+xml
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)
2358.678
8.813
2430.901
6.761
2438.224
10.922
3745.988
26.95
3905.101
7.808
3913.019
7.823
4289.738
7.706
4418.204
6.676
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 0 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Frndzcafe.net should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
https://frndzcafe.net/themes/fonts.css
581
70
https://frndzcafe.net/themes/bootstrap/local.css
2214
70
https://frndzcafe.net/themes/audio.css
1218
70
https://frndzcafe.net/themes/styler.css
649
70
https://frndzcafe.net/themes/Devilxxx.css
4144
70
https://frndzcafe.net/themes/fc_js.js
778
70
Properly size images
Images can slow down the page's load time. Frndzcafe.net should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Frndzcafe.net should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Frndzcafe.net should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Frndzcafe.net should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Frndzcafe.net should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images — Potential savings of 17 KB
Unoptimized images can consume more cellular data than what is necessary.
URL Size (Bytes) Potential Savings (Bytes)
https://frndzcafe.net/images/copyright_proof.jpg
19683
17074
Serve images in next-gen formats — Potential savings of 18 KB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Size (Bytes) Potential Savings (Bytes)
https://frndzcafe.net/images/copyright_proof.jpg
19683
18297
Enable text compression — Potential savings of 3 KB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Size (Bytes) Potential Savings (Bytes)
https://frndzcafe.net/
4348
2588
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 190 ms
Redirects can cause additional delays before the page can begin loading. Frndzcafe.net should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://frndzcafe.net/
0
https://frndzcafe.net/
190
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Frndzcafe.net 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.

Diagnostics

Avoids enormous network payloads — Total size was 113 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=UA-139985968-1
30922
https://frndzcafe.net/images/copyright_proof.jpg
20011
https://www.google-analytics.com/analytics.js
18767
https://cdn.ywxi.net/meter/frndzcafe.net/205.svg?ts=1588321309280&l=en-US
7912
https://cdn.ywxi.net/js/1.js
4950
https://images.dmca.com/Badges/_dmca_premi_badge_4.png?ID=521fda4a-7544-4e4c-bb11-8a8e35d0607f
4931
https://frndzcafe.net/images/register_now.gif
4733
https://frndzcafe.net/images/slogo.png
4715
https://frndzcafe.net/
4569
https://frndzcafe.net/themes/Devilxxx.css
4144
Avoids an excessive DOM size — 33 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
33
Maximum DOM Depth
6
Maximum Child Elements
9
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. Frndzcafe.net should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
Other
146.954
4.591
1.148
Minimizes main-thread work — 0.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
64.692
Script Evaluation
54.787
Rendering
41.213
Style & Layout
29.836
Script Parsing & Compilation
7.311
Parse HTML & CSS
6.504
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 21 requests • 113 KB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
21
115354
Script
6
56884
Image
6
42855
Stylesheet
5
8806
Document
1
4569
Other
3
2240
Media
0
0
Font
0
0
Third-party
10
71450
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 Size (Bytes) Main-Thread Blocking Time (Ms)
30922
0
19320
0
12862
0
1948
0

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.

Diagnostics

Serve static assets with an efficient cache policy — 15 resources found
Frndzcafe.net can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Size (Bytes)
https://www.trustedsite.com/rpc/ajax?do=tmjs-visit&host=frndzcafe.net&rand=1588361998969
0
689
https://frndzcafe.net/themes/Devilxxx.css
1000
4144
https://frndzcafe.net/themes/bootstrap/local.css
1000
2214
https://frndzcafe.net/themes/audio.css
1000
1218
https://frndzcafe.net/themes/fc_js.js
1000
778
https://frndzcafe.net/themes/styler.css
1000
649
https://frndzcafe.net/themes/fonts.css
1000
581
https://cdn.ywxi.net/js/1.js
94000
4950
https://cdn.ywxi.net/meter/frndzcafe.net/205.svg?ts=1588321309280&l=en-US
3592000
7912
https://www.google-analytics.com/analytics.js
7200000
18767
https://frndzcafe.net/images/copyright_proof.jpg
604800000
20011
https://frndzcafe.net/images/register_now.gif
604800000
4733
https://frndzcafe.net/images/slogo.png
604800000
4715
https://images.dmca.com/Badges/_dmca_premi_badge_4.png?ID=521fda4a-7544-4e4c-bb11-8a8e35d0607f
2592000000
4931
https://images.dmca.com/Badges/DMCABadgeHelper.min.js
2592000000
778

Metrics

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

Opportunities

Reduce server response times (TTFB) — Root document took 1,400 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
69

Accessibility

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

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Frndzcafe.net may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Frndzcafe.net may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Frndzcafe.net may provide relevant information that dialogue cannot, by using audio descriptions.

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.
`<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.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
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.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

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.

Contrast

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

Internationalization and localization

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

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
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.
85

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
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.
Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.
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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://frndzcafe.net/
Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
100

SEO

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

Manual Checks

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

Progressive Web App

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

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of frndzcafe.net on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://frndzcafe.net/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

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 79
Accessibility 69
Best Practices 85
SEO 97
Progressive Web App 48
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
79

Performance

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

Metrics

First Contentful Paint — 2.3 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 2.3 s
The time taken for the primary content of the page to be rendered.
Time to Interactive — 3.8 s
The time taken for the page to become fully interactive.
Max Potential First Input Delay — 120 ms
Users could experience a delay when interacting with the page.

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive frndzcafe.net as laggy when the latency is higher than 0.05 seconds.
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).
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://frndzcafe.net/
0
622.12699977681
307
0
301
text/html
https://frndzcafe.net/
622.72599991411
1910.7319999021
4569
4348
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=UA-139985968-1
1924.1139998194
1946.6849998571
30922
81746
200
application/javascript
Script
https://frndzcafe.net/themes/fonts.css
1924.3459999561
3129.0719998069
581
329
200
text/css
Stylesheet
https://frndzcafe.net/themes/bootstrap/local.css
1924.6549999807
3112.3059999663
2215
9659
200
text/css
Stylesheet
https://frndzcafe.net/themes/audio.css
1924.8639999423
3143.6379998922
1218
6412
200
text/css
Stylesheet
https://frndzcafe.net/themes/styler.css
1925.1259998418
3261.637999909
649
730
200
text/css
Stylesheet
https://frndzcafe.net/themes/Devilxxx.css
1925.2749998122
2231.7269998603
4144
24888
200
text/css
Stylesheet
https://frndzcafe.net/themes/fc_js.js
1925.5099999718
3183.662999887
778
883
200
application/javascript
Script
https://frndzcafe.net/images/slogo.png
1925.7590000052
3088.9519997872
4715
4388
200
image/png
Image
https://frndzcafe.net/images/register_now.gif
1975.7489999756
3176.2389999349
4733
4406
200
image/gif
Image
https://images.dmca.com/Badges/_dmca_premi_badge_4.png?ID=521fda4a-7544-4e4c-bb11-8a8e35d0607f
3092.8189998958
3111.6449998226
4931
4535
200
image/png
Image
https://images.dmca.com/Badges/DMCABadgeHelper.min.js
1952.6579999365
1969.6539998986
778
465
200
application/javascript
Script
https://frndzcafe.net/images/copyright_proof.jpg
3113.3249998093
4628.8449999411
20012
19683
200
image/jpeg
Image
https://cdn.ywxi.net/js/1.js
3177.4039999582
3193.9049998764
4950
17366
200
text/javascript
Script
https://www.google-analytics.com/analytics.js
3195.6209999043
3200.8639997803
18767
45229
200
text/javascript
Script
https://www.google-analytics.com/r/collect?v=1&_v=j81&a=173747433&t=pageview&_s=1&dl=https%3A%2F%2Ffrndzcafe.net%2F&ul=en-us&de=UTF-8&dt=Mobile%20chat%2C%20Free%20chatrooms%2C%20Easy%20Text%20Dating&sd=24-bit&sr=412x660&vp=980x1569&je=0&_u=IEBAAUAB~&jid=1603006869&gjid=794451445&cid=1805295938.1588362014&tid=UA-139985968-1&_gid=362589315.1588362014&_r=1&gtm=2ou4m0&z=549982703
3234.1279999819
3237.6489997841
553
35
200
image/gif
Image
https://s3-us-west-2.amazonaws.com/mfesecure-public/host/frndzcafe.net/client.json?source=jsmain
3315.4669997748
3689.7069998085
974
199
200
application/json
XHR
https://s3-us-west-2.amazonaws.com/mfesecure-public/host/frndzcafe.net/client.json?source=jsinline
3316.7209997773
3690.7259998843
974
199
200
application/json
XHR
https://www.trustedsite.com/rpc/ajax?do=tmjs-visit&host=frndzcafe.net&rand=1588362014348
3693.7819998711
3782.6309998054
689
6
200
text/javascript
Script
https://cdn.ywxi.net/meter/frndzcafe.net/205.svg?ts=1588321309280&l=en-US
3700.7459998131
3726.8189999741
7920
20606
200
image/svg+xml
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)
1935.437
8.463
1945.266
8.211
1975.202
7.843
1983.48
12.9
3226.296
30.263
3284.844
20.661
3305.607
26.537
3332.282
6.607
3712.034
7.787
3749.116
13.474
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 80 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Frndzcafe.net should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
https://frndzcafe.net/themes/fonts.css
581
180
https://frndzcafe.net/themes/bootstrap/local.css
2215
180
https://frndzcafe.net/themes/audio.css
1218
180
https://frndzcafe.net/themes/styler.css
649
180
https://frndzcafe.net/themes/Devilxxx.css
4144
180
https://frndzcafe.net/themes/fc_js.js
778
180
Properly size images
Images can slow down the page's load time. Frndzcafe.net should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Frndzcafe.net should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Frndzcafe.net should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Frndzcafe.net should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Frndzcafe.net should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images — Potential savings of 17 KB
Unoptimized images can consume more cellular data than what is necessary.
URL Size (Bytes) Potential Savings (Bytes)
https://frndzcafe.net/images/copyright_proof.jpg
19683
17074
Serve images in next-gen formats — Potential savings of 18 KB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Size (Bytes) Potential Savings (Bytes)
https://frndzcafe.net/images/copyright_proof.jpg
19683
18297
Enable text compression — Potential savings of 3 KB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Size (Bytes) Potential Savings (Bytes)
https://frndzcafe.net/
4348
2588
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. Frndzcafe.net should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://frndzcafe.net/
0
https://frndzcafe.net/
630
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Frndzcafe.net 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.

Diagnostics

Avoids enormous network payloads — Total size was 113 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=UA-139985968-1
30922
https://frndzcafe.net/images/copyright_proof.jpg
20012
https://www.google-analytics.com/analytics.js
18767
https://cdn.ywxi.net/meter/frndzcafe.net/205.svg?ts=1588321309280&l=en-US
7920
https://cdn.ywxi.net/js/1.js
4950
https://images.dmca.com/Badges/_dmca_premi_badge_4.png?ID=521fda4a-7544-4e4c-bb11-8a8e35d0607f
4931
https://frndzcafe.net/images/register_now.gif
4733
https://frndzcafe.net/images/slogo.png
4715
https://frndzcafe.net/
4569
https://frndzcafe.net/themes/Devilxxx.css
4144
Avoids an excessive DOM size — 33 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
33
Maximum DOM Depth
6
Maximum Child Elements
9
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. Frndzcafe.net should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
Other
831.624
17.056
4.5
https://www.google-analytics.com/analytics.js
118.472
113
5.472
https://www.googletagmanager.com/gtag/js?id=UA-139985968-1
90.844
79.932
10.912
https://cdn.ywxi.net/js/1.js
52.276
47.46
4.656
Minimizes main-thread work — 1.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
320.792
Script Evaluation
259.968
Style & Layout
238.336
Rendering
186.276
Parse HTML & CSS
64.824
Script Parsing & Compilation
30.004
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 21 requests • 113 KB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
21
115379
Script
6
56884
Image
6
42864
Stylesheet
5
8807
Document
1
4569
Other
3
2255
Media
0
0
Font
0
0
Third-party
10
71458
Minimize third-party usage — Third-party code blocked the main thread for 50 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 Size (Bytes) Main-Thread Blocking Time (Ms)
19320
53.2
30922
0
12870
0
1948
0

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.

Metrics

First CPU Idle — 3.7 s
The time taken for the page's main thread to be quiet enough to handle input.

Diagnostics

Serve static assets with an efficient cache policy — 15 resources found
Frndzcafe.net can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Size (Bytes)
https://www.trustedsite.com/rpc/ajax?do=tmjs-visit&host=frndzcafe.net&rand=1588362014348
0
689
https://frndzcafe.net/themes/Devilxxx.css
1000
4144
https://frndzcafe.net/themes/bootstrap/local.css
1000
2215
https://frndzcafe.net/themes/audio.css
1000
1218
https://frndzcafe.net/themes/fc_js.js
1000
778
https://frndzcafe.net/themes/styler.css
1000
649
https://frndzcafe.net/themes/fonts.css
1000
581
https://cdn.ywxi.net/js/1.js
78000
4950
https://cdn.ywxi.net/meter/frndzcafe.net/205.svg?ts=1588321309280&l=en-US
3576000
7920
https://www.google-analytics.com/analytics.js
7200000
18767
https://frndzcafe.net/images/copyright_proof.jpg
604800000
20012
https://frndzcafe.net/images/register_now.gif
604800000
4733
https://frndzcafe.net/images/slogo.png
604800000
4715
https://images.dmca.com/Badges/_dmca_premi_badge_4.png?ID=521fda4a-7544-4e4c-bb11-8a8e35d0607f
2592000000
4931
https://images.dmca.com/Badges/DMCABadgeHelper.min.js
2592000000
778

Other

First Contentful Paint (3G) — 4673 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

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

Opportunities

Reduce server response times (TTFB) — Root document took 1,290 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
69

Accessibility

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

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Frndzcafe.net may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Frndzcafe.net may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Frndzcafe.net may provide relevant information that dialogue cannot, by using audio descriptions.

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.
`<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.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
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.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

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.

Contrast

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

Internationalization and localization

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

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
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.
85

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
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.
Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.
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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://frndzcafe.net/
Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
97

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for frndzcafe.net. 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 frndzcafe.net on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
Legible text
100.00%
≥ 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.
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.

Mobile Friendly

Tap targets are not sized appropriately — 75% 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
41x21

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

Progressive Web App

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

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of frndzcafe.net on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://frndzcafe.net/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

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: 206.233.165.165
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
PSINet/ Don Adams
Registration

Domain Registrant

Private Registration: Yes
Name: Redacted for privacy
Organization: Redacted for privacy
Country: CN
City: Redacted for privacy
State: LIAONING
Post Code: Redacted for privacy
Email:
Phone: Redacted for privacy
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Gname.com Pte. Ltd. 104.18.15.137
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: frndzcafe.net
Issued By: cPanel, Inc. Certification Authority
Valid From: 5th March, 2020
Valid To: 3rd June, 2020
Subject: CN = frndzcafe.net
Hash: d0c17bba
Issuer: CN = cPanel, Inc. Certification Authority
O = cPanel, Inc.
S = US
Version: 2
Serial Number: 0xBCBDA9B8AF47D61A37FF8302F1149487
Serial Number (Hex): BCBDA9B8AF47D61A37FF8302F1149487
Valid From: 5th March, 2024
Valid To: 3rd June, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:7E:03:5A:65:41:6B:A7:7E:0A:E1:B8:9D:08:EA:1D:8E:1D:6A:C7:65
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.comodoca.com/cPanelIncCertificationAuthority.crl

Certificate Policies: Policy: 1.3.6.1.4.1.6449.1.2.2.52
CPS: https://sectigo.com/CPS
Policy: 2.23.140.1.2.1

Authority Information Access: CA Issuers - URI:http://crt.comodoca.com/cPanelIncCertificationAuthority.crt
OCSP - URI:http://ocsp.comodoca.com

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 07:B7:5C:1B:E5:7D:68:FF:F1:B0:C6:1D:23:15:C7:BA:
E6:57:7C:57:94:B7:6A:EE:BC:61:3A:1A:69:D3:A2:1C
Timestamp : Mar 5 18:27:23.295 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:72:A8:23:EA:DA:8E:0C:83:60:CC:42:E6:
C1:CF:08:87:11:57:D3:A4:D8:AD:81:3C:83:6E:69:81:
7A:98:52:C9:02:20:76:BC:9E:3E:E4:19:71:3C:72:DA:
32:CC:C6:4A:35:F4:3B:21:31:77:44:BC:11:F4:8C:90:
59:A8:42:72:D1:76
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E7:12:F2:B0:37:7E:1A:62:FB:8E:C9:0C:61:84:F1:EA:
7B:37:CB:56:1D:11:26:5B:F3:E0:F3:4B:F2:41:54:6E
Timestamp : Mar 5 18:27:23.234 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:B5:58:0C:A7:59:8B:9B:10:53:63:B5:
80:85:97:C6:16:D0:E5:14:DC:8D:EC:75:34:6D:0C:5E:
85:B6:9B:5B:DE:02:20:23:88:BA:FE:6D:D0:FE:A2:6B:
88:17:7C:2E:3F:C9:3A:67:F5:61:CC:C8:CB:7D:82:8C:
99:5D:51:B7:11:3D:B7
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:cpanel.frndzcafe.net
DNS:cpcalendars.frndzcafe.net
DNS:cpcontacts.frndzcafe.net
DNS:mail.frndzcafe.net
DNS:mail.peperonityweb.com
DNS:peperonityweb.com
DNS:webdisk.frndzcafe.net
DNS:webmail.frndzcafe.net
DNS:www.frndzcafe.net
DNS:www.peperonityweb.com
DNS:frndzcafe.net
Technical

DNS Lookup

A Records

Host IP Address Class TTL
frndzcafe.net. 216.10.249.83 IN 14399

NS Records

Host Nameserver Class TTL
frndzcafe.net. ns2.frndzcafe.net. IN 21599
frndzcafe.net. ns1.frndzcafe.net. IN 21599

MX Records

Priority Host Server Class TTL
0 frndzcafe.net. frndzcafe.net. IN 14399

SOA Records

Domain Name Primary NS Responsible Email TTL
frndzcafe.net. ns1.frndzcafe.net. root.216-10-249-83.webhostbox.net. 21599

TXT Records

Host Value Class TTL
frndzcafe.net. v=spf1 IN 14399

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 6th November, 2022
Content-Type: text/html; charset=UTF-8; charset=utf-8
Content-Length: 103328
Connection: keep-alive
Vary: Accept-Encoding

Whois Lookup

Created: 5th September, 2021
Changed: 5th September, 2022
Expires: 5th September, 2023
Registrar: Gname.com Pte. Ltd.
Status: clientTransferProhibited
Nameservers: ns1.gname-dns.com
ns2.gname-dns.com
Full Whois: Domain Name: FRNDZCAFE.NET
Registry Domain ID: 2638926050_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.gname.com
Registrar URL: http://www.gname.com
Updated Date: 2022-09-05T06:00:32Z
Creation Date: 2021-09-05T18:14:49Z
Registry Expiry Date: 2023-09-05T18:14:49Z
Registrar: Gname.com Pte. Ltd.
Registrar IANA ID: 1923
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.GNAME-DNS.COM
Name Server: NS2.GNAME-DNS.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2022-11-06T06:25:31Z <<<

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

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

Nameservers

Name IP Address
ns1.gname-dns.com 162.159.27.251
ns2.gname-dns.com 162.159.27.239
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5

Sites hosted on the same IP address