Dxy.cn - SEO Checker - Website Review

Your Website Score is

Similar Ranking

stream-me.com

北京商铺

010shangpu.com

hunter.trade

com-mac-optimizer.live

IRAN UNIVERSITY OF SCIENCE & TECHNOLOGY - دانشگاه علم و صنعت ایران

iust.ac.ir

ALGEBRA HOMEWORK HELP, ALGEBRA SOLVERS,--- MATH TUTORS

algebra.com

JOBSEARCH.AZ

jobsearch.az

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

3 dxy.cn Last Updated: 10 months

Success 62% of passed verification steps

Warning 15% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 80%

Best Practices Desktop Score 46%

SEO Desktop Score 90%

Progressive Web App Desktop Score 38%

Performance Mobile Score 94%

Best Practices Mobile Score 54%

SEO Mobile Score 92%

Progressive Web App Mobile Score 41%

Page Authority Authority 53%

Domain Authority Domain Authority 33%

Moz Rank 5.3/10

Bounce Rate Rate 0%

Charset Encoding

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

Title Tag 16 Characters

丁香园 - 中国医疗领域的连接者

Meta Description 83 Characters

丁香园是面向医生、医疗机构、医药从业者以及生命科学领域人士的专业性社会化网络，提供医学、医疗、药学、生命科学等相关领域的交流平台、专业知识、最新科研进展以及技术服务。

Effective URL 17 Characters

http://www.dxy.cn

Excerpt Page content

丁香园 - 中国医疗领域的连接者丁香无线丁香园论坛丁香医生新浪微博 ...

Meta Keywords 17 Detected

医学药学生物医学论坛医生临床医学知识病例讨论医学考试论文实验方法数据库文献疾病社区用药助手丁香园

Keywords Cloud Density

丁香医生3 丁香诊所3 丁香无线2 多点执业2 热门话题2 有奖答题2 试用中心2 丁当商城2 insight2 丁香导航2

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

Keyword	Freq	Title	Desc	Domain	H1	H2
丁香医生	3
丁香诊所	3
丁香无线	2
多点执业	2
热门话题	2
有奖答题	2
试用中心	2
丁当商城	2
insight	2
丁香导航	2

Google Preview Your look like this in google search result

丁香园 - 中国医疗领域的连接者

http://www.dxy.cn

Robots.txt File Detected

http://dxy.cn/robots.txt

Sitemap.xml File Detected

http://dxy.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 / 618 months 16 days

Nameservers

ns3.dnsv4.com

ns4.dnsv4.com

Page Size Code & Text Ratio

Document Size: ~152.71 KB

Code Size: ~107.86 KB

Text Size: ~44.84 KB Ratio: 29.36%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

jQuery

JavaScript Frameworks

Nginx

Web Servers

PWA - Manifest

Manifest is not valid

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

Desktop

Enable text compression Potential savings of 4 KB

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

Efficiently encode images Potential savings of 845 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 190 ms

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

JavaScript execution time 0.6 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 1,166 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 3,038 KB

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

Speed Index 2.9 s

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

First CPU Idle 1.4 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 6,398 KB

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

Minimizes main-thread work 1.7 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 13 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,432 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 9 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 95 requests • 6,398 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 52 resources found

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

Max Potential First Input Delay 390 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.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

Estimated Input Latency 30 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

Uses deprecated APIs 1 warning found

Deprecated APIs will eventually be removed from the browser

Serve images in next-gen formats Potential savings of 4,965 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 58 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

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

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

Eliminate render-blocking resources Potential savings of 210 ms

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

Mobile

JavaScript execution time 0.5 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 565 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 1,407 KB

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

Speed Index 4.0 s

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

First CPU Idle 2.1 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,649 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 1.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 3 chains found

Avoids an excessive DOM size 324 elements

First Meaningful Paint 1.7 s

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

Keep request counts low and transfer sizes small 36 requests • 2,649 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 16 resources found

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

Max Potential First Input Delay 100 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.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

First Contentful Paint (3G) 3152 ms

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

Estimated Input Latency 10 ms

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

Serve images in next-gen formats Potential savings of 2,251 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 21 insecure requests found

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

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

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

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 50 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.

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
Server: nginx
Date: Sat, 07 Dec 2019 20:20:26 GMT
Content-Type: text/html
Connection: keep-alive
Last-Modified: Sat, 07 Dec 2019 20:20:01 GMT
Vary: Accept-Encoding
Content-Encoding: gzip
Expires: Sat, 07 Dec 2019 20:30:26 GMT
Cache-Control: max-age=600
Access-Control-Allow-Credentials: true
Access-Control-Allow-Methods: POST,GET,OPTIONS,DELETE,PUT

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	dxy.cn	112.124.103.79	IN	210
NS	dxy.cn	ns3.dnsv4.com	IN	86311
NS	dxy.cn	ns4.dnsv4.com	IN	86311
MX	dxy.cn	mxbiz1.qq.com	IN	600
MX	dxy.cn	mxbiz2.qq.com	IN	600
TXT	dxy.cn	MS=ms79625336	IN	600
TXT	dxy.cn	MS=77ABC6080C975FF86E1E2A1646E4AC1B367C17C5	IN	600
TXT	dxy.cn	dfdv6rtato11v1t9ji0ec1g26m	IN	600
TXT	dxy.cn	v=spf1 include:spf.mail.qq.com -all	IN	7200

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

3 dxy.cn Last Updated: 10 months

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

jQuery

Nginx

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