mobile01.Com - Info mobile01.com

mobile01.com receives about 535,000 unique visitors and 1,193,050 (2.23 per visitor) page views per day which should earn about $2,520.07/day from advertising revenue. Estimated site value is $1,579,780.29. According to Alexa Traffic Rank mobile01.com is ranked number 793 in the world and 0.107% of global Internet users visit it. Site is hosted in Taipei, 03, Taiwan and links to network IP address 202.39.235.195.

About - mobile01.com

「全球華人最注目的社群網站是哪個?」這問題的答案非常簡單,就是Mobile01!
How did mobile01.com look in the past? Edit Site Info

How popular is mobile01.com?

Daily Unique Visitors:
535,000
Monthly Unique Visitors:
16,050,000
Daily Pageviews:
1,193,050 (2.23 per visitor)
Alexa Rank:
793 visit alexa
Alexa Reach:
0.107% (Percent of global Internet users)
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic
majestic
Quantcast

Visitors by country

Users%Pageviews%Rank
Taiwan 82.4%85.3%22
China 7.7%6.7%1134
Hong Kong 4.3%3.1%152
Japan 2.0%1.5%3414
United States 1.1%1.0%13668
Macao 0.7%0.7%46

Where do visitors go on this site?

Reach%Pageviews%PerUser
mobile01.com
98.15%96.90%2.24
m.mobile01.com
4.27%2.04%1.1
attach.mobile01.com
0.91%0.70%1.8
upload.mobile01.com
0.15%0.08%1.1
git.mobile01.com
0.02%0.19%30
OTHER
0%0.08%0

Competitive Data

SEMrush mobile01.com
Domain:
  mobile01.com
Rank:
  216,861
Organic Keywords:
  43,529
Organic Traffic:
  6,334
Organic Cost:
  $229.00
Adwords Keywords:
  0
Adwords Traffic:
  0
Adwords Cost:
  $0.00

Data

Domain Authority:
  53
Page Authority:
  46
MozRank:
  4

Backlinks Report

Total Sites Linking In (Alexa):
11,798
Total Backlinks:
  399,205
Follow Links:
  368,544
Nofollow Links:
  30,661
Referring Domains:
  3,330
Referring IPs:
  3,377

How socially engaged is mobile01.com?

Facebook:
  0
Google +:
  5,765
Linkedin:
  2
Stumbles:
  40
Buffer:
  1
Pins:
  0

How much mobile01.com can earn?

Daily Revenue:
$2,520.07
Monthly Revenue:
$75,602.10
Yearly Revenue:
$919,825.55
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Taiwan 1,017,672$1,933.58
China 79,934$247.00
United States 11,931$136.84
Hong Kong 36,985$127.60
Japan 17,896$57.27
Macao 8,351$17.79

How much money do mobile01.com lose due to Adblock?

Daily Revenue Loss:
$380.95
Monthly Revenue Loss:
$11,428.41
Yearly Revenue Loss:
$139,045.64
Daily Pageviews Blocked:
179,769
Monthly Pageviews Blocked:
5,393,063
Yearly Pageviews Blocked:
65,615,603
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Taiwan 162,827$309.37
China 10,391$32.11
United States 2,147$24.63
Hong Kong 3,698$12.76
Japan 537$1.72
Macao 167$0.36

How much is mobile01.com worth?

Website Value:
$1,579,780.29

Where is mobile01.com hosted?

Server location
Server IP:
202.39.235.195
ASN:
AS3462 
ISP:
Data Communication Business Group 
Server Location:
Taipei
03
Taiwan
 

Other sites hosted on 202.39.235.195

There are no other sites hosted on this IP

How fast does mobile01.com load?

Average Load Time:
(1205 ms) 71 % of sites are slower

Page Speed (Google PageSpeed Insights)

Suggestions Summary

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

Your page has 6 blocking script resources and 4 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://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js
http://attach2.mobile01.com/js/jquery.browser.min.js
http://attach2.mobile01.com/js/jquery.cookie.min.js
http://attach2.mobile01.com/js/jquery.lazyload.min.js
http://attach2.mobile01.com/js/viewportSize-min.js
http://attach2.mobile01.com/js/jquery.mmenu.min.all.js
Optimize CSS Delivery of the following:

http://m.mobile01.com/style/mobile.css
http://m.mobile01.com/style/appmenu.css
http://m.mobile01.com/style/jquery.mmenu.all.css
http://m.mobile01.com/style/android.css

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://mobile01.com/
http://www.mobile01.com/
http://m.mobile01.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="adredir.php?id=58032"></a> and 1 others are close to other tap targets .
The tap target <a href="newsdetail.php?id=17605">第五屆 Garmin &amp; M…e01 西拉雅單車活動全記錄</a> and 1 others are close to other tap targets .
The tap target <a href="newsdetail.php?id=17605">第五屆 Garmin &amp; M…e01 西拉雅單車活動全記錄</a> is close to 1 other tap targets .
The tap target <div id="ad-close">關閉廣告</div> is close to 2 other tap targets .
The tap target <div id="ad-close">關閉廣告</div> and 1 others are close to other tap targets .
The tap target <a href="javascript:clo…ullscreenad();">關閉廣告</a> is close to 2 other tap targets .

Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 45% of the final above-the-fold content could be rendered with the full HTML response .

Optimize images

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

Optimize the following images to reduce their size by 65.2KiB (11% reduction).

Losslessly compressing http://attach2.mobile01.com/image/news/headline/c072a4b741f820ec4c3e7c4468a10434.jpg could save 38.2KiB (11% reduction).
Compressing and resizing http://attach2.mobile01.com/images/app/m01app-mobile01-3.jpg could save 22.1KiB (97% reduction).
Losslessly compressing http://m.mobile01.com/image/mobile01.png could save 4.1KiB (78% reduction).
Losslessly compressing http://attach2.mobile01.com/image/mod_ad/mobile01-1817c43cd53fb5196427f1df8dcb626b.jpg could save 877B (1% reduction).

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://m.mobile01.com/image/mobile01.png (expiration not specified)
http://m.mobile01.com/style/android.css (expiration not specified)
http://m.mobile01.com/style/appmenu.css (expiration not specified)
http://m.mobile01.com/style/jquery.mmenu.all.css (expiration not specified)
http://m.mobile01.com/style/mobile.css (expiration not specified)
https://d31qbv1cthcecs.cloudfront.net/atrk.js (expiration not specified)
http://www.google-***ytics.com/ga.js (2 hours)

Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 28.1KiB (***% reduction).

Compressing http://attach2.mobile01.com/js/jquery.mmenu.min.all.js could save 24.8KiB (72% reduction).
Compressing http://attach2.mobile01.com/js/jquery.lazyload.min.js could save 2KiB (61% reduction).
Compressing http://attach2.mobile01.com/js/jquery.browser.min.js could save ***2B (47% reduction).
Compressing http://attach2.mobile01.com/js/jquery.cookie.min.js could save 594B (47% reduction).

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 2KiB (6% reduction).

Minifying http://attach2.mobile01.com/js/jquery.mmenu.min.all.js could save 2KiB (6% 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 777B (14% reduction).

Minifying http://m.mobile01.com/style/jquery.mmenu.all.css could save 777B (14% reduction) after compression.

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 679B (7% reduction).

Minifying http://m.mobile01.com/ could save 679B (7% reduction) after compression.
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.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
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.
Avoid app install interstitials that hide content
Your page does not appear to have any app install interstitials that hide a significant amount of content. Learn more about the importance of avoiding the use of app install interstitials.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Download optimized image, JavaScript, and CSS resources for this page.

Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  91
Vendor reliability:
  91
Privacy:
  91
Child safety:
  88

Site Categories (dmoz)

Currently Not Available

What sites are related to mobile01.com?

Http Header

Currently Not Available

DNS Lookup

Type Ip Target TTL
MX aspmx3.googlemail.com 3600
MX aspmx4.googlemail.com 3600
MX aspmx5.googlemail.com 3600
MX mail.mobile01.com 3600
MX mail2.mobile01.com 3600
MX mail3.mobile01.com 3600
MX mail4.mobile01.com 3600
MX mail5.mobile01.com 3600
MX mail6.mobile01.com 3600
MX aspmx.l.google.com 3600
MX alt1.aspmx.l.google.com 3600
MX alt2.aspmx.l.google.com 3600
MX aspmx2.googlemail.com 3600
SOA 3600
Mname ns-cloud-b1.googledomains.com
Rname cloud-dns-hostmaster.google.com
Serial Number 2017072501
Refresh 86400
Retry 3600
Expire 2419200
Minimum TTL 0
A 202.39.235.195 3600
NS ns-cloud-b1.googledomains.com 3600
NS ns-cloud-b4.googledomains.com 3600
NS ns-cloud-b3.googledomains.com 3600
NS ns-cloud-b2.googledomains.com 3600

Whois Lookup

Domain Created:
2003-02-25
Domain Age:
14 years 6 months 23 days  
WhoIs:
 

whois lookup at whois.tucows.com...
IP Address: 67.212.187.106
Maximum Daily connection limit reached. Lookup refused.
whois lookup at whois.crsnic.net...
Whois Server Version 2.0

Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.

Domain Name: MOBILE01.COM
Registrar: TUCOWS DOMAINS INC.
Sponsoring Registrar IANA ID: ***
Whois Server: whois.tucows.com
Referral URL: http://www.tucowsdomains.com
Name Server: NS-CLOUD-B1.GOOGLEDOMAINS.COM
Name Server: NS-CLOUD-B2.GOOGLEDOMAINS.COM
Name Server: NS-CLOUD-B3.GOOGLEDOMAINS.COM
Name Server: NS-CLOUD-B4.GOOGLEDOMAINS.COM
Status: ok https://icann.org/epp#ok
Updated Date: 25-aug-2016
Creation Date: 25-feb-2003
Expiration Date: 25-feb-2025

>>> Last update of whois database: Thu, 20 Apr 2017 15:35:20 GMT <<<

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 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
Registrars.
Last update was 3 days ago
loader
This can take up to 60 seconds. Please wait...

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!
mobile01.com widget