chichananime.com

chichananime.com is SSL secured

Free website and domain report on chichananime.com

Last Updated: 25th September, 2022 Update Now
Overview

Snoop Summary for chichananime.com

This is a free and comprehensive report about chichananime.com. The domain chichananime.com is currently hosted on a server located in United States with the IP address 172.93.103.99, where USD is the local currency and the local language is English. Our records indicate that chichananime.com is privately registered by PERFECT PRIVACY, LLC. If chichananime.com was to be sold it would possibly be worth $324 USD (based on the daily revenue potential of the website over a 24 month period). Chichananime.com is somewhat popular with an estimated 151 daily unique visitors. This report was last updated 25th September, 2022.

About chichananime.com

Site Preview: chichananime.com chichananime.com
Title:
Description:
Keywords and Tags: blogs, wiki
Related Terms:
Fav Icon:
Age: Over 2 years old
Domain Created: 17th January, 2022
Domain Updated: 16th May, 2022
Domain Expires: 17th January, 2023
Review

Snoop Score

1/5

Valuation

$324 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 7,301,679
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 7
Moz Page Authority: 17

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 151
Monthly Visitors: 4,596
Yearly Visitors: 55,115
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $13 USD
Yearly Revenue: $157 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: chichananime.com 16
Domain Name: chichananime 12
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 92
Performance 96
Accessibility 78
Best Practices 92
SEO 100
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
96

Performance

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

Metrics

Time to Interactive — 1.0 s
The time taken for the page to become fully interactive.
Speed Index — 1.2 s
The time taken for the page contents to be visibly populated.
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).
Largest Contentful Paint — 1.1 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.023
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
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://chichananime.com/
http/1.1
0
74.50499990955
832
472
200
text/html
Document
http://chichananime.com/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTY1NTA0MTE3MiwiaWF0IjoxNjU1MDMzOTcyLCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIycnJ0cDg3cWVwNTgyZmwzdDgycTZtaTgiLCJuYmYiOjE2NTUwMzM5NzIsInRzIjoxNjU1MDMzOTcyMDM2ODE4fQ.C7ibOotHOWveME_TQ3tjotUrjkv695kuia1lFL-yS4s&sid=5370fc9a-ea44-11ec-bacb-77edc0c82caa
http/1.1
96.762999892235
731.65799980052
423
0
302
text/plain
http://ww1.chichananime.com/
http/1.1
733.55799983256
777.17699995264
1959
1747
200
text/html
Document
http://ww1.chichananime.com/js/parking.2.90.1.js
http/1.1
790.13399989344
894.00299987756
22652
69039
200
application/javascript
Script
http://ww1.chichananime.com/_fd
http/1.1
910.7509998139
1006.6050000023
2337
3061
200
text/html
Fetch
https://www.google.com/adsense/domains/caf.js
h2
911.80899995379
926.32699990645
53600
145082
200
text/javascript
Script
http://ww1.chichananime.com/px.gif?ch=1&rn=1.6563030780863952
http/1.1
914.15899991989
970.85799998604
421
42
200
image/gif
Image
http://ww1.chichananime.com/px.gif?ch=2&rn=1.6563030780863952
http/1.1
914.34599994682
959.15699983016
421
42
200
image/gif
Image
https://partner.googleadservices.com/gampad/cookie.js?domain=ww1.chichananime.com&client=dp-bodis30_3ph&product=SAS&callback=__sasCookie
h2
1018.2969998568
1027.7989997994
825
193
200
text/javascript
Script
https://www.google.com/afs/ads?psid=3762894382&pcsa=false&channel=pid-bodis-gcontrol139%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol311%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol446&client=dp-bodis30_3ph&r=m&hl=en&max_radlink_len=60&type=3&uiopt=true&swp=as-drid-2898040491288658&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300953%2C17300956&format=r3&nocache=1571655033972989&num=0&output=afd_ads&domain_name=ww1.chichananime.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1655033972990&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=77&frm=0&uio=-&cont=rs&jsid=caf&jsv=50759&rurl=http%3A%2F%2Fww1.chichananime.com%2F&referer=http%3A%2F%2Fchichananime.com%2F
h2
1039.8979999591
1118.0059998296
2379
5609
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=0
h2
1128.7659998052
1143.3379999362
53582
145057
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2312254d
h2
1175.8929998614
1182.2059999686
1187
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
h2
1176.0739998426
1183.6170000024
1194
444
200
image/svg+xml
Image
https://fonts.googleapis.com/css?family=Quicksand
h2
1211.5959997755
1218.5029999819
1221
1090
200
text/css
Stylesheet
http://ww1.chichananime.com/_tr
http/1.1
1238.3799999952
1307.0239999797
559
2
200
text/html
Fetch
https://fonts.gstatic.com/s/quicksand/v29/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xDwxUD2GFw.woff
h2
1309.9459998775
1313.4569998365
18163
17236
200
font/woff
Font
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=tcocia59bnjb&aqid=ddClYoLYAsXtowbKzKvwBw&psid=3762894382&pbt=bs&adbx=475&adby=65.8125&adbh=496&adbw=400&adbah=160%2C160%2C160&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=5075900582475864444&csala=17%7C94%7C29%7C49&lle=0&llm=1000&ifv=0&usr=1
h2
2710.7149998192
2730.5659998674
332
0
204
text/html
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)
122.739
9.175
822.818
7.484
941.118
16.18
979.148
9.023
1051.147
33.1
1084.261
7.964
1163.38
5.971
1195.051
27.191
1228.072
5.178
1233.259
9.563
1249.055
31.803
1350.816
7.17
1375.994
7.287
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Chichananime.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Chichananime.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Chichananime.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Chichananime.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Chichananime.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Chichananime.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 62 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.google.com/adsense/domains/caf.js
53600
32374
https://www.google.com/adsense/domains/caf.js?pac=0
53582
31407
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 40 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://ww1.chichananime.com/
44.613
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Chichananime.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 0 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)
http://ww1.chichananime.com/js/parking.2.90.1.js
144
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 158 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
53600
https://www.google.com/adsense/domains/caf.js?pac=0
53582
http://ww1.chichananime.com/js/parking.2.90.1.js
22652
https://fonts.gstatic.com/s/quicksand/v29/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xDwxUD2GFw.woff
18163
https://www.google.com/afs/ads?psid=3762894382&pcsa=false&channel=pid-bodis-gcontrol139%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol311%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol446&client=dp-bodis30_3ph&r=m&hl=en&max_radlink_len=60&type=3&uiopt=true&swp=as-drid-2898040491288658&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300953%2C17300956&format=r3&nocache=1571655033972989&num=0&output=afd_ads&domain_name=ww1.chichananime.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1655033972990&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=77&frm=0&uio=-&cont=rs&jsid=caf&jsv=50759&rurl=http%3A%2F%2Fww1.chichananime.com%2F&referer=http%3A%2F%2Fchichananime.com%2F
2379
http://ww1.chichananime.com/_fd
2337
http://ww1.chichananime.com/
1959
https://fonts.googleapis.com/css?family=Quicksand
1221
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
1194
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2312254d
1187
Uses efficient cache policy on static assets — 2 resources found
Chichananime.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://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
82800000
1194
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2312254d
82800000
1187
Avoids an excessive DOM size — 17 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
17
Maximum DOM Depth
5
Maximum Child Elements
7
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Chichananime.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://ww1.chichananime.com/js/parking.2.90.1.js
73.32
68.597
1.16
https://www.google.com/adsense/domains/caf.js?pac=0
65.963
40.11
2.361
https://www.google.com/adsense/domains/caf.js
50.409
34.213
2.196
Minimizes main-thread work — 0.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
150.608
Other
66.95
Style & Layout
29.287
Rendering
11.521
Script Parsing & Compilation
9.308
Parse HTML & CSS
7.73
Keep request counts low and transfer sizes small — 17 requests • 158 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
17
162087
Script
4
130659
Font
1
18163
Document
3
5170
Image
5
3555
Other
3
3319
Stylesheet
1
1221
Media
0
0
Third-party
9
132483
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)
109893
0
19384
0
825
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
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
0.013262411347518
0.010141843971631
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.
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 chichananime.com on mobile screens.
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.

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 — 1.0 s
The time taken for the first image or text on the page to be rendered.

Audits

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

Other

Avoid multiple page redirects — Potential savings of 260 ms
Redirects can cause additional delays before the page can begin loading. Chichananime.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://chichananime.com/
190
http://chichananime.com/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTY1NTA0MTE3MiwiaWF0IjoxNjU1MDMzOTcyLCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIycnJ0cDg3cWVwNTgyZmwzdDgycTZtaTgiLCJuYmYiOjE2NTUwMzM5NzIsInRzIjoxNjU1MDMzOTcyMDM2ODE4fQ.C7ibOotHOWveME_TQ3tjotUrjkv695kuia1lFL-yS4s&sid=5370fc9a-ea44-11ec-bacb-77edc0c82caa
70
http://ww1.chichananime.com/
0

Other

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/quicksand/v29/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xDwxUD2GFw.woff
3.5109999589622
78

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of chichananime.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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

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"]`
Chichananime.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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

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

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
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 — 8 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://chichananime.com/
Allowed
http://chichananime.com/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTY1NTA0MTE3MiwiaWF0IjoxNjU1MDMzOTcyLCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIycnJ0cDg3cWVwNTgyZmwzdDgycTZtaTgiLCJuYmYiOjE2NTUwMzM5NzIsInRzIjoxNjU1MDMzOTcyMDM2ODE4fQ.C7ibOotHOWveME_TQ3tjotUrjkv695kuia1lFL-yS4s&sid=5370fc9a-ea44-11ec-bacb-77edc0c82caa
Allowed
http://ww1.chichananime.com/
Allowed
http://ww1.chichananime.com/js/parking.2.90.1.js
Allowed
http://ww1.chichananime.com/_fd
Allowed
http://ww1.chichananime.com/px.gif?ch=1&rn=1.6563030780863952
Allowed
http://ww1.chichananime.com/px.gif?ch=2&rn=1.6563030780863952
Allowed
http://ww1.chichananime.com/_tr
Allowed
100

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
Avg. (All Categories) 76
Performance 81
Accessibility 78
Best Practices 92
SEO 100
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
81

Performance

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

Metrics

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

Audits

Max Potential First Input Delay — 100 ms
Users could experience a delay when interacting with the page.
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://chichananime.com/
http/1.1
0
86.167000001296
832
472
200
text/html
Document
http://chichananime.com/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTY1NTA0MTIxOCwiaWF0IjoxNjU1MDM0MDE4LCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIycnJ0cGF1ajN0N2lqaGpqMWcwczg5cDUiLCJuYmYiOjE2NTUwMzQwMTgsInRzIjoxNjU1MDM0MDE4NjIxNDY2fQ.S98AW19B6cHG9BZAD1RTS06vII2yBnnKbBF1vliEvdY&sid=6f3616f4-ea44-11ec-814e-6a8d8943dad3
http/1.1
98.269999958575
626.38000003062
424
0
302
text/plain
http://ww1.chichananime.com/
http/1.1
626.69299996924
788.7069999706
1953
1755
200
text/html
Document
http://ww1.chichananime.com/js/parking.2.90.1.js
http/1.1
797.57499997504
917.79900004622
22652
69039
200
application/javascript
Script
http://ww1.chichananime.com/_fd
http/1.1
930.28800003231
1000.8829999715
2150
2781
200
text/html
Fetch
https://www.google.com/adsense/domains/caf.js
h2
932.55499994848
946.11300004181
53600
145082
200
text/javascript
Script
http://ww1.chichananime.com/px.gif?ch=1&rn=5.212331172603273
http/1.1
932.73600004613
962.96399994753
421
42
200
image/gif
Image
http://ww1.chichananime.com/px.gif?ch=2&rn=5.212331172603273
http/1.1
932.800999959
963.20999995805
421
42
200
image/gif
Image
https://partner.googleadservices.com/gampad/cookie.js?domain=ww1.chichananime.com&client=dp-bodis30_3ph&product=SAS&callback=__sasCookie
h2
1008.509999956
1020.4330000561
825
193
200
text/javascript
Script
https://www.google.com/afs/ads?psid=3762894382&pcsa=false&channel=pid-bodis-gcontrol138%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol311%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol446&client=dp-bodis30_3ph&r=m&hl=en&max_radlink_len=60&type=3&uiopt=true&swp=as-drid-2898040491288658&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300953%2C17300956&format=r3&nocache=4571655034019557&num=0&output=afd_ads&domain_name=ww1.chichananime.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1655034019558&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=77&frm=0&uio=-&cont=rs&jsid=caf&jsv=50759&rurl=http%3A%2F%2Fww1.chichananime.com%2F&referer=http%3A%2F%2Fchichananime.com%2F
h2
1019.8620000156
1104.7280000057
2369
5692
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=0
h2
1114.8939999985
1127.7899999404
53582
145057
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2312254d
h2
1159.0429999633
1163.2619999582
1188
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
h2
1159.529000055
1162.9299999913
1194
444
200
image/svg+xml
Image
https://fonts.googleapis.com/css?family=Quicksand
h2
1175.7119999966
1191.2770000054
1219
1089
200
text/css
Stylesheet
http://ww1.chichananime.com/_tr
http/1.1
1191.6669999482
1234.5289998921
564
2
200
text/html
Fetch
https://fonts.gstatic.com/s/quicksand/v29/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-wjw3UD0.woff2
h2
1199.5980000356
1204.3350000167
14760
13832
200
font/woff2
Font
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=nj87l1rq0udt&aqid=o9ClYuWEJavMj-8P79uQgAI&psid=3762894382&pbt=bs&adbx=0&adby=65.8125&adbh=496&adbw=360&adbah=160%2C160%2C160&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=5075900582475864444&csala=8%7C99%7C26%7C32&lle=0&llm=1000&ifv=1&usr=1
h2
2675.9610000299
2694.822999998
332
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=cqzqfus9mrrh&aqid=o9ClYuWEJavMj-8P79uQgAI&psid=3762894382&pbt=bv&adbx=0&adby=65.8125&adbh=496&adbw=360&adbah=160%2C160%2C160&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=5075900582475864444&csala=8%7C99%7C26%7C32&lle=0&llm=1000&ifv=1&usr=1
h2
3176.8630000297
3192.9440000094
332
0
204
text/html
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)
134.722
5.542
836.058
5.547
967.393
10.763
998.751
7.084
1047.125
19.64
1152.214
6.263
1180.428
25.525
1217.784
19.004
1236.908
5.079
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Chichananime.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Chichananime.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Chichananime.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Chichananime.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Chichananime.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Chichananime.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
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 160 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://ww1.chichananime.com/
163.009
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Chichananime.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 0 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)
http://ww1.chichananime.com/js/parking.2.90.1.js
144
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 155 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
53600
https://www.google.com/adsense/domains/caf.js?pac=0
53582
http://ww1.chichananime.com/js/parking.2.90.1.js
22652
https://fonts.gstatic.com/s/quicksand/v29/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-wjw3UD0.woff2
14760
https://www.google.com/afs/ads?psid=3762894382&pcsa=false&channel=pid-bodis-gcontrol138%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol311%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol446&client=dp-bodis30_3ph&r=m&hl=en&max_radlink_len=60&type=3&uiopt=true&swp=as-drid-2898040491288658&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300953%2C17300956&format=r3&nocache=4571655034019557&num=0&output=afd_ads&domain_name=ww1.chichananime.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1655034019558&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=77&frm=0&uio=-&cont=rs&jsid=caf&jsv=50759&rurl=http%3A%2F%2Fww1.chichananime.com%2F&referer=http%3A%2F%2Fchichananime.com%2F
2369
http://ww1.chichananime.com/_fd
2150
http://ww1.chichananime.com/
1953
https://fonts.googleapis.com/css?family=Quicksand
1219
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
1194
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2312254d
1188
Uses efficient cache policy on static assets — 2 resources found
Chichananime.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://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
82800000
1194
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2312254d
82800000
1188
Avoids an excessive DOM size — 17 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
17
Maximum DOM Depth
5
Maximum Child Elements
7
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Chichananime.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.google.com/adsense/domains/caf.js?pac=0
208.412
149.028
9.66
http://ww1.chichananime.com/js/parking.2.90.1.js
185.288
172.32
4.556
Unattributable
84.504
1.772
0
http://ww1.chichananime.com/
84.112
9.3
6.672
https://www.google.com/adsense/domains/caf.js
50.244
24.692
9.424
Minimizes main-thread work — 0.7 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
369.124
Other
173.64
Style & Layout
46.06
Script Parsing & Compilation
36.284
Parse HTML & CSS
22.532
Rendering
17.336
Keep request counts low and transfer sizes small — 18 requests • 155 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
18
158818
Script
4
130659
Font
1
14760
Document
3
5154
Image
6
3888
Other
3
3138
Stylesheet
1
1219
Media
0
0
Third-party
10
129401
Minimize third-party usage — Third-party code blocked the main thread for 10 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)
110215
13.476
15979
0
825
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
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
0.03349609375
0.00045451863606771
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.google.com/adsense/domains/caf.js?pac=0
3493
102
http://ww1.chichananime.com/js/parking.2.90.1.js
2932
76
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.
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 chichananime.com on mobile screens.
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.

Budgets

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

Metrics

Speed Index — 3.5 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 3.7 s
The timing of the largest text or image that is painted.

Audits

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

Other

Reduce unused JavaScript — Potential savings of 62 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.google.com/adsense/domains/caf.js
53600
32374
https://www.google.com/adsense/domains/caf.js?pac=0
53582
31398

Metrics

First Contentful Paint — 3.3 s
The time taken for the first image or text on the page to be rendered.

Other

Avoid multiple page redirects — Potential savings of 810 ms
Redirects can cause additional delays before the page can begin loading. Chichananime.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://chichananime.com/
630
http://chichananime.com/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTY1NTA0MTIxOCwiaWF0IjoxNjU1MDM0MDE4LCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIycnJ0cGF1ajN0N2lqaGpqMWcwczg5cDUiLCJuYmYiOjE2NTUwMzQwMTgsInRzIjoxNjU1MDM0MDE4NjIxNDY2fQ.S98AW19B6cHG9BZAD1RTS06vII2yBnnKbBF1vliEvdY&sid=6f3616f4-ea44-11ec-814e-6a8d8943dad3
180
http://ww1.chichananime.com/
0
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/quicksand/v29/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-wjw3UD0.woff2
4.7369999811053
First Contentful Paint (3G) — 6295 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
78

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of chichananime.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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

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"]`
Chichananime.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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

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

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
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 — 8 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://chichananime.com/
Allowed
http://chichananime.com/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTY1NTA0MTIxOCwiaWF0IjoxNjU1MDM0MDE4LCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIycnJ0cGF1ajN0N2lqaGpqMWcwczg5cDUiLCJuYmYiOjE2NTUwMzQwMTgsInRzIjoxNjU1MDM0MDE4NjIxNDY2fQ.S98AW19B6cHG9BZAD1RTS06vII2yBnnKbBF1vliEvdY&sid=6f3616f4-ea44-11ec-814e-6a8d8943dad3
Allowed
http://ww1.chichananime.com/
Allowed
http://ww1.chichananime.com/js/parking.2.90.1.js
Allowed
http://ww1.chichananime.com/_fd
Allowed
http://ww1.chichananime.com/px.gif?ch=1&rn=5.212331172603273
Allowed
http://ww1.chichananime.com/px.gif?ch=2&rn=5.212331172603273
Allowed
http://ww1.chichananime.com/_tr
Allowed
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for chichananime.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 chichananime.com on mobile screens.
Document uses legible font sizes — 87.2% 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
.privacy
8.53%
11px
.si133
4.27%
10px
87.20%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of chichananime.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 chichananime.com on mobile screens.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

Server Location

Server IP Address: 172.93.103.99
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Mark Lopez
Registration

Domain Registrant

Private Registration: Yes
Name: PERFECT PRIVACY, LLC
Organization:
Country: US
City: Jacksonville
State: FL
Post Code: 32256
Email: 1nam6vnu06hts82bljh49q1coa@domaindiscreet.com
Phone: +1.9027492701
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Name Connection Area LLC 162.159.133.53
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: chichananime.com
Issued By: R3
Valid From: 30th July, 2022
Valid To: 28th October, 2022
Subject: CN = chichananime.com
Hash: 1506fe72
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x0473C1FE17DDA919AADDA15BE9AFCC607A20
Serial Number (Hex): 0473C1FE17DDA919AADDA15BE9AFCC607A20
Valid From: 30th July, 2024
Valid To: 28th October, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
Timestamp : Jul 30 11:37:06.023 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:8C:F4:F3:75:34:57:11:6A:3C:A6:E5:
5C:71:4B:33:9C:F6:DE:62:58:0D:C8:2D:B0:37:BD:B0:
0C:EB:FE:E9:DF:02:21:00:E2:72:44:32:EC:59:F7:22:
65:93:9F:76:09:39:6C:EB:C8:93:98:EF:34:3D:CD:76:
9C:04:2D:B1:84:3D:A1:DD
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
Timestamp : Jul 30 11:37:06.482 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:E9:70:7A:F9:04:A6:25:7B:E5:68:04:
A6:9C:EC:E2:24:7E:7C:8F:9D:27:E8:D5:D5:70:83:17:
51:2D:DC:EA:8E:02:21:00:99:C0:5A:41:A8:B6:AC:BE:
E1:87:B0:BC:53:CA:82:04:37:E1:08:9A:11:1B:B6:AD:
34:F2:AC:48:D2:0C:49:B3
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:chichananime.com
DNS:*.chichananime.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
chichananime.com. 207.244.67.218 IN 600

NS Records

Host Nameserver Class TTL
chichananime.com. ns1.chookdns.com. IN 600
chichananime.com. ns2.chookdns.com. IN 600

SOA Records

Domain Name Primary NS Responsible Email TTL
chichananime.com. ns1.chookdns.com. admin.chichananime.com. 600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Expires: 7th March, 2020
Date: 7th March, 2020
Cache-Control: private, max-age=0
Server: GSE
Last-Modified: 7th March, 2020
ETag: "a0c66d83-cd5a-4508-89d3-ac1c67b40889"
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Length: 0

Whois Lookup

Created: 17th January, 2022
Changed: 16th May, 2022
Expires: 17th January, 2023
Registrar: SNAPNAMES 19, LLC
Status: ok
Nameservers: ns1.commonmx.com
ns2.commonmx.com
Owner Name: PERFECT PRIVACY, LLC
Owner Street: 5335 Gate Parkway
Owner Post Code: 32256
Owner City: Jacksonville
Owner State: FL
Owner Country: US
Owner Phone: +1.9027492701
Owner Email: 1nam6vnu06hts82bljh49q1coa@domaindiscreet.com
Admin Name: PERFECT PRIVACY, LLC
Admin Street: 5335 Gate Parkway
Admin Post Code: 32256
Admin City: Jacksonville
Admin State: FL
Admin Country: US
Admin Phone: +1.9027492701
Admin Email: 1nam6vnu06hts82bljh49q1coa@domaindiscreet.com
Tech Name: PERFECT PRIVACY, LLC
Tech Street: 5335 Gate Parkway
Tech Post Code: 32256
Tech City: Jacksonville
Tech State: FL
Tech Country: US
Tech Phone: +1.9027492701
Tech Email: 1nam6vnu06hts82bljh49q1coa@domaindiscreet.com
Full Whois: Domain Name: chichananime.com
Registry Domain ID: 2669029252_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.web.com
Registrar URL: http://www.networksolutions.com
Updated Date: 2022-05-16T11:51:05Z
Creation Date: 2022-01-17T19:26:59Z
Registrar Registration Expiration Date: 2023-01-17T19:26:59Z
Registrar: SNAPNAMES 19, LLC
Registrar IANA ID: 1048
Reseller:
Domain Status: ok http://icann.org/epp#OK
Registry Registrant ID:
Registrant Name: PERFECT PRIVACY, LLC
Registrant Organization:
Registrant Street: 5335 Gate Parkway
Registrant City: Jacksonville
Registrant State/Province: FL
Registrant Postal Code: 32256
Registrant Country: US
Registrant Phone: +1.9027492701
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: 1nam6vnu06hts82bljh49q1coa@domaindiscreet.com
Registry Admin ID:
Admin Name: PERFECT PRIVACY, LLC
Admin Organization:
Admin Street: 5335 Gate Parkway
Admin City: Jacksonville
Admin State/Province: FL
Admin Postal Code: 32256
Admin Country: US
Admin Phone: +1.9027492701
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: 1nam6vnu06hts82bljh49q1coa@domaindiscreet.com
Registry Tech ID:
Tech Name: PERFECT PRIVACY, LLC
Tech Organization:
Tech Street: 5335 Gate Parkway
Tech City: Jacksonville
Tech State/Province: FL
Tech Postal Code: 32256
Tech Country: US
Tech Phone: +1.9027492701
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: 1nam6vnu06hts82bljh49q1coa@domaindiscreet.com
Name Server: ns2.commonmx.com
Name Server: ns1.commonmx.com
DNSSEC: Unsigned
Registrar Abuse Contact Email: domain.operations@web.com
Registrar Abuse Contact Phone: +1.8773812449
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-09-25T14:34:29Z <<<

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

The data in SNAPNAMES 19, LLC's WHOIS database is provided to you by
SNAPNAMES 19, LLC for information purposes only, that is, to assist you in
obtaining information about or related to a domain name registration
record. SNAPNAMES 19, LLC makes this information available "as is," and
does not guarantee its accuracy. By submitting a WHOIS query, you
agree that you will use this data only for lawful purposes and that,
under no circumstances will you use this data to: (1) allow, enable,
or otherwise support the transmission of mass unsolicited, commercial
advertising or solicitations via direct mail, electronic mail, or by
telephone; or (2) enable high volume, automated, electronic processes
that apply to SNAPNAMES 19, LLC (or its systems). The compilation,
repackaging, dissemination or other use of this data is expressly
prohibited without the prior written consent of SNAPNAMES 19, LLC.
SNAPNAMES 19, LLC reserves the right to modify these terms at any time.
By submitting this query, you agree to abide by these terms.

Nameservers

Name IP Address
ns1.commonmx.com 104.243.45.206
ns2.commonmx.com 185.107.56.196
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
0/5
0/5
$360 USD 1/5