Yahoo.Com.Cn - Info 
yahoo.com.cn receives about 17,238 unique visitors and 27,580 (1.60 per visitor) page views per day which should earn about $235.36/day from advertising revenue. Estimated site value is $171,814.45. According to Alexa Traffic Rank yahoo.com.cn is ranked number 177,602 in the world and 0.00038% of global Internet users visit it. Site is hosted in Sunnyvale, CA, 94089, Switzerland and links to network IP address 212.82.100.150. This server doesn't support HTTPS and doesn't support HTTP/2.
About - yahoo.com.cn
Technologies used on Website
- Web Servers
- Apache Traffic Server
- JavaScript Libraries
- Lightbox
- JavaScript Frameworks
- Prototype
- RequireJS
yahoo.com.cn Profile
Title: Bad Request
Description: 含新闻、资讯、邮箱和搜索引擎。
Description: 含新闻、资讯、邮箱和搜索引擎。
Last update was 18 days ago
This can take up to 60 seconds. Please wait...
This can take up to 60 seconds. Please wait...
*HypeStat.com is not linking to, promoting or affiliated with yahoo.com.cn in any way. Only publicly available statistics data are displayed.
How popular is yahoo.com.cn?
17.2K daily visitors
Is this your site?
Verify your site's metrics.
Verify your site's metrics.
- Daily Unique Visitors:
- 17,238
- Monthly Unique Visitors:
- 413,712
- Pages per Visit:
- 1.60
- Daily Pageviews:
- 27,580
- Alexa Rank:
- 177,602 visit alexa
- Alexa Reach:
- 0.00038% (of global internet users)
- Avg. visit duration:
- 00:07
- Bounce rate:
- 87.75%
Traffic sources
- Direct:
- 90.42%
- Referral:
- 6.80%
- Search:
- 2.78%
- Social:
- 0%
- Paid:
- 0%
Visitors by country
- Users%Pageviews%Rank
- United States 75.8%74.4%56651
Where do visitors go on this site?
- Reach%Pageviews%PerUser
- yahoo.com.cn
- 100.00%100.00%1.9
Competitive Data
- Domain:
- yahoo.com.cn
- Rank:
(Rank based on keywords, cost and organic traffic) - 12,960,140
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 18
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 3
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $0.00
- Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results) - 0
- Adwords Traffic:
(Number of visitors brought to the website via paid search results) - 0
- Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation) - $0.00
Backlinks Report
- Total Sites Linking In (Alexa):
- 1,008
- Total Backlinks:
- 4,416,071
- Follow Links:
- 4,387,194
- Nofollow Links:
- 28,876
- Referring Domains:
- 14,032
- Referring IPs:
- 11,471
- Authority Domain Score:
- 47
Backlinks by country
Currently Not AvailableBacklinks by TLDs
Currently Not Available+ Moz Data
- Domain Authority:
- n/a
- Page Authority:
- n/a
- MozRank:
- n/a
+ Ad Experience Report
Summary of the ad experience rating of a site for a specific platform.
Desktop summary
- Root domain:
- yahoo.com.cn
- Region:
(The Ad Standard region to which this site has been assigned.) - Pending
- Ad filtering:
(Chrome is not filtering ads on your site.) - Off
- Status:
(The status of the site that is reviewed for the Better Ads Standards.) - Not reviewed
Mobile summary
- Region:
(The Ad Standard region to which this site has been assigned.) - Pending
- Ad filtering:
(Chrome is not filtering ads on your site.) - Off
- Status:
(The status of the site that is reviewed for the Better Ads Standards.) - Not reviewed
+ Abusive Experience Report
- Root domain:
- yahoo.com.cn
- Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.) - Off
- Status:
(The status of the site reviewed for the abusive experiences.) - Not reviewed
+ How much yahoo.com.cn can earn?
- Daily Revenue:
- $235.36
- Monthly Revenue:
- $7,060.80
- Yearly Revenue:
- $85,906.40
Daily earning by country
- PageviewsEarning
- United States 20,520$235.36
How much money do yahoo.com.cn lose due to Adblock?
- Daily Revenue Loss:
- $42.36
- Monthly Revenue Loss:
- $1,270.94
- Yearly Revenue Loss:
- $15,463.08
- Daily Pageviews Blocked:
- 3,694
- Monthly Pageviews Blocked:
- 110,805
- Yearly Pageviews Blocked:
- 1,348,132
Daily revenue loss by country
- BlockedLost Money
- United States 3,694$42.36
How much is yahoo.com.cn worth?
- Website Value:
- $171,814.45
+ Where is yahoo.com.cn hosted?
- Server IP:
- 212.82.100.150
- ASN:
- AS34010
- ISP:
- Yahoo! UK Services Limited
- Server Location:
- Sunnyvale
CA
94089
Switzerland, CH
Other sites hosted on 212.82.100.150
+ How fast does yahoo.com.cn load?
- Average Load Time:
- (1739 ms) 52 % of sites are slower
Page Speed (Google PageSpeed Insights) - Desktop
Field Data
Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.
First Contentful Paint (FCP)2.0s
First Input Delay (FID)32ms
Origin Data
All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.
First Contentful Paint (FCP)1.8s
First Input Delay (FID)31ms
Lab Data
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. Learn more.
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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. Learn more.
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. Learn more.
Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
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.
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Screenshot Thumbnails
This is what the load of your site looked like.
Eliminate render-blocking resources - Potential savings of 230 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
- URL
- SizePotential Savings
- https://s.yimg.com/zz/combo?pv/static/lib/syc-purple_64c01318026693c7b459e893936d024d.css
- 9 KB230
Network Requests
Lists the network requests that were made during page load.
Lists the network requests that were made during page load.
- URL
- Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
- http://yahoo.com.cn/
- 0 ms33 ms1 KB0 KB301text/html
- http://sg.search.yahoo.com/
- 33 ms108 ms0 KB0 KB301text/html
- https://sg.search.yahoo.com/
- 108 ms263 ms7 KB13 KB200text/htmlDocument
- https://s.yimg.com/zz/combo?pv/static/lib/syc-purple_64c01318026693c7b459e893936d024d.css
- 275 ms293 ms9 KB37 KB200text/cssStylesheet
- https://s.yimg.com/pv/static/img/yahoo-search-logo-142x37.png
- 298 ms316 ms4 KB3 KB200image/pngImage
- https://s.yimg.com/pv/static/lib/syc-purple_3a80e0e1d7345f5ba9fd6117a473c8d2.js
- 319 ms381 ms149 KB499 KB200application/x-javascriptScript
Minimize third-party usage - Third-party code blocked the main thread for 40 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. Learn more.
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. Learn more.
- Third-Party
- SizeMain-Thread Blocking Time
- 169 KB37 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.
Lists the toplevel main thread tasks that executed during page load.
- Start Time
- End Time
- 287 ms
- 7 ms
- 321 ms
- 12 ms
- 423 ms
- 109 ms
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. Learn more.
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
- URL
- Total CPU TimeScript EvaluationScript Parse
- https://s.yimg.com/pv/static/lib/syc-purple_3a80e0e1d7345f5ba9fd6117a473c8d2.js
- 120 ms104 ms8 ms
Avoids enormous network payloads - Total size was 170 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
- URL
- Size
- https://s.yimg.com/pv/static/lib/syc-purple_3a80e0e1d7345f5ba9fd6117a473c8d2.js
- 149 KB
- https://s.yimg.com/zz/combo?pv/static/lib/syc-purple_64c01318026693c7b459e893936d024d.css
- 9 KB
- https://sg.search.yahoo.com/
- 7 KB
- https://s.yimg.com/pv/static/img/yahoo-search-logo-142x37.png
- 4 KB
- http://yahoo.com.cn/
- 1 KB
- http://sg.search.yahoo.com/
- 0 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
- Category
- Time Spent
- Script Evaluation
- 112 ms
- Other
- 22 ms
- Style & Layout
- 15 ms
- Script Parsing & Compilation
- 10 ms
- Rendering
- 5 ms
- Garbage Collection
- 5 ms
- Parse HTML & CSS
- 4 ms
Avoids an excessive DOM size - 39 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). Learn more.
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). Learn more.
- Statistic
- ElementValue
- Total DOM Elements
- 39
- Maximum DOM Depth
- 10
- Maximum Child Elements
- 6
Avoid multiple page redirects - Potential savings of 380 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Redirects introduce additional delays before the page can be loaded. Learn more.
- URL
- Time Spent
- (Initial: http://yahoo.com.cn/)
- 0
- http://sg.search.yahoo.com/
- 190
- https://sg.search.yahoo.com/
- 190
Keep request counts low and transfer sizes small - 6 requests • 170 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
- Resource Type
- RequestsTransfer Size
- Total
- 6170 KB
- Script
- 1149 KB
- Stylesheet
- 19 KB
- Document
- 17 KB
- Image
- 14 KB
- Other
- 21 KB
- Media
- 00 KB
- Font
- 00 KB
- Third-party
- 4163 KB
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.
First Contentful Paint (FCP)1.6s
First Input Delay (FID)231ms
Origin Data
All pages served from this origin have an FAST speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.
First Contentful Paint (FCP)580ms
First Input Delay (FID)31ms
Lab Data
First Contentful Paint 1.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
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. Learn more.
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 3.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint (3G) 3690 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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. Learn more.
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. Learn more.
Speed Index 2.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 3.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
Screenshot Thumbnails
This is what the load of your site looked like.
- URL
- Size
- https://s.yimg.com/pv/static/lib/mobile-core-js-1-mi6_8263a5253d05f226f4f8be4ccd30305a.js
- 91 KB
- https://sg.search.yahoo.com/
- 30 KB
- https://s.yimg.com/pv/static/lib/mobile-core-js-2-mi6_e5471bc02c5f80eeac293a42a17a0563.js
- 8 KB
- https://s.yimg.com/pv/static/img/yahoo-search-logo-142x37-2x.png
- 7 KB
- https://s.yimg.com/pv/static/lib/ios-default-set_201312031214.js
- 6 KB
- https://geo.yahoo.com/p?s=958781386&sec=msetdefsearch&src=mi5&setyh=0&prmpt=0&bcookie=e1dtqedfbsvi5%26b%3D3%26s%3Due&srcpvid=SxPUrDEwLjHgt7pzXr5.RQQPNzQuMQAAAAAyPL8J&lang=en&intl=sg&fr=&fr2=&tsrc=&vtestid=&mtestid=&nptrsn=na&1589542469427
- 1 KB
- http://yahoo.com.cn/
- 1 KB
- http://sg.search.yahoo.com/
- 0 KB
- Category
- Time Spent
- Script Evaluation
- 222 ms
- Other
- 81 ms
- Style & Layout
- 58 ms
- Script Parsing & Compilation
- 47 ms
- Parse HTML & CSS
- 13 ms
- Rendering
- 10 ms
- Statistic
- ElementValue
- Total DOM Elements
- 43
- Maximum DOM Depth
- 8
- Maximum Child Elements
- 11
- URL
- Time Spent
- (Initial: http://yahoo.com.cn/)
- 0
- http://sg.search.yahoo.com/
- 630
- https://sg.search.yahoo.com/
- 630
- Resource Type
- RequestsTransfer Size
- Total
- 8144 KB
- Script
- 3105 KB
- Document
- 130 KB
- Image
- 28 KB
- Other
- 21 KB
- Stylesheet
- 00 KB
- Media
- 00 KB
- Font
- 00 KB
- Third-party
- 5113 KB
- URL
- Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
- http://yahoo.com.cn/
- 0 ms121 ms1 KB0 KB301text/html
- http://sg.search.yahoo.com/
- 122 ms194 ms0 KB0 KB301text/html
- https://sg.search.yahoo.com/
- 195 ms387 ms30 KB74 KB200text/htmlDocument
- https://s.yimg.com/pv/static/img/yahoo-search-logo-142x37-2x.png
- 411 ms441 ms7 KB6 KB200image/pngImage
- https://s.yimg.com/pv/static/lib/mobile-core-js-1-mi6_8263a5253d05f226f4f8be4ccd30305a.js
- 445 ms504 ms91 KB275 KB200application/x-javascriptScript
- https://s.yimg.com/pv/static/lib/mobile-core-js-2-mi6_e5471bc02c5f80eeac293a42a17a0563.js
- 445 ms462 ms8 KB19 KB200application/x-javascriptScript
- https://s.yimg.com/pv/static/lib/ios-default-set_201312031214.js
- 446 ms462 ms6 KB14 KB200application/x-javascriptScript
- https://geo.yahoo.com/p?s=958781386&sec=msetdefsearch&src=mi5&setyh=0&prmpt=0&bcookie=e1dtqedfbsvi5%26b%3D3%26s%3Due&srcpvid=SxPUrDEwLjHgt7pzXr5.RQQPNzQuMQAAAAAyPL8J&lang=en&intl=sg&fr=&fr2=&tsrc=&vtestid=&mtestid=&nptrsn=na&1589542469427
- 469 ms563 ms1 KB0 KB200image/gifImage
- Third-Party
- SizeMain-Thread Blocking Time
- 143 KB117 ms
- Start Time
- End Time
- 410 ms
- 7 ms
- 420 ms
- 7 ms
- 430 ms
- 16 ms
- 462 ms
- 5 ms
- 538 ms
- 48 ms
- URL
- Total CPU TimeScript EvaluationScript Parse
- https://s.yimg.com/pv/static/lib/mobile-core-js-1-mi6_8263a5253d05f226f4f8be4ccd30305a.js
- 191 ms168 ms20 ms
- Other
- 178 ms15 ms4 ms
- https://sg.search.yahoo.com/
- 53 ms37 ms16 ms
Serve images in next-gen formats
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. Learn more.
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. Learn more.
Avoid chaining critical requests - 1 chain 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. Learn more.
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. Learn more.
Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Use video formats for animated content
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. Learn more.
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. Learn more.
Server response times are low (TTFB) - Root document took 190 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.
Time To First Byte identifies the time at which your server sends a response. Learn more.
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.
Optimized images load faster and consume less cellular data. Learn more.
Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
A long cache lifetime can speed up repeat visits to your page. Learn more.
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. Learn more.
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. Learn more.
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.
Minifying CSS files can reduce network payload sizes. Learn more.
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. Learn more.
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. Learn more.
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Remove unused CSS
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. Learn more.
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. Learn more.
Page Speed (Google PageSpeed Insights) - v2
Suggestions Summary
Avoid landing page redirects
Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.Avoid landing page redirects for the following chain of redirected URLs.
http://yahoo.com.cn/http://sg.search.yahoo.com/https://sg.search.yahoo.com/Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.The following tap targets are close to other nearby tap targets and may need additional spacing around them.
The tap target
<a href="https://sg.sea…mb=H/7hxSzRuXa">Settings</a> and 2 others are close to other tap targets .Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.Enable compression
You have compression enabled. Learn more about enabling compression.Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.Reduce server response time
Your server responded quickly. Learn more about server response time optimization.Minify CSS
Your CSS is minified. Learn more about minifying CSS.Minify HTML
Your HTML is minified. Learn more about minifying HTML.Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.Eliminate render-blocking JavaScript and CSS in above-the-fold content
You have no render-blocking resources. Learn more about removing render-blocking resources.Optimize images
Your images are optimized. Learn more about optimizing images.Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes. Download optimized image, JavaScript, and CSS resources for this page. + Does yahoo.com.cn use compression?
yahoo.com.cn does not use compression.
Original size: 3.28 KB
Compressed size: n/a
File reduced by: n/a
Compressed size: n/a
File reduced by: n/a
+ Google Safe Browsing
+ SSL Checker - SSL Certificate Verify
yahoo.com.cn does not support HTTPS
Verifying SSL Support. Please wait...
+ Verify HTTP/2 Support
yahoo.com.cn does not support HTTP/2
Verifying HTTP/2.0 Support. Please wait...
+ Site Categories (dmoz)
Currently Not Available
+ Http Header
Date: Tue, 26 Nov 2019 10:20:21 GMT
Connection: close
Server: ATS
Cache-Control: no-store
Content-Type: text/html
Content-Language: en
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Referrer-Policy: strict-origin-when-cross-origin
Content-Security-Policy: sandbox; default-src 'self'; script-src 'none'; object-src 'none'; report-uri https://csp.yahoo.com/beacon/csp?src=generic
Content-Length: 220
+ DNS Lookup
| Type | Ip | Target | TTL |
| CAA | 3600 | ||
| CAA | 3600 | ||
| CAA | 3600 | ||
| SOA | 3600 | ||
| Mname | hidden-master.yahoo.com | ||
| Rname | hostmaster.yahoo-inc.com | ||
| Serial Number | 2020041500 | ||
| Refresh | 3600 | ||
| Retry | 900 | ||
| Expire | 1814400 | ||
| Minimum TTL | 0 | ||
| MX | 1800 | ||
| TXT | 3600 | ||
| A | 98.136.103.23 | 150 | |
| A | 74.6.136.150 | 150 | |
| A | 212.82.100.150 | 150 | |
| NS | ns1.yahoo.com | 3450 | |
| NS | ns2.yahoo.com | 3450 | |
| NS | ns3.yahoo.com | 3450 |
+ Whois Lookup
- Domain Created:
- 0000-00-00
- Domain Age:
- WhoIs:
+ How socially engaged is yahoo.com.cn?