Your Website Score is
SEO Rank : 19 Website URL: nanime.us Last Updated: 1 month
Success
70% of passed verification steps
Warning
7% of total warning
Errors
23% of total errors, require fast action
Share
Estimation Traffic and Earnings
1,376
Unique Visits
Daily
2,545
Pages Views
Daily
$6
Income
Daily
38,528
Unique Visits
Monthly
72,533
Pages Views
Monthly
$150
Income
Monthly
445,824
Unique Visits
Yearly
855,120
Pages Views
Yearly
$1,584
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 0%
Domain Authority
Domain Authority 0%
Moz Rank
0.0/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
40 Characters
NANIME - NONTON STREAMING ANIME SUB INDO
Meta Description
82 Characters
Nonton anime sub indo, streaming anime subtitle indonesia, download anime sub indo
Effective URL
17 Characters
https://nanime.us
Excerpt
Page content
Nanime - Nonton Streaming Anime Sub Indo
Nanime
GenreAnime OngoingDonghuaLive ActionMovieList Semua AnimeJadwal RilisBatch
Nanime - Nonton Streaming Anime Sub IndoNonton Anime Sub Indo, Download anime sub indo Home
Google Preview
Your look like this in google search result
NANIME - NONTON STREAMING ANIME SUB INDO
https://nanime.us
Nonton anime sub indo, streaming anime subtitle indonesia, download anime sub indo
Robots.txt
File Detected
Sitemap.xml
File Detected
Page Size
Code & Text Ratio
Document Size: ~44.19 KB
Code Size: ~39.45 KB
Text Size: ~4.75 KB Ratio: 10.74%
Social Data
Desktop
First CPU Idle
2.1 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Eliminate render-blocking resources
Potential savings of 630 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Initial server response time was short
Root document took 460 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint
1.0 s
First Contentful Paint marks the time at which the first text or image is painted
Avoids large JavaScript libraries with smaller alternatives
0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Estimated Input Latency
20 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
JavaScript execution time
0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoids enormous network payloads
Total size was 822 KiB
Large network payloads cost users real money and are highly correlated with long load times
Includes front-end JavaScript libraries with known security vulnerabilities
2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
User Timing marks and measures
15 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 11.7 s
A fast page load over a cellular network ensures a good mobile user experience
Total Blocking Time
110 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid chaining critical requests
8 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Remove unused JavaScript
Potential savings of 124 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Minimizes main-thread work
1.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid long main-thread tasks
5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve static assets with an efficient cache policy
55 resources found
A long cache lifetime can speed up repeat visits to your page
Minimize third-party usage
Third-party code blocked the main thread for 80 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Remove unused CSS
Potential savings of 32 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Speed Index
2.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Time to Interactive
2.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Cumulative Layout Shift
0.044
Cumulative Layout Shift measures the movement of visible elements within the viewport
Max Potential First Input Delay
100 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid serving legacy JavaScript to modern browsers
Potential savings of 9 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Avoids an excessive DOM size
447 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Enable text compression
Potential savings of 4 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Keep request counts low and transfer sizes small
146 requests • 822 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Largest Contentful Paint
1.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Meaningful Paint
1.0 s
First Meaningful Paint measures when the primary content of a page is visible
Mobile
Tap targets are not sized appropriately
28% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Remove unused CSS
Potential savings of 33 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Avoid long main-thread tasks
8 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Time to Interactive
6.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoids enormous network payloads
Total size was 480 KiB
Large network payloads cost users real money and are highly correlated with long load times
Initial server response time was short
Root document took 180 ms
Keep the server response time for the main document short because all other requests depend on it
Eliminate render-blocking resources
Potential savings of 1,440 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Speed Index
4.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Document doesn't use legible font sizes
34.24% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Largest Contentful Paint
4.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
First Meaningful Paint
3.2 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid chaining critical requests
9 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Includes front-end JavaScript libraries with known security vulnerabilities
2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
First CPU Idle
4.7 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
First Contentful Paint (3G)
6135 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Max Potential First Input Delay
190 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Estimated Input Latency
20 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Minimizes main-thread work
1.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoids an excessive DOM size
437 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Minimize third-party usage
Third-party code blocked the main thread for 30 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Keep request counts low and transfer sizes small
39 requests • 480 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy
30 resources found
A long cache lifetime can speed up repeat visits to your page
Total Blocking Time
130 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
JavaScript execution time
0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint
3.2 s
First Contentful Paint marks the time at which the first text or image is painted
Remove unused JavaScript
Potential savings of 20 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Speed And Optimization Tips
Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links
View links
| First 20 Links | Relationship | HTTP Status |
| Nanime | Internal Link | 200 |
| Anime | Internal Link | 200 |
| Ongoing | Internal Link | 200 |
| Donghua | Internal Link | 200 |
| Live Action | Internal Link | 200 |
| Movie | Internal Link | 200 |
| List Semua Anime | Internal Link | 200 |
| Jadwal Rilis | Internal Link | 200 |
| Game | Internal Link | 200 |
| Contact | Internal Link | 200 |
| Batch | Internal Link | 200 |
| Nonton anime Fugou Keiji: Balance:Unlimited Sub Indo | Internal Link | 200 |
| Nonton anime Yahari Ore no Seishun Love Comedy wa Machigatteiru. Kan Sub Indo | Internal Link | 200 |
| Nonton anime Gibiate Sub Indo | Internal Link | 200 |
| Nonton anime Deca-Dence Sub Indo | Internal Link | 200 |
| Nonton anime Re:Zero kara Hajimeru Isekai Seikatsu 2nd Season Sub Indo | Internal Link | 200 |
| Nonton anime Ahiru no Sora Sub Indo | Internal Link | 200 |
| Nonton anime Houkago Teibou Nisshi Sub Indo | Internal Link | 200 |
| Nonton anime Shadowverse (TV) Sub Indo | Internal Link | 200 |
| Nonton anime Black Clover Sub Indo | Internal Link | 200 |
Alexa Rank
1,150
Local Rank: ID / Users: 90.8% / PageViews: 94.4%93,743
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| nanime.co | Already Registered |
| nanime.us | Already Registered |
| nanime.com | Available Buy Now! |
| nanime.org | Already Registered |
| nanime.net | Already Registered |
| nnime.us | Available Buy Now! |
| hanime.us | Already Registered |
| uanime.us | Available Buy Now! |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200
date: Wed, 23 Dec 2020 07:23:55 GMT
content-type: text/html; charset=UTF-8
set-cookie: __cfduid=d99eed5c7cbb348b5a8a2204aed5398801608708234; expires=Fri, 22-Jan-21 07:23:54 GMT; path=/; domain=.nanime.us; HttpOnly; SameSite=Lax; Secure
cf-cache-status: DYNAMIC
cf-request-id: 073014b6d700003636f293a000000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=w0wH8ZHeI9hBcuLJsId%2FDmqZf5mHrXJL4ww%2F1sz6HO8uBcKCRuelE1BNtSeJhH5e7gxCC%2BVibLzOSX0jVTBHTWVh6fqfq5dPPuY%3D"}],"group":"cf-nel","max_age":604800}
nel: {"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 606057048c523636-LAX
content-encoding: gzip
Click to Add/Show Comments