Your Website Score is

Similar Ranking

74
2NN 2ちゃんねるニュース速報+ナビ - 2CH NEWS NAVIGATOR
2nn.jp
74
XENFORO - COMPELLING COMMUNITY FORUM SOFTWARE
xenforo.com
74
YAMAHA CORPORATION - GLOBAL
yamaha.com
74
INSTITUTE OF PHYSICS - FOR PHYSICS • FOR PHYSICISTS • FOR ALL : INSTITUTE OF PHYSICS
iop.org
74
手机新浪网
sina.cn
74
BACKGROUND CHECKS AND PUBLIC RECORDS SEARCH - TRUTHFINDER
truthfinder.com
74
MINNE | ハンドメイド・手作り・クラフト作品のマーケット
minne.com

Latest Sites

24
THIẾT KẾ - THI CÔNG NỘI THẤT - SẢN XUẤT TRỰC TIẾP | NỘI THẤT MẠNH HỆ
noithatmanhhe.vn
19
SẢN PHẨM NỘI THẤT: GIƯỜNG TẦNG, GIƯỜNG BÀN, GIƯỜNG GẤP
nhacanhothongminh.com
16
CRYPTO-MINING.BIZ - REGISTERED AT NAMECHEAP.COM
crypto-mining.biz
57
99.9% DICE - BITCOIN, DOGECOIN, LITECOIN & ETHEREUM GAMBLING
999dice.com
19
RELANDICE BOT FOR 999DICE
relandice.com
23
❶ BẢO PHONG | LẮP ĐẶT CAMERA, CAMERA WIFI GIÁ RẺ Ở HUẾ !
baophong.vn
51
ONE MORE STEP
seeking.com

Top Technologies

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

74 sina.cn Last Updated: 10 months

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

Desktop

Mobile

Performance Desktop Score 80%
Best Practices Desktop Score 77%
SEO Desktop Score 89%
Progressive Web App Desktop Score 50%
Performance Mobile Score 52%
Best Practices Mobile Score 69%
SEO Mobile Score 90%
Progressive Web App Mobile Score 52%
Page Authority Authority 64%
Domain Authority Domain Authority 85%
Moz Rank 6.4/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 5 Characters
手机新浪网
Meta Description 107 Characters
手机新浪网是新浪网的手机门户网站,为亿万用户打造一个手机联通世界的超级平台,提供24小时全面及时的中文资讯,内容覆盖国内外突发新闻事件、体坛赛事、娱乐时尚、产业资讯、实用信息等。手机新浪网触屏版 - sina.cn
Effective URL 14 Characters
http://sina.cn
Excerpt Page content
手机新浪网 您的浏览器不支持JavaScript脚本,请开启! 标准版智能版 新浪移动_手机新浪网_用户设置 新闻财经体育娱乐军事汽车科技视频美图NBA博客房产股票游戏小说星座教育女性健康微博更多 ...
Keywords Cloud Density
点击查看更多15 sinaimg12 https12 translate6 transform3 查看更多热点资讯2 对社会有意1 1周运及重要星象1 我相信爱情1 爱情一定是美好的1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
点击查看更多 15
sinaimg 12
https 12
translate 6
transform 3
查看更多热点资讯 2
对社会有意 1
1周运及重要星象 1
我相信爱情 1
爱情一定是美好的 1
Google Preview Your look like this in google search result
手机新浪网
http://sina.cn
手机新浪网是新浪网的手机门户网站,为亿万用户打造一个手机联通世界的超级平台,提供24小时全面及时的中文资讯,内容覆盖国内外突发新闻事件、体坛赛事、娱乐时尚、产业资讯、实用信息等。手机新浪网触屏版 - sina.cn
Robots.txt File Detected
Sitemap.xml File Detected
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 21 days

Nameservers
ns3.sina.com.cn
ns2.sina.com.cn
Page Size Code & Text Ratio
Document Size: ~233.87 KB
Code Size: ~166.71 KB
Text Size: ~67.15 KB Ratio: 28.71%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

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

Desktop

Desktop Screenshot
Defer offscreen images Potential savings of 234 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 17 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.5 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 985 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
Avoid chaining critical requests 4 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,181 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 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 104 requests • 985 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 81 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 70 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.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
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 32 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 89 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 1 insecure request 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
Avoid multiple page redirects Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded
Reduce server response times (TTFB) Root document took 1,550 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 250 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 64 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 34 KB
Optimized images load faster and consume less cellular data
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Mobile

Mobile Screenshot
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 59 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 20 KB
Optimized images load faster and consume less cellular data
Total Blocking Time 950 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.8 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 198 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 7.8 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 6.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 1,097 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 9.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 2.4 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 4 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,178 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 2.4 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 102 requests • 1,097 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 75 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 310 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.7 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) 4755 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 80 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
Tap targets are not sized appropriately 95% 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 96.13% 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 32 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 58 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
Avoid multiple page redirects Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded
Does not use HTTPS 1 insecure request 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 1,330 ms
Time To First Byte identifies the time at which your server sends a response

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

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 204 No Content
Server: openresty
Date: Thu, 28 Nov 2019 03:01:37 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
X-CUSTOM: Method is illegal
Cache-Control: no-cache
SINA-LB:aGEuMTY5LmcxLmh5ZHMubGIuc2luYW5vZGUuY29t
SINA-TS:OWRlMjgwY2UgMCA0IDQgMTEgNAo=
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome