4anime.org

4anime.org is SSL secured

Free website and domain report on 4anime.org

Last Updated: 30th August, 2021 Update Now
Overview

Snoop Summary for 4anime.org

This is a free and comprehensive report about 4anime.org. 4anime.org is hosted in Netherlands on a server with an IP address of 82.192.82.227, where the local currency is EUR and Dutch is the local language. If 4anime.org was to be sold it would possibly be worth $332 USD (based on the daily revenue potential of the website over a 24 month period). 4anime.org receives an estimated 155 unique visitors every day - a decent amount of traffic! This report was last updated 30th August, 2021.

What is 4anime.org?

4anime.org is an anime/cartoons site where you can download, stream and watch anime and cartoon series online, with english subtitles. We advise against visiting websites like 4anime.org due to their potentially illegal/unsafe content.

About 4anime.org

Site Preview: 4anime.org 4anime.org
Title:
Description:
Keywords and Tags: anime, cartoons, download anime, download cartoons, dubbed anime, english subtitles, parked domain, stream anime, stream cartoons, watch anime, watch cartoons
Related Terms: 4anime, 4anime 2, 4anime com, 4anime to
Fav Icon:
Age: Over 3 years old
Domain Created: 4th April, 2021
Domain Updated: 6th April, 2021
Domain Expires: 4th April, 2022
Review

Snoop Score

1/5

Valuation

$332 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 7,224,458
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: 155
Monthly Visitors: 4,718
Yearly Visitors: 56,575
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $13 USD
Yearly Revenue: $161 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: 4anime.org 10
Domain Name: 4anime 6
Extension (TLD): org 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 78
Performance 92
Accessibility 86
Best Practices 93
SEO 100
Progressive Web App 18
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
92

Performance

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

Metrics

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

Other

Max Potential First Input Delay — 90 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://4anime.org/
http/1.1
0
185.03499997314
820
466
200
text/html
Document
http://4anime.org/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTYzMDMxMDY0MiwiaWF0IjoxNjMwMzAzNDQyLCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIycWcwMGx1ODB2Z3MyMTIxNnMwZGRrMjMiLCJuYmYiOjE2MzAzMDM0NDIsInRzIjoxNjMwMzAzNDQyMTI2MTU4fQ.ZzmaSla6QjaB5VmM8BGJQcSVNxiO9TAj8PzsbGpJAxg&sid=12ef9726-0958-11ec-b938-3492d6c14f7b
http/1.1
198.6480000196
714.60399997886
412
0
302
text/plain
http://ww1.4anime.org/
http/1.1
715.36000003107
785.18600005191
2005
1865
200
text/html
Document
http://ww1.4anime.org/js/parking.2.68.3.js
http/1.1
796.84800002724
884.35099995695
19675
59006
200
application/javascript
Script
http://ww1.4anime.org/_fd
http/1.1
895.33299999312
955.20399999805
1883
2261
200
text/html
Fetch
https://www.google.com/adsense/domains/caf.js
h2
896.09399996698
910.88199999649
57469
155506
200
text/javascript
Script
http://ww1.4anime.org/px.gif?ch=1&rn=2.636202981723301
http/1.1
897.15299999807
978.93099999055
421
42
200
image/gif
Image
http://ww1.4anime.org/px.gif?ch=2&rn=2.636202981723301
http/1.1
897.30399998371
1017.5700000254
421
42
200
image/gif
Image
https://www.google.com/afs/ads/i/iframe.html
h2
1041.7049999814
1046.9260000391
1625
1243
200
text/html
Document
https://www.google.com/afs/ads/i/iframe.html
h2
1046.3560000062
1053.3640000504
1625
1243
200
text/html
Document
https://www.google.com/afs/ads/i/iframe.html
h2
1055.217999965
1064.587000059
1625
1243
200
text/html
Document
https://www.google.com/dp/ads?channel=pid-bodis-gcontrol230%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol306&hl=en&pcsa=false&client=dp-bodis30_3ph&r=m&psid=8799259212&type=3&max_radlink_len=60&swp=as-drid-2898040491288658&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300494%2C17300496%2C17300756%2C17300758%2C17300769%2C17300771%2C17300794%2C17300797%2C17300798&format=r3%7Cn3&ad=n3&num=0&output=afd_ads&domain_name=ww1.4anime.org&v=3&adext=as1%2Csr1&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1630303442987&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=77&frm=0&uio=sl1sr1--&cont=rs%7Cads&csize=w1334h0%7Cw1334h0%7Cw1334h0%7Cw1334h0&inames=master-1%7Cslave-1-1%7Cslave-1-a-1%7Cslave-1-b-1&jsv=42366&rurl=http%3A%2F%2Fww1.4anime.org%2F&referer=http%3A%2F%2F4anime.org%2F
h2
1061.8999999715
1203.6640000297
8851
13410
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
h2
1221.1120000575
1235.5309999548
57455
155497
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Raleway&display=swap
h2
1267.9860000499
1285.6799999718
1290
1783
200
text/css
Stylesheet
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
h2
1285.0229999749
1288.2329999702
976
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
h2
1285.2780000539
1293.4870000463
982
444
200
image/svg+xml
Image
https://fonts.gstatic.com/s/raleway/v22/1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrcVIT9d0c8.woff
h2
1311.4350000396
1314.5889999578
21085
20328
200
font/woff
Font
https://fonts.googleapis.com/css2?family=Raleway&display=swap
h2
1336.9630000088
1351.032000035
1290
1783
200
text/css
Stylesheet
http://ww1.4anime.org/_tr
http/1.1
1361.5230000578
1408.1030000234
564
2
200
text/html
Fetch
https://www.google.com/js/bg/UDeKqTBFYaEY2ioWtDs_l49rHnl3Z0jd0o7HlKSj4tA.js
h2
1371.083999984
1375.5990000209
14179
35917
200
text/javascript
Script
https://fonts.gstatic.com/s/raleway/v22/1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrcVIT9d0c8.woff
h2
1544.3039999809
1548.2779999729
21050
20328
200
font/woff
Font
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=1tcq16jgreyk&aqid=03QsYcrxBb-8tOUPrMaxQA&psid=8799259212&pbt=bs&adbx=475&adby=64.8125&adbh=451&adbw=400&adbah=145%2C145%2C145&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=4236648535494711615&csadii=30&csadr=282&lle=0&llm=1000&ifv=1&usr=1
h2
2842.8870000644
2860.6930000242
359
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=zi1h9mzc7hhg&aqid=03QsYcrxBb-8tOUPrMaxQA&psid=8799259212&pbt=bv&adbx=475&adby=64.8125&adbh=451&adbw=400&adbah=145%2C145%2C145&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=4236648535494711615&csadii=30&csadr=282&lle=0&llm=1000&ifv=1&usr=1
h2
3339.7000000114
3362.1190000558
359
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)
194.35
7.927
795.482
6.676
895.18
9.541
926.408
7.725
1025.54
40.917
1068.948
7.255
1076.358
8.025
1084.74
8.065
1214.062
10.388
1255.5
38.897
1296.137
5.764
1323.766
16.835
1340.627
27.496
1368.694
8.072
1384.166
161.093
2841.898
7.464
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.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. 4anime.org 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. 4anime.org should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. 4anime.org should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 4anime.org should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 4anime.org should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 4anime.org 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 33 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
57469
34285
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 70 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.4anime.org/
70.823
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. 4anime.org 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.4anime.org/js/parking.2.68.3.js
112
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 211 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
57469
https://www.google.com/adsense/domains/caf.js
57455
https://fonts.gstatic.com/s/raleway/v22/1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrcVIT9d0c8.woff
21085
https://fonts.gstatic.com/s/raleway/v22/1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrcVIT9d0c8.woff
21050
http://ww1.4anime.org/js/parking.2.68.3.js
19675
https://www.google.com/js/bg/UDeKqTBFYaEY2ioWtDs_l49rHnl3Z0jd0o7HlKSj4tA.js
14179
https://www.google.com/dp/ads?channel=pid-bodis-gcontrol230%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol306&hl=en&pcsa=false&client=dp-bodis30_3ph&r=m&psid=8799259212&type=3&max_radlink_len=60&swp=as-drid-2898040491288658&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300494%2C17300496%2C17300756%2C17300758%2C17300769%2C17300771%2C17300794%2C17300797%2C17300798&format=r3%7Cn3&ad=n3&num=0&output=afd_ads&domain_name=ww1.4anime.org&v=3&adext=as1%2Csr1&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1630303442987&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=77&frm=0&uio=sl1sr1--&cont=rs%7Cads&csize=w1334h0%7Cw1334h0%7Cw1334h0%7Cw1334h0&inames=master-1%7Cslave-1-1%7Cslave-1-a-1%7Cslave-1-b-1&jsv=42366&rurl=http%3A%2F%2Fww1.4anime.org%2F&referer=http%3A%2F%2F4anime.org%2F
8851
http://ww1.4anime.org/
2005
http://ww1.4anime.org/_fd
1883
https://www.google.com/afs/ads/i/iframe.html
1625
Uses efficient cache policy on static assets — 2 resources found
4anime.org 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
982
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
82800000
976
Avoids an excessive DOM size — 15 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
15
Maximum DOM Depth
5
Maximum Child Elements
5
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. 4anime.org should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.google.com/adsense/domains/caf.js
266.686
222.233
10.582
http://ww1.4anime.org/js/parking.2.68.3.js
71.527
63.514
1.148
Minimizes main-thread work — 0.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
312.068
Other
86.618
Style & Layout
28.527
Script Parsing & Compilation
21.453
Rendering
9.068
Parse HTML & CSS
8.691
Garbage Collection
4.705
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 — 23 requests • 211 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
23
216421
Script
4
148778
Font
2
42135
Document
6
16551
Image
6
3518
Other
3
2859
Stylesheet
2
2580
Media
0
0
Third-party
15
190220
Minimize third-party usage — Third-party code blocked the main thread for 90 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)
143547
89.342
44715
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
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0091054472025217
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.google.com/js/bg/UDeKqTBFYaEY2ioWtDs_l49rHnl3Z0jd0o7HlKSj4tA.js
1019
161
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 — 1.3 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.4 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.3 s
The timing of the largest text or image that is painted.

Other

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

Opportunities

Avoid multiple page redirects — Potential savings of 260 ms
Redirects can cause additional delays before the page can begin loading. 4anime.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://4anime.org/
190
http://4anime.org/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTYzMDMxMDY0MiwiaWF0IjoxNjMwMzAzNDQyLCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIycWcwMGx1ODB2Z3MyMTIxNnMwZGRrMjMiLCJuYmYiOjE2MzAzMDM0NDIsInRzIjoxNjMwMzAzNDQyMTI2MTU4fQ.ZzmaSla6QjaB5VmM8BGJQcSVNxiO9TAj8PzsbGpJAxg&sid=12ef9726-0958-11ec-b938-3492d6c14f7b
70
http://ww1.4anime.org/
0

Diagnostics

Avoid `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.
Source
86

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of 4anime.org. 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 `[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 `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

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

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

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids 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

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
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://4anime.org/
Allowed
http://4anime.org/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTYzMDMxMDY0MiwiaWF0IjoxNjMwMzAzNDQyLCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIycWcwMGx1ODB2Z3MyMTIxNnMwZGRrMjMiLCJuYmYiOjE2MzAzMDM0NDIsInRzIjoxNjMwMzAzNDQyMTI2MTU4fQ.ZzmaSla6QjaB5VmM8BGJQcSVNxiO9TAj8PzsbGpJAxg&sid=12ef9726-0958-11ec-b938-3492d6c14f7b
Allowed
http://ww1.4anime.org/
Allowed
http://ww1.4anime.org/js/parking.2.68.3.js
Allowed
http://ww1.4anime.org/_fd
Allowed
http://ww1.4anime.org/px.gif?ch=1&rn=2.636202981723301
Allowed
http://ww1.4anime.org/px.gif?ch=2&rn=2.636202981723301
Allowed
http://ww1.4anime.org/_tr
Allowed
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for 4anime.org. 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 4anime.org 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.
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 4anime.org. 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 4anime.org 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) 72
Performance 67
Accessibility 86
Best Practices 93
SEO 91
Progressive Web App 25
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
67

Performance

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

Metrics

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.028
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 110 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://4anime.org/
http/1.1
0
106.7439999897
820
466
200
text/html
Document
http://4anime.org/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTYzMDMxMDY4NiwiaWF0IjoxNjMwMzAzNDg2LCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIycWcwMG9nY2ZvZmxkZ3ZvYzRmZWlhODEiLCJuYmYiOjE2MzAzMDM0ODYsInRzIjoxNjMwMzAzNDg2MjI0NDY4fQ.ZBFKY3pHwwh2GQLQ4u_w3fo1StMJtKwdVtx64NQStrw&sid=2d39a478-0958-11ec-bcda-819e93cff14a
http/1.1
122.46900005266
2329.2160000419
414
0
302
text/plain
http://ww1.4anime.org/
http/1.1
2329.7729999758
2374.3650000542
2012
1873
200
text/html
Document
http://ww1.4anime.org/js/parking.2.68.3.js
http/1.1
2386.7409999948
2542.9520000471
19675
59006
200
application/javascript
Script
http://ww1.4anime.org/_fd
http/1.1
2554.5670000138
2658.2459999481
1885
2261
200
text/html
Fetch
https://www.google.com/adsense/domains/caf.js
h2
2555.3379999474
2569.0470000263
57454
155497
200
text/javascript
Script
http://ww1.4anime.org/px.gif?ch=1&rn=7.4455344624816515
http/1.1
2556.4180000219
2637.4200000428
421
42
200
image/gif
Image
http://ww1.4anime.org/px.gif?ch=2&rn=7.4455344624816515
http/1.1
2556.6370000597
2616.1670000292
421
42
200
image/gif
Image
https://www.google.com/afs/ads/i/iframe.html
h2
2680.5150000146
2685.6070000213
1626
1243
200
text/html
Document
https://www.google.com/afs/ads/i/iframe.html
h2
2684.6920000389
2690.9590000287
1625
1243
200
text/html
Document
https://www.google.com/afs/ads/i/iframe.html
h2
2692.6130000502
2700.3529999638
1628
1243
200
text/html
Document
https://www.google.com/dp/ads?channel=pid-bodis-gcontrol230%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol306&hl=en&pcsa=false&client=dp-bodis30_3ph&r=m&psid=8799259212&type=3&max_radlink_len=60&swp=as-drid-2898040491288658&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300494%2C17300496%2C17300756%2C17300758%2C17300769%2C17300771%2C17300794%2C17300797%2C17300798&format=r3%7Cn3&ad=n3&num=0&output=afd_ads&domain_name=ww1.4anime.org&v=3&adext=as1%2Csr1&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1630303488799&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=77&frm=0&uio=sl1sr1--&cont=rs%7Cads&csize=w344h0%7Cw344h0%7Cw344h0%7Cw344h0&inames=master-1%7Cslave-1-1%7Cslave-1-a-1%7Cslave-1-b-1&jsv=42366&rurl=http%3A%2F%2Fww1.4anime.org%2F&referer=http%3A%2F%2F4anime.org%2F
h2
2697.5940000266
2837.5940000406
8930
13433
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
h2
2848.52400003
2861.4740000339
57505
155550
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Raleway&display=swap
h2
2887.33399997
2898.0310000479
1287
1778
200
text/css
Stylesheet
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
h2
2903.7259999895
2909.6869999776
987
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
h2
2903.8739999523
2907.2839999571
982
444
200
image/svg+xml
Image
https://fonts.gstatic.com/s/raleway/v22/1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrEVJz9d.woff2
h2
2921.8549999641
2925.2349999733
17006
16248
200
font/woff2
Font
https://fonts.googleapis.com/css2?family=Raleway&display=swap
h2
2928.4029999981
2934.5550000435
1287
1778
200
text/css
Stylesheet
http://ww1.4anime.org/_tr
http/1.1
2949.5769999921
3041.0289999563
564
2
200
text/html
Fetch
https://www.google.com/js/bg/D3lOyaz33AOyGTIEqdOSEmJb5cnEgELXkEp-WZBOrR0.js
h2
2972.1770000178
2977.0299999509
14242
35880
200
text/javascript
Script
https://fonts.gstatic.com/s/raleway/v22/1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrEVJz9d.woff2
h2
2975.0779999886
2977.9760000529
17006
16248
200
font/woff2
Font
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=ier73za6qmgs&aqid=AHUsYfmON66_tOUPrKK_qAg&psid=8799259212&pbt=bs&adbx=0&adby=64.8125&adbh=451&adbw=360&adbah=145%2C145%2C145&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=4236648535494711615&csadii=26&csadr=237&lle=0&llm=1000&ifv=1&usr=1
h2
4430.4750000592
4454.4699999969
359
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=6bxyd09p2er2&aqid=AHUsYfmON66_tOUPrKK_qAg&psid=8799259212&pbt=bv&adbx=0&adby=64.8125&adbh=451&adbw=360&adbah=145%2C145%2C145&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=4236648535494711615&csadii=26&csadr=237&lle=0&llm=1000&ifv=1&usr=1
h2
4931.0109999496
4951.7149999738
359
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)
117.214
8.584
2385.227
6.745
2554.551
10.032
2586.506
8.637
2667.249
37.696
2706.31
6.842
2713.271
7.311
2720.912
7.228
2847.78
5.535
2879.263
33.571
2933.035
23.74
2956.859
12.296
2969.243
7.816
2979.172
7.877
2989.65
104.135
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.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. 4anime.org 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. 4anime.org should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. 4anime.org should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 4anime.org should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 4anime.org should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 4anime.org 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 50 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.4anime.org/
45.589
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. 4anime.org 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.4anime.org/js/parking.2.68.3.js
112
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 203 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
57505
https://www.google.com/adsense/domains/caf.js
57454
http://ww1.4anime.org/js/parking.2.68.3.js
19675
https://fonts.gstatic.com/s/raleway/v22/1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrEVJz9d.woff2
17006
https://fonts.gstatic.com/s/raleway/v22/1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrEVJz9d.woff2
17006
https://www.google.com/js/bg/D3lOyaz33AOyGTIEqdOSEmJb5cnEgELXkEp-WZBOrR0.js
14242
https://www.google.com/dp/ads?channel=pid-bodis-gcontrol230%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol306&hl=en&pcsa=false&client=dp-bodis30_3ph&r=m&psid=8799259212&type=3&max_radlink_len=60&swp=as-drid-2898040491288658&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300494%2C17300496%2C17300756%2C17300758%2C17300769%2C17300771%2C17300794%2C17300797%2C17300798&format=r3%7Cn3&ad=n3&num=0&output=afd_ads&domain_name=ww1.4anime.org&v=3&adext=as1%2Csr1&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1630303488799&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=77&frm=0&uio=sl1sr1--&cont=rs%7Cads&csize=w344h0%7Cw344h0%7Cw344h0%7Cw344h0&inames=master-1%7Cslave-1-1%7Cslave-1-a-1%7Cslave-1-b-1&jsv=42366&rurl=http%3A%2F%2Fww1.4anime.org%2F&referer=http%3A%2F%2F4anime.org%2F
8930
http://ww1.4anime.org/
2012
http://ww1.4anime.org/_fd
1885
https://www.google.com/afs/ads/i/iframe.html
1628
Uses efficient cache policy on static assets — 2 resources found
4anime.org 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/search.svg?c=%231967d2
82800000
987
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
82800000
982
Avoids an excessive DOM size — 15 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
15
Maximum DOM Depth
5
Maximum Child Elements
5
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. 4anime.org should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 1.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.google.com/adsense/domains/caf.js
822.944
647.536
37.124
http://ww1.4anime.org/js/parking.2.68.3.js
263.6
250.92
4.328
Unattributable
136.628
5.344
0
https://www.google.com/afs/ads/i/iframe.html
103.616
29.892
11.476
http://ww1.4anime.org/
101.252
11.504
9.088
Minimizes main-thread work — 1.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
981.244
Other
329.932
Style & Layout
90.776
Script Parsing & Compilation
75
Parse HTML & CSS
30.124
Rendering
29.652
Garbage Collection
12.616
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 — 23 requests • 204 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
23
208495
Script
4
148876
Font
2
34012
Document
6
16641
Image
6
3529
Other
3
2863
Stylesheet
2
2574
Media
0
0
Third-party
15
182283
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
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.028209991455078
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 3 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/js/bg/D3lOyaz33AOyGTIEqdOSEmJb5cnEgELXkEp-WZBOrR0.js
3614
208
https://www.google.com/adsense/domains/caf.js
3340
134
http://ww1.4anime.org/js/parking.2.68.3.js
1810
75
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

Time to Interactive — 4.5 s
The time taken for the page to become fully interactive.

Opportunities

Reduce unused JavaScript — Potential savings of 33 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
57454
34275

Metrics

First Contentful Paint — 4.3 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 7.1 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 4.6 s
The timing of the largest text or image that is painted.

Other

First Meaningful Paint — 4.3 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 8770 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Avoid multiple page redirects — Potential savings of 810 ms
Redirects can cause additional delays before the page can begin loading. 4anime.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://4anime.org/
630
http://4anime.org/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTYzMDMxMDY4NiwiaWF0IjoxNjMwMzAzNDg2LCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIycWcwMG9nY2ZvZmxkZ3ZvYzRmZWlhODEiLCJuYmYiOjE2MzAzMDM0ODYsInRzIjoxNjMwMzAzNDg2MjI0NDY4fQ.ZBFKY3pHwwh2GQLQ4u_w3fo1StMJtKwdVtx64NQStrw&sid=2d39a478-0958-11ec-bcda-819e93cff14a
180
http://ww1.4anime.org/
0

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 350 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)
143728
349.356
36586
0
Avoid `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.
Source
86

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of 4anime.org. 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 `[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 `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

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

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

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids 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

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
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://4anime.org/
Allowed
http://4anime.org/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTYzMDMxMDY4NiwiaWF0IjoxNjMwMzAzNDg2LCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIycWcwMG9nY2ZvZmxkZ3ZvYzRmZWlhODEiLCJuYmYiOjE2MzAzMDM0ODYsInRzIjoxNjMwMzAzNDg2MjI0NDY4fQ.ZBFKY3pHwwh2GQLQ4u_w3fo1StMJtKwdVtx64NQStrw&sid=2d39a478-0958-11ec-bcda-819e93cff14a
Allowed
http://ww1.4anime.org/
Allowed
http://ww1.4anime.org/js/parking.2.68.3.js
Allowed
http://ww1.4anime.org/_fd
Allowed
http://ww1.4anime.org/px.gif?ch=1&rn=7.4455344624816515
Allowed
http://ww1.4anime.org/px.gif?ch=2&rn=7.4455344624816515
Allowed
http://ww1.4anime.org/_tr
Allowed
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for 4anime.org. 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 4anime.org 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.
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.

Mobile Friendly

Document doesn't use legible font sizes — 39.24% 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
40.51%
11px
.si133
20.25%
10px
39.24%
≥ 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.
25

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 4anime.org. 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 4anime.org 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.
Hosting

Server Location

Server IP Address: 82.192.82.227
Continent: Europe
Country: Netherlands
Netherlands Flag
Region:
City:
Longitude: 4.8995
Latitude: 52.3824
Currencies: EUR
Languages: Dutch

Web Hosting Provider

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

Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: 4anime.org
Issued By: R3
Valid From: 16th August, 2021
Valid To: 14th November, 2021
Subject: CN = 4anime.org
Hash: 6c258419
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03E2AC65EB7A44C3DBF95964EEEEAA6F5BA4
Serial Number (Hex): 03E2AC65EB7A44C3DBF95964EEEEAA6F5BA4
Valid From: 16th August, 2024
Valid To: 14th November, 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 : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
Timestamp : Aug 16 10:47:57.803 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:D7:71:08:C0:46:60:75:E8:5C:D2:A4:
6E:68:E0:6C:A6:3F:05:CF:BF:87:E9:9F:15:7F:2C:9F:
43:44:B0:05:55:02:20:3E:0F:D8:DA:84:6C:86:15:42:
A1:E8:20:D3:DA:D2:87:70:D7:A5:54:54:80:EA:FE:AF:
63:1B:C8:6C:16:C6:A0
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Aug 16 10:47:58.287 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:0E:68:45:59:C6:F4:F1:FB:A3:98:28:F1:
5D:A0:13:59:20:C9:26:C3:D9:3C:B2:18:88:89:63:3D:
A5:F8:38:89:02:21:00:96:72:55:9F:05:C6:2C:D5:81:
2B:64:B7:38:11:7B:C4:23:3C:89:81:E7:B3:87:B7:77:
91:FE:C3:62:31:68:BF
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:4anime.org
DNS:*.4anime.org
Technical

DNS Lookup

A Records

Host IP Address Class TTL
4anime.org. 162.210.199.87 IN 600

NS Records

Host Nameserver Class TTL
4anime.org. ns1.koaladns.com. IN 600
4anime.org. ns2.koaladns.com. IN 600

SOA Records

Domain Name Primary NS Responsible Email TTL
4anime.org. ns1.koaladns.com. admin.4anime.org. 600

HTTP Response Headers

Whois Lookup

Created: 4th April, 2021
Changed: 6th April, 2021
Expires: 4th April, 2022
Registrar: DropCatch.com 978 LLC
Status: ok
Nameservers: ns1.brainydns.com
ns2.brainydns.com
Owner Organization: www.DropCatch.com
Owner State: CO
Owner Country: US
Full Whois: Domain Name: 4ANIME.ORG
Registry Domain ID: D402200000016446091-LROR
Registrar WHOIS Server: whois.namebright.com
Registrar URL: http://www.NameBright.com
Updated Date: 2021-06-04T03:50:51Z
Creation Date: 2021-04-04T14:30:08Z
Registry Expiry Date: 2022-04-04T14:30:08Z
Registrar Registration Expiration Date:
Registrar: DropCatch.com 978 LLC
Registrar IANA ID: 2737
Registrar Abuse Contact Email: abuse@NameBright.com
Registrar Abuse Contact Phone: +1.7204960020
Reseller:
Domain Status: ok https://icann.org/epp#ok
Registrant Organization: www.DropCatch.com
Registrant State/Province: CO
Registrant Country: US
Name Server: NS1.BRAINYDNS.COM
Name Server: NS2.BRAINYDNS.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/)
>>> Last update of WHOIS database: 2021-08-30T06:02:48Z <<<

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

Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.

Nameservers

Name IP Address
ns1.brainydns.com 207.244.71.177
ns2.brainydns.com 185.107.56.191
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

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

Sites hosted on the same IP address

Domain Valuation Snoop Score
$2,428 USD 2/5
$788 USD 1/5