OTAKOMU.JP オタク.com


otakomu.jp website information.

otakomu.jp domain name is registered by .JP top-level domain registry. See the other sites registred in .JP domain zone.

Following name servers are specified for otakomu.jp domain:

  • ns2.value-domain.com
  • ns1.value-domain.com

and probably website otakomu.jp is hosted by CNNIC-ALIBABA-CN-NET-AP Alibaba (China) Technology Co., Ltd., CN web hosting company. Check the complete list of other most popular websites hosted by CNNIC-ALIBABA-CN-NET-AP Alibaba (China) Technology Co., Ltd., CN hosting company.

According to Alexa traffic rank the highest website otakomu.jp position was 6005 (in the world). The lowest Alexa rank position was 650197. Now website otakomu.jp ranked in Alexa database as number 24105 (in the world).

Website otakomu.jp Desktop speed measurement score (57/100) is better than the results of 31.79% of other sites shows that the page desktop performance can be improved.

otakomu.jp Mobile usability score (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of otakomu.jp (44/100) is better than the results of 24.22% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Oct-18-2021 24,105N/A
Oct-17-2021 N/AN/A
Oct-16-2021 50,398-18,967
Oct-15-2021 31,431-15,975
Oct-14-2021 15,45624,340
Oct-13-2021 39,796N/A
Oct-12-2021 N/AN/A

Advertisement

otakomu.jp Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



otakomu.jp whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


otakomu.jp server information

Servers Location

IP Address
203.104.130.159
Country
Japan
Region
Tokyo
City
Tokyo

otakomu.jp desktop page speed rank

Last tested: 2018-10-07


Desktop Speed Bad
57/100

otakomu.jp Desktop Speed Test Quick Summary


priority - 45 Optimize images

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

Optimize the following images to reduce their size by 441.4KiB (45% reduction).

Compressing https://cdn-fluct.sh.adingo.jp/img/2018/10/05/1538…poALVAf.jpg?1538940417 could save 90KiB (73% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/img/2018/10/05/1538…poALVAf.jpg?1538940420 could save 90KiB (73% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/img/2018/10/05/1538…pXON1fa.jpg?1538940418 could save 88.7KiB (75% reduction).
Compressing and resizing http://otakomu.jp/wp-content/uploads/2018/10/2018y…_110143131-600x335.jpg could save 38KiB (83% reduction).
Compressing and resizing http://i0.wp.com/otakomu.jp/wp-content/uploads/201…181007102052.jpg?w=381 could save 25.8KiB (71% reduction).
Compressing and resizing http://i1.wp.com/otakomu.jp/wp-content/uploads/201…181007070723.jpg?w=381 could save 21.1KiB (72% reduction).
Compressing and resizing http://i1.wp.com/otakomu.jp/wp-content/uploads/201…180101020010.jpg?w=402 could save 19.1KiB (72% reduction).
Compressing http://spcdnpc.i-mobile.co.jp/ad_creative.ashx?advid=5031537&eid=20 could save 10.6KiB (44% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…3-featured-360x210.jpg could save 6.9KiB (15% reduction).
Compressing http://i0.wp.com/otakomu.jp/wp-content/uploads/201…--_---------------.jpg could save 4.9KiB (13% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…5-featured-360x210.jpg could save 4.1KiB (13% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…8-featured-360x210.jpg could save 4KiB (14% reduction).
Compressing http://i2.wp.com/otakomu.jp/wp-content/uploads/201…_fixw_640_hq.jpg?w=360 could save 3.6KiB (11% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…7-featured-360x210.jpg could save 3.2KiB (13% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…0-featured-360x210.jpg could save 2.9KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…1-featured-360x210.jpg could save 2.7KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…8-featured-360x210.jpg could save 2.6KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…9-featured-360x210.jpg could save 2.5KiB (13% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…5-featured-360x210.jpg could save 2.5KiB (12% reduction).
Compressing http://0taku.livedoor.biz/pict/sprite_otkm3.png could save 2.5KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…3-featured-360x210.jpg could save 2.3KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…6-featured-360x210.jpg could save 2KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…2-featured-360x210.jpg could save 1.8KiB (13% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…8-featured-360x210.jpg could save 1.7KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…4-featured-360x210.jpg could save 1.5KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/themes/otkm13/img/logo_footer.jpg could save 1.5KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…2-featured-360x210.jpg could save 1.4KiB (13% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…4-featured-360x210.jpg could save 1.4KiB (11% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…6-featured-360x210.jpg could save 1.2KiB (12% reduction).
Compressing http://0taku.livedoor.biz/img/arrow.png could save 938B (89% reduction).

priority - 16 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://cm.send.microad.jp/fl/cm (expiration not specified)
http://otakomu-master.sakura.ne.jp/otakomu_parts/j…komu_tweet_rank1_sp.js (expiration not specified)
http://otakomu-master.sakura.ne.jp/otakomu_parts/js/otakomu_tweet_rank3.js (expiration not specified)
http://otaku.vis1.shinobi.jp/js/ (expiration not specified)
http://x8.sarashi.com/ufo/147876800 (expiration not specified)
https://assets.gunosy.com/adnet/gunosy_ads.min.js (expiration not specified)
https://assets.gunosy.com/adnet/gunosy_slide_ads.min.js (expiration not specified)
https://file.ziyu.net/rranking.gif (expiration not specified)
https://prague-mark.adtdp.com/cs/fluct (expiration not specified)
https://j.zucks.net.zimg.jp/j?f=356927 (5 minutes)
https://blogroll.livedoor.net/23039/roll_data (10 minutes)
http://connect.facebook.net/ja_JP/sdk.js (20 minutes)
http://0taku.livedoor.biz/JS/blogroll.js (60 minutes)
http://0taku.livedoor.biz/img/arrow.png (60 minutes)
http://0taku.livedoor.biz/pict/sprite_otkm3.png (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000048826 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073617 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073620 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073622 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073623 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073629 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073630 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073658 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073665 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073666 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073667 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073668 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073669 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073670 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073671 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073672 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000074301 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000082319 (60 minutes)
https://gum.criteo.com/sync?c=46&r=2&j=handleData (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

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

Your page has 5 blocking script resources and 3 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://j.microad.net/js/compass.js
http://otakomu.jp/wp-content/themes/otkm13/js/index.js
http://otaku.vis1.shinobi.jp/js/
http://spdeliver.i-mobile.co.jp/script/adsnativepc.js?20101001
http://otakomu-master.sakura.ne.jp/otakomu_parts/js/otakomu_tweet_rank3.js

Optimize CSS Delivery of the following:

http://otakomu.jp/wp-content/themes/otkm13/style.css
http://otakomu.jp/wp-content/plugins/wordpress-pop…tyle/wpp.css?ver=3.3.3
http://otakomu.jp/wp-content/plugins/jetpack/css/jetpack.css?ver=3.9.7

priority - 5 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 48.9KiB (60% reduction).

Compressing http://0taku.livedoor.biz/JS/blogroll.js could save 10.7KiB (76% reduction).
Compressing http://otakomu-master.sakura.ne.jp/otakomu_parts/j…komu_tweet_rank1_sp.js could save 4.4KiB (76% reduction).
Compressing https://j.zucks.net.zimg.jp/j?f=356927 could save 3.7KiB (58% reduction).
Compressing http://otakomu-master.sakura.ne.jp/otakomu_parts/js/otakomu_tweet_rank3.js could save 3.1KiB (69% reduction).
Compressing https://image6.pubmatic.com/AdServer/PugMaster?rnd…nsent=&sec=1&kdntuid=1 could save 2.4KiB (67% reduction).
Compressing https://simage2.pubmatic.com/AdServer/Pug?vcode=bz…4fc2-81aa-1fbcf8010292 could save 1.5KiB (97% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000048826 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073617 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073620 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073622 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073623 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073629 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073630 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073658 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073665 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073666 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073667 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073668 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073669 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073670 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073671 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073672 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000074301 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000082319 could save 1.2KiB (51% reduction).
Compressing http://xid.i-mobile.co.jp/RestoreXidToMediaStorage.html could save 789B (59% reduction).
Compressing http://clt.a-i-ad.com/api/mk?mkid=431 could save 609B (60% reduction).
Compressing http://otakomu.jp/wp-content/themes/otkm13/js/index.js could save 327B (42% reduction).
Compressing http://st.shinobi.jp/img/services/admaxdsp/static/javascripts/trac.js could save 314B (39% reduction).

priority - 5 Reduce server response time

In our test, your server responded in 0.69 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.

priority - 1 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 6.4KiB (20% reduction).

Minifying http://otakomu.jp/wp-content/themes/otkm13/css/ionic.css could save 3.4KiB (22% reduction) after compression.
Minifying http://otakomu.jp/wp-content/themes/otkm13/style.css could save 1.4KiB (17% reduction) after compression.
Minifying http://otakomu.jp/wp-content/themes/otkm13/style_sp.css could save 1.2KiB (17% reduction) after compression.
Minifying http://otakomu.jp/wp-content/plugins/wordpress-pop…tyle/wpp.css?ver=3.3.3 could save 304B (58% reduction) after compression.

priority - 1 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 5.2KiB (34% reduction).

Minifying http://0taku.livedoor.biz/JS/blogroll.js could save 4.7KiB (34% reduction).
Minifying http://otakomu.jp/wp-content/themes/otkm13/js/index.js could save 298B (38% reduction).
Minifying http://clt.a-i-ad.com/api/mk?mkid=431 could save 242B (25% reduction).

priority - 1 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 4.9KiB (19% reduction).

Minifying http://otakomu.jp/ could save 3KiB (13% reduction) after compression.
Minifying https://simage2.pubmatic.com/AdServer/Pug?vcode=bz…4fc2-81aa-1fbcf8010292 could save 1.5KiB (99% reduction).
Minifying http://xid.i-mobile.co.jp/RestoreXidToMediaStorage.html could save 428B (33% reduction).

otakomu.jp Desktop Resources

Total Resources241
Number of Hosts75
Static Resources104
JavaScript Resources55
CSS Resources5

otakomu.jp Desktop Resource Breakdown

otakomu.jp mobile page speed rank

Last tested: 2018-10-07


Mobile Speed Bad
44/100

otakomu.jp Mobile Speed Test Quick Summary


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

Your page has 7 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://j.microad.net/js/compass.js
http://otakomu.jp/wp-content/themes/otkm13/js/index.js
http://otaku.vis1.shinobi.jp/js/
http://spdeliver.i-mobile.co.jp/script/adsnativepc.js?20101001
http://otakomu-master.sakura.ne.jp/otakomu_parts/js/otakomu_tweet_rank3.js
https://cdn-fluct.sh.adingo.jp/f.js?G=1000082319
http://sh.adingo.jp/?G=1000082319&href=http%3A%2F%…95002596243284&guid=ON

Optimize CSS Delivery of the following:

http://otakomu.jp/wp-content/themes/otkm13/style_sp.css
http://otakomu.jp/wp-content/themes/otkm13/css/ionic.css
http://otakomu.jp/wp-content/plugins/wordpress-pop…tyle/wpp.css?ver=3.3.3
http://otakomu.jp/wp-content/plugins/jetpack/css/jetpack.css?ver=3.9.7

priority - 34 Optimize images

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

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

Compressing https://cdn-fluct.sh.adingo.jp/img/2018/10/05/1538…pMMeIkZ.jpg?1538940432 could save 101.2KiB (72% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/img/2018/10/05/1538…p26yi5n.jpg?1538940431 could save 88KiB (74% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/img/2018/09/29/1538…prbRRSs.jpg?1538940434 could save 61.3KiB (64% reduction).
Compressing http://spcdnpc.i-mobile.co.jp/ad_creative.ashx?advid=5031537&eid=20 could save 10.6KiB (44% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…3-featured-360x210.jpg could save 6.9KiB (15% reduction).
Compressing http://otakomu.jp/wp-content/uploads/2018/10/2018y…_110143131-600x335.jpg could save 5.2KiB (12% reduction).
Compressing http://i0.wp.com/otakomu.jp/wp-content/uploads/201…--_---------------.jpg could save 4.9KiB (13% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…5-featured-360x210.jpg could save 4.1KiB (13% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…8-featured-360x210.jpg could save 4KiB (14% reduction).
Compressing http://spcdnsp.i-mobile.co.jp/ad_creative.ashx?advid=4627289&eid=19 could save 3.9KiB (20% reduction).
Compressing http://i2.wp.com/otakomu.jp/wp-content/uploads/201…_fixw_640_hq.jpg?w=360 could save 3.6KiB (11% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…7-featured-360x210.jpg could save 3.2KiB (13% reduction).
Compressing http://spcdnsp.i-mobile.co.jp/ad_creative.ashx?advid=5011353&eid=19 could save 3KiB (22% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…0-featured-360x210.jpg could save 2.9KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…1-featured-360x210.jpg could save 2.7KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…8-featured-360x210.jpg could save 2.6KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…9-featured-360x210.jpg could save 2.5KiB (13% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…5-featured-360x210.jpg could save 2.5KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…3-featured-360x210.jpg could save 2.3KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…6-featured-360x210.jpg could save 2KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…2-featured-360x210.jpg could save 1.8KiB (13% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…8-featured-360x210.jpg could save 1.7KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…4-featured-360x210.jpg could save 1.5KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/themes/otkm13/img/logo_footer.jpg could save 1.5KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…2-featured-360x210.jpg could save 1.4KiB (13% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…4-featured-360x210.jpg could save 1.4KiB (11% reduction).
Compressing http://otakomu.jp/wp-content/uploads/wordpress-pop…6-featured-360x210.jpg could save 1.2KiB (12% reduction).
Compressing http://otakomu.jp/wp-content/themes/otkm13/img/title.png could save 1KiB (32% reduction).
Compressing http://0taku.livedoor.biz/img/arrow.png could save 938B (89% reduction).

priority - 15 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://cm.send.microad.jp/fl/cm (expiration not specified)
http://otakomu-master.sakura.ne.jp/otakomu_parts/j…komu_tweet_rank1_sp.js (expiration not specified)
http://otakomu-master.sakura.ne.jp/otakomu_parts/js/otakomu_tweet_rank3.js (expiration not specified)
http://otaku.vis1.shinobi.jp/js/ (expiration not specified)
http://x8.sarashi.com/ufo/147876800 (expiration not specified)
https://assets.gunosy.com/adnet/gunosy_ads.min.js (expiration not specified)
https://assets.gunosy.com/adnet/gunosy_slide_ads.min.js (expiration not specified)
https://file.ziyu.net/rranking.gif (expiration not specified)
https://prague-mark.adtdp.com/cs/fluct (expiration not specified)
https://j.zucks.net.zimg.jp/j?f=356927 (5 minutes)
https://j.zucks.net.zimg.jp/j?f=229817 (5 minutes)
https://blogroll.livedoor.net/23039/roll_data (10 minutes)
http://connect.facebook.net/ja_JP/sdk.js (20 minutes)
http://0taku.livedoor.biz/JS/blogroll.js (60 minutes)
http://0taku.livedoor.biz/img/arrow.png (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000048826 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073630 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000073658 (60 minutes)
https://cdn-fluct.sh.adingo.jp/f.js?G=1000082319 (60 minutes)
https://gum.criteo.com/sync?c=46&r=2&j=handleData (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

priority - 7 Reduce server response time

In our test, your server responded in 0.69 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.

priority - 4 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 34.8KiB (64% reduction).

Compressing http://0taku.livedoor.biz/JS/blogroll.js could save 10.7KiB (76% reduction).
Compressing http://otakomu-master.sakura.ne.jp/otakomu_parts/j…komu_tweet_rank1_sp.js could save 4.4KiB (76% reduction).
Compressing https://j.zucks.net.zimg.jp/j?f=356927 could save 3.7KiB (58% reduction).
Compressing https://j.zucks.net.zimg.jp/j?f=229817 could save 3.7KiB (58% reduction).
Compressing http://otakomu-master.sakura.ne.jp/otakomu_parts/js/otakomu_tweet_rank3.js could save 3.1KiB (69% reduction).
Compressing https://image6.pubmatic.com/AdServer/PugMaster?rnd…nsent=&sec=1&kdntuid=1 could save 2.4KiB (67% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000048826 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073630 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000073658 could save 1.2KiB (51% reduction).
Compressing https://cdn-fluct.sh.adingo.jp/f.js?G=1000082319 could save 1.2KiB (51% reduction).
Compressing http://xid.i-mobile.co.jp/RestoreXidToMediaStorage.html could save 789B (59% reduction).
Compressing http://clt.a-i-ad.com/api/mk?mkid=431 could save 609B (60% reduction).
Compressing http://otakomu.jp/wp-content/themes/otkm13/js/index.js could save 327B (42% reduction).
Compressing http://st.shinobi.jp/img/services/admaxdsp/static/javascripts/trac.js could save 314B (39% reduction).
Compressing https://sh.zucks.net/opt/json/api/v2?f=229817&rnd=…%3A%2F%2Fotakomu.jp%2F could save 189B (22% reduction).

priority - 1 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 6.4KiB (20% reduction).

Minifying http://otakomu.jp/wp-content/themes/otkm13/css/ionic.css could save 3.4KiB (22% reduction) after compression.
Minifying http://otakomu.jp/wp-content/themes/otkm13/style.css could save 1.4KiB (17% reduction) after compression.
Minifying http://otakomu.jp/wp-content/themes/otkm13/style_sp.css could save 1.2KiB (17% reduction) after compression.
Minifying http://otakomu.jp/wp-content/plugins/wordpress-pop…tyle/wpp.css?ver=3.3.3 could save 304B (58% reduction) after compression.

priority - 1 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 5.2KiB (34% reduction).

Minifying http://0taku.livedoor.biz/JS/blogroll.js could save 4.7KiB (34% reduction).
Minifying http://otakomu.jp/wp-content/themes/otkm13/js/index.js could save 298B (38% reduction).
Minifying http://clt.a-i-ad.com/api/mk?mkid=431 could save 242B (25% reduction).

priority - 0 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 3.4KiB (14% reduction).

Minifying http://otakomu.jp/ could save 3KiB (13% reduction) after compression.
Minifying http://xid.i-mobile.co.jp/RestoreXidToMediaStorage.html could save 428B (33% reduction).

otakomu.jp Mobile Resources

Total Resources242
Number of Hosts75
Static Resources91
JavaScript Resources42
CSS Resources5

otakomu.jp Mobile Resource Breakdown

otakomu.jp mobile page usability

Last tested: 2018-10-07


Mobile Usability Good
99/100

otakomu.jp Mobile Usability Test Quick Summary


priority - 0 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 <button class="no-pc fb butto…button-primary"></button> is close to 1 other tap targets.

The tap target <a href="fb://profile/435865549854582"></a> is close to 1 other tap targets.

The tap target <a href="fb://profile/435865549854582"></a> is close to 1 other tap targets.

otakomu.jp similar domains

Similar domains:
www.otakomu.com
www.otakomu.net
www.otakomu.org
www.otakomu.info
www.otakomu.biz
www.otakomu.us
www.otakomu.mobi
www.takomu.jp
www.otakomu.jp
www.itakomu.jp
www.oitakomu.jp
www.iotakomu.jp
www.ktakomu.jp
www.oktakomu.jp
www.kotakomu.jp
www.ltakomu.jp
www.oltakomu.jp
www.lotakomu.jp
www.ptakomu.jp
www.optakomu.jp
www.potakomu.jp
www.oakomu.jp
www.orakomu.jp
www.otrakomu.jp
www.ortakomu.jp
www.ofakomu.jp
www.otfakomu.jp
www.oftakomu.jp
www.ogakomu.jp
www.otgakomu.jp
www.ogtakomu.jp
www.oyakomu.jp
www.otyakomu.jp
www.oytakomu.jp
www.otkomu.jp
www.otqkomu.jp
www.otaqkomu.jp
www.otqakomu.jp
www.otwkomu.jp
www.otawkomu.jp
www.otwakomu.jp
www.otskomu.jp
www.otaskomu.jp
www.otsakomu.jp
www.otzkomu.jp
www.otazkomu.jp
www.otzakomu.jp
www.otaomu.jp
www.otajomu.jp
www.otakjomu.jp
www.otajkomu.jp
www.otaiomu.jp
www.otakiomu.jp
www.otaikomu.jp
www.otamomu.jp
www.otakmomu.jp
www.otamkomu.jp
www.otalomu.jp
www.otaklomu.jp
www.otalkomu.jp
www.otaoomu.jp
www.otakoomu.jp
www.otaokomu.jp
www.otakmu.jp
www.otakimu.jp
www.otakoimu.jp
www.otakkmu.jp
www.otakokmu.jp
www.otakkomu.jp
www.otaklmu.jp
www.otakolmu.jp
www.otakpmu.jp
www.otakopmu.jp
www.otakpomu.jp
www.otakou.jp
www.otakonu.jp
www.otakomnu.jp
www.otakonmu.jp
www.otakoju.jp
www.otakomju.jp
www.otakojmu.jp
www.otakoku.jp
www.otakomku.jp
www.otakom.jp
www.otakomy.jp
www.otakomuy.jp
www.otakomyu.jp
www.otakomh.jp
www.otakomuh.jp
www.otakomhu.jp
www.otakomj.jp
www.otakomuj.jp
www.otakomi.jp
www.otakomui.jp
www.otakomiu.jp

otakomu.jp Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


otakomu.jp TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.