6.cn - SEO Checker - Website Review

Your Website Score is

Similar Ranking

MARKETING EYE BRISBANE | NEXT LEVEL MARKETING AGENCY

marketingeyebrisbane.com.au

LAYER CHICKEN CAGE

poultrymachine.com

FILERIO : : CLOUD FILE STORAGE - EASY WAY TO SHARE YOUR FILES

filerio.in

GROW YOUR BUSINESS WITH CONTESTS & SOCIAL MARKETING APPS

gleam.io

TERCEIRO Z - HENTAI, INCESTO, PORNÔ, QUADRINHOS ERÓTICOS E MUITO MAIS!

terceiroz.com

ERROR: THE REQUESTED URL COULD NOT BE RETRIEVED

qhnky.com

METASRC PATCH 9.24 HOME - 5V5

metasrc.com

Latest Sites

AMERICA NO.1 RAMEN MALL

ramenmall.com

SEARCH FOR WHOLESALE PRODUCTS WHOLESALE | SUPPLY LEADER — WHOLESALE SUPPLY

supplyleader.com

home.takepocket.com

ENGINEERING DESTINATION

engineeringdestination.com

BITINCOME.PRO

bitincome.pro

SIMPLY EARN MONEY | MONEY EARNING IDEAS

simplyearnmoney.com

FIEWIN

fiewin.com

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

19 6.cn Last Updated: 1 year

Success 63% of passed verification steps

Warning 7% of total warning

Errors 30% of total errors, require fast action

Mobile

Performance Desktop Score 85%

Best Practices Desktop Score 62%

SEO Desktop Score 80%

Progressive Web App Desktop Score 19%

Performance Mobile Score 65%

Best Practices Mobile Score 92%

SEO Mobile Score 91%

Progressive Web App Mobile Score 52%

Page Authority Authority 0%

Domain Authority Domain Authority 0%

Moz Rank 0.0/10

Bounce Rate Rate 0%

Charset Encoding

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

Title Tag 31 Characters

六间房 - 美女视频 - 美女直播 - 视频聊天 - 视频交友

Meta Description 69 Characters

六间房是真人互动视频直播社区。秀场视频直播间，支持数万人同时在线视频聊天、在线K歌跳舞、视频交友。赶快加入，免费与数万个美女主播在线聊天。

Effective URL 16 Characters

https://www.6.cn

Excerpt Page content

六间房 - 美女视频 - 美女直播 - 视频聊天 - 视频交友首页小视频排行实时战况全站排行分区排行 ...

Meta Keywords 4 Detected

美女视频美女直播视频聊天视频交友

Google Preview Your look like this in google search result

六间房 - 美女视频 - 美女直播 - 视频聊天 - 视频交友

https://www.6.cn

Robots.txt File Detected

http://6.cn/robots.txt

Sitemap.xml File No Found

http://6.cn/sitemap.xml

Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system

Updated: 1970-01-01 / 51 years

Create on: 1970-01-01 / 51 years

Expires on: 1970-01-01 / 626 months 16 days

Nameservers

ns2.6.cn

ns1.6.cn

Page Size Code & Text Ratio

Document Size: ~33.34 KB

Code Size: ~21.8 KB

Text Size: ~11.54 KB Ratio: 34.61%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Desktop

Serve images in next-gen formats Potential savings of 575 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

Reduce server response times (TTFB) Root document took 610 ms

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

Eliminate render-blocking resources Potential savings of 130 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 644 KB

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

Efficiently encode images Potential savings of 197 KB

Optimized images load faster and consume less cellular data

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

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 164 KB

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

Properly size images Potential savings of 229 KB

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

Speed Index 2.1 s

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

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

Avoids enormous network payloads Total size was 2,288 KB

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

Minimizes main-thread work 1.2 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.6 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 3 vulnerabilities detected

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

Avoid chaining critical requests 5 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 3,003 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)

Minify JavaScript Potential savings of 5 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 0.6 s

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

Keep request counts low and transfer sizes small 101 requests • 2,288 KB

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

Serve static assets with an efficient cache policy 21 resources found

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

Max Potential First Input Delay 50 ms

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

Time to Interactive 2.5 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

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 11.9 s

A fast page load over a cellular network ensures a good mobile user experience

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 66 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

Mobile

Does not use HTTPS 25 insecure requests found

All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs

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

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

Efficiently encode images Potential savings of 142 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 20 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 390 ms

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

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 668 KB

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

Speed Index 4.8 s

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

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 5,315 KB

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

Minimize main-thread work 3.6 s

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

First Contentful Paint 2.2 s

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

Avoid chaining critical requests 9 chains found

Avoids an excessive DOM size 352 elements

First Meaningful Paint 4.4 s

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

Keep request counts low and transfer sizes small 83 requests • 5,315 KB

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

Use video formats for animated content Potential savings of 2,895 KB

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes

Uses efficient cache policy on static assets 10 resources found

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

Max Potential First Input Delay 400 ms

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

Time to Interactive 7.1 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 100 ms

First Contentful Paint (3G) 4710 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 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

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

Serve images in next-gen formats Potential savings of 643 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

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: Mon, 23 Dec 2019 18:00:07 GMT
Content-Type: text/html
Connection: keep-alive
Expires: Mon, 23 Dec 2019 18:01:12 GMT
Server: openresty
Last-Modified: Mon, 23 Dec 2019 17:57:09 GMT
ETag: W/"5e00fff5-30610"
Cache-Control: max-age=120
Content-Encoding: gzip
X-HITS: 0
Accept-Ranges: bytes
Age: 55
X-Via: 1.1 shuangxian183:1 (Cdn Cache Server V2.0), 1.1 hx172:10 (Cdn Cache Server V2.0), 1.1 PSmglsjLAX2ax172:17 (Cdn Cache Server V2.0)
X-Ws-Request-Id: 5e0100a7_PSmglsjLAX2jx17_37448-5422

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	6.cn	43.228.180.125	IN	522
NS	6.cn	ns2.6.cn	IN	600
NS	6.cn	ns1.6.cn	IN	600
MX	6.cn	mx.6.cn	IN	600
TXT	6.cn	v=spf1 ip4:125.208.4.244/32 ip4:125.208.4.219/32 ip4:125.208.4.220/32 a mx ~all	IN	60

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

19 6.cn Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments