Guancha.cn - SEO Checker - Website Review

Your Website Score is

Similar Ranking

国联资源网_中国领先的B2B电子商务集群,高效的链商资源整合服务网络

ibicn.com

REVOLVE (リボルブ)で、有名デザイナーズブランドの洋服をショッピング

revolveclothing.co.jp

VOITURE AU MAROC - VOITURE OCCASION AU MAROC - ANNONCES MOTEUR.MA

moteur.ma

مكتبة نور - تحميل كتب PDF

noor-book.com

BEST WIFI BROADBAND & INTERNET SERVICE PROVIDER (ISP) IN INDIA | TIKONA INFINET PRIVATE LIMITED

tikona.in

DOWNLOAD--- SOFTWARE FOR WINDOWS - JALECO.COM

jaleco.com

نماشا - سرویس رایگان اشتراک ویدیو

namasha.com

Latest Sites

❶ BẢO PHONG | LẮP ĐẶT CAMERA, CAMERA WIFI GIÁ RẺ Ở HUẾ !

baophong.vn

ONE MORE STEP

seeking.com

MEGOGO.NET - ФИЛЬМЫ И ТЕЛЕКАНАЛЫ ОНЛАЙН

megogo.net

MANOMANO : A--- EN LIGNE BRICOLAGE, RÉNOVATION ET JARDINAGE

manomano.fr

TECHTUDO - A TECNOLOGIA DESCOMPLICADA.

techtudo.com.br

AGILE PROJECT MANAGEMENT | PIVOTAL TRACKER

pivotaltracker.com

MOTORPLUS - PORTAL BERITA MOTOR PERTAMA DAN TERKINI

motorplus-online.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

31 guancha.cn Last Updated: 10 months

Success 63% of passed verification steps

Warning 7% of total warning

Errors 30% of total errors, require fast action

Mobile

Performance Desktop Score 88%

Best Practices Desktop Score 54%

SEO Desktop Score 80%

Progressive Web App Desktop Score 38%

Performance Mobile Score 49%

Best Practices Mobile Score 54%

SEO Mobile Score 90%

Progressive Web App Mobile Score 26%

Page Authority Authority 53%

Domain Authority Domain Authority 63%

Moz Rank 5.3/10

Bounce Rate Rate 0%

Charset Encoding

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

Title Tag 14 Characters

观察者网-中国关怀全球视野

Meta Description 51 Characters

观察者网，致力于荟萃中外思想者精华，鼓励青年学人探索，建中西文化交流平台，为崛起中的精英提供决策参考。

Effective URL 22 Characters

https://www.guancha.cn

Excerpt Page content

观察者网-中国关怀全球视野首页风闻观察员国际 ...

Meta Keywords 1 Detected

观察者网，观察者，春秋综合研究院，新闻，新媒体，观察，中国模式，政治，军事，历史，评论

Keywords Cloud Density

中国雷人秀5 明星那点事儿4 两岸关系4 俄罗斯之声3 美国一梦3 台湾艺人在宁波录制节目时不幸突逝3 查看更多>>3 听听观友怎么说3 三八线之南2 婚姻故事2

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

Keyword	Freq	Title	Desc	Domain	H1	H2
中国雷人秀	5
明星那点事儿	4
两岸关系	4
俄罗斯之声	3
美国一梦	3
台湾艺人在宁波录制节目时不幸突逝	3
查看更多>>	3
听听观友怎么说	3
三八线之南	2
婚姻故事	2

Google Preview Your look like this in google search result

观察者网-中国关怀全球视野

https://www.guancha.cn

观察者网，致力于荟萃中外思想者精华，鼓励青年学人探索，建中西文化交流平台，为崛起中的精英提供决策参考。

Robots.txt File Detected

http://guancha.cn/robots.txt

Sitemap.xml File No Found

http://guancha.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 / 617 months 14 days

Nameservers

ns1.dnsv4.com

ns2.dnsv4.com

Page Size Code & Text Ratio

Document Size: ~272.23 KB

Code Size: ~152.88 KB

Text Size: ~119.35 KB Ratio: 43.84%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Desktop

Does not use HTTPS 3 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 500 ms

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

Eliminate render-blocking resources Potential savings of 30 ms

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

Efficiently encode images Potential savings of 262 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 80 ms

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

JavaScript execution time 0.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 194 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 293 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.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 1,445 KB

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

Minimize main-thread work 2.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 0.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 3 vulnerabilities detected

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

Avoid chaining critical requests 14 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 2,779 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 73 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 0.7 s

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

Keep request counts low and transfer sizes small 66 requests • 1,445 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 81 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

Serve static assets with an efficient cache policy 46 resources found

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

Max Potential First Input Delay 120 ms

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

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

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

Minify CSS Potential savings of 2 KB

Minifying CSS files can reduce network payload sizes

Remove unused CSS Potential savings of 19 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 625 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

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

Does not use HTTPS 5 insecure requests found

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 540 ms

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

Efficiently encode images Potential savings of 41 KB

Optimized images load faster and consume less cellular data

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

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

Reduce JavaScript execution time 1.4 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 211 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

Speed Index 4.8 s

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

First CPU Idle 5.8 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 1,915 KB

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

Minimize main-thread work 10.8 s

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

First Contentful Paint 3.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 2 vulnerabilities detected

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

Avoid chaining critical requests 24 chains found

Avoids an excessive DOM size 336 elements

First Meaningful Paint 3.7 s

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

Keep request counts low and transfer sizes small 110 requests • 1,915 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 81 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

Serve static assets with an efficient cache policy 78 resources found

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

Max Potential First Input Delay 420 ms

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

Time to Interactive 10.6 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 at 10.6 s

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

Estimated Input Latency 100 ms

First Contentful Paint (3G) 7245 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 91% 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 100% 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

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: Wed, 27 Nov 2019 08:02:25 GMT
Content-Type: text/html
Content-Length: 45222
Connection: keep-alive
Server: NWS_Oversea_AP
Cache-Control: max-age=60
Expires: Wed, 27 Nov 2019 08:03:24 GMT
Last-Modified: Wed, 27 Nov 2019 07:50:22 GMT
Content-Encoding: gzip
X-NWS-LOG-UUID: 9906d839-2b3e-4b5c-9d3d-a406529d2d2d
X-Cache-Lookup: Hit From Disktank3 Gz
X-NWS-UUID-VERIFY: 72b23e3aac379defcf43ee5354069c1c
Vary: Accept-Encoding
ETag: "5dde2abe-3cb04"

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	dnspod-vip4.mydnspod.net	49.51.8.209	IN	598
A	dnspod-vip4.mydnspod.net	119.28.48.239	IN	28
CNAME	guancha.cn	dnspod-vip4.mydnspod.net	IN	521

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

31 guancha.cn Last Updated: 10 months

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