NEKOMEMO.COM 〓 ねこメモ 〓


nekomemo.com website information.

nekomemo.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

No name server records were found.

and probably website nekomemo.com 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 nekomemo.com position was 13370 (in the world). The lowest Alexa rank position was 999973. Now website nekomemo.com ranked in Alexa database as number 964219 (in the world).

Website nekomemo.com Desktop speed measurement score (74/100) is better than the results of 57.94% of other sites shows that the page desktop performance can be improved.

nekomemo.com 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 nekomemo.com (55/100) is better than the results of 43.86% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Mar-04-2024 964,21923,970
Mar-03-2024 988,189-6,449
Mar-02-2024 981,7403,422
Mar-01-2024 985,16211,205
Feb-29-2024 996,367-4,800
Feb-28-2024 991,567-8,581
Feb-27-2024 982,9861,361

Advertisement

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



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


Domain Name: NEKOMEMO.COM
Registry Domain ID: 1756032931_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.discount-domain.com
Registrar URL: http://gmo.jp
Updated Date: 2020-10-05T11:46:03Z
Creation Date: 2012-10-31T08:29:35Z
Registry Expiry Date: 2021-10-31T08:29:35Z
Registrar: GMO Internet, Inc. d/b/a Onamae.com
Registrar IANA ID: 49
Registrar Abuse Contact Email: abuse@gmo.jp
Registrar Abuse Contact Phone: +81.337709199
Domain Status: ok https://icann.org/epp#ok
Name Server: NS1.DOMAINKING.CLOUD
Name Server: NS2.DOMAINKING.CLOUD
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-04-25T07:55:43Z

nekomemo.com server information

Servers Location

IP Address
Country
Region
City

nekomemo.com desktop page speed rank

Last tested: 2019-12-07


Desktop Speed Medium
74/100

nekomemo.com Desktop Speed Test Quick Summary


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://a248.e.akamai.net/f/248/45380/24h/img.rc.im…p/rc/dn/doko/js2/ad.js (expiration not specified)
http://blog.with2.net/img/banner/c/banner_1/br_c_1348_1.gif (expiration not specified)
http://blogroll.livedoor.net/blogroll/banner/freead-banner-192x76.jpg (expiration not specified)
http://blogroll.livedoor.net/blogroll/banner/pcad-banner-192x76.jpg (expiration not specified)
http://blogroll.livedoor.net/css/default2.css (expiration not specified)
http://blogroll.livedoor.net/js/blogroll.js (expiration not specified)
http://clicktrack.ziyu.net/js/2894.js (expiration not specified)
http://file.ziyu.net/rranking.gif (expiration not specified)
http://nekomemo.com/settings/ad.js (expiration not specified)
http://nekomemo.com/settings/header.js (expiration not specified)
http://pranking3.ziyu.net/rranking.gif (expiration not specified)
http://rranking3.ziyu.net/rranking.gif (expiration not specified)
http://x5.yukishigure.com/ufo/095541500 (expiration not specified)
http://blogroll.livedoor.net/33459/roll_data (10 minutes)
http://blogroll.livedoor.net/33460/roll_data (10 minutes)
http://blogroll.livedoor.net/49506/roll_data (10 minutes)
http://blogroll.livedoor.net/49507/roll_data (10 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
http://nekomemo.com/parts/birdcall_title_alpha.png (60 minutes)
http://nekomemo.com/parts/icon_set.png (60 minutes)
http://nekomemo.com/parts/more.png (60 minutes)
http://nekomemo.com/parts/random-top-gazou.js (60 minutes)
http://nekomemo.com/parts/wallpaper.png (60 minutes)
http://nekomemo.com/twitt_bell.js (60 minutes)
http://nekomemo.com/widget.js (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)
http://cdn.b.st-hatena.com/images/users/gif/normal/00123.gif (2.8 hours)
http://cdn.b.st-hatena.com/images/users/gif/normal/00001.gif (6.3 hours)
http://cdn.b.st-hatena.com/images/users/gif/normal/00000.gif (6.9 hours)
http://cdn.b.st-hatena.com/images/users/gif/normal/00004.gif (7.1 hours)
http://cdn.b.st-hatena.com/images/users/gif/normal/00002.gif (8.1 hours)
http://cdn.b.st-hatena.com/images/users/gif/normal/00006.gif (10.3 hours)

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

Your page has 6 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://parts.blog.livedoor.jp/js/jquery-1.8.0.min.js
http://nekomemo.com/parts/random-top-gazou.js
http://parts.blog.livedoor.jp/js/c2.js
http://parts.blog.livedoor.jp/js/smartphone.js?v=20131007
http://nekomemo.com/settings/header.js
http://nekomemo.com/settings/ad.js

Optimize CSS Delivery of the following:

http://parts.blog.livedoor.jp/css/template.css?v=20130404
http://nekomemo.com/site.css?_=20150523030136

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 49KiB (76% reduction).

Compressing http://nekomemo.com/twitt_bell.js could save 15.4KiB (82% reduction).
Compressing http://blogroll.livedoor.net/js/blogroll.js could save 11.8KiB (78% reduction).
Compressing http://nekomemo.com/widget.js could save 6.1KiB (74% reduction).
Compressing http://js.kau.li/ssp.js?count=1 could save 4.7KiB (68% reduction).
Compressing http://js.kau.li/ssp.js?count=2 could save 4.7KiB (68% reduction).
Compressing http://nekomemo.com/parts/random-top-gazou.js could save 3.2KiB (89% reduction).
Compressing http://ad.kau.li/?url=http%3A%2F%2Fnekomemo.com%2F…F65100&id=17535&mnum=3 could save 1.1KiB (56% reduction).
Compressing http://ad.kau.li/?url=http%3A%2F%2Fnekomemo.com%2F…F65100&id=17535&mnum=3 could save 1.1KiB (53% reduction).
Compressing http://blogroll.livedoor.net/css/default2.css could save 889B (69% reduction).

priority - 3 Optimize images

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

Optimize the following images to reduce their size by 17.5KiB (18% reduction).

Losslessly compressing http://blog-imgs-30.fc2.com/n/e/k/nekomemo22/neko018.jpg could save 4.8KiB (15% reduction).
Losslessly compressing http://nekomemo.com/parts/icon_set.png could save 4.3KiB (36% reduction).
Losslessly compressing http://livedoor.blogimg.jp/nekomemo/imgs/3/2/32d51cf3.png could save 3.7KiB (16% reduction).
Losslessly compressing http://nekomemo.com/parts/more.png could save 1.5KiB (40% reduction).
Losslessly compressing http://blogroll.livedoor.net/blogroll/banner/freead-banner-192x76.jpg could save 939B (7% reduction).
Losslessly compressing http://blogroll.livedoor.net/blogroll/banner/pcad-banner-192x76.jpg could save 922B (8% reduction).
Losslessly compressing http://blogroll.livedoor.net/img/blank.gif?channel_id=49506 could save 712B (88% reduction).
Losslessly compressing http://blogroll.livedoor.net/img/blank.gif?channel_id=49507 could save 712B (88% reduction).

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

Minifying http://blogroll.livedoor.net/js/blogroll.js could save 5.1KiB (34% reduction).
Minifying http://nekomemo.com/widget.js could save 3.4KiB (42% reduction).
Minifying http://js.kau.li/ssp.js?count=1 could save 1.9KiB (28% reduction).
Minifying http://js.kau.li/ssp.js?count=2 could save 1.9KiB (28% reduction).
Minifying http://b.st-hatena.com/js/bookmark_button.js could save 1.9KiB (23% reduction) after compression.
Minifying http://parts.blog.with2.net/2.0/?id=863629:qNgl0P9Xz7E&c=white could save 1,022B (3% reduction) after compression.
Minifying http://parts.blog.livedoor.jp/plugin/popular_artic…e_plugin.js?v=20130911 could save 872B (26% reduction) after compression.

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

Minifying http://nekomemo.com/site.css?_=20150523030136 could save 2.5KiB (32% reduction) after compression.
Minifying http://parts.blog.livedoor.jp/css/template.css?v=20130404 could save 1.6KiB (27% reduction) after compression.

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

Minifying http://nekomemo.com/ could save 2.8KiB (8% reduction) after compression.

nekomemo.com Desktop Resources

Total Resources249
Number of Hosts31
Static Resources122
JavaScript Resources36
CSS Resources4

nekomemo.com Desktop Resource Breakdown

nekomemo.com mobile page speed rank

Last tested: 2018-10-07


Mobile Speed Bad
55/100

nekomemo.com Mobile Speed Test Quick Summary


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

Your page has 13 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://parts.blog.livedoor.jp/js/lite2/common.js?v=20150425
http://parts.blog.livedoor.jp/js/lite2/main.js?v=20180620
http://parts.blog.livedoor.jp/js/jquery-1.11.1.min.js
http://parts.blog.livedoor.jp/js/jquery.cookie.min.js
http://parts.blog.livedoor.jp/js/micro_template.js
http://parts.blog.livedoor.jp/js/c2.js
http://nekomemo.com/settings/lite2/ads.js
http://js.ad-stir.com/js/nativeapi.js
http://api.unthem.com/js/spad.js?zname=spad0020&re…d=5480043&_=5907622380
https://js.ad-stir.com/js/adstir.js?20130527
http://ad.ad-stir.com/ad?app_id=MEDIA-759075f2&ad_…B4158870457A4481974656
http://spad.i-mobile.co.jp/script/adssp.js?20110215
http://spad.i-mobile.co.jp/script/adcore_sp_inline-0.2.js?20110201

Optimize CSS Delivery of the following:

http://parts.blog.livedoor.jp/css/lite2/common.css?201810041057
http://parts.blog.livedoor.jp/css/lite2/usr/basic2013.css?20160714

priority - 18 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 178KiB (73% reduction).

Compressing http://parts.blog.livedoor.jp/css/lite2/common.css?201810041057 could save 87.9KiB (81% reduction).
Compressing http://parts.blog.livedoor.jp/js/jquery-1.11.1.min.js could save 61.1KiB (65% reduction).
Compressing http://parts.blog.livedoor.jp/js/lite2/main.js?v=20180620 could save 14KiB (77% reduction).
Compressing http://parts.blog.livedoor.jp/js/lite2/common.js?v=20150425 could save 4.7KiB (63% reduction).
Compressing http://parts.blog.livedoor.jp/css/lite2/usr/basic2013.css?20160714 could save 4.7KiB (76% reduction).
Compressing http://parts.blog.livedoor.jp/js/c2.js could save 3.1KiB (65% reduction).
Compressing http://parts.blog.livedoor.jp/js/jquery.cookie.min.js could save 1,021B (54% reduction).
Compressing http://parts.blog.livedoor.jp/js/micro_template.js could save 806B (54% reduction).
Compressing http://xid.i-mobile.co.jp/RestoreXidToMediaStorage.html could save 789B (59% 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://nekomemo.com/_/json/blog_news_sp_kind_1.json (expiration not specified)
http://nekomemo.com/_/json/blog_news_sp_kind_map.json (expiration not specified)
http://nekomemo.com/_/json/ranking_category_min_66.json (expiration not specified)
http://nekomemo.com/settings/lite2/ads.js (expiration not specified)
https://blogroll.livedoor.net/url/http://2ch-c.net/?gt=20181007121501 (2 minutes)
https://blogroll.livedoor.net/url/http://2ch-c.net/?gt=20181008065501 (2 minutes)
https://blogroll.livedoor.net/url/http://blog.live…l/?id=5754821_52486241 (2 minutes)
https://blogroll.livedoor.net/url/http://giko-news.com/archives/5789960 (2 minutes)
https://blogroll.livedoor.net/url/http://giko-news.com/archives/5793324 (2 minutes)
https://blogroll.livedoor.net/url/http://giko-news.com/archives/5793908 (2 minutes)
https://blogroll.livedoor.net/url/http://matomeant…om/feed/30000034230311 (2 minutes)
https://blogroll.livedoor.net/url/http://moudamepo…ate=17&date=1538629201 (2 minutes)
https://blogroll.livedoor.net/url/http://newmofu.d…2F%2F%3Aptth&noadult=1 (2 minutes)
https://blogroll.livedoor.net/url/http://newpuru.d…629552&c=all&noadult=1 (2 minutes)
https://blogroll.livedoor.net/url/http://nullpoant…om/feed/30000029391319 (2 minutes)
https://blogroll.livedoor.net/23554/roll_data (10 minutes)
http://cdn.api.b.hatena.ne.jp/entry/button/?url=ht…ut=simple&format=image (58.2 minutes)
http://js.ad-stir.com/js/adstir.js?20130527 (60 minutes)
http://js.ad-stir.com/js/nativeapi.js (60 minutes)
http://t.blog.livedoor.jp/u.js (60 minutes)
https://js.ad-stir.com/js/adstir.js?20130527 (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 3 Optimize images

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

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

Compressing http://spcdnsp.i-mobile.co.jp/ad_creative.ashx?advid=4997340&eid=3 could save 12.4KiB (44% reduction).
Compressing http://parts.blog.livedoor.jp/img/lite2/item/socia…ons/twitter_simple.png could save 1.4KiB (47% reduction).
Compressing http://parts.blog.livedoor.jp/img/lite2/item/social_buttons/line_simple.png could save 1.3KiB (45% reduction).
Compressing http://parts.blog.livedoor.jp/img/lite2/item/socia…tons/hatebu_simple.png could save 1.2KiB (48% reduction).
Compressing http://parts.blog.livedoor.jp/img/lite2/item/socia…ns/facebook_simple.png could save 1.1KiB (54% reduction).
Compressing http://parts.blog.livedoor.jp/img/lite2/noimage_s.png could save 1KiB (28% reduction).
Compressing http://parts.blog.livedoor.jp/img/lite2/icon_comment.png could save 954B (84% reduction).
Compressing http://parts.blog.livedoor.jp/img/cms_lite/common/icon/icon_forward.png could save 930B (83% reduction).
Compressing http://parts.blog.livedoor.jp/img/lite2/icon_new.png could save 897B (82% reduction).
Compressing http://parts.blog.livedoor.jp/img/lite2/arrow_pull.png could save 874B (72% reduction).
Compressing https://blogroll.livedoor.net/img/blank.gif?channe…=23554&_=1538954795279 could save 739B (91% reduction).
Compressing http://resize.blogsys.jp/5faba8b8784f7dbc1834a725f…/imgs/e/3/e3e2d890.png could save 349B (20% reduction).
Compressing http://resize.blogsys.jp/a42a4376b6a0778d1ba39b938…/imgs/7/3/7361ee6f.jpg could save 322B (23% reduction).
Compressing http://resize.blogsys.jp/8b7a9b40e8b2fee31f89bf46f…mgs/3/a/3a9e8336-s.jpg could save 315B (22% reduction).
Compressing http://resize.blogsys.jp/ab9c67a659b0b62285e8290b6…mgs/d/0/d073596f-s.jpg could save 315B (19% reduction).
Compressing http://parts.blog.livedoor.jp/img/lite2/icon_pager_first.png could save 236B (43% reduction).
Compressing http://parts.blog.livedoor.jp/img/lite2/icon_pager_last.png could save 219B (40% reduction).

priority - 2 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 16.1KiB (15% reduction).

Minifying http://parts.blog.livedoor.jp/css/lite2/common.css?201810041057 could save 14.8KiB (14% reduction).
Minifying http://parts.blog.livedoor.jp/css/lite2/usr/basic2013.css?20160714 could save 1.3KiB (22% reduction).

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 12.4KiB (31% reduction).

Minifying http://parts.blog.livedoor.jp/js/lite2/main.js?v=20180620 could save 6.1KiB (34% reduction).
Minifying http://parts.blog.livedoor.jp/js/lite2/common.js?v=20150425 could save 2.5KiB (34% reduction).
Minifying http://b.st-hatena.com/js/bookmark_button.js could save 1.9KiB (22% reduction) after compression.
Minifying http://parts.blog.livedoor.jp/js/c2.js could save 1KiB (22% reduction).
Minifying http://parts.blog.livedoor.jp/js/micro_template.js could save 866B (58% 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 428B (33% reduction).

Minifying http://xid.i-mobile.co.jp/RestoreXidToMediaStorage.html could save 428B (33% reduction).

nekomemo.com Mobile Resources

Total Resources86
Number of Hosts16
Static Resources68
JavaScript Resources25
CSS Resources2

nekomemo.com Mobile Resource Breakdown

nekomemo.com mobile page usability

Last tested: 2018-10-07


Mobile Usability Good
99/100

nekomemo.com 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 <a href="http://2ch-c.n…20181007121501" class="blogroll-link">ワイ「飯おごってやんよ」→会…イ「会計別々で」友「は!?」</a> and 9 others are close to other tap targets.
The tap target <a href="http://nav.cx/cNkU9VI" class="blogroll_ad_li…_portal_matome">会社の懇親会のビンゴで商品券…遣だからって差別しないで!」</a> is close to 1 other tap targets.

nekomemo.com similar domains

Similar domains:
www.nekomemo.com
www.nekomemo.net
www.nekomemo.org
www.nekomemo.info
www.nekomemo.biz
www.nekomemo.us
www.nekomemo.mobi
www.ekomemo.com
www.nekomemo.com
www.bekomemo.com
www.nbekomemo.com
www.bnekomemo.com
www.hekomemo.com
www.nhekomemo.com
www.hnekomemo.com
www.jekomemo.com
www.njekomemo.com
www.jnekomemo.com
www.mekomemo.com
www.nmekomemo.com
www.mnekomemo.com
www.nkomemo.com
www.nwkomemo.com
www.newkomemo.com
www.nwekomemo.com
www.nskomemo.com
www.neskomemo.com
www.nsekomemo.com
www.ndkomemo.com
www.nedkomemo.com
www.ndekomemo.com
www.nrkomemo.com
www.nerkomemo.com
www.nrekomemo.com
www.neomemo.com
www.nejomemo.com
www.nekjomemo.com
www.nejkomemo.com
www.neiomemo.com
www.nekiomemo.com
www.neikomemo.com
www.nemomemo.com
www.nekmomemo.com
www.nemkomemo.com
www.nelomemo.com
www.neklomemo.com
www.nelkomemo.com
www.neoomemo.com
www.nekoomemo.com
www.neokomemo.com
www.nekmemo.com
www.nekimemo.com
www.nekoimemo.com
www.nekkmemo.com
www.nekokmemo.com
www.nekkomemo.com
www.neklmemo.com
www.nekolmemo.com
www.nekpmemo.com
www.nekopmemo.com
www.nekpomemo.com
www.nekoemo.com
www.nekonemo.com
www.nekomnemo.com
www.nekonmemo.com
www.nekojemo.com
www.nekomjemo.com
www.nekojmemo.com
www.nekokemo.com
www.nekomkemo.com
www.nekommo.com
www.nekomwmo.com
www.nekomewmo.com
www.nekomwemo.com
www.nekomsmo.com
www.nekomesmo.com
www.nekomsemo.com
www.nekomdmo.com
www.nekomedmo.com
www.nekomdemo.com
www.nekomrmo.com
www.nekomermo.com
www.nekomremo.com
www.nekomeo.com
www.nekomeno.com
www.nekomemno.com
www.nekomenmo.com
www.nekomejo.com
www.nekomemjo.com
www.nekomejmo.com
www.nekomeko.com
www.nekomemko.com
www.nekomekmo.com
www.nekomem.com
www.nekomemi.com
www.nekomemoi.com
www.nekomemio.com
www.nekomemk.com
www.nekomemok.com
www.nekomeml.com
www.nekomemol.com
www.nekomemlo.com
www.nekomemp.com
www.nekomemop.com
www.nekomempo.com
www.nekomemo.con

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


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