Yyls.Cc - Info yyls.cc

yyls.cc receives about 408 unique visitors and 408 (1.00 per visitor) page views per day which should earn about $1.67/day from advertising revenue. Estimated site value is $1,215.97. According to Alexa Traffic Rank yyls.cc is ranked number 3,163,908 in the world and 9.0E-6% of global Internet users visit it. Site is hosted in United States and links to network IP address 104.28.0.98. This server supports HTTPS and HTTP/2.

About - yyls.cc


Technologies used on Website

CDN
CloudFlare
Programming Languages
PHP
CMS
WordPress
Blogs
WordPress
JavaScript Libraries
jQuery Migrate
jQuery
Databases
MySQL

yyls.cc Profile

Title: yyls | 每日推播最新最熱門的娛樂情報!
Description: YYLS!線上漫畫| 這裡是蘊藏豐富卡通動漫畫,免費卡通,動漫畫,分享下載與在線上觀看.
Last update was 85 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with yyls.cc in any way. Only publicly available statistics data are displayed.

How popular is yyls.cc?

408 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
408
Monthly Unique Visitors:
9,792
Pages per Visit:
1.00
Daily Pageviews:
408
Alexa Rank:
3,163,908 visit alexa
Alexa Reach:
9.0E-6%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Users%Pageviews%Rank
Taiwan 90.49%--
Hong Kong 2.26%--
Japan 1.76%--
United States 1.65%--
China 1.16%--
Australia 0.74%--
Malaysia 0.46%--
Canada 0.21%--
Macao 0.20%--
Singapore 0.19%--
United Kingdom 0.15%--
Viet Nam 0.11%--
Korea, Republic of 0.08%--
New Zealand 0.06%--
Germany 0.06%--
France 0.05%--
Thailand 0.05%--

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  yyls.cc
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
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

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is yyls.cc?

Facebook:
  1
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
yyls.cc
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:
yyls.cc
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 yyls.cc can earn?

Daily Revenue:
$1.67
Monthly Revenue:
$50.10
Yearly Revenue:
$609.55
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Taiwan 369$0.70
United States 7$0.08
Hong Kong 9$0.03
Japan 7$0.02
Australia 3$0.02
China 5$0.01
Canada 1$0.01
Malaysia 2$0.01
United Kingdom 1$0.00
Singapore 1$0.00
New Zealand 0$0.00
Macao 1$0.00
Germany 0$0.00
France 0$0.00
Korea, Republic of 0$0.00
Thailand 0$0.00
Viet Nam 0$0.00

How much money do yyls.cc lose due to Adblock?

Daily Revenue Loss:
$0.14
Monthly Revenue Loss:
$4.22
Yearly Revenue Loss:
$51.35
Daily Pageviews Blocked:
64
Monthly Pageviews Blocked:
1,906
Yearly Pageviews Blocked:
23,192
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Taiwan 59$0.11
United States 1$0.01
Australia 1$0.00
Hong Kong 1$0.00
China 1$0.00
Canada 0$0.00
Japan 0$0.00
Singapore 0$0.00
United Kingdom 0$0.00
Malaysia 0$0.00
New Zealand 0$0.00
Germany 0$0.00
France 0$0.00
Macao 0$0.00
Thailand 0$0.00
Korea, Republic of 0$0.00
Viet Nam 0$0.00

How much is yyls.cc worth?

Website Value:
$1,215.97

+ Where is yyls.cc hosted?

Server IP:
104.28.0.98
ASN:
AS13335 
ISP:
Cloudflare Inc 
Server Location:

United States, US
 

Other sites hosted on 104.28.0.98

+ How fast does yyls.cc load?

Average Load Time:
(1150 ms) 74 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

97
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

Origin Data

All pages served from this origin have an 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.

Lab Data

Max Potential First Input Delay 20 ms
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 0.8 s
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.
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.
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.8 s
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.7 s
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.
First Meaningful Paint 0.8 s
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 600 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.

URL
SizePotential Savings
http://yyls.cc/cdn-cgi/apps/head/D_vLW92kHxBYmQZuMRSGNvAesdI.js
3 KB70
http://yyls.cc/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70
1 KB110
http://yyls.cc/wp-content/themes/arras-theme-master/css/layouts/2c-r-fixed.css?ver=2011-12-12
1 KB110
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/violet.css?ver=2011-12-12
1 KB110
http://yyls.cc/wp-content/themes/arras-theme-master/user.css?ver=2011-12-12
0 KB110
http://yyls.cc/wp-includes/js/jquery/jquery.js?ver=1.11.0
37 KB230
http://yyls.cc/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
4 KB70
http://yyls.cc/wp-content/themes/arras-theme-master/js/superfish/superfish.js?ver=2011-12-01
2 KB70
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://yyls.cc/
0 ms414 ms5 KB19 KB200text/htmlDocument
http://yyls.cc/cdn-cgi/apps/head/D_vLW92kHxBYmQZuMRSGNvAesdI.js
425 ms468 ms3 KB6 KB200application/javascriptScript
http://yyls.cc/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70
426 ms578 ms1 KB0 KB200text/cssStylesheet
http://yyls.cc/wp-content/themes/arras-theme-master/css/layouts/2c-r-fixed.css?ver=2011-12-12
426 ms677 ms1 KB1 KB200text/cssStylesheet
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/violet.css?ver=2011-12-12
426 ms675 ms1 KB3 KB200text/cssStylesheet
http://yyls.cc/wp-content/themes/arras-theme-master/user.css?ver=2011-12-12
427 ms679 ms0 KB0 KB200text/cssStylesheet
http://yyls.cc/wp-includes/js/jquery/jquery.js?ver=1.11.0
427 ms805 ms37 KB94 KB200application/javascriptScript
http://yyls.cc/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
427 ms683 ms4 KB7 KB200application/javascriptScript
http://yyls.cc/wp-content/themes/arras-theme-master/js/superfish/superfish.js?ver=2011-12-01
427 ms680 ms2 KB4 KB200application/javascriptScript
http://ad.sitemaji.com/ysm_yyls.js
427 ms1279 ms7 KB19 KB200application/javascriptScript
http://yyls.cc/wp-content/uploads/2019/05/IjLiWzgDUy46L3A1-115x115.jpg
428 ms510 ms4 KB4 KB200image/jpegImage
http://yyls.cc/wp-content/uploads/2019/05/TTrqGtx98PJzTPk1-115x115.jpg
428 ms470 ms6 KB5 KB200image/jpegImage
http://yyls.cc/wp-content/uploads/2019/05/BYgQx1p7mFQL1lJ1-115x115.jpg
555 ms597 ms7 KB7 KB200image/jpegImage
http://yyls.cc/wp-includes/js/hoverIntent.min.js?ver=r7
472 ms725 ms1 KB1 KB200application/javascriptScript
http://yyls.cc/wp-content/themes/arras-theme-master/js/jquery.cycle.min.js
511 ms554 ms9 KB27 KB200application/javascriptScript
http://www.google-analytics.com/analytics.js
598 ms601 ms18 KB44 KB200text/javascriptScript
http://www.google-analytics.com/r/collect?v=1&_v=j81&a=590386694&t=pageview&_s=1&dl=http%3A%2F%2Fyyls.cc%2F&ul=en-us&de=UTF-8&dt=yyls%20%7C%20%E6%AF%8F%E6%97%A5%E6%8E%A8%E6%92%AD%E6%9C%80%E6%96%B0%E6%9C%80%E7%86%B1%E9%96%80%E7%9A%84%E5%A8%9B%E6%A8%82%E6%83%85%E5%A0%B1%EF%BC%81&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEAB~&jid=857154436&gjid=2077578199&cid=1926856574.1583844888&tid=UA-49487003-1&_gid=1387365634.1583844888&_r=1&z=2131974403
626 ms629 ms0 KB0 KB200image/gifImage
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/default.css
676 ms757 ms4 KB16 KB200text/cssStylesheet
http://yyls.cc/wp-content/themes/arras-theme-master/css/base.css
759 ms803 ms3 KB9 KB200text/cssStylesheet
http://yyls.cc/wp-content/themes/arras-theme-master/images/searchsubmit.gif
838 ms880 ms1 KB0 KB200image/gifImage
http://yyls.cc/wp-content/themes/arras-theme-master/images/social/rss.png
838 ms897 ms2 KB2 KB200image/pngImage
http://ssl.sitemaji.com/geo/?callback=SD.util.geoCache.callback
1284 ms1681 ms0 KB0 KB200text/plainScript
http://yyls.cc/wp-content/themes/arras-theme-master/images/feed-title-white.jpg
1286 ms1328 ms1 KB0 KB200image/jpegImage
Uses efficient cache policy on static assets - 20 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://www.google-analytics.com/analytics.js
7200000 ms18 KB
http://ad.sitemaji.com/ysm_yyls.js
86400000 ms7 KB
http://ssl.sitemaji.com/geo/?callback=SD.util.geoCache.callback
86400000 ms0 KB
http://yyls.cc/wp-includes/js/jquery/jquery.js?ver=1.11.0
432000000 ms37 KB
http://yyls.cc/wp-content/themes/arras-theme-master/js/jquery.cycle.min.js
432000000 ms9 KB
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/default.css
432000000 ms4 KB
http://yyls.cc/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
432000000 ms4 KB
http://yyls.cc/wp-content/themes/arras-theme-master/css/base.css
432000000 ms3 KB
http://yyls.cc/wp-content/themes/arras-theme-master/js/superfish/superfish.js?ver=2011-12-01
432000000 ms2 KB
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/violet.css?ver=2011-12-12
432000000 ms1 KB
http://yyls.cc/wp-includes/js/hoverIntent.min.js?ver=r7
432000000 ms1 KB
http://yyls.cc/wp-content/themes/arras-theme-master/css/layouts/2c-r-fixed.css?ver=2011-12-12
432000000 ms1 KB
http://yyls.cc/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70
432000000 ms1 KB
http://yyls.cc/wp-content/themes/arras-theme-master/user.css?ver=2011-12-12
432000000 ms0 KB
http://yyls.cc/wp-content/uploads/2019/05/BYgQx1p7mFQL1lJ1-115x115.jpg
2592000000 ms7 KB
http://yyls.cc/wp-content/uploads/2019/05/TTrqGtx98PJzTPk1-115x115.jpg
2592000000 ms6 KB
http://yyls.cc/wp-content/uploads/2019/05/IjLiWzgDUy46L3A1-115x115.jpg
2592000000 ms4 KB
http://yyls.cc/wp-content/themes/arras-theme-master/images/social/rss.png
2592000000 ms2 KB
http://yyls.cc/wp-content/themes/arras-theme-master/images/feed-title-white.jpg
2592000000 ms1 KB
http://yyls.cc/wp-content/themes/arras-theme-master/images/searchsubmit.gif
2592000000 ms1 KB
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. Learn more.

Third-Party
SizeMain-Thread Blocking Time
19 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
434 ms
7 ms
623 ms
20 ms
828 ms
23 ms
851 ms
77 ms
1303 ms
160 ms
1463 ms
40 ms
JavaScript execution time - 0.0 s
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
Other
285 ms3 ms1 ms
http://yyls.cc/wp-includes/js/jquery/jquery.js?ver=1.11.0
50 ms29 ms2 ms
Avoids enormous network payloads - Total size was 116 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://yyls.cc/wp-includes/js/jquery/jquery.js?ver=1.11.0
37 KB
http://www.google-analytics.com/analytics.js
18 KB
http://yyls.cc/wp-content/themes/arras-theme-master/js/jquery.cycle.min.js
9 KB
http://yyls.cc/wp-content/uploads/2019/05/BYgQx1p7mFQL1lJ1-115x115.jpg
7 KB
http://ad.sitemaji.com/ysm_yyls.js
7 KB
http://yyls.cc/wp-content/uploads/2019/05/TTrqGtx98PJzTPk1-115x115.jpg
6 KB
http://yyls.cc/
5 KB
http://yyls.cc/wp-content/uploads/2019/05/IjLiWzgDUy46L3A1-115x115.jpg
4 KB
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/default.css
4 KB
http://yyls.cc/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
4 KB
Minimizes main-thread work - 0.4 s
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
Style & Layout
248 ms
Script Evaluation
59 ms
Other
29 ms
Rendering
13 ms
Script Parsing & Compilation
11 ms
Parse HTML & CSS
11 ms
Avoids an excessive DOM size - 194 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.

Statistic
ElementValue
Total DOM Elements
194
Maximum DOM Depth
11
Maximum Child Elements
18
Keep request counts low and transfer sizes small - 23 requests • 116 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
23116 KB
Script
980 KB
Image
721 KB
Stylesheet
610 KB
Document
15 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
426 KB
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.

Server response times are low (TTFB) - Root document took 420 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
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.

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.

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.

Preconnect to required origins
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.

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.

Defer offscreen images
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.

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.

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.

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. Learn more.

Preload key requests
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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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.


Page Speed (Google PageSpeed Insights) - Mobile

94
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

Origin Data

All pages served from this origin have an 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.

Lab Data

Speed Index 3.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.5 s
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 2.1 s
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.
First Meaningful Paint 2.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
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. Learn more.
Time to Interactive 2.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
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.
First Contentful Paint (3G) 4152.5 ms
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 60 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 116 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://yyls.cc/wp-includes/js/jquery/jquery.js?ver=1.11.0
37 KB
http://www.google-analytics.com/analytics.js
18 KB
http://yyls.cc/wp-content/themes/arras-theme-master/js/jquery.cycle.min.js
9 KB
http://yyls.cc/wp-content/uploads/2019/05/BYgQx1p7mFQL1lJ1-115x115.jpg
7 KB
http://ad.sitemaji.com/ysm_yyls.js
7 KB
http://yyls.cc/wp-content/uploads/2019/05/TTrqGtx98PJzTPk1-115x115.jpg
6 KB
http://yyls.cc/
5 KB
http://yyls.cc/wp-content/uploads/2019/05/IjLiWzgDUy46L3A1-115x115.jpg
4 KB
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/default.css
4 KB
http://yyls.cc/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
4 KB
Minimizes main-thread work - 1.6 s
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
Style & Layout
1061 ms
Script Evaluation
279 ms
Other
149 ms
Script Parsing & Compilation
49 ms
Parse HTML & CSS
47 ms
Rendering
46 ms
Avoids an excessive DOM size - 194 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.

Statistic
ElementValue
Total DOM Elements
194
Maximum DOM Depth
11
Maximum Child Elements
18
Keep request counts low and transfer sizes small - 23 requests • 116 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
23116 KB
Script
980 KB
Image
721 KB
Stylesheet
610 KB
Document
15 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
426 KB
Eliminate render-blocking resources - Potential savings of 1,590 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.

URL
SizePotential Savings
http://yyls.cc/cdn-cgi/apps/head/D_vLW92kHxBYmQZuMRSGNvAesdI.js
3 KB180
http://yyls.cc/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70
1 KB330
http://yyls.cc/wp-content/themes/arras-theme-master/css/layouts/2c-r-fixed.css?ver=2011-12-12
1 KB330
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/violet.css?ver=2011-12-12
1 KB330
http://yyls.cc/wp-content/themes/arras-theme-master/user.css?ver=2011-12-12
0 KB330
http://yyls.cc/wp-includes/js/jquery/jquery.js?ver=1.11.0
37 KB930
http://yyls.cc/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
4 KB180
http://yyls.cc/wp-content/themes/arras-theme-master/js/superfish/superfish.js?ver=2011-12-01
2 KB180
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://yyls.cc/
0 ms354 ms5 KB19 KB200text/htmlDocument
http://yyls.cc/cdn-cgi/apps/head/D_vLW92kHxBYmQZuMRSGNvAesdI.js
368 ms412 ms3 KB6 KB200application/javascriptScript
http://yyls.cc/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70
368 ms704 ms1 KB0 KB200text/cssStylesheet
http://yyls.cc/wp-content/themes/arras-theme-master/css/layouts/2c-r-fixed.css?ver=2011-12-12
368 ms648 ms1 KB1 KB200text/cssStylesheet
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/violet.css?ver=2011-12-12
368 ms629 ms1 KB3 KB200text/cssStylesheet
http://yyls.cc/wp-content/themes/arras-theme-master/user.css?ver=2011-12-12
369 ms706 ms0 KB0 KB200text/cssStylesheet
http://yyls.cc/wp-includes/js/jquery/jquery.js?ver=1.11.0
369 ms631 ms37 KB94 KB200application/javascriptScript
http://yyls.cc/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
369 ms624 ms4 KB7 KB200application/javascriptScript
http://yyls.cc/wp-content/themes/arras-theme-master/js/superfish/superfish.js?ver=2011-12-01
369 ms618 ms2 KB4 KB200application/javascriptScript
http://ad.sitemaji.com/ysm_yyls.js
370 ms1235 ms7 KB19 KB200application/javascriptScript
http://yyls.cc/wp-content/uploads/2019/05/IjLiWzgDUy46L3A1-115x115.jpg
370 ms482 ms4 KB4 KB200image/jpegImage
http://yyls.cc/wp-content/uploads/2019/05/TTrqGtx98PJzTPk1-115x115.jpg
370 ms420 ms6 KB5 KB200image/jpegImage
http://yyls.cc/wp-content/uploads/2019/05/BYgQx1p7mFQL1lJ1-115x115.jpg
531 ms574 ms7 KB7 KB200image/jpegImage
http://yyls.cc/wp-includes/js/hoverIntent.min.js?ver=r7
422 ms567 ms1 KB1 KB200application/javascriptScript
http://yyls.cc/wp-content/themes/arras-theme-master/js/jquery.cycle.min.js
483 ms529 ms9 KB27 KB200application/javascriptScript
http://www.google-analytics.com/analytics.js
569 ms573 ms18 KB44 KB200text/javascriptScript
http://www.google-analytics.com/r/collect?v=1&_v=j81&a=2059955906&t=pageview&_s=1&dl=http%3A%2F%2Fyyls.cc%2F&ul=en-us&de=UTF-8&dt=yyls%20%7C%20%E6%AF%8F%E6%97%A5%E6%8E%A8%E6%92%AD%E6%9C%80%E6%96%B0%E6%9C%80%E7%86%B1%E9%96%80%E7%9A%84%E5%A8%9B%E6%A8%82%E6%83%85%E5%A0%B1%EF%BC%81&sd=24-bit&sr=412x660&vp=1000x1601&je=0&_u=IEBAAEAB~&jid=583838377&gjid=177540773&cid=495281679.1583844881&tid=UA-49487003-1&_gid=104797587.1583844881&_r=1&z=1371789278
603 ms610 ms0 KB0 KB200image/gifImage
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/default.css
630 ms679 ms4 KB16 KB200text/cssStylesheet
http://yyls.cc/wp-content/themes/arras-theme-master/css/base.css
680 ms726 ms3 KB9 KB200text/cssStylesheet
http://yyls.cc/wp-content/themes/arras-theme-master/images/searchsubmit.gif
761 ms804 ms1 KB0 KB200image/gifImage
http://yyls.cc/wp-content/themes/arras-theme-master/images/social/rss.png
762 ms805 ms2 KB2 KB200image/pngImage
http://ssl.sitemaji.com/geo/?callback=SD.util.geoCache.callback
1241 ms1668 ms0 KB0 KB200text/plainScript
http://yyls.cc/wp-content/themes/arras-theme-master/images/feed-title-white.jpg
1244 ms1292 ms1 KB0 KB200image/jpegImage
Uses efficient cache policy on static assets - 20 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://www.google-analytics.com/analytics.js
7200000 ms18 KB
http://ad.sitemaji.com/ysm_yyls.js
86400000 ms7 KB
http://ssl.sitemaji.com/geo/?callback=SD.util.geoCache.callback
86400000 ms0 KB
http://yyls.cc/wp-includes/js/jquery/jquery.js?ver=1.11.0
432000000 ms37 KB
http://yyls.cc/wp-content/themes/arras-theme-master/js/jquery.cycle.min.js
432000000 ms9 KB
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/default.css
432000000 ms4 KB
http://yyls.cc/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
432000000 ms4 KB
http://yyls.cc/wp-content/themes/arras-theme-master/css/base.css
432000000 ms3 KB
http://yyls.cc/wp-content/themes/arras-theme-master/js/superfish/superfish.js?ver=2011-12-01
432000000 ms2 KB
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/violet.css?ver=2011-12-12
432000000 ms1 KB
http://yyls.cc/wp-includes/js/hoverIntent.min.js?ver=r7
432000000 ms1 KB
http://yyls.cc/wp-content/themes/arras-theme-master/css/layouts/2c-r-fixed.css?ver=2011-12-12
432000000 ms1 KB
http://yyls.cc/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70
432000000 ms1 KB
http://yyls.cc/wp-content/themes/arras-theme-master/user.css?ver=2011-12-12
432000000 ms0 KB
http://yyls.cc/wp-content/uploads/2019/05/BYgQx1p7mFQL1lJ1-115x115.jpg
2592000000 ms7 KB
http://yyls.cc/wp-content/uploads/2019/05/TTrqGtx98PJzTPk1-115x115.jpg
2592000000 ms6 KB
http://yyls.cc/wp-content/uploads/2019/05/IjLiWzgDUy46L3A1-115x115.jpg
2592000000 ms4 KB
http://yyls.cc/wp-content/themes/arras-theme-master/images/social/rss.png
2592000000 ms2 KB
http://yyls.cc/wp-content/themes/arras-theme-master/images/feed-title-white.jpg
2592000000 ms1 KB
http://yyls.cc/wp-content/themes/arras-theme-master/images/searchsubmit.gif
2592000000 ms1 KB
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
SizeMain-Thread Blocking Time
19 KB41 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
380 ms
7 ms
600 ms
26 ms
750 ms
29 ms
779 ms
93 ms
1259 ms
5 ms
1264 ms
174 ms
1438 ms
29 ms
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. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
1285 ms13 ms4 ms
http://yyls.cc/wp-includes/js/jquery/jquery.js?ver=1.11.0
179 ms137 ms7 ms
http://www.google-analytics.com/analytics.js
101 ms95 ms6 ms
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.

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.

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. Learn more.

Preload key requests
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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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.

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.

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. Learn more.

Enable text compression
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.

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.

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.

Preconnect to required origins
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.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. 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.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

每日推播最新最熱門的娛樂情報! renders only 4 pixels tall (11 CSS pixels) .
時尚 and 9 others render only 5 pixels tall (14 CSS pixels) .
推薦文章 and 1 others render only 5 pixels tall (14 CSS pixels) .
做自媒體的第六天,居然就看到收益了?廢話不多說直接上圖 and 2 others render only 6 pixels tall (16 CSS pixels) .
裙裝在女孩子中的受歡迎度到底…日時節簡直是到了人手 […] and 2 others render only 4 pixels tall (12 CSS pixels) .
Continue Reading... and 2 others render only 4 pixels tall (12 CSS pixels) .
汽車 and 17 others render only 4 pixels tall (11 CSS pixels) .
當年紅極一時的油改氣,如今什麼不見了?計程車司機說出了大實話 and 17 others render only 4 pixels tall (12 CSS pixels) .
第 1 頁,共 81 頁 renders only 4 pixels tall (12 CSS pixels) .
1 renders only 4 pixels tall (12 CSS pixels) .
最後一頁 » and 8 others render only 4 pixels tall (12 CSS pixels) .
... and 1 others render only 4 pixels tall (12 CSS pixels) .
About Arras WordPress Theme renders only 4 pixels tall (11 CSS pixels) .
Copyright yyls…ghts Reserved. renders only 4 pixels tall (11 CSS pixels) .

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:

http://yyls.cc/cdn-cgi/apps/head/D_vLW92kHxBYmQZuMRSGNvAesdI.js
http://yyls.cc/wp-includes/js/jquery/jquery.js?ver=1.11.0
http://yyls.cc/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
http://yyls.cc/wp-content/themes/arras-theme-master/js/superfish/superfish.js?ver=2011-12-01
http://ad.sitemaji.com/ysm_yyls.js
Optimize CSS Delivery of the following:

http://yyls.cc/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70
http://yyls.cc/wp-content/themes/arras-theme-master/css/layouts/2c-r-fixed.css?ver=2011-12-12
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/violet.css?ver=2011-12-12
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/default.css
http://yyls.cc/wp-content/themes/arras-theme-master/css/base.css
http://yyls.cc/wp-content/themes/arras-theme-master/user.css?ver=2011-12-12

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 <input type="submit" class="searchsubmit"> is close to 1 other tap targets .
The tap target <a href="http://yyls.cc/?cat=2">時尚</a> and 9 others are close to other tap targets .
The tap target <a href="http://yyls.cc/?p=1486">下一代本田思域Type R可能將採用混合動力</a> and 17 others are close to other tap targets .
The tap target <a href="http://yyls.cc/?paged=2" class="page larger">2</a> and 7 others are close to other tap targets .

Configure the viewport

Your page specifies a fixed-width desktop viewport. Use a responsive viewport to allow your page to render properly on all devices.

Configuring a viewport specifying width=device-width instead of width=1000 will allow your page to adapt for devices of various widths. This may require additional work to adapt your styling for smaller screens.

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://www.google-***ytics.com/***ytics.js (2 hours)
http://yyls.cc/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70 (5 days)
http://yyls.cc/wp-content/themes/arras-theme-master/css/base.css (5 days)
http://yyls.cc/wp-content/themes/arras-theme-master/css/layouts/2c-r-fixed.css?ver=2011-12-12 (5 days)
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/default.css (5 days)
http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/violet.css?ver=2011-12-12 (5 days)
http://yyls.cc/wp-content/themes/arras-theme-master/js/jquery.cycle.min.js (5 days)
http://yyls.cc/wp-content/themes/arras-theme-master/js/superfish/superfish.js?ver=2011-12-01 (5 days)
http://yyls.cc/wp-content/themes/arras-theme-master/user.css?ver=2011-12-12 (5 days)
http://yyls.cc/wp-includes/js/hoverIntent.min.js?ver=r7 (5 days)
http://yyls.cc/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1 (5 days)
http://yyls.cc/wp-includes/js/jquery/jquery.js?ver=1.11.0 (5 days)

Reduce server response time

In our test, your server responded in 0.37 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 4.1KiB (24% reduction).

Compressing http://yyls.cc/wp-content/uploads/2019/05/BYgQx1p7mFQL1lJ1-115x115.jpg could save 1.2KiB (18% reduction).
Compressing http://yyls.cc/wp-content/themes/arras-theme-master/images/social/rss.png could save 1.2KiB (62% reduction).
Compressing http://yyls.cc/wp-content/uploads/2019/05/TTrqGtx98PJzTPk1-115x115.jpg could save 1KiB (20% reduction).
Compressing http://yyls.cc/wp-content/uploads/2019/05/IjLiWzgDUy46L3A1-115x115.jpg could save 784B (21% reduction).

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 580B (15% reduction).

Minifying http://yyls.cc/wp-content/themes/arras-theme-master/css/base.css could save 321B (12% reduction) after compression.
Minifying http://yyls.cc/wp-content/themes/arras-theme-master/css/styles/violet.css?ver=2011-12-12 could save 147B (17% reduction) after compression.
Minifying http://yyls.cc/wp-content/themes/arras-theme-master/css/layouts/2c-r-fixed.css?ver=2011-12-12 could save 112B (34% reduction) after compression.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 3***B (25% reduction).

Minifying http://yyls.cc/wp-content/themes/arras-theme-master/js/superfish/superfish.js?ver=2011-12-01 could save 3***B (25% reduction) after compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
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.
Enable compression
You have compression enabled. Learn more about enabling compression.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
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.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does yyls.cc use compression?

yyls.cc use gzip compression.
Original size: 18.99 KB
Compressed size: 4.84 KB
File reduced by: 14.15 KB (74%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

yyls.cc supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: sni.cloudflaressl.com
Organization:
Location:
Issuer: CloudFlare Inc ECC CA-2
Valid from: Jan 29 00:00:00 2020 GMT
Valid until: Oct 9 12:00:00 2020 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

yyls.cc supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Tue, 10 Mar 2020 12:54:32 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: __cfduid=d20d9096a1986a78bf86fd2fdbeeef5791583844871; expires=Thu, 09-Apr-20 12:54:31 GMT; path=/; domain=.yyls.cc; HttpOnly; SameSite=Lax
Vary: Accept-Encoding
X-Powered-By: PHP/5.6.40
X-Pingback: http://yyls.cc/xmlrpc.php
CF-Cache-Status: DYNAMIC
Server: cloudflare
CF-RAY: 571d2f500c58c64f-MSP
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
HINFO 3600
A 104.28.1.98 277
A 104.28.0.98 277
NS beth.ns.cloudflare.com 3577
NS walt.ns.cloudflare.com 3577

+ Whois Lookup

Domain Created:
2013-12-01
Domain Age:
6 years 3 months 9 days  
WhoIs:
 

whois lookup at whois.godaddy.com...
Domain Name: yyls.cc
Registry Domain ID: 108497959_DOMAIN_CC-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2019-12-02T10:47:53Z
Creation Date: 2013-12-01T01:05:57Z
Registrar Registration Expiration Date: 2020-12-01T01:05:57Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited http://www.icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 14455 N. Hayden Road
Registrant City: Scottsdale
Registrant State/Province: Arizona
Registrant Postal Code: 85260
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: +1.4806242598
Registrant Fax Ext:
Registrant Email: email
Registry Admin ID: Not Available From Registry
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin Street: 14455 N. Hayden Road
Admin City: Scottsdale
Admin State/Province: Arizona
Admin Postal Code: 85260
Admin Country: US
Admin Phone: +1.4806242599
Admin Phone Ext:
Admin Fax: +1.4806242598
Admin Fax Ext:
Admin Email: email
Registry Tech ID: Not Available From Registry
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 14455 N. Hayden Road
Tech City: Scottsdale
Tech State/Province: Arizona
Tech Postal Code: 85260
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: +1.4806242598
Tech Fax Ext:
Tech Email: email
Name Server: BETH.NS.CLOUDFLARE.COM
Name Server: WALT.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2020-03-10T12:00:00Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

Notes:

IMPORTANT: Port43 will provide the ICANN-required minimum data set per
ICANN Temporary Specification, adopted 17 May 2018.
Visit https://whois.godaddy.com to look up contact data for domains
not covered by GDPR policy.

The data contained in GoDaddy.com, LLC's WhoIs database,
while believed by the company to be reliable, is provided "as is"
with no guarantee or warranties regarding its accuracy. This
information is provided for the sole purpose of assisting you
in obtaining information about domain name registration records.
Any use of this data for any other purpose is expressly forbidden without the prior written
permission of GoDaddy.com, LLC. By submitting an inquiry,
you agree to these terms of usage and limitations of warranty. In particular,
you agree not to use this data to allow, enable, or otherwise make possible,
dissemination or collection of this data, in part or in its entirety, for any
purpose, such as the transmission of unsolicited advertising and
and solicitations of any kind, including spam. You further agree
not to use this data to enable high volume, automated or robotic electronic
processes designed to collect or compile this data for any purpose,
including mining this data for your own personal or commercial purposes.

Please note: the registrant of the domain name is specified
in the "registrant" section. In most cases, GoDaddy.com, LLC
is not the registrant of domain names listed in this database.
whois lookup at whois.nic.cc...
Domain Name: YYLS.CC
Registry Domain ID: 108497959_DOMAIN_CC-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2019-12-02T15:48:01Z
Creation Date: 2013-12-01T06:05:57Z
Registry Expiry Date: 2020-12-01T06:05:57Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: 480-624-2505
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: BETH.NS.CLOUDFLARE.COM
Name Server: WALT.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2020-03-10T12:54:37Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the
expiration date of the domain name registrant's agreement with the
sponsoring registrar. Users may consult the sponsoring registrar's
Whois database to view the registrar's reported date of expiration
for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign's ("VeriSign") Whois
database is provided by VeriSign for information purposes only, and to
assist persons in obtaining information about or related to a domain name
registration record. VeriSign does not guarantee its accuracy.
By submitting a Whois query, you agree to abide by the following terms of
use: You agree that you may use this Data only for lawful purposes and that
under no cir***stances will you use this Data to: (1) allow, enable, or
otherwise support the transmission of mass unsolicited, commercial
advertising or solicitations via e-mail, telephone, or facsimile; or
(2) enable high volume, automated, electronic processes that apply to
VeriSign (or its computer systems). The compilation, repackaging,
dissemination or other use of this Data is expressly prohibited without
the prior written consent of VeriSign. You agree not to use electronic
processes that are automated and high-volume to access or query the
Whois database except as reasonably necessary to register domain names
or modify existing registrations. VeriSign reserves the right to restrict
your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.
Last update was 85 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with yyls.cc in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

dummydonald.com
26 secs
dohop.pl
38 secs
dumcjnews.com
1 min
uploadhaven.com
1 min
dociran.com
1 min
duir.ac.bd
2 mins
docemassagem.com
2 mins
niagarafallsreview.ca
3 mins
do-88.com
3 mins
duiofjs-deactivated20130210.tumblr.com
3 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
yyls.cc widget