Please select GA View:

Dotplace.Jp - Info dotplace.jp

dotplace.jp receives about 1,000 unique visitors and 1,900 (1.90 per visitor) page views per day which should earn about $6.00/day from advertising revenue. Estimated site value is $2,493.24. According to Alexa Traffic Rank dotplace.jp is ranked number 418,630 in the world and 0.0002% of global Internet users visit it. Site is hosted in Tokyo, 40, 100-0001, Japan and links to network IP address 52.193.50.226. This server doesn't support HTTPS and doesn't support HTTP/2.

About - dotplace.jp


dotplace.jp Profile

Title: DOTPLACE
Description: 『DOTPLACE(ドットプレイス)』は、これからの執筆・編集・出版に携わる人のためのサイトです。激変するメディアを取材して情報発信する「広場」を作り、ここから本の未来を作ろうというプロジェクトです。
Keywords: DOTPLACE,ドットプレイス,電子出版,出版,電子本,本,電子書籍,書籍,編集
Last update was 805 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is dotplace.jp?

1K daily visitors
Daily Unique Visitors:
1,000
Monthly Unique Visitors:
30,000
Pages per Visit:
1.90
Daily Pageviews:
1,900
Alexa Rank:
418,630 visit alexa
Alexa Reach:
0.0002%   (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
Japan 86.6%94.4%32906

Where do visitors go on this site?

Reach%Pageviews%PerUser
dotplace.jp
100.00%100.00%2.4

Competitive Data

SEMrush
Domain:
  dotplace.jp
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

Data

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

How socially engaged is dotplace.jp?

Facebook:
  1,159
Google +:
  124
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:
dotplace.jp
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:
dotplace.jp
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 dotplace.jp can earn?

Daily Revenue:
$6.00
Monthly Revenue:
$180.00
Yearly Revenue:
$2,190.00
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Japan 1,794$5.74

How much money do dotplace.jp lose due to Adblock?

Daily Revenue Loss:
$0.17
Monthly Revenue Loss:
$5.17
Yearly Revenue Loss:
$62.85
Daily Pageviews Blocked:
54
Monthly Pageviews Blocked:
1,614
Yearly Pageviews Blocked:
19,640
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Japan 54$0.17

How much is dotplace.jp worth?

Website Value:
$2,493.24

Where is dotplace.jp hosted?

Server IP:
52.193.50.226
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:
Tokyo
40
100-0001
Japan
 

Other sites hosted on 52.193.50.226

There are no other sites hosted on this IP

How fast does dotplace.jp load?

Average Load Time:
(1170 ms) 59 % of sites are slower

Page Speed (Google PageSpeed Insights)

Suggestions Summary

Optimize images

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

Optimize the following images to reduce their size by 6.7MiB (84% reduction).

Compressing and resizing http://dotplace.jp/wp-content/uploads/2016/12/title3.jpg could save 2.3MiB (99% reduction).
Compressing and resizing http://dotplace.jp/wp-content/uploads/2016/12/title.jpg could save 1MiB (99% reduction).
Compressing and resizing http://dotplace.jp/wp-content/uploads/2016/12/title2.jpg could save 956.3KiB (99% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/12/juhan_top_022.jpg could save 784.1KiB (90% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/12/20161201ts1000_395_.jpg could save 374.8KiB (45% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/12/hoshino01.jpg could save 340.8KiB (80% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/12/TIBF2016_e.jpg could save 273.1KiB (72% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/11/odyssey-banner-1.jpg could save 215.5KiB (82% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/12/After10Years_2_e.jpg could save 120.9KiB (50% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/12/95a704ea7e4f658848231f87022b6800.jpg could save 81.8KiB (53% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/11/juhan_top_tokubetsu.jpg could save 79.2KiB (60% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/11/ota.jpg could save 37.7KiB (90% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/11/profile.jpg could save 30KiB (85% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/08/83ce8bfebb1dddf11b262c31d8f38c79.jpg could save 23.5KiB (85% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/12/oyanagikaeP_140.jpg could save 22.7KiB (81% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/07/MG_4895_prof.jpg could save 20.9KiB (79% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/10/brandpublishing_banner.jpg could save 14KiB (41% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/12/accd018c8dc2214b221f2d9ce7fddf0a.jpg could save 12.9KiB (37% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2014/08/labeltop_cork.png could save 11.9KiB (25% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/01/ad60671eda8a79f1e944db43e113704a.png could save 8.4KiB (30% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/06/scsc-335x130.png could save 7KiB (18% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/12/title-335x130.jpg could save 5.5KiB (25% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2014/08/labeltop_machinohonya.png could save 5.3KiB (19% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/12/title2-335x130.jpg could save 5.1KiB (23% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/12/TIBF2016_e-335x130.jpg could save 4.5KiB (21% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2016/12/juhan_top_022-335x130.jpg could save 3.7KiB (23% reduction).
Compressing http://dotplace.jp/wp-content/uploads/2014/08/manazashi_labeltop.png could save 3.7KiB (22% reduction).
Compressing http://dotplace.jp/wp-content/themes/dotplace_v1_1act/img/weekly-nonhover.png could save 3.5KiB (55% reduction).
Compressing http://dotplace.jp/wp-content/themes/dotplace_v1_1act/img/information-nonhover.png could save 3.3KiB (61% reduction).
Compressing http://dotplace.jp/wp-content/themes/dotplace_v1_1act/img/dotplace-nonhover.png could save 3.2KiB (56% reduction).
Compressing http://dotplace.jp/wp-content/themes/dotplace_v1_1act/img/rss_top_icon.png could save 2.8KiB (91% reduction).
Compressing http://dotplace.jp/wp-content/themes/dotplace_v1_1act/img/twitter_top_icon.png could save 2.8KiB (92% reduction).
Compressing http://dotplace.jp/wp-content/themes/dotplace_v1_1act/img/googleplus_top_icon.png could save 2.7KiB (90% reduction).
Compressing http://dotplace.jp/wp-content/themes/dotplace_v1_1act/img/facebook_top_icon.png could save 2.7KiB (93% reduction).
Compressing http://dotplace.jp/wp-content/themes/dotplace_v1_1act/img/articles-nonhover.png could save 2.6KiB (72% reduction).

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

Your page has 10 blocking script resources and 8 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.9.1/jquery.min.js
https://nehan.googlecode.com/hg/nehan5.min.js
https://nehan.googlecode.com/hg/jquery.nehan.min.js
http://dotplace.jp/wp-content/themes/dotplace/js/vendor/modernizr-2.6.2.min.js
http://ajax.googleapis.com/ajax/libs/jqueryui/1.10.3/jquery-ui.min.js
http://dotplace.jp/wp-content/themes/dotplace/js/vendor/jQueryAutoHeight.js
http://dotplace.jp/wp-content/themes/dotplace/js/plugins.js
http://dotplace.jp/wp-content/themes/dotplace_v1_1act/js/main.js
http://webfont.fontplus.jp/accessor/script/fontplus.js?6BmUmW2XndA%3D&aa=1
http://dotplace.jp/wp-content/themes/dotplace_v1_1act/js/dotplace_ga.js
Optimize CSS Delivery of the following:

https://nehan.googlecode.com/hg/nehan5.css
https://nehan.googlecode.com/hg/jquery.nehan.css
http://dotplace.jp/wp-content/themes/dotplace_v1_1act/css/normalize.css
http://dotplace.jp/wp-content/themes/dotplace_v1_1act/css/main.css
http://dotplace.jp/wp-content/plugins/contact-form-7/includes/css/styles.css?ver=4.3.1
http://dotplace.jp/wp-content/plugins/wordpress-po***r-posts/style/wpp.css?ver=3.3.3
http://dotplace.jp/wp-content/plugins/tablepress/css/default.min.css?ver=1.7
http://dotplace.jp/wp-content/plugins/anteru-toolbox/css/anteru.css?ver=4.3.6

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.

本とその周辺で生きていく。 │ dotplace.jp renders only 4 pixels tall (12 CSS pixels) .
CONTACT and 1 others render only 3 pixels tall (10 CSS pixels) .
鷹野凌 今月の出版業界気になるニュースまとめ and 1 others render only 6 pixels tall (18 CSS pixels) .
INTERVIEW and 13 others render only 5 pixels tall (16 CSS pixels) .
DOTPLACE GALLERY and 1 others render only 7 pixels tall (19 CSS pixels) .
2031: A BOOK-A…2031年ブックアートの旅) renders only 8 pixels tall (22 CSS pixels) .
第3回 ミュンヘンでの活版印刷研修 and 1 others render only 5 pixels tall (15 CSS pixels) .
第3回 ミュンヘンでの活版印…た。活版印刷工房フリー... and 1 others render only 4 pixels tall (12 CSS pixels) .
Jan 06, 2017 and 1 others render only 3 pixels tall (10 CSS pixels) .
写真と映画の中間領域にある可…キュメンタリー映画」特集上映 and 5 others render only 5 pixels tall (16 CSS pixels) .
星野智幸×赤瀬智彦 『星野…記念 作家×編集者対談 後編 and 11 others render only 7 pixels tall (19 CSS pixels) .
2016年12月「出版業界気になるニュース2016年回顧」 and 3 others render only 5 pixels tall (16 CSS pixels) .
Dec 29, 2016 and 11 others render only 3 pixels tall (10 CSS pixels) .
Oct 13, 2016 and 3 others render only 3 pixels tall (10 CSS pixels).
2/27にトークイベント開催…て起業をテーマに考える60分 and 3 others render only 4 pixels tall (12 CSS pixels).
PEOPLE renders only 6 pixels tall (18 CSS pixels) .
ペドロ・コスタ and 4 others render only 6 pixels tall (18 CSS pixels) .
(おおた・やすとも) and 3 others render only 4 pixels tall (13 CSS pixels) .
佐渡島庸平、大原ケイ、今村友紀、山内康裕、羽賀翔一 and 2 others render only 5 pixels tall (15 CSS pixels) .
街の本屋の逆襲 and 2 others render only 5 pixels tall (16 CSS pixels) .
出版不況の煽りを受け、苦境に…れからの街の本屋”の姿とは。 and 2 others render only 4 pixels tall (11 CSS pixels) .
1 and 4 others render only 4 pixels tall (12 CSS pixels).
英国出版事情 (2/3)「本…インドー」と化した書店の危機 and 4 others render only 5 pixels tall (14 CSS pixels).
2016年12月「出版業界気になるニュース2016年回顧」 and 2 others render only 4 pixels tall (13 CSS pixels).
電子本の売り方がよくわからな…ら何でもやってみる企画(仮) and 58 others render only 3 pixels tall (10 CSS pixels).

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://twitter.com/dotplace" class="twitter_btn ir">twitter</a> is close to 1 other tap targets .
The tap target <a href="https://www.fa…k.com/dotplace" class="facebook_btn">facebook</a> is close to 2 other tap targets .
The tap target <a href="https://plus.g…7185136133658/" class="googleplus_btn">Google+</a> is close to 2 other tap targets .
The tap target <a href="/feed" class="rss_btn">RSS</a> is close to 1 other tap targets .
The tap target <a href="http://dotplac…archives/26411">DOTPLACEによる出版支…ishing」始動のお知らせ</a> and 1 others are close to other tap targets .
The tap target <a href="http://dotplac…archives/27124">鷹野凌 今月の出版業界気にな…なるニュース2016年回顧」</a> is close to 1 other tap targets .
The tap target <div class="slider_prev"> is close to 1 other tap targets .
The tap target <div class="slider_next"> is close to 1 other tap targets .
The tap target <a href="http://dotplac…archives/26411" class="title">DOTPLACEによる出版支…ishing」始動のお知らせ</a> and 3 others are close to other tap targets.
The tap target <a id="more-top-info" href="javascript:void(0);" class="more_btn"> is close to 1 other tap targets.
The tap target <a href="/archives/category/column" class="category_title">COLUMN</a> and 73 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=1100 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://connect.facebook.net/ja_JP/all.js (20 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
https://apis.google.com/js/platform.js (30 minutes)
http://www.google-***ytics.com/***ytics.js (2 hours)

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 4.9KiB (33% reduction).

Minifying http://dotplace.jp/wp-content/themes/dotplace_v1_1act/css/main.css could save 3.6KiB (28% reduction) after compression.
Minifying http://dotplace.jp/wp-content/themes/dotplace_v1_1act/css/normalize.css could save 1.3KiB (61% 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 4.1KiB (27% reduction).

Minifying http://cdn-ak.b.st-hatena.com/js/bookmark_button.js could save 1.9KiB (23% reduction) after compression.
Minifying http://dotplace.jp/wp-content/themes/dotplace_v1_1act/js/dotplace_ga.js could save 922B (31% reduction) after compression.
Minifying http://dotplace.jp/wp-content/themes/dotplace_v1_1act/js/main.js could save 792B (26% reduction) after compression.
Minifying http://dotplace.jp/wp-content/themes/dotplace/js/vendor/jQueryAutoHeight.js could save 531B (51% reduction) after compression.

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 2.8KiB (65% reduction).

Compressing https://platform.twitter.com/js/button.3943c052be33b5e812dac6838df9cb3d.js could save 2.8KiB (65% reduction).
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.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
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.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
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:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

SSL Checker - SSL Certificate Verify

dotplace.jp does not support HTTPS
loader
Verifying SSL Support. Please wait...

Verify HTTP/2 Support

dotplace.jp does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

Http Header

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Sat, 07 Jan 2017 15:42:05 GMT
Content-Type: text/html; ch***t=UTF-8
Connection: close
X-Cached: Sat, 07 Jan 2017 15:42:05 GMT
Location: http://dotplace.jp/
HTTP/1.1 200 OK
Server: nginx
Date: Sat, 07 Jan 2017 15:42:06 GMT
Content-Type: text/html; ch***t=UTF-8
Connection: close
Vary: Accept-Encoding
X-Cached: Sat, 07 Jan 2017 13:25:33 GMT
Last-Modified: Sat, 07 Jan 2017 13:25:33 GMT

DNS Lookup

Type Ip Target TTL
SOA 900
Mname ns-53.awsdns-06.com
Rname awsdns-hostmaster.amazon.com
Serial Number 1
Refresh 7200
Retry 900
Expire 1209600
Minimum TTL 0
A 52.193.50.226 300
NS ns-1518.awsdns-61.org 3600
NS ns-53.awsdns-06.com 3600
NS ns-673.awsdns-20.net 3600
NS ns-1822.awsdns-35.co.uk 3600

Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.jprs.jp...
[ JPRS database provides information on network administration. Its use is ]
[ restricted to network administration purposes. For further information, ]
[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]
[ at the end of command, e.g. 'whois -h whois.jprs.jp ***/e'. ]

Domain Information: [ドメイン情報]
[Domain Name] DOTPLACE.JP

[登録者名] 株式会社AZホールディングス
[Registrant] AZ Holdings, Inc.

[Name Server] ns-53.awsdns-06.com
[Name Server] ns-1822.awsdns-35.co.uk
[Name Server] ns-1518.awsdns-61.org
[Name Server] ns-673.awsdns-20.net
[Signing Key]

[登録年月日] 2013/02/06
[有効期限] 2017/02/28
[状態] Active
[最終更新] 2016/03/01 01:05:18 (JST)

Contact Information: [公開連絡窓口]
[名前] Whois情報公開代行サービス by お名前.com
[Name] Whois Privacy Protection Service by onamae.com
[Email] email
[Web Page]
[郵便番号] 150-8512
[住所] 東京都渋谷区
桜丘町 26-1
セルリアンタワー 11階
[Postal Address] Shibuya-ku
26-1 Sakuragaoka-cho
Cerulean Tower 11F
[電話番号] +81.354562560
[FAX番号]
Last update was 805 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

72sheep.com
0 secs
72shade.com
2 secs
72sgreenwood.com
17 secs
viber.com
18 secs
72sfounders.com
23 secs
72seventytwo.com
24 secs
72services.org
28 secs
72services.net
30 secs
72services.com
31 secs
72sense.com
34 secs

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!
dotplace.jp widget