Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

yaoi.com

yaoi.com may not be SSL secured

Free website and domain report on yaoi.com

Last Updated: 5th May, 2021 Update Now
Overview

Snoop Summary for yaoi.com

This is a free and comprehensive report about yaoi.com. Yaoi.com is hosted in Scottsdale, Arizona in United States on a server with an IP address of 97.74.42.79, where USD is the local currency and the local language is English. If yaoi.com was to be sold it would possibly be worth $719 USD (based on the daily revenue potential of the website over a 24 month period). Yaoi.com is somewhat popular with an estimated 341 daily unique visitors. This report was last updated 5th May, 2021.

About yaoi.com

Site Preview:
Title: Yaoi
Description: Check out this GoDaddy hosted webpage! http://yaoi.com.
Keywords and Tags: hardware, internet services, software
Related Terms: mangago yaoi, yaoi, yaoi mangago
Fav Icon:
Age: Over 25 years old
Domain Created: 3rd January, 1999
Domain Updated: 28th April, 2015
Domain Expires: 3rd January, 2023
Review

Snoop Score

1/5

Valuation

$719 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,932,185
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: 341
Monthly Visitors: 10,369
Yearly Visitors: 124,348
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $30 USD
Yearly Revenue: $354 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: yaoi.com 8
Domain Name: yaoi 4
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 66
Performance 98
Accessibility 66
Best Practices 67
SEO 82
Progressive Web App 18
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://yaoi.com/
Updated: 5th May, 2021

3.95 seconds
First Contentful Paint (FCP)
11%
46%
43%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

98

Performance

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

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.2 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 0.8 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.8 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.042
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 0.8 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.8 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 yaoi.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 Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://yaoi.com/
http/1.1
0
226.58300001058
6342
18271
200
text/html
Document
http://img1.wsimg.com/ip/v1.2.18/style/ss-1.0.0.0.css
http/1.1
239.99199998798
275.65900000627
5417
26600
200
text/css
Stylesheet
https://widget.starfieldtech.com/API.svc/jquery.js
http/1.1
240.14999999781
915.0850000151
287
0
301
https://widget.starfieldtech.com/API.svc/jquery-ui.js
http/1.1
240.42099999497
914.74999999627
289
0
301
http://img1.wsimg.com/ip/v1.2.18/scripts/ss-merged-1.0.0.0.js
http/1.1
240.66700000549
258.61399999121
14780
53778
200
application/x-javascript
Script
https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&user=745794&proxy=%2fCygnus%2fProxy&action=%2fCygnus%2fAction
http/1.1
240.82700000145
1169.9150000059
141058
140897
200
text/javascript
Script
http://img1.wsimg.com/ip/v1.2.18/images/common/transparent.png
http/1.1
1143.4310000041
1198.4489999886
2066
1715
200
image/png
Image
http://img1.wsimg.com/tcc/tcc_l.combined.1.0.5.min.js
http/1.1
1089.7800000093
1142.1569999948
2568
5969
200
application/x-javascript
Script
https://img3.wsimg.com/widgetfw/jQuery/v1.8.0/jquery-ui.js
http/1.1
915.05199999665
1068.265000009
34477
131605
200
application/x-javascript
Script
https://img4.wsimg.com/starfield/jquery/v1.6.4/jquery.js
http/1.1
915.33799999161
1083.8640000147
32516
91668
200
application/x-javascript
Script
http://img1.wsimg.com/ip/v1.2.18/images/common/tab_login.png
http/1.1
1183.8170000119
1202.9099999927
1935
1584
200
image/png
Image
http://img1.wsimg.com/ip/v1.2.18/images/common/flyout_repeat.png
http/1.1
1184.0640000009
1218.9460000081
475
126
200
image/png
Image
http://img1.wsimg.com/ip/v1.2.18/images/common/flyout_arrow.png
http/1.1
1184.4189999974
1219.4489999965
771
422
200
image/png
Image
http://img1.wsimg.com/ip/v1.2.18/images/common/gd/flyout_logo.png
http/1.1
1184.5909999975
1215.6360000081
1337
988
200
image/png
Image
https://img3.wsimg.com/starfield/curl/v1.5.2/curl.js
http/1.1
1206.6909999994
1340.8120000095
7564
18326
200
application/x-javascript
Script
http://img1.wsimg.com/ip/v1.2.18/style/jquery.gd.shareLinks.css
http/1.1
1228.3940000052
1275.4779999959
1154
2338
200
text/css
Stylesheet
http://img1.wsimg.com/ip/v1.2.18/images/common/shareIcons2.png
http/1.1
1231.220000016
1282.452000014
27108
26756
200
image/png
Image
http://img2.wsimg.com/starfield/sf.core/v1.5.2/sf.core.css
http/1.1
1353.2359999954
1390.046000015
7071
38517
200
text/css
Stylesheet
http://img.secureserver.net/t/1/tl/event?cts=1620234446527&ap=IPv1&tce=1620234445337&tcs=1620234445337&tdc=1620234446731&tdclee=1620234446571&tdcles=1620234446528&tdi=1620234446528&tdl=1620234445568&tdle=1620234445337&tdls=1620234445337&tfs=1620234445337&tns=1620234445336&trqs=1620234445337&tre=1620234445564&trps=1620234445564&tles=1620234446731&tlee=1620234446731&dh=yaoi.com&dp=%2F&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_14_6)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F90.0.4420.0%20Safari%2F537.36%20Chrome-Lighthouse&feedtype=perf&z=8673291
http/1.1
1396.184000012
1416.1840000015
790
0
301
https://img.secureserver.net/t/1/tl/event?cts=1620234446527&ap=IPv1&tce=1620234445337&tcs=1620234445337&tdc=1620234446731&tdclee=1620234446571&tdcles=1620234446528&tdi=1620234446528&tdl=1620234445568&tdle=1620234445337&tdls=1620234445337&tfs=1620234445337&tns=1620234445336&trqs=1620234445337&tre=1620234445564&trps=1620234445564&tles=1620234446731&tlee=1620234446731&dh=yaoi.com&dp=%2F&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_14_6)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F90.0.4420.0%20Safari%2F537.36%20Chrome-Lighthouse&feedtype=perf&z=8673291
http/1.1
1416.4530000126
1522.2519999952
628
43
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
256.235
8.213
1116.74
27.978
1204.277
5.774
1210.064
5.36
1215.501
46.545
1346.538
5.454
1369.378
9.124
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 90 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Yaoi.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://img1.wsimg.com/ip/v1.2.18/style/ss-1.0.0.0.css
5417
190
http://img1.wsimg.com/ip/v1.2.18/scripts/ss-merged-1.0.0.0.js
14780
228
https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&user=745794&proxy=%2fCygnus%2fProxy&action=%2fCygnus%2fAction
141058
590
Properly size images
Images can slow down the page's load time. Yaoi.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Yaoi.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Yaoi.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Yaoi.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Yaoi.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 19 KiB
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 Resource Size (Bytes) Potential Savings (Bytes)
http://img1.wsimg.com/ip/v1.2.18/images/common/shareIcons2.png
26756
19506
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 230 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://yaoi.com/
227.577
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Yaoi.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Yaoi.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 29 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&user=745794&proxy=%2fCygnus%2fProxy&action=%2fCygnus%2fAction
20281
http://img1.wsimg.com/tcc/tcc_l.combined.1.0.5.min.js
9526
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 282 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&user=745794&proxy=%2fCygnus%2fProxy&action=%2fCygnus%2fAction
141058
https://img3.wsimg.com/widgetfw/jQuery/v1.8.0/jquery-ui.js
34477
https://img4.wsimg.com/starfield/jquery/v1.6.4/jquery.js
32516
http://img1.wsimg.com/ip/v1.2.18/images/common/shareIcons2.png
27108
http://img1.wsimg.com/ip/v1.2.18/scripts/ss-merged-1.0.0.0.js
14780
https://img3.wsimg.com/starfield/curl/v1.5.2/curl.js
7564
http://img2.wsimg.com/starfield/sf.core/v1.5.2/sf.core.css
7071
http://yaoi.com/
6342
http://img1.wsimg.com/ip/v1.2.18/style/ss-1.0.0.0.css
5417
http://img1.wsimg.com/tcc/tcc_l.combined.1.0.5.min.js
2568
Avoids an excessive DOM size — 40 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
40
Maximum DOM Depth
Yaoi.official
9
Maximum Child Elements
Yaoi Yaoi.official Facebook Twitter MySpace Del.icio.us StumbleUpon A website …
5
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Yaoi.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://yaoi.com/
135.499
68.927
4.775
Minimizes main-thread work — 0.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
101.847
Other
42.898
Style & Layout
23.783
Rendering
16.548
Script Parsing & Compilation
13.725
Parse HTML & CSS
8.647
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 — 20 requests • 282 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
20
288633
Script
6
232963
Image
7
34320
Stylesheet
3
13642
Document
1
6342
Other
3
1366
Media
0
0
Font
0
0
Third-party
19
282291
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)
SHOW DETAILS
139239
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Yaoi
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
Yaoi
0.042315945133964
A website created by GoDaddy’s Website Builder
1.7021276595745E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
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.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

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

Remove unused JavaScript — Potential savings of 272 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&user=745794&proxy=%2fCygnus%2fProxy&action=%2fCygnus%2fAction
141058
121196
https://widget.starfieldtech.com/API.svc/jquery-ui.js
131605
117079
https://widget.starfieldtech.com/API.svc/jquery.js
91668
40277
Enable text compression — Potential savings of 104 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&user=745794&proxy=%2fCygnus%2fProxy&action=%2fCygnus%2fAction
140897
106137

Diagnostics

Serve static assets with an efficient cache policy — 1 resource found
Yaoi.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&user=745794&proxy=%2fCygnus%2fProxy&action=%2fCygnus%2fAction
0
141058
66

Accessibility

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

Navigation

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

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<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.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Yaoi.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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
Yaoi.official

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
html

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that yaoi.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.

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.
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.
Name Version
jQuery
1.6.4
jQuery UI
1.8.11
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.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 13 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 Request Resolution
http://yaoi.com/
Allowed
http://img1.wsimg.com/ip/v1.2.18/style/ss-1.0.0.0.css
Allowed
http://img1.wsimg.com/ip/v1.2.18/scripts/ss-merged-1.0.0.0.js
Allowed
http://img1.wsimg.com/ip/v1.2.18/images/common/transparent.png
Allowed
http://img1.wsimg.com/tcc/tcc_l.combined.1.0.5.min.js
Allowed
http://img1.wsimg.com/ip/v1.2.18/images/common/tab_login.png
Allowed
http://img1.wsimg.com/ip/v1.2.18/images/common/flyout_repeat.png
Allowed
http://img1.wsimg.com/ip/v1.2.18/images/common/flyout_arrow.png
Allowed
http://img1.wsimg.com/ip/v1.2.18/images/common/gd/flyout_logo.png
Allowed
http://img1.wsimg.com/ip/v1.2.18/style/jquery.gd.shareLinks.css
Allowed
http://img1.wsimg.com/ip/v1.2.18/images/common/shareIcons2.png
Allowed
http://img2.wsimg.com/starfield/sf.core/v1.5.2/sf.core.css
Allowed
http://img.secureserver.net/t/1/tl/event?cts=1620234446527&ap=IPv1&tce=1620234445337&tcs=1620234445337&tdc=1620234446731&tdclee=1620234446571&tdcles=1620234446528&tdi=1620234446528&tdl=1620234445568&tdle=1620234445337&tdls=1620234445337&tfs=1620234445337&tns=1620234445336&trqs=1620234445337&tre=1620234445564&trps=1620234445564&tles=1620234446731&tlee=1620234446731&dh=yaoi.com&dp=%2F&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_14_6)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F90.0.4420.0%20Safari%2F537.36%20Chrome-Lighthouse&feedtype=perf&z=8673291
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 8 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
SHOW DETAILS
5
Medium
SHOW DETAILS
3
High

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
http://img1.wsimg.com/ip/v1.2.18/images/common/transparent.png
1350 x 1350
200 x 200
1350 x 1350

Audits

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

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Crawling and Indexing

robots.txt is not valid — 298 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
3
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
Unknown directive
4
<html xmlns="http://www.w3.org/1999/xhtml" version="XHTML+RDFa 1.1"
Unknown directive
5
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
Unknown directive
6
xsi:schemaLocation="http://www.w3.org/1999/xhtml http://www.w3.org/MarkUp/SCHEMA/xhtml-rdfa-2.xsd"
Unknown directive
7
xmlns:og="http://ogp.me/ns#">
Unknown directive
8
<head>
Syntax not understood
9
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
Syntax not understood
10
<meta name="viewport" content="width=1024" />
Syntax not understood
12
<meta name="description" content="Check out this GoDaddy hosted webpage! http://yaoi.com." />
Unknown directive
13
<meta property="og:title" content="Yaoi" />
Unknown directive
14
<meta property="og:description" content="Check out this GoDaddy hosted webpage! http://yaoi.com." />
Unknown directive
16
<meta property="og:image" content="http://imagesak.websitetonight.com/skins/pl.gd/images/logo1.gif" />
Unknown directive
19
<link rel="shortcut icon" type="image/ico" href="http://img1.wsimg.com/ip/v1.2.18/images/favicon.ico" />
Unknown directive
20
<link rel="icon" type="image/png" href="http://img1.wsimg.com/ip/v1.2.18/images/favicon.jpg" />
Unknown directive
21
<title>
Syntax not understood
22
Yaoi
Syntax not understood
23
</title>
Syntax not understood
25
<link href="http://img1.wsimg.com/ip/v1.2.18/style/ss-1.0.0.0.css" rel="stylesheet" type="text/css" />
Unknown directive
30
<script type="text/javascript" src="https://widget.starfieldtech.com/API.svc/jquery.js"></script>
Unknown directive
31
<script type="text/javascript" src="https://widget.starfieldtech.com/API.svc/jquery-ui.js"></script>
Unknown directive
33
<script src="http://img1.wsimg.com/ip/v1.2.18/scripts/ss-merged-1.0.0.0.js" type="text/javascript"></script>
Unknown directive
35
<script type="text/javascript" src="https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&amp;user=745794&amp;proxy=%2fCygnus%2fProxy&amp;action=%2fCygnus%2fAction"></script>
Unknown directive
39
<script type="text/javascript">// <![CDATA[
Syntax not understood
40
$j(document).ready( function() {
Syntax not understood
41
// ---- Configure the application settings for communicating with Cygnus.
Syntax not understood
42
$c.Stage.applicationEventHandlerElement = $j("#page");
Syntax not understood
44
var appSettings = $c.Stage.applicationSettings;
Syntax not understood
45
appSettings.showConfigControl = false;
Syntax not understood
46
appSettings.showToggleControl = false;
Syntax not understood
47
appSettings.showCloseControl = true;
Syntax not understood
48
appSettings.hideCloseControlOnEdit = true;
Syntax not understood
49
appSettings.widgetActions.closeControlClick = function (widgetId, widgetType) {
Syntax not understood
50
// this will hide the widget since it's already open
Syntax not understood
51
$ss.showWidget(widgetId, $j(".ss-service[wid='" + widgetId + "']"));
Syntax not understood
52
};
Syntax not understood
53
appSettings.widgetEvents.saveConfigSuccess =
Syntax not understood
54
function(widgetId, widgetType) {
Syntax not understood
55
var li = $j("li:has(a[wid='" + widgetId + "'])");
Unknown directive
56
if (li.length > 0)
Syntax not understood
57
{
Syntax not understood
58
li.show();
Syntax not understood
59
li.find("a").removeClass("uninitialized");
Syntax not understood
60
$ss.showLauncher();
Syntax not understood
61
$ss.showSavedConfirmation('App saved successfully.');
Syntax not understood
62
}
Syntax not understood
63
else
Syntax not understood
64
{
Syntax not understood
65
if (widgetType == "fbpage")
Syntax not understood
66
{
Syntax not understood
67
$ss.showSavedConfirmation('Facebook Page saved successfully.');
Syntax not understood
68
}
Syntax not understood
69
}
Syntax not understood
70
};
Syntax not understood
71
appSettings.widgetEvents.saveConfigFailure =
Syntax not understood
72
function(widgetId, widgetType) {
Syntax not understood
73
//alert("failed!");
Syntax not understood
74
};
Syntax not understood
75
appSettings.widgetEvents.cancelledConfig =
Syntax not understood
76
function(widgetId, widgetType) {
Syntax not understood
77
var a = $j("a[wid='" + widgetId + "']");
Syntax not understood
78
if (a.hasClass("uninitialized"))
Syntax not understood
79
{
Syntax not understood
80
//close the widget since it's already open if it's not be initialized.
Syntax not understood
81
$ss.showWidget(widgetId, $j(".ss-service[wid='" + widgetId + "']"));
Syntax not understood
82
$ss.openAdminPanel('widgets');
Syntax not understood
83
}
Syntax not understood
84
};
Syntax not understood
85
appSettings.widgetEvents.openedConfig =
Syntax not understood
86
function(widgetId, widgetType)
Syntax not understood
87
{
Syntax not understood
88
if (widgetType != "fbpage")
Syntax not understood
89
{
Syntax not understood
90
// close tabs
Syntax not understood
91
$ss.hideAdminPanel();
Syntax not understood
92
}
Syntax not understood
93
};
Syntax not understood
94
appSettings.widgetEvents.closedConfig =
Syntax not understood
95
function(widgetId, widgetType)
Syntax not understood
96
{
Syntax not understood
97
if (widgetType == "fbpage")
Syntax not understood
98
{
Syntax not understood
99
$ss.facebookPage.close(widgetId);
Syntax not understood
100
}
Syntax not understood
101
};
Syntax not understood
102
appSettings.widgetEvents.dataModified =
Syntax not understood
103
function(widgetId, widgetType, data) {
Syntax not understood
104
if ($j.isPopulated(data))
Syntax not understood
105
{
Syntax not understood
106
if (widgetType == "fbpage")
Syntax not understood
107
{
Syntax not understood
108
$j('.widget-fbpage-title').text(data.Title.value);
Syntax not understood
109
}
Syntax not understood
110
else
Syntax not understood
111
{
Syntax not understood
112
var a = $j("#ss-launcher").find("a[wid=" + widgetId + "]");
Syntax not understood
113
var children = a.children();
Syntax not understood
114
a
Syntax not understood
115
.text(data.LinkTitle.value)
Syntax not understood
116
.append(children);
Syntax not understood
117
$j("#widgets-added-list").find("li[wid=" + widgetId + "] .widget-added-label-title").text(data.LinkTitle.value);
Syntax not understood
118
}
Syntax not understood
119
}
Syntax not understood
120
};
Syntax not understood
121
appSettings.widgetEvents.revealed =
Syntax not understood
122
function(widgetId, widgetType) {
Syntax not understood
123
if ($j.isFunction($ss.stage.layout.revealed)) $ss.stage.layout.revealed();
Syntax not understood
124
};
Syntax not understood
125
appSettings.widgetEvents.obscured =
Syntax not understood
126
function(widgetId, widgetType) {
Syntax not understood
127
if ($j.isFunction($ss.stage.layout.obscured)) $ss.stage.layout.obscured();
Syntax not understood
128
};
Syntax not understood
130
appSettings.widgetEvents.widgetModalDisplayed =
Syntax not understood
131
appSettings.widgetEvents.contentUpdated =
Syntax not understood
132
function(wigetId, widgetType) { $ss.fixPalette(); };
Syntax not understood
134
appSettings.applicationUtilityProviders.getImages = function(widgetId, success, failure)
Syntax not understood
135
{
Syntax not understood
136
// show a dialog for the user to select images that were uploaded as backgrounds
Syntax not understood
137
// one day maybe we can change this to be a uploader instead.
Syntax not understood
138
$ss.facebookPage.gatherImages(null, function(result) {
Syntax not understood
139
// if the user closed the dialog
Syntax not understood
140
if (result)
Syntax not understood
141
{
Syntax not understood
142
success(result.images);
Syntax not understood
143
}
Syntax not understood
144
else // do the failure callback otherwise.
Syntax not understood
145
{
Syntax not understood
146
failure({ error: 'Error', message: 'Unable to get images.' });
Unknown directive
147
}
Syntax not understood
148
});
Syntax not understood
149
}
Syntax not understood
151
appSettings.baseWidgetColors = {
Syntax not understood
152
background: '#091249',
Unknown directive
153
textTitle: '#FFFFFF',
Unknown directive
154
textContent: '#FFFFFF',
Unknown directive
155
textLinks: '#84B6E7',
Unknown directive
156
borderTitle: '#84B6E7'
Unknown directive
157
};
Syntax not understood
159
appSettings.applicationEvents.colorsChanged = "widgets.colorsChanged";
Syntax not understood
161
appSettings.widgetInitializeOptions.fbpage = { hideFacebookConnectDisplay: true };
Unknown directive
163
appSettings.modalContainerCssClass ="modal-container";
Syntax not understood
165
$c.CommManager.applicationData = { "domainName": "yaoi.com" };
Unknown directive
167
// ---- DONE application setting configuration
Syntax not understood
169
// load/style the page and all it's components
Syntax not understood
170
$ss = SimpleSite({
Syntax not understood
171
basePath: "/",
Unknown directive
172
cdnImagePath: "http://img1.wsimg.com/ip/v1.2.18/images/",
Unknown directive
173
cdnCssPath: "http://img1.wsimg.com/ip/v1.2.18/style/",
Unknown directive
174
eventReceiver: "#page",
Unknown directive
175
background: {"id":1,"originalSrc":"http://img1.wsimg.com/ip/v1.2.18/images/common/transparent.png","src":"http://img1.wsimg.com/ip/v1.2.18/images/common/transparent.png","thumbnail":"http://img1.wsimg.com/ip/v1.2.18/images/common/transparent.png","orientation":"3","variation":"","isUserOwner":false,"cropHistory":null,"stockBackgroundId":0,"isUncropped":false},
Unknown directive
176
layout: {"id":7,"name":"Top Menu","type":"3","variation":"c","VariationName":"Centered"},
Unknown directive
177
layoutControls:
Unknown directive
178
{
Syntax not understood
179
content: '#ss-main',
Unknown directive
180
title: '#ss-name',
Unknown directive
181
description: '#ss-description',
Unknown directive
182
launcher: '#ss-launcher',
Unknown directive
183
page: '#page',
Unknown directive
184
widgetContainer: '#ss-widgetContainer',
Unknown directive
185
about: '#ss-about',
Unknown directive
186
background: '#ss-background'
Unknown directive
187
},
Syntax not understood
188
palette: {
Unknown directive
189
"id": 43,
Unknown directive
190
"name": null,
Unknown directive
191
"userCreated": false,
Unknown directive
192
"isActive": true,
Unknown directive
193
"backgrounds": {
Unknown directive
194
"page": "#FFFFFF",
Unknown directive
195
"main": "#091249",
Unknown directive
196
"meta": "#FFFFFF",
Unknown directive
197
"block": "#091249"
Unknown directive
198
},
Syntax not understood
199
"fonts": {
Unknown directive
200
"title": "#477EB4",
Unknown directive
201
"description": "#BBBBBB",
Unknown directive
202
"services": "#84B6E7",
Unknown directive
203
"primary": "#FFFFFF",
Unknown directive
204
"secondary": "#FFFFFF",
Unknown directive
205
"links": "#84B6E7"
Unknown directive
206
}
Syntax not understood
207
},
Syntax not understood
208
fonts: {"titleFontId":0,"generalFontId":4,"titleSize":52,"descriptionSize":28,"servicesSize":24,"titleFontIsEmbed":false,"generalFontIsEmbed":false},
Unknown directive
209
titleFont: {"id":0,"appliesTo":"title","faceName":"Arial","defaultSize":60,"isEmbed":false},
Unknown directive
210
generalFont: {"id":4,"appliesTo":"title","faceName":"Times New Roman","defaultSize":60,"isEmbed":false},
Unknown directive
211
fontControls:
Unknown directive
212
{
Syntax not understood
213
title: {reset: '.ss-title', apply: '.ss-title' },
Unknown directive
214
description: {reset: '.ss-description', apply: '.ss-description' },
Unknown directive
215
services: {reset: '.ss-service', apply: '.ss-service'},
Unknown directive
216
block: {reset: '.ss-block, #ss-widgetContainer', apply: '.ss-block, #ss-widgetContainer' }
Unknown directive
217
},
Syntax not understood
218
styleControls:
Unknown directive
219
{
Syntax not understood
220
// Page background
Syntax not understood
221
background: {reset: '#ss-background', apply: '#ss-background' },
Unknown directive
222
title: {reset: '.ss-title', apply: '.ss-title', borders: {reset: '#ss-launcher li', apply: '#ss-launcher li'} },
Unknown directive
223
description: {reset: '.ss-description', apply: '.ss-description' },
Unknown directive
224
services: {reset: '.ss-service', apply: '.ss-service', borders: {reset: '.accordion-arrow-inheritor, .accordion-button', apply: '.accordion-arrow-inheritor, .accordion-button'}},
Unknown directive
225
block: {
Unknown directive
226
reset: '.ss-block, #ss-widgetContainer',
Unknown directive
227
apply: '.ss-block, #ss-widgetContainer, .modal-widget',
Unknown directive
228
foreground: { apply: '.contrast' }
Unknown directive
229
},
Syntax not understood
230
// Widget text
Syntax not understood
231
primary: {
Unknown directive
232
reset: '.widget-container .title-bar, .widget-container .text-highlight, .widget-instance h1, .widget-instance h2, .widget-instance h3, .widget-instance h4, .widget-instance h5, .widget-instance h6, .modal-widget .title-bar, .modal-widget .text-highlight, .modal-widget h1, .modal-widget h2, .modal-widget h3, .modal-widget h4, .modal-widget h5, .modal-widget h6',
Unknown directive
233
apply: '.widget-container .title-bar, .widget-container .text-highlight, .widget-instance h1, .widget-instance h2, .widget-instance h3, .widget-instance h4, .widget-instance h5, .widget-instance h6, .modal-widget .title-bar, .modal-widget .text-highlight, .modal-widget h1, .modal-widget h2, .modal-widget h3, .modal-widget h4, .modal-widget h5, .modal-widget h6'
Unknown directive
234
},
Syntax not understood
235
secondary: {
Unknown directive
236
reset: '.widget-instance, .widget-instance div:not(.watermark, .charCounter, .text-highlight, .contrast, .error, .form-errors, .required, :isThirdPartyInclude), .widget-instance span:not(.watermark, .charCounter, .text-highlight, .contrast, .error, .form-errors, .required, :isThirdPartyInclude), .widget-instance li, .widget-instance p, .modal-widget, .modal-widget div:not(.watermark, .charCounter), .modal-widget li, .modal-widget span:not(.text-highlight,.contrast), .modal-widget p',
Unknown directive
237
apply: '.widget-instance, .widget-instance div:not(.watermark, .charCounter, .text-highlight, .contrast, .error, .form-errors, .required, :isThirdPartyInclude), .widget-instance span:not(.watermark, .charCounter, .text-highlight, .contrast, .error, .form-errors, .required, :isThirdPartyInclude), .widget-instance li, .widget-instance p, .modal-widget, .modal-widget div:not(.watermark, .charCounter), .modal-widget li, .modal-widget span:not(.text-highlight,.welcome-subtitle,.contrast), .modal-widget p',
Unknown directive
238
background: { apply: '.contrast, .speech-balloon-tail' },
Unknown directive
239
borders: { apply: '.speech-balloon-tail' }
Unknown directive
240
},
Syntax not understood
241
//main: { reset: '#ss-launcher, .modal-widget', apply: '.modal-widget, .layout3-c #ss-launcher, .layout2-c #ss-launcher, .layout2-l #ss-launcher, .layout2-r #ss-launcher' }, //'.ss-main, .layout3-c #ss-launcher',
Unknown directive
242
//meta: { reset: '#ss-main', apply: '.layout1-c #ss-main, .layout1-l #ss-main, .layout1-r #ss-main, .layout4-c #ss-main, .layout4-l #ss-main, .layout4-r #ss-main' }, //'.ss-main, .layout3-c #ss-launcher',
Unknown directive
243
main: { reset: '#ss-launcher', apply: '#ss-launcher' },
Unknown directive
244
meta: { reset: '#ss-about', apply: '#ss-about' }, //'.ss-main, .layout3-c #ss-launcher',
Unknown directive
245
links: { reset: '.modal-widget a', apply: '.widget-instance a:not(.contrast, :isInWidgetConfigPanel, :isThirdPartyInclude), .modal-widget a:not(.welcome-link), a.widget-link', borders: {reset: '.widget-container .title-bar, .widget-container .contrast-border, hr', apply: '.widget-container .title-bar, .widget-container .contrast-border, hr' }},
Unknown directive
246
page: { reset: '.ss-background, body', apply: '.ss-background, body' },
Unknown directive
247
launcher: { reset: '#ss-launcher', apply: '#ss-launcher' },
Unknown directive
248
widgetContainer: { reset: '#ss-widgetContainer', apply: '#ss-widgetContainer' }
Unknown directive
249
},
Syntax not understood
250
siteInfo: {
Unknown directive
251
title: "Yaoi",
Unknown directive
252
description: "Yaoi.official",
Unknown directive
253
domain: "yaoi.com",
Unknown directive
254
showShareLinks: true
Unknown directive
255
},
Syntax not understood
256
shareLinksData: {
Unknown directive
257
twitter: { ciCode: '44667', message: "Check out this GoDaddy hosted webpage! http://yaoi.com.", value:1 },
Unknown directive
258
facebook: { ciCode: '44670', value:0 },
Unknown directive
259
myspace: { ciCode: '44666', message: "Yaoi", value:2 },
Unknown directive
260
delicious: { ciCode: '44668', message: "Check out this GoDaddy hosted webpage! http://yaoi.com.", value:3 },
Unknown directive
261
stumbleupon: { ciCode: '44669', value:4 }
Unknown directive
262
},
Syntax not understood
263
previewMessageData: [{"appId":"1", message:"<div class=\"preview-warning-info\">This is only a preview. We may still be setting up your domain.</div><div>To get started customizing your site, click <b>Owner Login</b>. After domain setup is complete, view your live site at your domain address.</div><br/><div>Domain address:<br /><a href=\"http://[[domain]]\">[[domain]]</a></div>"}],
Unknown directive
264
wstAppName : 'GoDaddy Website Builder',
Unknown directive
265
gcWstAppName : 'Websites + Marketing',
Unknown directive
266
gDCrossSellISC : 'https://www.godaddy.com/websites/website-builder'
Unknown directive
268
});
Syntax not understood
270
$ss.showLauncher();
Syntax not understood
272
// display the main container (nav and about) which should be formatted by now
Syntax not understood
273
$j("#ss-mainContainer").css("visibility", "visible");
Syntax not understood
276
$ss.stage.showShareLinksPanel(true);
Syntax not understood
279
$j("#ss-description").linkify({fontColorParent: '#ss-description', initText: "Yaoi.official"});
Syntax not understood
280
$j("#ss-title").linkify({fontColorParent: '#ss-name', initText: "Yaoi"});
Syntax not understood
282
// show modal dialog if needed.
Syntax not understood
283
$ss.stage.showPreviewModal();
Syntax not understood
284
});
Syntax not understood
285
// ]]></script>
Syntax not understood
287
<script type="text/javascript">// <![CDATA[
Syntax not understood
289
$j(document).ready(function () {
Syntax not understood
293
var loginHref = $j("#login-link").attrSafe("href").replace(/&lcid=.*?(&|$)/gi, '&lcid=' + (location.hostname.toLowerCase() == $ss.stage.siteInfo.domain.toLowerCase()));
Syntax not understood
294
$j("#login-link").attrSafe("href", loginHref);
Syntax not understood
295
});
Syntax not understood
297
// ]]></script>
Syntax not understood
299
</head>
Syntax not understood
301
<body class="non-admin compliant rslrgd">
Syntax not understood
303
<div class="site-wrapper">
Syntax not understood
305
<img id="ss-background" class="ss-background" style="display: none; position: fixed; z-index:-1000; background-color: #FFFFFF; height: 100%; width:100%;" src="http://img1.wsimg.com/ip/v1.2.18/images/common/transparent.png" alt="background" />
Unknown directive
307
<div class="page" id="page">
Syntax not understood
309
<div id="content">
Syntax not understood
310
<div id="ss-mainContainer" style="visibility:hidden;">
Unknown directive
311
<div id="ss-main" class="ss-main">
Syntax not understood
313
<div id="ss-launcher" style="display: none" >
Unknown directive
314
<ul>
Syntax not understood
315
<li class="link-home"><a class="ss-service" href="javascript:$ss.hideWidgets();">Home</a></li>
Unknown directive
317
<li id="menu-affiliate-link" style="display:none;">
Unknown directive
319
</li>
Syntax not understood
320
</ul>
Syntax not understood
321
</div>
Syntax not understood
322
<div id="ss-about" class="no-launcher" >
Syntax not understood
324
<h1 id="ss-name" class="ss-title" style="zoom:1/*DNR: fixes IE bug*/; font-size: 52px; font-family:Arial;">Yaoi</h1>
Unknown directive
325
<div id="ss-description" class="ss-description" style="font-size: 28px; font-family:Times New Roman;">Yaoi.official</div>
Unknown directive
327
</div>
Syntax not understood
329
</div>
Syntax not understood
330
</div>
Syntax not understood
331
<div id="ss-widgetContainer" style="display:none;"></div>
Unknown directive
332
</div>
Syntax not understood
334
<div id="logindisplay">
Syntax not understood
336
<a href="https://sso.godaddy.com/?realm=idp&amp;app=instant-page&amp;path=login%3fartifact%3d%26domain%3dyaoi.com%26oid%3d%26sd%3d%26lcid%3dTrue%26idpinfo%3dnull%26auto%3dtrue%26source%3d" cicode="41766" id="login-link"></a>
Unknown directive
338
</div>
Syntax not understood
339
<div id="sharePanel"></div>
Syntax not understood
342
<div class="cross-sell">
Syntax not understood
343
<div class="blurb">
Syntax not understood
344
<span class="arrow"></span>
Syntax not understood
345
<span class="logo"></span>
Syntax not understood
346
A website created by GoDaddy’s
Syntax not understood
348
<a class="want-one-link" target="_blank" href="https://www.godaddy.com/websites/website-builder" rel="nofollow"><span><b>Website Builder</b></span></a>
Unknown directive
350
</div>
Syntax not understood
351
</div>
Syntax not understood
353
</div>
Syntax not understood
354
</div>
Syntax not understood
355
<script type='text/javascript'>'undefined' == typeof _trfd && (window._trfd = []), _trfd.push({ 'tccl.baseHost': 'secureserver.net' }), _trfd.push({ 'ap': 'IPv1' }), _trfd.push({ 'tccl.DataCenter': 'P3'}), _trfd.push({ 'tccl.ServerName': 'P3PWINSTPG002'});</script><script src='//img1.wsimg.com/tcc/tcc_l.combined.1.0.5.min.js' type='text/javascript'></script>
Unknown directive
356
</body>
Syntax not understood
357
</html>
Syntax not understood
358
<!-- Version: 1.8.0.0 -->
Unknown directive

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img

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

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of yaoi.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
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) 62
Performance 84
Accessibility 66
Best Practices 67
SEO 77
Progressive Web App 17
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://yaoi.com/
Updated: 5th May, 2021

4.48 seconds
First Contentful Paint (FCP)
15%
39%
46%

0.25 seconds
First Input Delay (FID)
2%
94%
4%

84

Performance

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

Metrics

Speed Index — 3.3 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 3.6 s
The time taken for the page to become fully interactive.
Total Blocking Time — 80 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.013
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 3.4 s
The time taken for the page's main thread to be quiet enough to handle input.
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 yaoi.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 Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://yaoi.com/
http/1.1
0
91.164999641478
6342
18271
200
text/html
Document
http://img1.wsimg.com/ip/v1.2.18/style/ss-1.0.0.0.css
http/1.1
103.14599983394
121.81300017983
5417
26600
200
text/css
Stylesheet
https://widget.starfieldtech.com/API.svc/jquery.js
http/1.1
103.36800012738
495.38899958134
262
0
301
https://widget.starfieldtech.com/API.svc/jquery-ui.js
http/1.1
103.63699961454
495.12199964374
264
0
301
http://img1.wsimg.com/ip/v1.2.18/scripts/ss-merged-1.0.0.0.js
http/1.1
104.01599947363
236.35500017554
14780
53778
200
application/x-javascript
Script
https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&user=745794&proxy=%2fCygnus%2fProxy&action=%2fCygnus%2fAction
http/1.1
104.20299973339
544.84200011939
141058
140897
200
text/javascript
Script
http://img1.wsimg.com/ip/v1.2.18/images/common/transparent.png
http/1.1
620.69499958307
674.15700014681
2066
1715
200
image/png
Image
http://img1.wsimg.com/tcc/tcc_l.combined.1.0.5.min.js
http/1.1
583.58899969608
618.79999935627
2568
5969
200
application/x-javascript
Script
https://img3.wsimg.com/widgetfw/jQuery/v1.8.0/jquery-ui.js
http/1.1
495.35199999809
575.79899951816
34477
131605
200
application/x-javascript
Script
https://img4.wsimg.com/starfield/jquery/v1.6.4/jquery.js
http/1.1
495.5739993602
663.88399992138
32516
91668
200
application/x-javascript
Script
http://img1.wsimg.com/ip/v1.2.18/images/common/tab_login.png
http/1.1
711.0620001331
750.41900016367
1935
1584
200
image/png
Image
http://img1.wsimg.com/ip/v1.2.18/images/common/flyout_repeat.png
http/1.1
711.35099977255
746.5429995209
475
126
200
image/png
Image
http://img1.wsimg.com/ip/v1.2.18/images/common/flyout_arrow.png
http/1.1
711.63199935108
748.02399985492
771
422
200
image/png
Image
http://img1.wsimg.com/ip/v1.2.18/images/common/gd/flyout_logo.png
http/1.1
711.99799980968
735.18299963325
1337
988
200
image/png
Image
https://img3.wsimg.com/starfield/curl/v1.5.2/curl.js
http/1.1
746.17199972272
892.67999958247
7564
18326
200
application/x-javascript
Script
http://img1.wsimg.com/ip/v1.2.18/style/jquery.gd.shareLinks.css
http/1.1
790.77199939638
827.1229993552
1154
2338
200
text/css
Stylesheet
http://img1.wsimg.com/ip/v1.2.18/images/common/shareIcons2.png
http/1.1
795.67399993539
816.6239997372
27108
26756
200
image/png
Image
http://img2.wsimg.com/starfield/sf.core/v1.5.2/sf.core.css
http/1.1
903.16499955952
945.47200016677
7071
38517
200
text/css
Stylesheet
http://img.secureserver.net/t/1/tl/event?cts=1620234459059&ap=IPv1&tce=1620234458333&tcs=1620234458333&tdc=1620234459285&tdclee=1620234459134&tdcles=1620234459060&tdi=1620234459059&tdl=1620234458429&tdle=1620234458333&tdls=1620234458333&tfs=1620234458333&tns=1620234458333&trqs=1620234458333&tre=1620234458425&trps=1620234458425&tles=1620234459285&tlee=1620234459285&dh=yaoi.com&dp=%2F&ua=Mozilla%2F5.0%20(Linux%3B%20Android%207.0%3B%20Moto%20G%20(4))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F90.0.4420.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&feedtype=perf&z=2021024698
http/1.1
954.94499988854
975.95599945635
801
0
301
https://img.secureserver.net/t/1/tl/event?cts=1620234459059&ap=IPv1&tce=1620234458333&tcs=1620234458333&tdc=1620234459285&tdclee=1620234459134&tdcles=1620234459060&tdi=1620234459059&tdl=1620234458429&tdle=1620234458333&tdls=1620234458333&tfs=1620234458333&tns=1620234458333&trqs=1620234458333&tre=1620234458425&trps=1620234458425&tles=1620234459285&tlee=1620234459285&dh=yaoi.com&dp=%2F&ua=Mozilla%2F5.0%20(Linux%3B%20Android%207.0%3B%20Moto%20G%20(4))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F90.0.4420.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&feedtype=perf&z=2021024698
http/1.1
976.3259999454
1081.3440000638
628
43
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
125.641
6.449
704.37
36.918
741.308
12.493
754.998
77.76
925.887
8.272
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Yaoi.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Yaoi.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Yaoi.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Yaoi.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Yaoi.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 19 KiB
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 Resource Size (Bytes) Potential Savings (Bytes)
http://img1.wsimg.com/ip/v1.2.18/images/common/shareIcons2.png
26756
19506
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 90 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://yaoi.com/
92.156
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Yaoi.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Yaoi.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 29 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&user=745794&proxy=%2fCygnus%2fProxy&action=%2fCygnus%2fAction
20281
http://img1.wsimg.com/tcc/tcc_l.combined.1.0.5.min.js
9526
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://img1.wsimg.com/ip/v1.2.18/images/common/transparent.png
0

Diagnostics

Avoids enormous network payloads — Total size was 282 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&user=745794&proxy=%2fCygnus%2fProxy&action=%2fCygnus%2fAction
141058
https://img3.wsimg.com/widgetfw/jQuery/v1.8.0/jquery-ui.js
34477
https://img4.wsimg.com/starfield/jquery/v1.6.4/jquery.js
32516
http://img1.wsimg.com/ip/v1.2.18/images/common/shareIcons2.png
27108
http://img1.wsimg.com/ip/v1.2.18/scripts/ss-merged-1.0.0.0.js
14780
https://img3.wsimg.com/starfield/curl/v1.5.2/curl.js
7564
http://img2.wsimg.com/starfield/sf.core/v1.5.2/sf.core.css
7071
http://yaoi.com/
6342
http://img1.wsimg.com/ip/v1.2.18/style/ss-1.0.0.0.css
5417
http://img1.wsimg.com/tcc/tcc_l.combined.1.0.5.min.js
2568
Avoids an excessive DOM size — 40 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
40
Maximum DOM Depth
Yaoi.official
9
Maximum Child Elements
Yaoi Yaoi.official Facebook Twitter MySpace Del.icio.us StumbleUpon A website …
5
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Yaoi.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.5 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://yaoi.com/
736.592
390.452
18.032
Unattributable
87.996
5.48
1.044
https://widget.starfieldtech.com/API.svc/jquery.js
80.128
51.512
10.064
https://img3.wsimg.com/starfield/curl/v1.5.2/curl.js
77.076
62.384
6.992
Minimizes main-thread work — 1.0 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
527.696
Other
186.14
Style & Layout
154.28
Rendering
82.888
Script Parsing & Compilation
52.712
Parse HTML & CSS
42.016
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 — 20 requests • 282 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
20
288594
Script
6
232963
Image
7
34320
Stylesheet
3
13642
Document
1
6342
Other
3
1327
Media
0
0
Font
0
0
Third-party
19
282252
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)
SHOW DETAILS
139239
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Yaoi Yaoi.official Facebook Twitter MySpace Del.icio.us StumbleUpon A website …
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
Yaoi
0.013341349345735
A website created by GoDaddy’s Website Builder
7.8718917000725E-6
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
http://img1.wsimg.com/tcc/tcc_l.combined.1.0.5.min.js
3593
156
http://img1.wsimg.com/ip/v1.2.18/scripts/ss-merged-1.0.0.0.js
3519
74
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

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

Metrics

First Contentful Paint — 3.1 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 3.5 s
The timing of the largest text or image that is painted.

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 640 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Yaoi.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://img1.wsimg.com/ip/v1.2.18/style/ss-1.0.0.0.css
5417
630
http://img1.wsimg.com/ip/v1.2.18/scripts/ss-merged-1.0.0.0.js
14780
921
https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&user=745794&proxy=%2fCygnus%2fProxy&action=%2fCygnus%2fAction
141058
2430

Opportunities

Remove unused JavaScript — Potential savings of 272 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&user=745794&proxy=%2fCygnus%2fProxy&action=%2fCygnus%2fAction
141058
121196
https://widget.starfieldtech.com/API.svc/jquery-ui.js
131605
117079
https://widget.starfieldtech.com/API.svc/jquery.js
91668
40277
Enable text compression — Potential savings of 104 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&user=745794&proxy=%2fCygnus%2fProxy&action=%2fCygnus%2fAction
140897
106137

Diagnostics

Serve static assets with an efficient cache policy — 1 resource found
Yaoi.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&user=745794&proxy=%2fCygnus%2fProxy&action=%2fCygnus%2fAction
0
141058

Other

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

Accessibility

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

Navigation

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

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<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.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Yaoi.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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
Yaoi.official

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
html

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that yaoi.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.

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.
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.
Name Version
jQuery
1.6.4
jQuery UI
1.8.11
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.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 13 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 Request Resolution
http://yaoi.com/
Allowed
http://img1.wsimg.com/ip/v1.2.18/style/ss-1.0.0.0.css
Allowed
http://img1.wsimg.com/ip/v1.2.18/scripts/ss-merged-1.0.0.0.js
Allowed
http://img1.wsimg.com/ip/v1.2.18/images/common/transparent.png
Allowed
http://img1.wsimg.com/tcc/tcc_l.combined.1.0.5.min.js
Allowed
http://img1.wsimg.com/ip/v1.2.18/images/common/tab_login.png
Allowed
http://img1.wsimg.com/ip/v1.2.18/images/common/flyout_repeat.png
Allowed
http://img1.wsimg.com/ip/v1.2.18/images/common/flyout_arrow.png
Allowed
http://img1.wsimg.com/ip/v1.2.18/images/common/gd/flyout_logo.png
Allowed
http://img1.wsimg.com/ip/v1.2.18/style/jquery.gd.shareLinks.css
Allowed
http://img1.wsimg.com/ip/v1.2.18/images/common/shareIcons2.png
Allowed
http://img2.wsimg.com/starfield/sf.core/v1.5.2/sf.core.css
Allowed
http://img.secureserver.net/t/1/tl/event?cts=1620234459059&ap=IPv1&tce=1620234458333&tcs=1620234458333&tdc=1620234459285&tdclee=1620234459134&tdcles=1620234459060&tdi=1620234459059&tdl=1620234458429&tdle=1620234458333&tdls=1620234458333&tfs=1620234458333&tns=1620234458333&trqs=1620234458333&tre=1620234458425&trps=1620234458425&tles=1620234459285&tlee=1620234459285&dh=yaoi.com&dp=%2F&ua=Mozilla%2F5.0%20(Linux%3B%20Android%207.0%3B%20Moto%20G%20(4))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F90.0.4420.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&feedtype=perf&z=2021024698
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 8 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
SHOW DETAILS
5
Medium
SHOW DETAILS
3
High

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
http://img1.wsimg.com/ip/v1.2.18/images/common/transparent.png
1820 x 1820
200 x 200
3640 x 3640

Audits

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

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for yaoi.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 yaoi.com on mobile screens.
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Crawling and Indexing

robots.txt is not valid — 298 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
3
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
Unknown directive
4
<html xmlns="http://www.w3.org/1999/xhtml" version="XHTML+RDFa 1.1"
Unknown directive
5
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
Unknown directive
6
xsi:schemaLocation="http://www.w3.org/1999/xhtml http://www.w3.org/MarkUp/SCHEMA/xhtml-rdfa-2.xsd"
Unknown directive
7
xmlns:og="http://ogp.me/ns#">
Unknown directive
8
<head>
Syntax not understood
9
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
Syntax not understood
10
<meta name="viewport" content="width=1024" />
Syntax not understood
12
<meta name="description" content="Check out this GoDaddy hosted webpage! http://yaoi.com." />
Unknown directive
13
<meta property="og:title" content="Yaoi" />
Unknown directive
14
<meta property="og:description" content="Check out this GoDaddy hosted webpage! http://yaoi.com." />
Unknown directive
16
<meta property="og:image" content="http://imagesak.websitetonight.com/skins/pl.gd/images/logo1.gif" />
Unknown directive
19
<link rel="shortcut icon" type="image/ico" href="http://img1.wsimg.com/ip/v1.2.18/images/favicon.ico" />
Unknown directive
20
<link rel="icon" type="image/png" href="http://img1.wsimg.com/ip/v1.2.18/images/favicon.jpg" />
Unknown directive
21
<title>
Syntax not understood
22
Yaoi
Syntax not understood
23
</title>
Syntax not understood
25
<link href="http://img1.wsimg.com/ip/v1.2.18/style/ss-1.0.0.0.css" rel="stylesheet" type="text/css" />
Unknown directive
30
<script type="text/javascript" src="https://widget.starfieldtech.com/API.svc/jquery.js"></script>
Unknown directive
31
<script type="text/javascript" src="https://widget.starfieldtech.com/API.svc/jquery-ui.js"></script>
Unknown directive
33
<script src="http://img1.wsimg.com/ip/v1.2.18/scripts/ss-merged-1.0.0.0.js" type="text/javascript"></script>
Unknown directive
35
<script type="text/javascript" src="https://widget.starfieldtech.com/API.svc/cygnus-duel.js?app=SS&amp;user=745794&amp;proxy=%2fCygnus%2fProxy&amp;action=%2fCygnus%2fAction"></script>
Unknown directive
39
<script type="text/javascript">// <![CDATA[
Syntax not understood
40
$j(document).ready( function() {
Syntax not understood
41
// ---- Configure the application settings for communicating with Cygnus.
Syntax not understood
42
$c.Stage.applicationEventHandlerElement = $j("#page");
Syntax not understood
44
var appSettings = $c.Stage.applicationSettings;
Syntax not understood
45
appSettings.showConfigControl = false;
Syntax not understood
46
appSettings.showToggleControl = false;
Syntax not understood
47
appSettings.showCloseControl = true;
Syntax not understood
48
appSettings.hideCloseControlOnEdit = true;
Syntax not understood
49
appSettings.widgetActions.closeControlClick = function (widgetId, widgetType) {
Syntax not understood
50
// this will hide the widget since it's already open
Syntax not understood
51
$ss.showWidget(widgetId, $j(".ss-service[wid='" + widgetId + "']"));
Syntax not understood
52
};
Syntax not understood
53
appSettings.widgetEvents.saveConfigSuccess =
Syntax not understood
54
function(widgetId, widgetType) {
Syntax not understood
55
var li = $j("li:has(a[wid='" + widgetId + "'])");
Unknown directive
56
if (li.length > 0)
Syntax not understood
57
{
Syntax not understood
58
li.show();
Syntax not understood
59
li.find("a").removeClass("uninitialized");
Syntax not understood
60
$ss.showLauncher();
Syntax not understood
61
$ss.showSavedConfirmation('App saved successfully.');
Syntax not understood
62
}
Syntax not understood
63
else
Syntax not understood
64
{
Syntax not understood
65
if (widgetType == "fbpage")
Syntax not understood
66
{
Syntax not understood
67
$ss.showSavedConfirmation('Facebook Page saved successfully.');
Syntax not understood
68
}
Syntax not understood
69
}
Syntax not understood
70
};
Syntax not understood
71
appSettings.widgetEvents.saveConfigFailure =
Syntax not understood
72
function(widgetId, widgetType) {
Syntax not understood
73
//alert("failed!");
Syntax not understood
74
};
Syntax not understood
75
appSettings.widgetEvents.cancelledConfig =
Syntax not understood
76
function(widgetId, widgetType) {
Syntax not understood
77
var a = $j("a[wid='" + widgetId + "']");
Syntax not understood
78
if (a.hasClass("uninitialized"))
Syntax not understood
79
{
Syntax not understood
80
//close the widget since it's already open if it's not be initialized.
Syntax not understood
81
$ss.showWidget(widgetId, $j(".ss-service[wid='" + widgetId + "']"));
Syntax not understood
82
$ss.openAdminPanel('widgets');
Syntax not understood
83
}
Syntax not understood
84
};
Syntax not understood
85
appSettings.widgetEvents.openedConfig =
Syntax not understood
86
function(widgetId, widgetType)
Syntax not understood
87
{
Syntax not understood
88
if (widgetType != "fbpage")
Syntax not understood
89
{
Syntax not understood
90
// close tabs
Syntax not understood
91
$ss.hideAdminPanel();
Syntax not understood
92
}
Syntax not understood
93
};
Syntax not understood
94
appSettings.widgetEvents.closedConfig =
Syntax not understood
95
function(widgetId, widgetType)
Syntax not understood
96
{
Syntax not understood
97
if (widgetType == "fbpage")
Syntax not understood
98
{
Syntax not understood
99
$ss.facebookPage.close(widgetId);
Syntax not understood
100
}
Syntax not understood
101
};
Syntax not understood
102
appSettings.widgetEvents.dataModified =
Syntax not understood
103
function(widgetId, widgetType, data) {
Syntax not understood
104
if ($j.isPopulated(data))
Syntax not understood
105
{
Syntax not understood
106
if (widgetType == "fbpage")
Syntax not understood
107
{
Syntax not understood
108
$j('.widget-fbpage-title').text(data.Title.value);
Syntax not understood
109
}
Syntax not understood
110
else
Syntax not understood
111
{
Syntax not understood
112
var a = $j("#ss-launcher").find("a[wid=" + widgetId + "]");
Syntax not understood
113
var children = a.children();
Syntax not understood
114
a
Syntax not understood
115
.text(data.LinkTitle.value)
Syntax not understood
116
.append(children);
Syntax not understood
117
$j("#widgets-added-list").find("li[wid=" + widgetId + "] .widget-added-label-title").text(data.LinkTitle.value);
Syntax not understood
118
}
Syntax not understood
119
}
Syntax not understood
120
};
Syntax not understood
121
appSettings.widgetEvents.revealed =
Syntax not understood
122
function(widgetId, widgetType) {
Syntax not understood
123
if ($j.isFunction($ss.stage.layout.revealed)) $ss.stage.layout.revealed();
Syntax not understood
124
};
Syntax not understood
125
appSettings.widgetEvents.obscured =
Syntax not understood
126
function(widgetId, widgetType) {
Syntax not understood
127
if ($j.isFunction($ss.stage.layout.obscured)) $ss.stage.layout.obscured();
Syntax not understood
128
};
Syntax not understood
130
appSettings.widgetEvents.widgetModalDisplayed =
Syntax not understood
131
appSettings.widgetEvents.contentUpdated =
Syntax not understood
132
function(wigetId, widgetType) { $ss.fixPalette(); };
Syntax not understood
134
appSettings.applicationUtilityProviders.getImages = function(widgetId, success, failure)
Syntax not understood
135
{
Syntax not understood
136
// show a dialog for the user to select images that were uploaded as backgrounds
Syntax not understood
137
// one day maybe we can change this to be a uploader instead.
Syntax not understood
138
$ss.facebookPage.gatherImages(null, function(result) {
Syntax not understood
139
// if the user closed the dialog
Syntax not understood
140
if (result)
Syntax not understood
141
{
Syntax not understood
142
success(result.images);
Syntax not understood
143
}
Syntax not understood
144
else // do the failure callback otherwise.
Syntax not understood
145
{
Syntax not understood
146
failure({ error: 'Error', message: 'Unable to get images.' });
Unknown directive
147
}
Syntax not understood
148
});
Syntax not understood
149
}
Syntax not understood
151
appSettings.baseWidgetColors = {
Syntax not understood
152
background: '#091249',
Unknown directive
153
textTitle: '#FFFFFF',
Unknown directive
154
textContent: '#FFFFFF',
Unknown directive
155
textLinks: '#84B6E7',
Unknown directive
156
borderTitle: '#84B6E7'
Unknown directive
157
};
Syntax not understood
159
appSettings.applicationEvents.colorsChanged = "widgets.colorsChanged";
Syntax not understood
161
appSettings.widgetInitializeOptions.fbpage = { hideFacebookConnectDisplay: true };
Unknown directive
163
appSettings.modalContainerCssClass ="modal-container";
Syntax not understood
165
$c.CommManager.applicationData = { "domainName": "yaoi.com" };
Unknown directive
167
// ---- DONE application setting configuration
Syntax not understood
169
// load/style the page and all it's components
Syntax not understood
170
$ss = SimpleSite({
Syntax not understood
171
basePath: "/",
Unknown directive
172
cdnImagePath: "http://img1.wsimg.com/ip/v1.2.18/images/",
Unknown directive
173
cdnCssPath: "http://img1.wsimg.com/ip/v1.2.18/style/",
Unknown directive
174
eventReceiver: "#page",
Unknown directive
175
background: {"id":1,"originalSrc":"http://img1.wsimg.com/ip/v1.2.18/images/common/transparent.png","src":"http://img1.wsimg.com/ip/v1.2.18/images/common/transparent.png","thumbnail":"http://img1.wsimg.com/ip/v1.2.18/images/common/transparent.png","orientation":"3","variation":"","isUserOwner":false,"cropHistory":null,"stockBackgroundId":0,"isUncropped":false},
Unknown directive
176
layout: {"id":7,"name":"Top Menu","type":"3","variation":"c","VariationName":"Centered"},
Unknown directive
177
layoutControls:
Unknown directive
178
{
Syntax not understood
179
content: '#ss-main',
Unknown directive
180
title: '#ss-name',
Unknown directive
181
description: '#ss-description',
Unknown directive
182
launcher: '#ss-launcher',
Unknown directive
183
page: '#page',
Unknown directive
184
widgetContainer: '#ss-widgetContainer',
Unknown directive
185
about: '#ss-about',
Unknown directive
186
background: '#ss-background'
Unknown directive
187
},
Syntax not understood
188
palette: {
Unknown directive
189
"id": 43,
Unknown directive
190
"name": null,
Unknown directive
191
"userCreated": false,
Unknown directive
192
"isActive": true,
Unknown directive
193
"backgrounds": {
Unknown directive
194
"page": "#FFFFFF",
Unknown directive
195
"main": "#091249",
Unknown directive
196
"meta": "#FFFFFF",
Unknown directive
197
"block": "#091249"
Unknown directive
198
},
Syntax not understood
199
"fonts": {
Unknown directive
200
"title": "#477EB4",
Unknown directive
201
"description": "#BBBBBB",
Unknown directive
202
"services": "#84B6E7",
Unknown directive
203
"primary": "#FFFFFF",
Unknown directive
204
"secondary": "#FFFFFF",
Unknown directive
205
"links": "#84B6E7"
Unknown directive
206
}
Syntax not understood
207
},
Syntax not understood
208
fonts: {"titleFontId":0,"generalFontId":4,"titleSize":52,"descriptionSize":28,"servicesSize":24,"titleFontIsEmbed":false,"generalFontIsEmbed":false},
Unknown directive
209
titleFont: {"id":0,"appliesTo":"title","faceName":"Arial","defaultSize":60,"isEmbed":false},
Unknown directive
210
generalFont: {"id":4,"appliesTo":"title","faceName":"Times New Roman","defaultSize":60,"isEmbed":false},
Unknown directive
211
fontControls:
Unknown directive
212
{
Syntax not understood
213
title: {reset: '.ss-title', apply: '.ss-title' },
Unknown directive
214
description: {reset: '.ss-description', apply: '.ss-description' },
Unknown directive
215
services: {reset: '.ss-service', apply: '.ss-service'},
Unknown directive
216
block: {reset: '.ss-block, #ss-widgetContainer', apply: '.ss-block, #ss-widgetContainer' }
Unknown directive
217
},
Syntax not understood
218
styleControls:
Unknown directive
219
{
Syntax not understood
220
// Page background
Syntax not understood
221
background: {reset: '#ss-background', apply: '#ss-background' },
Unknown directive
222
title: {reset: '.ss-title', apply: '.ss-title', borders: {reset: '#ss-launcher li', apply: '#ss-launcher li'} },
Unknown directive
223
description: {reset: '.ss-description', apply: '.ss-description' },
Unknown directive
224
services: {reset: '.ss-service', apply: '.ss-service', borders: {reset: '.accordion-arrow-inheritor, .accordion-button', apply: '.accordion-arrow-inheritor, .accordion-button'}},
Unknown directive
225
block: {
Unknown directive
226
reset: '.ss-block, #ss-widgetContainer',
Unknown directive
227
apply: '.ss-block, #ss-widgetContainer, .modal-widget',
Unknown directive
228
foreground: { apply: '.contrast' }
Unknown directive
229
},
Syntax not understood
230
// Widget text
Syntax not understood
231
primary: {
Unknown directive
232
reset: '.widget-container .title-bar, .widget-container .text-highlight, .widget-instance h1, .widget-instance h2, .widget-instance h3, .widget-instance h4, .widget-instance h5, .widget-instance h6, .modal-widget .title-bar, .modal-widget .text-highlight, .modal-widget h1, .modal-widget h2, .modal-widget h3, .modal-widget h4, .modal-widget h5, .modal-widget h6',
Unknown directive
233
apply: '.widget-container .title-bar, .widget-container .text-highlight, .widget-instance h1, .widget-instance h2, .widget-instance h3, .widget-instance h4, .widget-instance h5, .widget-instance h6, .modal-widget .title-bar, .modal-widget .text-highlight, .modal-widget h1, .modal-widget h2, .modal-widget h3, .modal-widget h4, .modal-widget h5, .modal-widget h6'
Unknown directive
234
},
Syntax not understood
235
secondary: {
Unknown directive
236
reset: '.widget-instance, .widget-instance div:not(.watermark, .charCounter, .text-highlight, .contrast, .error, .form-errors, .required, :isThirdPartyInclude), .widget-instance span:not(.watermark, .charCounter, .text-highlight, .contrast, .error, .form-errors, .required, :isThirdPartyInclude), .widget-instance li, .widget-instance p, .modal-widget, .modal-widget div:not(.watermark, .charCounter), .modal-widget li, .modal-widget span:not(.text-highlight,.contrast), .modal-widget p',
Unknown directive
237
apply: '.widget-instance, .widget-instance div:not(.watermark, .charCounter, .text-highlight, .contrast, .error, .form-errors, .required, :isThirdPartyInclude), .widget-instance span:not(.watermark, .charCounter, .text-highlight, .contrast, .error, .form-errors, .required, :isThirdPartyInclude), .widget-instance li, .widget-instance p, .modal-widget, .modal-widget div:not(.watermark, .charCounter), .modal-widget li, .modal-widget span:not(.text-highlight,.welcome-subtitle,.contrast), .modal-widget p',
Unknown directive
238
background: { apply: '.contrast, .speech-balloon-tail' },
Unknown directive
239
borders: { apply: '.speech-balloon-tail' }
Unknown directive
240
},
Syntax not understood
241
//main: { reset: '#ss-launcher, .modal-widget', apply: '.modal-widget, .layout3-c #ss-launcher, .layout2-c #ss-launcher, .layout2-l #ss-launcher, .layout2-r #ss-launcher' }, //'.ss-main, .layout3-c #ss-launcher',
Unknown directive
242
//meta: { reset: '#ss-main', apply: '.layout1-c #ss-main, .layout1-l #ss-main, .layout1-r #ss-main, .layout4-c #ss-main, .layout4-l #ss-main, .layout4-r #ss-main' }, //'.ss-main, .layout3-c #ss-launcher',
Unknown directive
243
main: { reset: '#ss-launcher', apply: '#ss-launcher' },
Unknown directive
244
meta: { reset: '#ss-about', apply: '#ss-about' }, //'.ss-main, .layout3-c #ss-launcher',
Unknown directive
245
links: { reset: '.modal-widget a', apply: '.widget-instance a:not(.contrast, :isInWidgetConfigPanel, :isThirdPartyInclude), .modal-widget a:not(.welcome-link), a.widget-link', borders: {reset: '.widget-container .title-bar, .widget-container .contrast-border, hr', apply: '.widget-container .title-bar, .widget-container .contrast-border, hr' }},
Unknown directive
246
page: { reset: '.ss-background, body', apply: '.ss-background, body' },
Unknown directive
247
launcher: { reset: '#ss-launcher', apply: '#ss-launcher' },
Unknown directive
248
widgetContainer: { reset: '#ss-widgetContainer', apply: '#ss-widgetContainer' }
Unknown directive
249
},
Syntax not understood
250
siteInfo: {
Unknown directive
251
title: "Yaoi",
Unknown directive
252
description: "Yaoi.official",
Unknown directive
253
domain: "yaoi.com",
Unknown directive
254
showShareLinks: true
Unknown directive
255
},
Syntax not understood
256
shareLinksData: {
Unknown directive
257
twitter: { ciCode: '44667', message: "Check out this GoDaddy hosted webpage! http://yaoi.com.", value:1 },
Unknown directive
258
facebook: { ciCode: '44670', value:0 },
Unknown directive
259
myspace: { ciCode: '44666', message: "Yaoi", value:2 },
Unknown directive
260
delicious: { ciCode: '44668', message: "Check out this GoDaddy hosted webpage! http://yaoi.com.", value:3 },
Unknown directive
261
stumbleupon: { ciCode: '44669', value:4 }
Unknown directive
262
},
Syntax not understood
263
previewMessageData: [{"appId":"1", message:"<div class=\"preview-warning-info\">This is only a preview. We may still be setting up your domain.</div><div>To get started customizing your site, click <b>Owner Login</b>. After domain setup is complete, view your live site at your domain address.</div><br/><div>Domain address:<br /><a href=\"http://[[domain]]\">[[domain]]</a></div>"}],
Unknown directive
264
wstAppName : 'GoDaddy Website Builder',
Unknown directive
265
gcWstAppName : 'Websites + Marketing',
Unknown directive
266
gDCrossSellISC : 'https://www.godaddy.com/websites/website-builder'
Unknown directive
268
});
Syntax not understood
270
$ss.showLauncher();
Syntax not understood
272
// display the main container (nav and about) which should be formatted by now
Syntax not understood
273
$j("#ss-mainContainer").css("visibility", "visible");
Syntax not understood
276
$ss.stage.showShareLinksPanel(true);
Syntax not understood
279
$j("#ss-description").linkify({fontColorParent: '#ss-description', initText: "Yaoi.official"});
Syntax not understood
280
$j("#ss-title").linkify({fontColorParent: '#ss-name', initText: "Yaoi"});
Syntax not understood
282
// show modal dialog if needed.
Syntax not understood
283
$ss.stage.showPreviewModal();
Syntax not understood
284
});
Syntax not understood
285
// ]]></script>
Syntax not understood
287
<script type="text/javascript">// <![CDATA[
Syntax not understood
289
$j(document).ready(function () {
Syntax not understood
293
var loginHref = $j("#login-link").attrSafe("href").replace(/&lcid=.*?(&|$)/gi, '&lcid=' + (location.hostname.toLowerCase() == $ss.stage.siteInfo.domain.toLowerCase()));
Syntax not understood
294
$j("#login-link").attrSafe("href", loginHref);
Syntax not understood
295
});
Syntax not understood
297
// ]]></script>
Syntax not understood
299
</head>
Syntax not understood
301
<body class="non-admin compliant rslrgd">
Syntax not understood
303
<div class="site-wrapper">
Syntax not understood
305
<img id="ss-background" class="ss-background" style="display: none; position: fixed; z-index:-1000; background-color: #FFFFFF; height: 100%; width:100%;" src="http://img1.wsimg.com/ip/v1.2.18/images/common/transparent.png" alt="background" />
Unknown directive
307
<div class="page" id="page">
Syntax not understood
309
<div id="content">
Syntax not understood
310
<div id="ss-mainContainer" style="visibility:hidden;">
Unknown directive
311
<div id="ss-main" class="ss-main">
Syntax not understood
313
<div id="ss-launcher" style="display: none" >
Unknown directive
314
<ul>
Syntax not understood
315
<li class="link-home"><a class="ss-service" href="javascript:$ss.hideWidgets();">Home</a></li>
Unknown directive
317
<li id="menu-affiliate-link" style="display:none;">
Unknown directive
319
</li>
Syntax not understood
320
</ul>
Syntax not understood
321
</div>
Syntax not understood
322
<div id="ss-about" class="no-launcher" >
Syntax not understood
324
<h1 id="ss-name" class="ss-title" style="zoom:1/*DNR: fixes IE bug*/; font-size: 52px; font-family:Arial;">Yaoi</h1>
Unknown directive
325
<div id="ss-description" class="ss-description" style="font-size: 28px; font-family:Times New Roman;">Yaoi.official</div>
Unknown directive
327
</div>
Syntax not understood
329
</div>
Syntax not understood
330
</div>
Syntax not understood
331
<div id="ss-widgetContainer" style="display:none;"></div>
Unknown directive
332
</div>
Syntax not understood
334
<div id="logindisplay">
Syntax not understood
336
<a href="https://sso.godaddy.com/?realm=idp&amp;app=instant-page&amp;path=login%3fartifact%3d%26domain%3dyaoi.com%26oid%3d%26sd%3d%26lcid%3dTrue%26idpinfo%3dnull%26auto%3dtrue%26source%3d" cicode="41766" id="login-link"></a>
Unknown directive
338
</div>
Syntax not understood
339
<div id="sharePanel"></div>
Syntax not understood
342
<div class="cross-sell">
Syntax not understood
343
<div class="blurb">
Syntax not understood
344
<span class="arrow"></span>
Syntax not understood
345
<span class="logo"></span>
Syntax not understood
346
A website created by GoDaddy’s
Syntax not understood
348
<a class="want-one-link" target="_blank" href="https://www.godaddy.com/websites/website-builder" rel="nofollow"><span><b>Website Builder</b></span></a>
Unknown directive
350
</div>
Syntax not understood
351
</div>
Syntax not understood
353
</div>
Syntax not understood
354
</div>
Syntax not understood
355
<script type='text/javascript'>'undefined' == typeof _trfd && (window._trfd = []), _trfd.push({ 'tccl.baseHost': 'secureserver.net' }), _trfd.push({ 'ap': 'IPv1' }), _trfd.push({ 'tccl.DataCenter': 'P3'}), _trfd.push({ 'tccl.ServerName': 'P3PWINSTPG004'});</script><script src='//img1.wsimg.com/tcc/tcc_l.combined.1.0.5.min.js' type='text/javascript'></script>
Unknown directive
356
</body>
Syntax not understood
357
</html>
Syntax not understood
358
<!-- Version: 1.8.0.0 -->
Unknown directive

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img

Mobile Friendly

Document doesn't use legible font sizes — 58.49% 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
SHOW DETAILS
.gd-shareLinks
41.51%
11px
SHOW DETAILS
58.49%
≥ 12px

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

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

PWA Optimized

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 yaoi.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

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

Web Hosting Provider

Name IP Address
GoDaddy.com, LLC
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
GoDaddy.com, LLC 23.57.132.86
Security

Visitor Safety

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

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
yaoi.com. 97.74.42.79 IN 599

NS Records

Host Nameserver Class TTL
yaoi.com. ns55.domaincontrol.com. IN 3599
yaoi.com. ns56.domaincontrol.com. IN 3599

MX Records

Priority Host Server Class TTL
10 yaoi.com. mailstore1.secureserver.net. IN 3599
0 yaoi.com. smtp.secureserver.net. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
yaoi.com. ns55.domaincontrol.com. dns.jomax.net. 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/10.0
Date: 5th May, 2021
Content-Length: 18271
X-AspNetMvc-Version: 3.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET

Whois Lookup

Created: 3rd January, 1999
Changed: 28th April, 2015
Expires: 3rd January, 2023
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: ns55.domaincontrol.com
ns56.domaincontrol.com
Owner Name: Registration Private
Owner Organization: Domains By Proxy, LLC
Owner Street: DomainsByProxy.com
14455 N. Hayden Road
Owner Post Code: 85260
Owner City: Scottsdale
Owner State: Arizona
Owner Country: US
Owner Phone: +1.4806242599
Owner Email: YAOI.COM@domainsbyproxy.com
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
14455 N. Hayden Road
Admin Post Code: 85260
Admin City: Scottsdale
Admin State: Arizona
Admin Country: US
Admin Phone: +1.4806242599
Admin Email: YAOI.COM@domainsbyproxy.com
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
14455 N. Hayden Road
Tech Post Code: 85260
Tech City: Scottsdale
Tech State: Arizona
Tech Country: US
Tech Phone: +1.4806242599
Tech Email: YAOI.COM@domainsbyproxy.com
Full Whois: Domain Name: YAOI.COM
Registry Domain ID: 4189442_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2015-04-28T04:06:55Z
Creation Date: 1999-01-03T00:00:00Z
Registrar Registration Expiration Date: 2023-01-03T00:00:00Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited http://www.icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 14455 N. Hayden Road
Registrant City: Scottsdale
Registrant State/Province: Arizona
Registrant Postal Code: 85260
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: +1.4806242598
Registrant Fax Ext:
Registrant Email: YAOI.COM@domainsbyproxy.com
Registry Tech ID: Not Available From Registry
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 14455 N. Hayden Road
Tech City: Scottsdale
Tech State/Province: Arizona
Tech Postal Code: 85260
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: +1.4806242598
Tech Fax Ext:
Tech Email: YAOI.COM@domainsbyproxy.com
Registry Admin ID: Not Available From Registry
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin Street: 14455 N. Hayden Road
Admin City: Scottsdale
Admin State/Province: Arizona
Admin Postal Code: 85260
Admin Country: US
Admin Phone: +1.4806242599
Admin Phone Ext:
Admin Fax: +1.4806242598
Admin Fax Ext:
Admin Email: YAOI.COM@domainsbyproxy.com
Name Server: NS55.DOMAINCONTROL.COM
Name Server: NS56.DOMAINCONTROL.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-05-05T17:07:22Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

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

Nameservers

Name IP Address
ns55.domaincontrol.com 97.74.107.28
ns56.domaincontrol.com 173.201.75.28
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
yaoi.ca
0/5
yaoi.com.br
0/5
yaoi.de
0/5
yaoi.info
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
dearcinema.com
0/5
erain.com
$391 USD 1/5
hediyeyarat.com
0/5
inrealestates.com
0/5
irissilks.com
0/5
Love W3 Snoop?
Update Now

Recently Updated

seiya-saiga.com
iblups.tv
youjizz.com
pining.com
youtobe.com
xhemster.com
tivejo.com
fucklocal.com
cutscenes.net
kpopalbums.com

Recently Viewed

wstter.com
asopori.com
filehold.com
advancedhandandwrist.org
vbaf.com
unfiltered.in
khu3s.net
toko.ly
xxxgaga.net
jelajahjogjatour.com