F95zone.to - SEO Checker - Website Review

Your Website Score is

Similar Ranking

LUMPTY: LEARNING FOR THE FUN OF IT

lumpty.com

FREE ADVERTISING TRAFFIC EXCHANGE - TRAFFIC AD BAR

trafficadbar.com

JUST A MOMENT...

rmz.cr

WEB色見本原色大辞典 - HTMLカラーコード

colordic.org

PRESS INFORMATION BUREAU

pib.gov.in

理想生活上天猫

小谊家的小球星-HELLO, WORLD!

tiyu68.com

Latest Sites

PORTSTONE PARTNERS LIMITED

portstonepartnersltd.com

VENICTRADE.COM

venictrade.com

COINLUNO.COM

coinluno.com

SIGNCURRENCY.COM

signcurrency.com

ALLTRADESFX.COM

alltradesfx.com

MODERN KITCHENS | READIKIT | HOME PAGE

readikit.com

av4.xyz

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

34 f95zone.to Last Updated: 11 months

Success 62% of passed verification steps

Warning 23% of total warning

Errors 15% of total errors, require fast action

Mobile

Performance Desktop Score 89%

Best Practices Desktop Score 85%

SEO Desktop Score 100%

Progressive Web App Desktop Score 58%

Performance Mobile Score 39%

Best Practices Mobile Score 85%

SEO Mobile Score 96%

Progressive Web App Mobile Score 56%

Page Authority Authority 37%

Domain Authority Domain Authority 45%

Moz Rank 3.7/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 7 Characters

F95ZONE

Meta Description 46 Characters

F95zone | Adult Games | Comics | Mods | Cheats

Effective URL 18 Characters

https://f95zone.to

Excerpt Page content

F95zone Menu Forums New posts Trending Bookmarks What's new New posts Latest activity New Thread Ratings Latest Updates LewdPatcher Nutaku ...

Keywords Cloud Density

threads21 messages21 games14 latest12 minutes10 forums9 help5 rpgm5 posts4 sidebar4

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
threads	21
messages	21
games	14
latest	12
minutes	10
forums	9
help	5
rpgm	5
posts	4
sidebar	4

Google Preview Your look like this in google search result

F95ZONE

https://f95zone.to

F95zone | Adult Games | Comics | Mods | Cheats

Robots.txt File No Found

http://f95zone.to/robots.txt

Sitemap.xml File Detected

http://f95zone.to/sitemap.xml

Page Size Code & Text Ratio

Document Size: ~94.89 KB

Code Size: ~70.39 KB

Text Size: ~24.5 KB Ratio: 25.82%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

PWA - Manifest

Manifest is not valid

Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Server response times are low (TTFB) Root document took 300 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 330 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Enable text compression Potential savings of 3 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Efficiently encode images Potential savings of 4 KB

Optimized images load faster and consume less cellular data

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

Total Blocking Time 0 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

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

Defer offscreen images Potential savings of 13 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

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

Properly size images Potential savings of 14 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 1.3 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 1.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).

Avoids enormous network payloads Total size was 2,066 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimizes main-thread work 1.1 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 1.3 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 1 vulnerability detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 29 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

Avoid an excessive DOM size 1,088 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)

First Meaningful Paint 1.3 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 78 requests • 2,066 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Uses efficient cache policy on static assets 2 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 30 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 1.3 s

Time to interactive is the amount of time it takes for the page to become fully interactive

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

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

Remove unused CSS Potential savings of 108 KB

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

Serve images in next-gen formats Potential savings of 109 KB

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

Mobile

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

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

Defer offscreen images Potential savings of 78 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Speed Index 5.7 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 7.0 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).

Avoids enormous network payloads Total size was 2,123 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 4.3 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 5.7 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 1 vulnerability detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 28 chains found

Avoid an excessive DOM size 1,092 elements

First Meaningful Paint 5.8 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 76 requests • 2,123 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Uses efficient cache policy on static assets 1 resource found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 170 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 8.0 s

Time to interactive is the amount of time it takes for the page to become fully interactive

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

Estimated Input Latency 20 ms

First Contentful Paint (3G) 12750 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Tap targets are not sized appropriately 57% 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

Document uses legible font sizes 91.62% 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

Remove unused CSS Potential savings of 109 KB

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

Serve images in next-gen formats Potential savings of 96 KB

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

Server response times are low (TTFB) Root document took 250 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 1,140 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Enable text compression Potential savings of 6 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Efficiently encode images Potential savings of 51 KB

Optimized images load faster and consume less cellular data

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

Total Blocking Time 200 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 200 OK
Date: Sun, 08 Dec 2019 17:23:31 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Set-Cookie: __cfduid=d8ba15b9875724dd23b4121b9343b5cb01575825811; expires=Tue, 07-Jan-20 17:23:31 GMT; path=/; domain=.f95zone.to; HttpOnly; Secure
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Last-Modified: Sun, 08 Dec 2019 17:23:35 GMT
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: private, no-cache, max-age=0
Vary: Accept-Encoding
Set-Cookie: xf_csrf=gAyfHIEpc3dd4gOg; path=/; secure
Strict-Transport-Security: max-age=15768000
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Alt-Svc: h3-23=":443"; ma=86400
Server: cloudflare
CF-RAY: 54206d791bed218a-EWR
Content-Encoding: gzip

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	f95zone.to	104.26.7.12	IN	208
A	f95zone.to	104.26.6.12	IN	208
NS	f95zone.to	ulla.ns.cloudflare.com	IN	56117
NS	f95zone.to	clyde.ns.cloudflare.com	IN	56117
TXT	f95zone.to	ca3-28447cbba7de42de8af7ec63335d9b6d	IN	300
AAAA	f95zone.to	2606:4700:20::681a:70c	IN	47
AAAA	f95zone.to	2606:4700:20::681a:60c	IN	47

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

34 f95zone.to Last Updated: 11 months

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

CloudFlare

Google Font API

React

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments