facetube.com

facetube.com may not be SSL secured

Free website and domain report on facetube.com

Last Updated: 30th January, 2021 Update Now
Overview

Snoop Summary for facetube.com

This is a free and comprehensive report about facetube.com. The domain facetube.com is currently hosted on a server located in Germany with the IP address 185.53.177.30, where the local currency is EUR and German is the local language. Our records indicate that facetube.com is privately registered by Moniker Privacy Services. If facetube.com was to be sold it would possibly be worth $106 USD (based on the daily revenue potential of the website over a 24 month period). Facetube.com receives an estimated 46 unique visitors every day - a small amount of traffic. This report was last updated 30th January, 2021.

About facetube.com

Site Preview: facetube.com facetube.com
Title: facetube.com
Description:
Keywords and Tags: parked domain, potentially illegal, scam, spam
Related Terms:
Fav Icon:
Age: Over 18 years old
Domain Created: 26th January, 2006
Domain Updated: 27th January, 2020
Domain Expires: 26th January, 2022
Review

Snoop Score

1/5

Valuation

$106 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 9,175,970
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: 46
Monthly Visitors: 1,400
Yearly Visitors: 16,790
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $4 USD
Yearly Revenue: $48 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: facetube.com 12
Domain Name: facetube 8
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 71
Performance 100
Accessibility 61
Best Practices 79
SEO 80
Progressive Web App 37
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
100

Performance

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

Metrics

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

Other

First CPU Idle — 0.4 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.
First Meaningful Paint — 0.4 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive facetube.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://facetube.com/
0
557.07999994047
1328
2058
200
text/html
Document
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefault.css
573.03599989973
601.24300001189
1997
4936
200
text/css
Stylesheet
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
573.25899996795
614.30200003088
827
829
200
text/css
Stylesheet
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
573.51200003177
619.46600000374
691
345
200
text/css
Stylesheet
http://iyfsearch.com/?dn=facetube.com&pid=9PO755G95
577.1029999014
890.06399991922
6500
21505
200
text/html
Document
http://iyfsearch.com/px.js?ch=1
904.12299986929
949.91800002754
628
346
200
application/javascript
Script
http://iyfsearch.com/px.js?ch=2
904.31099990383
991.74399999902
628
346
200
application/javascript
Script
http://i1.cdn-image.com/__media__/js/min.js?v2.2
904.80999997817
1166.0529999062
3417
8477
200
application/javascript
Script
http://i1.cdn-image.com/__media__/pics/8243/logo.png
993.23199992068
1155.778999906
4733
4422
200
image/png
Image
http://i1.cdn-image.com/__media__/pics/8243/bg.gif
1173.2860000338
1195.5969999544
4785
4474
200
image/gif
Image
http://i1.cdn-image.com/__media__/pics/8243/h_bg.gif
1173.7450000364
1269.1949999426
2528
2218
200
image/gif
Image
http://i1.cdn-image.com/__media__/pics/8243/lhs.gif
1174.1329999641
1200.4329999909
7035
6724
200
image/gif
Image
http://i1.cdn-image.com/__media__/pics/8243/rhs.gif
1174.9350000173
1342.9270000197
7074
6763
200
image/gif
Image
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
1187.7969999332
1226.8029998522
403
0
301
text/html
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
1227.006000001
1324.3040000089
34094
109551
200
text/javascript
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
590.785
10.965
651.629
9.467
925.008
7.16
1203.308
13.142
1216.558
10.962
1362.509
6.285
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. Facetube.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefault.css
1997
190
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
827
190
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
691
190
Properly size images
Images can slow down the page's load time. Facetube.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Facetube.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Facetube.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Facetube.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Facetube.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript — Potential savings of 97 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
109551
99187
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 560 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://facetube.com/
558.078
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Facetube.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Facetube.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

Diagnostics

Avoids enormous network payloads — Total size was 75 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
34094
http://i1.cdn-image.com/__media__/pics/8243/rhs.gif
7074
http://i1.cdn-image.com/__media__/pics/8243/lhs.gif
7035
http://iyfsearch.com/?dn=facetube.com&pid=9PO755G95
6500
http://i1.cdn-image.com/__media__/pics/8243/bg.gif
4785
http://i1.cdn-image.com/__media__/pics/8243/logo.png
4733
http://i1.cdn-image.com/__media__/js/min.js?v2.2
3417
http://i1.cdn-image.com/__media__/pics/8243/h_bg.gif
2528
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefault.css
1997
http://facetube.com/
1328
Avoids an excessive DOM size — 6 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
6
Maximum DOM Depth
3
Maximum Child Elements
4
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Facetube.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
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.
Minimizes main-thread work — 0.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
31.143
Script Evaluation
20.156
Style & Layout
18.476
Parse HTML & CSS
11.328
Rendering
8.651
Script Parsing & Compilation
6.975
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 — 15 requests • 75 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
15
76668
Script
4
38767
Image
5
26155
Document
2
7828
Stylesheet
3
3515
Other
1
403
Media
0
0
Font
0
0
Third-party
14
75340
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
34497
0
3515
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

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

Diagnostics

Serve static assets with an efficient cache policy — 12 resources found
Facetube.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefault.css
0
1997
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
0
827
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
0
691
http://iyfsearch.com/px.js?ch=1
0
628
http://iyfsearch.com/px.js?ch=2
0
628
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
1800000
34094
http://i1.cdn-image.com/__media__/js/min.js?v2.2
29426000
3417
http://i1.cdn-image.com/__media__/pics/8243/rhs.gif
81878000
7074
http://i1.cdn-image.com/__media__/pics/8243/h_bg.gif
81878000
2528
http://i1.cdn-image.com/__media__/pics/8243/bg.gif
82051000
4785
http://i1.cdn-image.com/__media__/pics/8243/logo.png
82257000
4733
http://i1.cdn-image.com/__media__/pics/8243/lhs.gif
82258000
7035
61

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of facetube.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.
`[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.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

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

Contrast

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

Tables and lists

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

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

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

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
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.
79

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 14 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://facetube.com/
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefault.css
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
http://iyfsearch.com/?dn=facetube.com&pid=9PO755G95
http://iyfsearch.com/px.js?ch=1
http://iyfsearch.com/px.js?ch=2
http://i1.cdn-image.com/__media__/js/min.js?v2.2
http://i1.cdn-image.com/__media__/pics/8243/logo.png
http://i1.cdn-image.com/__media__/pics/8243/bg.gif
http://i1.cdn-image.com/__media__/pics/8243/h_bg.gif
http://i1.cdn-image.com/__media__/pics/8243/lhs.gif
http://i1.cdn-image.com/__media__/pics/8243/rhs.gif
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

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

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

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

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

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

Fast and reliable

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

PWA Optimized

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 facetube.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

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

Installable

Does not use HTTPS — 14 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://facetube.com/
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefault.css
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
http://iyfsearch.com/?dn=facetube.com&pid=9PO755G95
http://iyfsearch.com/px.js?ch=1
http://iyfsearch.com/px.js?ch=2
http://i1.cdn-image.com/__media__/js/min.js?v2.2
http://i1.cdn-image.com/__media__/pics/8243/logo.png
http://i1.cdn-image.com/__media__/pics/8243/bg.gif
http://i1.cdn-image.com/__media__/pics/8243/h_bg.gif
http://i1.cdn-image.com/__media__/pics/8243/lhs.gif
http://i1.cdn-image.com/__media__/pics/8243/rhs.gif
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
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

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

Performance

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

Metrics

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

Other

First CPU Idle — 1.4 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.
First Meaningful Paint — 1.4 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive facetube.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://facetube.com/
0
311.52600003406
1203
1771
200
text/html
Document
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefault.css
325.20200009458
342.67699997872
1997
4936
200
text/css
Stylesheet
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
325.42200013995
340.96399997361
827
829
200
text/css
Stylesheet
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
325.66700014286
341.41899994574
691
345
200
text/css
Stylesheet
http://iyfsearch.com/?dn=facetube.com&pid=9PO755G95
329.28700000048
838.02200015634
6685
18143
200
text/html
Document
http://iyfsearch.com/px.js?ch=1
851.31300007924
981.72200005502
672
346
200
application/javascript
Script
http://iyfsearch.com/px.js?ch=2
851.52600007132
952.04300014302
628
346
200
application/javascript
Script
http://i1.cdn-image.com/__media__/js/min.js?v2.2
851.74900013953
937.79999995604
3417
8477
200
application/javascript
Script
http://i1.cdn-image.com/__media__/pics/8625/arrow.gif
989.11199998111
1171.5440000407
1537
1227
200
image/gif
Image
http://i1.cdn-image.com/__media__/pics/8625/searchIconN.gif
989.4159999676
1096.8379999977
1711
1401
200
image/gif
Image
http://i1.cdn-image.com/__media__/pics/8625/btnBg.gif
990.43000000529
1005.3020000923
1405
1095
200
image/gif
Image
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
997.21599998884
1022.307000123
403
0
301
text/html
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
1022.7090001572
1105.7460000739
34097
109555
200
text/javascript
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
339.653
9.216
867.57
6.702
1013.598
7.307
1021.049
6.345
1139.971
5.131
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
First Contentful Paint (3G) — 2772 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Properly size images
Images can slow down the page's load time. Facetube.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Facetube.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Facetube.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Facetube.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Facetube.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript — Potential savings of 97 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
109555
99187
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 310 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://facetube.com/
312.524
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Facetube.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Facetube.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

Diagnostics

Avoids enormous network payloads — Total size was 54 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
34097
http://iyfsearch.com/?dn=facetube.com&pid=9PO755G95
6685
http://i1.cdn-image.com/__media__/js/min.js?v2.2
3417
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefault.css
1997
http://i1.cdn-image.com/__media__/pics/8625/searchIconN.gif
1711
http://i1.cdn-image.com/__media__/pics/8625/arrow.gif
1537
http://i1.cdn-image.com/__media__/pics/8625/btnBg.gif
1405
http://facetube.com/
1203
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
827
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
691
Avoids an excessive DOM size — 6 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
6
Maximum DOM Depth
3
Maximum Child Elements
4
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Facetube.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.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)
http://iyfsearch.com/?dn=facetube.com&pid=9PO755G95
110.02
32.436
7.16
http://facetube.com/
92.928
14.736
5.052
Minimizes main-thread work — 0.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
110.168
Script Evaluation
60.452
Style & Layout
40.488
Parse HTML & CSS
30.792
Script Parsing & Compilation
24.324
Rendering
19.288
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 — 13 requests • 54 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
13
55273
Script
4
38814
Document
2
7888
Image
3
4653
Stylesheet
3
3515
Other
1
403
Media
0
0
Font
0
0
Third-party
12
54070
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
34500
0
3515
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

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

Opportunities

Eliminate render-blocking resources — Potential savings of 150 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Facetube.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefault.css
1997
630
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
827
630
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
691
630

Diagnostics

Serve static assets with an efficient cache policy — 10 resources found
Facetube.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefault.css
0
1997
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
0
827
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
0
691
http://iyfsearch.com/px.js?ch=1
0
672
http://iyfsearch.com/px.js?ch=2
0
628
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
1800000
34097
http://i1.cdn-image.com/__media__/js/min.js?v2.2
29414000
3417
http://i1.cdn-image.com/__media__/pics/8625/searchIconN.gif
30032000
1711
http://i1.cdn-image.com/__media__/pics/8625/btnBg.gif
74633000
1405
http://i1.cdn-image.com/__media__/pics/8625/arrow.gif
81891000
1537
61

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of facetube.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.
`[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.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

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

Contrast

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

Tables and lists

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

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

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

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
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.
79

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 12 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://facetube.com/
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefault.css
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
http://iyfsearch.com/?dn=facetube.com&pid=9PO755G95
http://iyfsearch.com/px.js?ch=1
http://iyfsearch.com/px.js?ch=2
http://i1.cdn-image.com/__media__/js/min.js?v2.2
http://i1.cdn-image.com/__media__/pics/8625/arrow.gif
http://i1.cdn-image.com/__media__/pics/8625/searchIconN.gif
http://i1.cdn-image.com/__media__/pics/8625/btnBg.gif
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

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

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

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

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

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

Fast and reliable

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

PWA Optimized

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 facetube.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

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

Installable

Does not use HTTPS — 12 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://facetube.com/
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefault.css
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
http://iyfsearch.com/?dn=facetube.com&pid=9PO755G95
http://iyfsearch.com/px.js?ch=1
http://iyfsearch.com/px.js?ch=2
http://i1.cdn-image.com/__media__/js/min.js?v2.2
http://i1.cdn-image.com/__media__/pics/8625/arrow.gif
http://i1.cdn-image.com/__media__/pics/8625/searchIconN.gif
http://i1.cdn-image.com/__media__/pics/8625/btnBg.gif
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
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

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

Server Location

Server IP Address: 185.53.177.30
Continent: Europe
Country: Germany
Germany Flag
Region:
City:
Longitude: 9.491
Latitude: 51.2993
Currencies: EUR
Languages: German

Web Hosting Provider

Registration

Domain Registrant

Private Registration: Yes
Name: Moniker Privacy Services
Organization: Moniker Privacy Services
Country: US
City: Fort Lauderdale
State: FL
Post Code: 33304
Email: e13db8461fb78a3b6a0c7cd966e0bcb744dbaee3817b13d48bf3dd93f6aad6c4@facetube.com.whoisproxy.org
Phone: +1.8006886311
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Moniker Online Services LLC 172.67.42.165
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating: 2/5 (2 reviews)
WOT Trustworthiness: 41/100
WOT Child Safety: 43/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
facetube.com. 185.53.177.30 IN 599

NS Records

Host Nameserver Class TTL
facetube.com. ns1.parkingspa.com. IN 21599
facetube.com. ns2.parkingspa.com. IN 21599

SOA Records

Domain Name Primary NS Responsible Email TTL
facetube.com. ns1.parkingspa.com. hostmaster.parkingcrew.com. 10799

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 30th January, 2021
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
X-Check: 3c12dc4d54f8e22d666785b733b0052100c53444
X-Language: english
X-Template: tpl_CleanPeppermintBlack_oneclick

Whois Lookup

Created: 26th January, 2006
Changed: 27th January, 2020
Expires: 26th January, 2022
Registrar: Moniker Online Services LLC
Status: clientTransferProhibited
Nameservers: ns1.parkingspa.com
ns2.parkingspa.com
Owner Name: Moniker Privacy Services
Owner Organization: Moniker Privacy Services
Owner Street: 2320 NE 9th St, Second Floor
Owner Post Code: 33304
Owner City: Fort Lauderdale
Owner State: FL
Owner Country: US
Owner Phone: +1.8006886311
Owner Email: 4829d2dcfe38a6675c502950c742fd9860aef29b702079d2d84a48f9b1853745@facetube.com.whoisproxy.org
Admin Name: Moniker Privacy Services
Admin Organization: Moniker Privacy Services
Admin Street: 2320 NE 9th St, Second Floor
Admin Post Code: 33304
Admin City: Fort Lauderdale
Admin State: FL
Admin Country: US
Admin Phone: +1.8006886311
Admin Email: 4829d2dcfe38a6675c502950c742fd9860aef29b702079d2d84a48f9b1853745@facetube.com.whoisproxy.org
Tech Name: Moniker Privacy Services
Tech Organization: Moniker Privacy Services
Tech Street: 2320 NE 9th St, Second Floor
Tech Post Code: 33304
Tech City: Fort Lauderdale
Tech State: FL
Tech Country: US
Tech Phone: +1.8006886311
Tech Email: 4829d2dcfe38a6675c502950c742fd9860aef29b702079d2d84a48f9b1853745@facetube.com.whoisproxy.org
Billing Name: Moniker Privacy Services
Billing Organization: Moniker Privacy Services
Billing Street: 2320 NE 9th St, Second Floor
Billing Post Code: 33304
Billing City: Fort Lauderdale
Billing State: FL
Billing Country: US
Billing Phone: +1.8006886311
Billing Fax: +1.9545859186
Billing Email: 4829d2dcfe38a6675c502950c742fd9860aef29b702079d2d84a48f9b1853745@facetube.com.whoisproxy.org
Full Whois: Domain Name: facetube.com
Registry Domain ID: 327806117_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.moniker.com
Registrar URL: http://www.moniker.com
Updated Date: 2020-01-27T08:24:01Z
Creation Date: 2006-01-26T14:58:56Z
Registrar Registration Expiration Date: 2022-01-26T14:58:56Z
Registrar: Moniker Online Services LLC
Registrar IANA ID: 228
Registrar Abuse Contact Email: abusereport@moniker.com
Registrar Abuse Contact Phone: +1.9546071294
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Moniker Privacy Services
Registrant Organization: Moniker Privacy Services
Registrant Street: 2320 NE 9th St, Second Floor
Registrant City: Fort Lauderdale
Registrant State/Province: FL
Registrant Postal Code: 33304
Registrant Country: US
Registrant Phone: +1.8006886311
Registrant Phone Ext:
Registrant Fax: +1.9545859186
Registrant Fax Ext:
Registrant Email: 4829d2dcfe38a6675c502950c742fd9860aef29b702079d2d84a48f9b1853745@facetube.com.whoisproxy.org
Registry Admin ID: Not Available From Registry
Admin Name: Moniker Privacy Services
Admin Organization: Moniker Privacy Services
Admin Street: 2320 NE 9th St, Second Floor
Admin City: Fort Lauderdale
Admin State/Province: FL
Admin Postal Code: 33304
Admin Country: US
Admin Phone: +1.8006886311
Admin Phone Ext:
Admin Fax: +1.9545859186
Admin Fax Ext:
Admin Email: 4829d2dcfe38a6675c502950c742fd9860aef29b702079d2d84a48f9b1853745@facetube.com.whoisproxy.org
Registry Tech ID: Not Available From Registry
Tech Name: Moniker Privacy Services
Tech Organization: Moniker Privacy Services
Tech Street: 2320 NE 9th St, Second Floor
Tech City: Fort Lauderdale
Tech State/Province: FL
Tech Postal Code: 33304
Tech Country: US
Tech Phone: +1.8006886311
Tech Phone Ext:
Tech Fax: +1.9545859186
Tech Fax Ext:
Tech Email: 4829d2dcfe38a6675c502950c742fd9860aef29b702079d2d84a48f9b1853745@facetube.com.whoisproxy.org
Registry Billing ID: Not Available From Registry
Billing Name: Moniker Privacy Services
Billing Organization: Moniker Privacy Services
Billing Street: 2320 NE 9th St, Second Floor
Billing City: Fort Lauderdale
Billing State/Province: FL
Billing Postal Code: 33304
Billing Country: US
Billing Phone: +1.8006886311
Billing Phone Ext:
Billing Fax: +1.9545859186
Billing Fax Ext:
Billing Email: 4829d2dcfe38a6675c502950c742fd9860aef29b702079d2d84a48f9b1853745@facetube.com.whoisproxy.org
Name Server: ns1.parkingspa.com
Name Server: ns2.parkingspa.com
DNSSEC: unsigned
Whoisprivacy: 4
URL of the ICANN WHOIS Data Problem Reporting System: https://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-01-30T02:16:09Z <<<

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

To contact the registered registrant please proceed to:
https://www.domain-contact.org

Please register your domains at; http://www.moniker.com
This data is provided by MONIKER ONLINE SERVICES LLC.
for information purposes, and to assist persons obtaining information
about or related to domain name registration records.
MONIKER ONLINE SERVICES LLC. does not guarantee its accuracy.
By submitting a WHOIS query, you agree that you will use this data
only for lawful purposes and that, under no circumstances, you will
use this data to
1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via E-mail
(spam) or
2) enable high volume, automated, electronic processes that apply
to this WHOIS server.
These terms may be changed without prior notice.
By submitting this query, you agree to abide by this policy.

Nameservers

Name IP Address
ns1.parkingspa.com 13.248.134.152
ns2.parkingspa.com 76.223.5.37
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$406 USD 1/5
0/5
$4,208 USD 2/5