Your Website Score is
SEO Rank : 46 Website URL: fakku.net Last Updated: 6 months
Success
78% of passed verification steps
Warning
7% of total warning
Errors
15% of total errors, require fast action
Share
Estimation Traffic and Earnings
2,612
Unique Visits
Daily
4,832
Pages Views
Daily
$10
Income
Daily
73,136
Unique Visits
Monthly
137,712
Pages Views
Monthly
$250
Income
Monthly
846,288
Unique Visits
Yearly
1,623,552
Pages Views
Yearly
$2,640
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 51%
Domain Authority
Domain Authority 54%
Moz Rank
5.1/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
45 Characters
HENTAI MANGA, ANIME, GAMES AND COMICS - FAKKU
Meta Description
138 Characters
FAKKU is the largest English hentai publisher in the world. Thousands of uncensored English hentai manga, comics, and doujinshi available.
Effective URL
21 Characters
https://www.fakku.net
Excerpt
Page content
Hentai Manga, Anime, Games and Comics - FAKKU
Anime
Comics
Doujin
Games
Manga
Tags
Forums
1
Login / Register
New Releases
Popular
Tags
Minazuki Mikka
...
Google Preview
Your look like this in google search result
HENTAI MANGA, ANIME, GAMES AND COMICS - FAKKU
https://www.fakku.net
FAKKU is the largest English hentai publisher in the world. Thousands of uncensored English hentai manga, comics, and doujinshi available.
Robots.txt
File Detected
Sitemap.xml
File Detected
Page Size
Code & Text Ratio
Document Size: ~195.37 KB
Code Size: ~164.3 KB
Text Size: ~31.07 KB Ratio: 15.90%
Social Data
Desktop
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 17.9 s
A fast page load over a cellular network ensures a good mobile user experience
Minimize third-party usage
Third-party code blocked the main thread for 0 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
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
Max Potential First Input Delay
30 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
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
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index
1.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Keep request counts low and transfer sizes small
57 requests • 5,693 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint
5.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve static assets with an efficient cache policy
54 resources found
A long cache lifetime can speed up repeat visits to your page
First CPU Idle
0.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/).
Reduce initial server response time
Root document took 810 ms
Keep the server response time for the main document short because all other requests depend on it
JavaScript execution time
0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint
0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid large layout shifts
4 elements found
These DOM elements contribute most to the CLS of the page.
Remove unused JavaScript
Potential savings of 20 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoid an excessive DOM size
2,888 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)
Time to Interactive
0.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Properly size images
Potential savings of 2,777 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Cumulative Layout Shift
0.602
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
Remove unused CSS
Potential savings of 42 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
Minimizes main-thread work
0.5 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
1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
First Meaningful Paint
0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid enormous network payloads
Total size was 5,693 KiB
Large network payloads cost users real money and are highly correlated with long load times
Mobile
First Meaningful Paint
2.3 s
First Meaningful Paint measures when the primary content of a page is visible
Time to Interactive
12.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Remove unused CSS
Potential savings of 42 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
Document uses legible font sizes
96.4% 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
Avoid enormous network payloads
Total size was 5,694 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid an excessive DOM size
2,888 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)
Reduce initial server response time
Root document took 940 ms
Keep the server response time for the main document short because all other requests depend on it
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
Remove unused JavaScript
Potential savings of 20 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
First Contentful Paint
2.3 s
First Contentful Paint marks the time at which the first text or image is painted
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
Total Blocking Time
60 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Keep request counts low and transfer sizes small
57 requests • 5,694 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
Properly size images
Potential savings of 250 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Tap targets are not sized appropriately
97% 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
First CPU Idle
2.6 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/).
Speed Index
3.1 s
Speed Index shows how quickly the contents of a page are visibly populated
First Contentful Paint (3G)
4595 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
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
Max Potential First Input Delay
130 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Defer offscreen images
Potential savings of 5,204 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
JavaScript execution time
0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Serve static assets with an efficient cache policy
54 resources found
A long cache lifetime can speed up repeat visits to your page
Page load is not fast enough on mobile networks
Interactive at 12.2 s
A fast page load over a cellular network ensures a good mobile user experience
Avoid long main-thread tasks
6 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint
5.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
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 |
| http://fakku.net/ | Internal Link | 301 |
| Hentai Anime | Internal Link | 301 |
| Hentai Manga | Internal Link | 301 |
| Hentai Doujin | Internal Link | 301 |
| Hentai Games | Internal Link | 301 |
| Hentai Manga | Internal Link | 301 |
| Hentai Tags | Internal Link | 301 |
| FAKKU Forums | Internal Link | 301 |
| Notifications | Internal Link | 301 |
| Cart | Internal Link | 301 |
| Login | Internal Link | 301 |
| Register | Internal Link | 301 |
| Popular | Internal Link | 301 |
| http://fakku.net/hentai/----or-die-1-english | Internal Link | 301 |
| Minazuki Mikka | Internal Link | 301 |
| ahegao | Internal Link | 301 |
| color | Internal Link | 301 |
| netorare | Internal Link | 301 |
| busty | Internal Link | 301 |
| stockings | Internal Link | 301 |
Alexa Rank
12,613
Local Rank: US / Users: 64.6% / PageViews: 85.1%39,056
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| fakku.co | Already Registered |
| fakku.us | Already Registered |
| fakku.com | Already Registered |
| fakku.org | Already Registered |
| fakku.net | Already Registered |
| fkku.net | Available Buy Now! |
| rakku.net | Already Registered |
| vakku.net | Available Buy Now! |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 404
date: Wed, 05 Aug 2020 02:51:37 GMT
content-type: text/html; charset=UTF-8
set-cookie: __cfduid=d20ee771f1259bddcc3beb9586cd9ff841596595897; expires=Fri, 04-Sep-20 02:51:37 GMT; path=/; domain=.fakku.net; HttpOnly; SameSite=Lax
vary: Accept-Encoding
x-frame-options: SAMEORIGIN
x-varnish: 275587417
age: 0
x-cache: MISS
device: desktop
cf-cache-status: DYNAMIC
cf-request-id: 045e211c3600005f9735abe200000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 5bdd37a6bfcc5f97-LAS
content-encoding: gzip
Click to Add/Show Comments