Your Website Score is
SEO Rank : 44 Website URL: ww1.gogoanime.io Last Updated: 3 months
Success
70% of passed verification steps
Warning
7% of total warning
Errors
23% of total errors, require fast action
Share
Estimation Traffic and Earnings
3,620
Unique Visits
Daily
6,697
Pages Views
Daily
$12
Income
Daily
101,360
Unique Visits
Monthly
190,865
Pages Views
Monthly
$300
Income
Monthly
1,172,880
Unique Visits
Yearly
2,250,192
Pages Views
Yearly
$3,168
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 42%
Domain Authority
Domain Authority 50%
Moz Rank
4.2/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
55 Characters
GOGOANIME | WATCH ANIME ONLINE, ENGLISH ANIME ONLINE HD
Meta Description
96 Characters
Watch anime online in English. You can watch free series and movies online and English subtitle.
Effective URL
20 Characters
https://gogoanime.so
Excerpt
Page content
Gogoanime | Watch anime online, English anime online HD
Login |
Sign up
...
Meta Keywords
6 Detected
Google Preview
Your look like this in google search result
GOGOANIME | WATCH ANIME ONLINE, ENGLISH ANIME ONLINE HD
https://gogoanime.so
Watch anime online in English. You can watch free series and movies online and English subtitle.
Robots.txt
File Detected
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~80.96 KB
Code Size: ~44.22 KB
Text Size: ~36.74 KB Ratio: 45.38%
Social Data
Delicious
Total: 0
Facebook
Total: 92
Google
Total: 0
Linkedin
Total: 0
Pinterest
Total: 0
Stumbleupon
Total: 0
Tumblr
Total: 0
Vk
Total: 0
Technologies
PWA - Manifest
Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest
Desktop
JavaScript execution time
0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 7 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 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
First Meaningful Paint
1.2 s
First Meaningful Paint measures when the primary content of a page is visible
Properly size images
Potential savings of 2,110 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
First CPU Idle
1.2 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/).
Avoid long main-thread tasks
2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Keep request counts low and transfer sizes small
62 requests • 6,541 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Minimizes main-thread work
0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Eliminate render-blocking resources
Potential savings of 460 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Remove unused JavaScript
Potential savings of 120 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Includes front-end JavaScript libraries with known security vulnerabilities
6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Serve images in next-gen formats
Potential savings of 4,177 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Preload key requests
Potential savings of 190 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Largest Contentful Paint element
1 element found
This is the largest contentful element painted 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
Total Blocking Time
40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser
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
Estimated Input Latency
10 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
Time to Interactive
1.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Speed Index
1.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Cumulative Layout Shift
0.17
Cumulative Layout Shift measures the movement of visible elements within the viewport
Initial server response time was short
Root document took 110 ms
Keep the server response time for the main document short because all other requests depend on it
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 16.0 s
A fast page load over a cellular network ensures a good mobile user experience
Largest Contentful Paint
3.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve static assets with an efficient cache policy
18 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid an excessive DOM size
1,158 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)
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
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
Avoid enormous network payloads
Total size was 6,541 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Contentful Paint
1.0 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests
7 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
Minify JavaScript
Potential savings of 35 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Mobile
Total Blocking Time
400 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve images in next-gen formats
Potential savings of 4,177 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid an excessive DOM size
1,158 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)
Largest Contentful Paint
15.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Preload key requests
Potential savings of 780 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
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
Page load is not fast enough on mobile networks
Interactive at 15.5 s
A fast page load over a cellular network ensures a good mobile user experience
Serve static assets with an efficient cache policy
16 resources found
A long cache lifetime can speed up repeat visits to your page
First Meaningful Paint
5.3 s
First Meaningful Paint measures when the primary content of a page is visible
Includes front-end JavaScript libraries with known security vulnerabilities
6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Document uses legible font sizes
97.36% 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
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
Minify JavaScript
Potential savings of 35 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
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
Cumulative Layout Shift
0.002
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minimize main-thread work
3.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Time to Interactive
15.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Reduce JavaScript execution time
2.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Eliminate render-blocking resources
Potential savings of 1,120 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Contentful Paint (3G)
4368 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Defer offscreen images
Potential savings of 3,164 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Initial server response time was short
Root document took 160 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid serving legacy JavaScript to modern browsers
Potential savings of 7 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
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser
First Contentful Paint
2.1 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests
7 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
First CPU Idle
5.3 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/).
Avoid enormous network payloads
Total size was 6,515 KiB
Large network payloads cost users real money and are highly correlated with long load times
Speed Index
4.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Properly size images
Potential savings of 412 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Remove unused JavaScript
Potential savings of 121 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Keep request counts low and transfer sizes small
59 requests • 6,515 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Max Potential First Input Delay
330 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
Reduce the impact of third-party code
Third-party code blocked the main thread for 670 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
Tap targets are not sized appropriately
87% 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
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
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
Warning! Not 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
Congratulations! Your Domain Authority is good
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 |
| login | Internal Link | 301 |
| Sign up | Internal Link | 301 |
| http://ww1.gogoanime.io/ | Internal Link | 301 |
| Action | Internal Link | 301 |
| Adventure | Internal Link | 301 |
| Cars | Internal Link | 301 |
| Comedy | Internal Link | 301 |
| Dementia | Internal Link | 301 |
| Demons | Internal Link | 301 |
| Drama | Internal Link | 301 |
| Dub | Internal Link | 301 |
| Ecchi | Internal Link | 301 |
| Fantasy | Internal Link | 301 |
| Game | Internal Link | 301 |
| Harem | Internal Link | 301 |
| Hentai | Internal Link | 301 |
| Historical | Internal Link | 301 |
| Horror | Internal Link | 301 |
| Josei | Internal Link | 301 |
| Kids | Internal Link | 301 |
Alexa Rank
Local Rank: O / Users: 57.5% / PageViews: 41.6%
25,004
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| ww1.gogoanime.co | Already Registered |
| ww1.gogoanime.us | Already Registered |
| ww1.gogoanime.com | Already Registered |
| ww1.gogoanime.org | Already Registered |
| ww1.gogoanime.net | Already Registered |
| w1.gogoanime.io | Already Registered |
| zw1.gogoanime.io | Already Registered |
| sw1.gogoanime.io | Already Registered |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200
date: Sun, 01 Nov 2020 00:41:40 GMT
content-type: text/html; charset=utf-8
set-cookie: __cfduid=d1e4ded0ef84cb93d5cfc28521f4fe9291604191300; expires=Tue, 01-Dec-20 00:41:40 GMT; path=/; domain=.gogoanime.so; HttpOnly; SameSite=Lax; Secure
vary: Accept-Encoding
vary: Accept-Encoding
x-powered-by: PHP/5.6.13
set-cookie: gogoanime=a2t1jqaqlruf78pkjmlpae4bo6; path=/
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
pragma: no-cache
cf-cache-status: DYNAMIC
cf-request-id: 0622d9c1b9000036e0070e2000000001
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=25ns0WCA76CWdVSmK5RWYyuNAaNS2RkOLbEEvliYRy3SCnFdw3hVWmsvYyFAa87HZ8qSPaqFGK6QkzEICjo76K458Ow6MAFzzn2IPac%3D"}],"group":"cf-nel","max_age":604800}
nel: {"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 5eb19249294436e0-LAX
content-encoding: gzip
Click to Add/Show Comments