Tenkomo.Com - Website Report

Tenkomo.Com

Traffic estimate for Tenkomo.com is about 5,320 unique visits and 10,108 page views per day. Each unique visitor makes about 1.9 page views on average. According to traffic estimate, Tenkomo.com should earn about $40.61 per day from the advertising revenue, which implies that this website is worth about $16,244.27. Alexa Traffic Rank estimates that it is ranked number 100,238 in the world and 0.0076% of global Internet users are visiting Tenkomo.com on a regular basis. Website hosting location for Tenkomo.com is: Las Vegas, NV, 89147, United States. Server IP address: 104.244.98.62


About - tenkomo.com

Edit WebSite Info

Earnings Report

Website Value: $16,244.27
Daily Revenue: $40.61
Monthly Revenue: $1,218.32
Yearly Revenue: $14,822.90

Traffic Report

Daily Unique Visitors: 5,320
Monthly Unique Visitors: 159,600
Daily Pageviews: 10,108 (1.9 per day)
Montly Pageviews: 303,240
Daily PageViews Per User: 1.9
Alexa Global Rank: 100,238
Alexa Reach: 0.0076% of global Internet users
Alexa Backlinks: 163
Average Page Load Time: 4,824

Country Report

Country Alexa Rank PageViews Visitors
Japan 8091 100.0% 100.0%

Contributing Subdomains

Domain Reach PageViews Per User
tenkomo.com 100.00% 100.00% 1.7

Social Report


Hosting Info

tenkomo.com Server Location
Server IP: 104.244.98.62
ASN: AS63210
ISP: FC2 INC
Server Location: Las Vegas NV 89147 United States

Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Reputation / Confidence
Trustworthiness: N/A
Child safety: N/A
MyWOT Categories: N/A

Google PageSpeed Insights

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

Your page has 5 blocking script resources and 2 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://templates.blog.fc2.com/template/sphone/basic_black/jquery.js
http://templates.blog.fc2.com/template/sphone/basic_black/iphone_resize.js
http://js1.nend.net/js/nendAdLoader.js
http://js1.nend.net/js/nendAdLoader.js
http://js1.nend.net/js/nendAdLoader.js

Optimize CSS Delivery of the following:
http://blog-imgs-120.fc2.com/t/e/n/tenkomo/css/50819.css
http://xn--cck5a8g8a2cyf.com/lp-sp/iframe/css/fc2-if-outside-g.css

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://asumi.shinobi.jp/encount (expiration not specified)
http://ct1.choumusubi.com/sc/0317724 (expiration not specified)
http://ct1.shinobi.jp/sd/0317724 (expiration not specified)
http://file.ziyu.net/b/b022.gif (expiration not specified)
https://blogroll.livedoor.net/css/default2.css (expiration not specified)
https://blogroll.livedoor.net/img/blog_favicon.ico (expiration not specified)
https://blogroll.livedoor.net/js/blogroll.js (expiration not specified)
https://blogroll.livedoor.net/url/http://matomeja.jp/feed/20180516194518/?d=sp&c=index (2 minutes)
https://blogroll.livedoor.net/url/http://matomeja.jp/feed/20180516224527/?d=sp&c=index (2 minutes)
https://blogroll.livedoor.net/url/http://matomeja.jp/feed/20180517063211/?d=sp&c=index (2 minutes)
https://blogroll.livedoor.net/url/http://matomeja.jp/feed/20180517090749/?d=sp&c=index (2 minutes)
https://blogroll.livedoor.net/url/http://matomeja.jp/feed/20180517112406/?d=sp&c=index (2 minutes)
https://blogroll.livedoor.net/url/http://moudamepo.com/pick.cgi?code=1032&cate=0&date=1526508009 (2 minutes)
https://blogroll.livedoor.net/url/http://moudamepo.com/pick.cgi?code=1165&cate=0&date=1526538117 (2 minutes)
https://blogroll.livedoor.net/url/http://moudamepo.com/pick.cgi?code=1954&cate=0&date=1526342447 (2 minutes)
https://blogroll.livedoor.net/url/http://moudamepo.com/pick.cgi?code=2211&cate=0&date=1526392829 (2 minutes)
https://blogroll.livedoor.net/url/http://moudamepo.com/pick.cgi?code=2232&cate=0&date=1510666300 (2 minutes)
https://blogroll.livedoor.net/url/http://owata-net.com/feed/20180516180950/?d=pc&c=index (2 minutes)
https://blogroll.livedoor.net/url/http://owata-net.com/feed/20180516190356/?d=pc&c=index (2 minutes)
https://blogroll.livedoor.net/url/http://owata-net.com/feed/20180516221126/?d=pc&c=index (2 minutes)
https://blogroll.livedoor.net/url/http://owata-net.com/feed/20180517062200/?d=pc&c=index (2 minutes)
https://blogroll.livedoor.net/url/http://owata-net.com/feed/20180517072059/?d=pc&c=index (2 minutes)
http://js1.nend.net/js/nendAdLoader.js (8.1 minutes)
https://blogroll.livedoor.net/149152/roll_data (10 minutes)
https://syndication.twitter.com/settings (10 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
https://sp.gmossp-sp.jp/ads/sync.ad?dsp=ninjya_adt&dspuid=e9ee351d-5645-4d2b-a117-550453366b0e (60 minutes)
http://templates.blog.fc2.com/template/sphone/basic_black/jquery.js (89.6 minutes)
http://templates.blog.fc2.com/template/sphone/basic_black/iphone_resize.js (100 minutes)
https://templates.blog.fc2.com/template/sphone/basic_black/chevron.png (100 minutes)
https://templates.blog.fc2.com/template/sphone/basic_black/dropmenu.png (100 minutes)
http://www.google-analytics.com/analytics.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 87.4KiB (70% reduction).
Compressing http://templates.blog.fc2.com/template/sphone/basic_black/jquery.js could save 83.4KiB (70% reduction).
Compressing http://templates.blog.fc2.com/template/sphone/basic_black/iphone_resize.js could save 1.4KiB (63% reduction).
Compressing https://blogroll.livedoor.net/css/default2.css could save 889B (69% reduction).
Compressing http://xid.i-mobile.co.jp/RestoreXidToMediaStorage.html could save 789B (59% reduction).
Compressing https://xn--cck5a8g8a2cyf.com/lp-sp/iframe/css/fc2-if-outside-g.css could save 738B (57% reduction).
Compressing http://st.shinobi.jp/img/services/admaxdsp/static/javascripts/trac.js could save 314B (39% reduction).

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://blogro…nnel_id=149152">パリを否定したせいで顔面エッフェル塔になった話</a> and 26 others are close to other tap targets.
The tap target <a href="//ct1.shinobi.jp/gg/0317724"></a> is close to 1 other tap targets.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 47.4KiB (39% reduction).
Minifying http://templates.blog.fc2.com/template/sphone/basic_black/jquery.js could save 46.2KiB (40% reduction).
Minifying http://templates.blog.fc2.com/template/sphone/basic_black/iphone_resize.js could save 704B (32% reduction).
Minifying https://blogroll.livedoor.net/js/blogroll.js could save 535B (16% reduction) after compression.

Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 30.5KiB (63% reduction).
Compressing http://spcdnsp.i-mobile.co.jp/ad_creative.ashx?advid=4152914&eid=3 could save 29.2KiB (65% reduction).
Compressing https://blogroll.livedoor.net/img/blank.gif?channel_id=149152 could save 739B (91% reduction).
Compressing http://file.ziyu.net/b/b022.gif could save 588B (22% reduction).

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 2KiB (34% reduction).
Minifying http://blog-imgs-120.fc2.com/t/e/n/tenkomo/css/50819.css could save 938B (28% reduction) after compression.
Minifying https://xn--cck5a8g8a2cyf.com/lp-sp/iframe/css/fc2-if-outside-g.css could save 740B (57% reduction).
Minifying https://blogroll.livedoor.net/css/default2.css could save 332B (26% reduction).

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 parse times.
Minify HTML for the following resources to reduce their size by 871B (17% reduction).
Minifying http://tenkomo.com/ could save 443B (12% reduction) after compression.
Minifying http://xid.i-mobile.co.jp/RestoreXidToMediaStorage.html could save 428B (33% reduction).

Avoid landing page redirects

Your page has no redirects. Learn more about avoiding landing page redirects.

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

Prioritize visible content

You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.

Reduce server response time

Your server responded quickly. Learn more about server response time optimization.

Http Header

Currently Not Available

DNS Lookup

Type Ip Target TTL
A 104.244.98.62 59
CNAME tenkomo.blog.fc2.com 86399

WhoIs Lookup

Domain Created: 2013-08-13
Domain Age: 5 years
WhoIs:
WhoIs lookup results from whois.verisign-grs.com server:

Domain Name: TENKOMO.COM
Registry Domain ID: 1821508442_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.enom.com
Registrar URL: http://www.enom.com
Updated Date: 2017-07-13T22:11:09Z
Creation Date: 2013-08-13T13:42:03Z
Registry Expiry Date: 2018-08-13T13:42:03Z
Registrar: eNom, Inc.
Registrar IANA ID: 48
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: MDNS1.FC2.COM
Name Server: MDNS2.FC2.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-05-17T08:11:25Z <<<
For more information on Whois status codes, please visit https://icann.

-------------
WhoIs lookup results for tenkomo.com from whois.crsnic.net server:

Domain Name: TENKOMO.COM
Registry Domain ID: 1821508442_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.enom.com
Registrar URL: http://www.enom.com
Updated Date: 2017-07-13T22:11:09Z
Creation Date: 2013-08-13T13:42:03Z
Registry Expiry Date: 2018-08-13T13:42:03Z
Registrar: eNom, Inc.
Registrar IANA ID: 48
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: MDNS1.FC2.COM
Name Server: MDNS2.FC2.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-05-17T08:11:40Z <<<
For more information on Whois status codes, please visit https://icann.