Your Website Score is

Similar Ranking

84
ATTENTION REQUIRED! | CLOUDFLARE
fanfiction.net
84
SCHWEIZER RADIO UND FERNSEHEN (SRF)
srf.ch
79
✧・*.HAPPY SUGAR RUSH!!.・*✧
renhanascola.carrd.co
79
PHOTOPEA | ONLINE PHOTO EDITOR
photopea.com
76
ПРЕЗИДЕНТ РОССИИ
kremlin.ru
74
YAHOO
yahoo.es

Latest Sites

43
PLEASE WAIT... | CLOUDFLARE
voz.vn
23
TRUST CHRIST OR GO TO HELL! - REBUKING THE PUKE. DESTROYING THE WICKED. IN JESUS' NAME.
trustchristorgotohell.org
99
YOUTUBE
youtube.com
96
YOUTUBE
youtu.be
22
HOME | SOIMBIOSIS: CRYPTO RISING
soimbiosis.com
99
YOUTUBE
m.youtube.com
19
F.A.C.E. THE AGENCY: TRAINING & BUSINESS DEVELOPMENT FIRM
face-theagency.com

Top Technologies

Google Font API
Font Scripts
CloudFlare
CDN
Nginx
Web Servers
Apache
Web Servers
WordPress
CMS
Font Awesome
Font Scripts
Twitter Bootstrap
Web Frameworks
Google Tag Manager
Tag Managers

84 fanfiction.net Last Updated: 3 years

Success 47% of passed verification steps
Warning 30% of total warning
Errors 23% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 98%
Best Practices Desktop Score 80%
SEO Desktop Score 91%
Progressive Web App Desktop Score 45%
Performance Mobile Score 48%
Best Practices Mobile Score 73%
SEO Mobile Score 92%
Progressive Web App Mobile Score 50%
Page Authority Authority 66%
Domain Authority Domain Authority 86%
Moz Rank 6.6/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 32 Characters
ATTENTION REQUIRED! | CLOUDFLARE
Meta Description 0 Characters
NO DATA
Effective URL 26 Characters
https://www.fanfiction.net
Excerpt Page content
Attention Required! | Cloudflare Please enable cookies. One more step Please complete the security check to access www.fanfiction.net ...
Keywords Cloud Density
please5 network3 infected2 cookies2 reload2 page2 captcha2 enable2 scan2 security2
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
please 5
network 3
infected 2
cookies 2
reload 2
page 2
captcha 2
enable 2
scan 2
security 2
Google Preview Your look like this in google search result
ATTENTION REQUIRED! | CLOUDFLARE
https://www.fanfiction.net
Attention Required! | Cloudflare Please enable cookies. One more step Please complete the security check to access www.fanfiction.net ...
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~11.72 KB
Code Size: ~8.97 KB
Text Size: ~2.75 KB Ratio: 23.45%

Social Data

Estimation Traffic and Earnings

43,371
Unique Visits
Daily
80,236
Pages Views
Daily
$78
Income
Daily
1,214,388
Unique Visits
Monthly
2,286,726
Pages Views
Monthly
$1,950
Income
Monthly
14,052,204
Unique Visits
Yearly
26,959,296
Pages Views
Yearly
$20,592
Income
Yearly

Desktop

Desktop Screenshot
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
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted
Speed Index 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Total Blocking Time 110 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce unused CSS Potential savings of 27 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Initial server response time was short Root document took 120 ms
Keep the server response time for the main document short because all other requests depend on it
Reduce unused JavaScript Potential savings of 94 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoids enormous network payloads Total size was 749 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Enable text compression Potential savings of 8 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Minimizes main-thread work 1.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Includes front-end JavaScript libraries with known security vulnerabilities 4 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
Avoid large layout shifts 2 elements found
These DOM elements contribute most to the CLS of the page.
User Timing marks and measures 8 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Serve static assets with an efficient cache policy 12 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid chaining critical requests 2 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 Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible
JavaScript execution time 1.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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 an excessive DOM size 1,106 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)
Cumulative Layout Shift 0.007
Cumulative Layout Shift measures the movement of visible elements within the viewport
Serve images in next-gen formats Potential savings of 24 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
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
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
Time to Interactive 1.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Keep request counts low and transfer sizes small 66 requests • 749 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint 0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid long main-thread tasks 4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Eliminate render-blocking resources Potential savings of 100 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Mobile

Mobile Screenshot
Document uses legible font sizes 98.85% 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
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 long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Initial server response time was short Root document took 130 ms
Keep the server response time for the main document short because all other requests depend on it
First Meaningful Paint 2.8 s
First Meaningful Paint measures when the primary content of a page is visible
Cumulative Layout Shift 0.027
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minimize main-thread work 7.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Reduce unused JavaScript Potential savings of 53 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Total Blocking Time 1,660 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Eliminate render-blocking resources Potential savings of 350 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Tap targets are sized appropriately 100% 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
Largest Contentful Paint 3.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid an excessive DOM size 916 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 the impact of third-party code Third-party code blocked the main thread for 1,260 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
Speed Index 4.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoids enormous network payloads Total size was 1,017 KiB
Large network payloads cost users real money and are highly correlated with long load times
Keep request counts low and transfer sizes small 234 requests • 1,017 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid chaining critical requests 2 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 Contentful Paint (3G) 5672 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
Avoid multiple page redirects Potential savings of 780 ms
Redirects introduce additional delays before the page can be loaded
Serve static assets with an efficient cache policy 40 resources found
A long cache lifetime can speed up repeat visits to your page
First Contentful Paint 2.8 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Time to Interactive 10.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Reduce JavaScript execution time 4.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Reduce unused CSS Potential savings of 18 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Max Potential First Input Delay 440 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task

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
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Warning! Not found a sitemap file for your website
SSL Secure
Warning! Your website is not SSL secured (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
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

2,318

Global Rank

841

United States
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
fanfiction.co Already Registered
fanfiction.us Already Registered
fanfiction.com Already Registered
fanfiction.org Already Registered
fanfiction.net Already Registered
fnfiction.net Already Registered
ranfiction.net Available
vanfiction.net Already Registered

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 403 Forbidden
Date: Thu, 17 Jun 2021 13:41:00 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
CF-Chl-Bypass: 1
Permissions-Policy: accelerometer=(),autoplay=(),camera=(),clipboard-read=(),clipboard-write=(),fullscreen=(),geolocation=(),gyroscope=(),hid=(),interest-cohort=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=()
Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: Thu, 01 Jan 1970 00:00:01 GMT
X-Frame-Options: SAMEORIGIN
cf-request-id: 0abbcd34d600002c5c15905000000001
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Vary: Accept-Encoding
Strict-Transport-Security: max-age=2592000; includeSubDomains; preload
Server: cloudflare
CF-RAY: 660cb167b9ff2c5c-ORD
alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400, h3=":443"; ma=86400
DNS Records DNS Resource Records associated with a hostname
View DNS Records