Creaders.Net - Info receives about 121,146 unique visitors and 848,021 (7.00 per visitor) page views per day which should earn about $7,129.85/day from advertising revenue. Estimated site value is $4,289,964.02. According to Alexa Traffic Rank is ranked number 3,085 in the world and 0.00714% of global Internet users visit it. Site is hosted in Seattle, Washington, 98111, United States and links to network IP address This server doesn't support HTTPS and doesn't support HTTP/2.

About -

领先海外的中文网站,全球华人的网络精神家园。Founded in 1998, is one of the largest overseas Chinese portals across North America, Europe,Australia, and South East Asia. engages millions of Internet users every month. As a continuously growing business for nearly two decades, has been providing Chinese communities around the world with breaking news, latest headlines, and a variety of column articles as well as over a hundred-thousand blogs with rich content yearly.
Edit Site Info

Technologies used on Website

Web Servers
Programming Languages
PHP Profile

Title: 万维读者网 -- Creaders.NET,
Keywords: 万维,万维读者,Creaders,bbsland,Chinese website,海外中文网,美国中文网,美国中文网站,加拿大中文网,新闻,博客,论坛,温哥华,多伦多,纽约,洛杉矶,旧金山,芝加哥,休斯顿,华盛顿,中国,移民,留学,华人,Chinese, immigrant, USA, Canada, Vancouver, Toronto, SanFanciso, LosAngela, New York, life, friends, friendship,international friendship, job, tourism, study, university, school,language,education
Last update was 3 days ago
This can take up to 60 seconds. Please wait...

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

How popular is

121.1K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
3,085 visit alexa
Alexa Reach:
0.00714%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources


Visitors by country

United States 39.89%48.79%1201
Canada 17.50%22.98%285
Hong Kong 12.00%4.74%228
Singapore 4.99%2.89%351
Australia 4.27%4.26%906
Taiwan 3.87%0.85%1769
Japan 3.08%3.14%7710
China 1.94%1.76%9144
Malaysia 1.91%0.42%1319
United Kingdom 1.74%1.70%3583
Germany 1.48%1.40%7513
New Zealand 1.10%1.12%361
Netherlands 0.66%0.63%4013
France 0.65%0.55%11471
Norway 0.49%0.24%2554
Spain 0.44%0.26%12311
Italy 0.42%0.24%15818
Sweden 0.41%0.52%3110
Korea, Republic of 0.36%0.21%16660
Russian Federation 0.30%0.23%30318
Macao 0.22%0.18%1017
Thailand 0.21%0.13%7628
Switzerland 0.19%0.22%11196
Viet Nam 0.17%0.08%15864
Austria 0.15%0.15%14614
Finland 0.14%0.16%7469
Philippines 0.13%0.06%10851
Belgium 0.12%0.15%13228
Denmark 0.12%0.14%5939
Indonesia 0.11%0.07%24687
India 0.10%0.09%187257
Ireland 0.10%0.07%12967
Cambodia 0.10%0.05%3651
Brazil 0.08%0.08%84904
Hungary 0.08%0.07%11459
United Arab Emirates 0.08%0.05%14374
Czech Republic 0.06%0.06%25570
South Africa 0.06%0.06%24851
Myanmar 0.06%0.03%11910
Saudi Arabia 0.06%0.06%26435
Poland 0.06%0.05%50582
Portugal 0.05%0.03%16120

Where do visitors go on this site?


Competitive Data

(Rank based on keywords, cost and organic traffic)
Organic Keywords:
(Number of keywords in top 20 Google SERP)
Organic Traffic:
(Number of visitors coming from top 20 search results)
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

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

Desktop summary

Root domain:
Last Change Time:
(The last time that the site changed status.)
2019-01-24 04:29:52
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)

Mobile summary

Last Change Time:
(The last time that the site changed status.)
2019-01-24 04:29:53
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)

+ Abusive Experience Report

Root domain:
Last Change Time:
(The last time that the site changed status.)
2019-01-24 04:29:53
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

United States 413,749$4,745.71
Canada 194,875$1,366.08
Australia 36,126$272.03
Hong Kong 40,196$138.68
United Kingdom 14,416$89.81
Japan 26,628$85.21
Singapore 24,508$73.28
New Zealand 9,498$71.33
Germany 11,872$57.34
China 14,925$46.12
Netherlands 5,343$27.19
Sweden 4,410$23.46
France 4,664$21.92
Taiwan 7,208$13.70
Switzerland 1,866$11.32
Malaysia 3,562$10.79
Norway 2,035$10.79
Finland 1,357$9.84
Italy 2,035$7.10
Belgium 1,272$6.27
Denmark 1,187$4.56
Austria 1,272$4.13
Korea, Republic of 1,781$4.13
Russian Federation 1,950$3.96
Macao 1,526$3.25
Ireland 594$2.94
Thailand 1,102$2.76
Spain 2,205$2.45
South Africa 509$2.24
United Arab Emirates 424$1.59
Hungary 594$1.23
India 763$1.22
Brazil 678$1.20
Czech Republic 509$1.10
Saudi Arabia 509$1.03
Philippines 509$0.82
Poland 424$0.77
Indonesia 594$0.73
Portugal 254$0.55
Viet Nam 678$0.50
Myanmar 254$0.37
Cambodia 424$0.34

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
United States 74,475$854.23
Canada 48,719$341.52
Australia 7,225$54.41
Singapore 7,107$21.25
New Zealand 2,279$17.12
Germany 3,443$16.63
United Kingdom 2,307$14.37
Hong Kong 4,020$13.87
Sweden 1,235$6.57
China 1,940$6.00
Netherlands 908$4.62
Japan 799$2.56
France 513$2.41
Finland 312$2.26
Taiwan 1,153$2.19
Norway 407$2.16
Switzerland 336$2.04
Italy 346$1.21
Ireland 232$1.15
Denmark 297$1.14
Austria 331$1.07
Malaysia 285$0.86
Belgium 153$0.75
Spain 419$0.47
Indonesia 344$0.42
India 214$0.34
Hungary 154$0.32
Poland 140$0.25
Russian Federation 117$0.24
United Arab Emirates 59$0.22
Saudi Arabia 107$0.22
Thailand 66$0.17
Korea, Republic of 71$0.17
Portugal 53$0.12
Czech Republic 51$0.11
Brazil 41$0.07
Macao 31$0.07
Philippines 36$0.06
South Africa 10$0.04
Cambodia 34$0.03
Viet Nam 27$0.02
Myanmar 5$0.01

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
SoftLayer Technologies Inc. 
Server Location:
Washington, WA
United States, US

Other sites hosted on

+ How fast does load?

Average Load Time:
(1579 ms) 58 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

Currently Not Available

Page Speed (Google PageSpeed Insights) - Mobile

0-49 50-89 90-100 i

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.8s % of loads for this page have a fast (<1s) First Contentful Paint (FCP) 71% 22% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 22% 5% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 5%
First Input Delay (FID)106ms 87% of loads for this page have a fast (<50ms) First Input Delay (FID) 87% 11% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 11% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

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)2.1s 59% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 59% 32% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 32% 7% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 7%
First Input Delay (FID)129ms % of loads for this page have a fast (<50ms) First Input Delay (FID) 86% 11% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 11% 1% of loads for this page have a slow (>250ms) First Input Delay (FID) 1%

Lab Data

Max Potential First Input Delay 160 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 5.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 430 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 1621 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Estimated Input Latency 60 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 3.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 5.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 0.9 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.9 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.

Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms247 ms0 KB0 KB302text/html
248 ms405 ms3 KB8 KB200text/htmlDocument
419 ms572 ms6 KB12 KB200application/x-javascriptScript
427 ms433 ms14 KB44 KB200text/javascriptScript
432 ms513 ms2 KB4 KB200text/javascriptScript
435 ms597 ms5 KB5 KB200image/pngImage
565 ms649 ms1 KB0 KB200image/gifImage
566 ms585 ms0 KB0 KB302
578 ms587 ms1 KB0 KB200application/javascriptScript
579 ms589 ms58 KB156 KB200text/javascriptScript
583 ms622 ms0 KB0 KB301text/html
584 ms588 ms17 KB45 KB200text/javascriptScript
585 ms860 ms0 KB0 KB200text/plainImage
619 ms696 ms0 KB0 KB302text/html
622 ms639 ms0 KB0 KB200application/x-javascriptScript
684 ms735 ms12 KB23 KB200text/plainXHR
693 ms702 ms24 KB62 KB200text/javascriptScript
694 ms698 ms4 KB0 KB200text/htmlOther
696 ms701 ms1 KB0 KB200image/gifImage;r=2131882012;rf=0;a=p-e4UytPLDQQKlw;;fpan=1;fpa=P0-616601920-1569615021422;ns=0;ce=1;qjs=1;qv=4c19192-20180628134937;cm=;ref=;je=0;sr=412x660x24;enc=n;dst=1;et=1569615021422;tzo=420;ogl=
704 ms847 ms0 KB0 KB200image/gifImage
770 ms1669 ms1 KB0 KB200image/gifFetch
775 ms782 ms41 KB119 KB200text/javascriptScript
776 ms781 ms15 KB41 KB200text/javascriptScript
776 ms783 ms30 KB78 KB200text/javascriptScript
783 ms789 ms29 KB77 KB200text/javascriptScript
821 ms829 ms29 KB80 KB200text/javascriptScript
829 ms842 ms14 KB51 KB200text/htmlDocument
850 ms850 ms0 KB0 KB200image/pngImage
862 ms870 ms9 KB22 KB200text/htmlDocument
928 ms949 ms1 KB0 KB200text/cssStylesheet
939 ms956 ms6 KB12 KB200text/javascriptScript
964 ms1060 ms2 KB2 KB200font/woff2Font
1109 ms1114 ms6 KB14 KB200image/svg+xmlImage
1110 ms1114 ms2 KB3 KB200image/svg+xmlImage
1110 ms1116 ms16 KB52 KB200image/svg+xmlImage
1110 ms1189 ms19 KB18 KB200image/jpegImage
1111 ms1117 ms3 KB5 KB200image/svg+xmlImage
1111 ms1143 ms17 KB17 KB200image/jpegImage
1111 ms1118 ms16 KB16 KB200image/jpegImage!KCulKzNYFK9BJ7vpb58CAAAAcFIAAAArmQFzXeVETAch50IZneegW_1RSmyO0uAJjq61gvcwsaZ2RkjKbJTWUNq_3SKRr-x2AATRvToo_HcN1aFtNgXLxltDxhM0DDD1Mrf0dyCXhb1mFL97gmDeH7TrbwQhh_tucdoPRF1nNz1UoABvD_XJVVPavKlEqmSgHJiy_dcUAhWii41hGvw582yAMmlntPuQM9MVANytjfodZMC2zVYXMsxD8O7FWfrqEwvluJ26w8whJ8EHszxE7TxwkbXj8hrvlb5H74Tu99s3zlon6ADBUPubS-3_ErRxBM2I90cVIYziVsKG9sI7J4dQdbcruKV0jkS0K-u37NwvMxt_HKPVoZ1KkqzlTR5rIQVXhPIGAKHvwmuYDP_cflLi5TXMnvhevuk5JhrmK1DWDEUjqbEpLOGsYOOuKEAZwXk1LIrPMkXp3Sa4gU06Pc7-SePNBp2zV2ZAwmE1i9JiMbwFuNMa2aDrd7PVofIEJi8eAPNgJmSlYyq2s9k
1133 ms1162 ms0 KB0 KB204image/gifImage,1073,1073,1073,1073&tos=1073,0,0,0,0&p=372,56,622,356&mcvt=1073&rs=3&ht=0&tfs=140&tls=1213&mc=1<e=1&bas=0&bac=0&met=no&avms=nio&niot_obs=20&niot_cbk=53&md=2&lm=2&rst=1569615021496&rpt=173&isd=0&msd=0&oseid=3&xdi=0&ps=412%2C660&ss=412%2C660&pt=323&bin=1&deb=1-1-1-6-12-32-21-11-0-0-0&tvt=1192&r=v&id=osdim&vs=4&za&uc=12&upc=1&tgt=DIV&cl=1&lop=1&tslp=896&cec=2&clc=2&cac=1&cd=0x0&itpl=19&v=20190923
2094 ms2107 ms0 KB0 KB200image/gifImage,1073,1073,1073,1073&tos=1073,0,0,0,0&p=372,56,622,356&mcvt=1073&rs=3&ht=0&tfs=140&tls=1213&mc=1<e=1&bas=0&bac=0&met=no&avms=nio&niot_obs=20&niot_cbk=53&md=2&lm=2&rst=1569615021496&rpt=173&isd=0&msd=0&oseid=3&xdi=0&ps=412%2C660&ss=412%2C660&pt=323&bin=1&deb=1-1-1-6-12-32-21-11-0-0-0&tvt=1192&r=v&id=osdim&vs=4&za&uc=12&upc=1&tgt=DIV&cl=1&lop=1&tslp=898&cec=2&clc=2&cac=1&cd=0x0&itpl=19&v=20190923
2094 ms2107 ms0 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 12 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
0 ms5 KB
0 ms1 KB
7200000 ms17 KB
86400000 ms41 KB
86400000 ms19 KB
86400000 ms17 KB
86400000 ms16 KB
86400000 ms16 KB
86400000 ms6 KB
86400000 ms3 KB
86400000 ms2 KB
86400000 ms0 KB
Third-Party Usage - 5 Third-Parties Found
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.

SizeMain Thread Time
369 KB1321 ms
2 KB32 ms
7 KB24 ms
18 KB13 ms
0 KB0 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
429 ms
9 ms
439 ms
15 ms
455 ms
119 ms
579 ms
9 ms
588 ms
13 ms
613 ms
28 ms
644 ms
74 ms
757 ms
49 ms
810 ms
41 ms
852 ms
20 ms
874 ms
8 ms
891 ms
36 ms
937 ms
10 ms
952 ms
5 ms
975 ms
11 ms
988 ms
30 ms
1019 ms
12 ms
1041 ms
5 ms
1051 ms
12 ms
1063 ms
15 ms
1078 ms
14 ms
1093 ms
13 ms
1109 ms
24 ms
1133 ms
8 ms
1144 ms
12 ms
1156 ms
33 ms
1204 ms
8 ms
2110 ms
7 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
96 ms
Reduce JavaScript execution time - 1.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Total CPU TimeScript EvaluationScript Parse
1737 ms537 ms8 ms
484 ms437 ms23 ms
238 ms225 ms12 ms
197 ms159 ms38 ms
176 ms166 ms5 ms
133 ms78 ms18 ms
75 ms65 ms10 ms
54 ms43 ms10 ms
51 ms46 ms6 ms
Avoids enormous network payloads - Total size was 409 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

58 KB
41 KB
30 KB
29 KB
29 KB
24 KB
19 KB
17 KB
17 KB
16 KB
Minimize main-thread work - 3.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Time Spent
Script Evaluation
1880 ms
Style & Layout
586 ms
518 ms
Script Parsing & Compilation
163 ms
102 ms
Parse HTML & CSS
54 ms
Serve images in next-gen formats - Potential savings of 27 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. Learn more.

SizePotential Savings
18 KB9 KB
17 KB9 KB
16 KB8 KB
Avoids an excessive DOM size - 31 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
Keep request counts low and transfer sizes small - 42 requests • 409 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
42409 KB
14274 KB
1688 KB
326 KB
719 KB
12 KB
11 KB
00 KB
39400 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 160 ms
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.

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.

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.

Minimize Critical Requests Depth - 2 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.

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

Suggestions Summary

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: (expiration not specified) (15 minutes) (50 minutes) (50 minutes) (50 minutes)*** (2 hours)

Optimize images

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

Optimize the following images to reduce their size by 18.6KiB (37% reduction).

Compressing***354260087/2019_DOM_INTL_SM_FallTactical_POSUS_300x250_20190915_6274/bg-Tokyo-300x250.jpg? could save 6.7KiB (37% reduction).
Compressing***354260087/2019_DOM_INTL_SM_FallTactical_POSUS_300x250_20190915_6274/bg-Shanghai-300x250.jpg? could save 6.3KiB (37% reduction).
Compressing***354260087/2019_DOM_INTL_SM_FallTactical_POSUS_300x250_20190915_6274/bg-Seoul-300x250.jpg? could save 5.6KiB (36% reduction).
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.
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.
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.
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.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
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 use compression? use gzip compression.
Original size: 137.78 KB
Compressed size: 25.61 KB
File reduced by: 112.17 KB (81%)

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify does not support HTTPS
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support does not support HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)


+ Http Header

Date: Thu, 12 Dec 2019 02:03:02 GMT
Server: Apache
X-Powered-By: PHP/5.3.3
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Cache-Control: no-cache, must-revaildate
Pragma: no-cache
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 26220
Connection: close
Content-Type: text/html

+ DNS Lookup

Type Ip Target TTL
TXT 3598
MX 3598
MX 3598
MX 3598
MX 3598
MX 3598
MX 3598
MX 3598
SOA 898
Serial Number 1
Refresh 7200
Retry 900
Expire 1209600
Minimum TTL 0
A 3598
NS 3598
NS 3598
NS 3598
NS 3598

+ Whois Lookup

Domain Created:
Domain Age:
21 years 8 months 11 days  

whois lookup at
IP Address Has Reached Rate Limit
whois lookup at
Registry Domain ID: 3572602_DOMAIN_NET-VRSN
Registrar WHOIS Server:
Registrar URL:
Updated Date: 2019-08-07T23:55:57Z
Creation Date: 1998-03-31T05:00:00Z
Registry Expiry Date: 2022-03-30T04:00:00Z
Registrar: Network Solutions, LLC
Registrar IANA ID: 2
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.8003337680
Domain Status: clientTransferProhibited
Name Server: NS-1438.AWSDNS-51.ORG
Name Server: NS-1646.AWSDNS-13.CO.UK
Name Server: NS-374.AWSDNS-46.COM
Name Server: NS-897.AWSDNS-48.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form:
>>> Last update of whois database: 2019-09-30T20:50:21Z <<<

For more information on Whois status codes, please visit

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 Global Registry
Services' ("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.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Last update was 3 days ago
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites
1 secs
51 secs
1 min
1 min
2 mins
2 mins
2 mins
4 mins
5 mins
5 mins

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) and we will remove/hide your site data manualy.


Install HypeStat extension in your browser to see statistics and technologies used with one click.
Make custom Widget for your website
Get the code now! widget