BACKLOG.JP Backlog|チームで使うプロジェクト管理・タスク管理ツール

backlog.jp Website Information

Daily Unique Visits: 2,513

Daily Page Views: 7,539

Income Per Day: $23

Estimated Value: $8,280

backlog.jp is registered under .JP top-level domain. Please check other sites in .JP zone.

No name server records were found.

and is probably hosted by AMAZON-AES - Amazon.com, Inc., US. See the full list of other websites hosted by AMAZON-AES - Amazon.com, Inc., US.

The highest website backlog.jp position in Alexa rank database was 400292 and the lowest rank position was 496440. Current position of backlog.jp in Alexa rank database is 428097.

Desktop speed score of backlog.jp (85/100) is better than the results of 80% of other sites and shows that the page is performing great on desktop computers.

Mobile usability score of backlog.jp (68/100) is better than the results of 19.67% of other sites and means that the page is not mobile-friendly.

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

Advertisement

backlog.jp Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


backlog.jp whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


[ 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 xxx/e'. ]
Domain Information: [ドメイン情報]
[Domain Name] BACKLOG.JP

[登録者名] Nulab Inc.
[Registrant] Nulab Inc.

[Name Server] ns-1694.awsdns-19.co.uk
[Name Server] ns-481.awsdns-60.com
[Name Server] ns-604.awsdns-11.net
[Name Server] ns-1384.awsdns-45.org
[Signing Key]

[登録年月日] 2005/03/08
[有効期限] 2025/03/31
[状態] Active
[最終更新] 2024/04/01 01:05:04 (JST)

Contact Information: [公開連絡窓口]
[名前] Masanori Hashimoto
[Name] Masanori Hashimoto
[Email] bb7423386447e53a7572de3fe22f0599-7131533@contact.gandi.net
[Web Page]
[郵便番号] 810-0041
[住所] 1-8-6 Daimyo, HCC BLD.
Fukuoka
[Postal Address] 1-8-6 Daimyo, HCC BLD.
Fukuoka
[電話番号] +81.927525231
[FAX番号]

backlog.jp server information

Servers Location

backlog.jp desktop page speed rank

Last tested: 2019-12-04


Desktop Speed Good
85/100

backlog.jp Desktop Speed Test Quick Summary


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

Your page has 3 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://static.zdassets.com/hc/assets/jquery-d5395…27403fc17855c46dbfc.js
https://use.typekit.net/zkw7fsx.js
https://p19.zdassets.com/hc/theming_assets/759768/…js?digest=360420895233

Optimize CSS Delivery of the following:

https://static.zdassets.com/hc/assets/application-…8fe3c4f62d8d644bc6.css
https://static.zdassets.com/hc/assets/theming_v1_s…fe398d782b729b53ac.css
https://p19.zdassets.com/hc/theming_assets/759768/…ss?digest=360420895233

priority - 4Leverage 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:

https://static.zdassets.com/answer_bot_embeddable/answerBot.js (10 minutes)
https://use.typekit.net/zkw7fsx.js (10 minutes)
https://static.zdassets.com/hc/assets/application-…8fe3c4f62d8d644bc6.css (11.3 minutes)
https://static.zdassets.com/hc/assets/hc_enduser-6…11c421fa1a4f058cde4.js (11.3 minutes)
https://static.zdassets.com/hc/assets/jquery-d5395…27403fc17855c46dbfc.js (11.3 minutes)
https://static.zdassets.com/hc/assets/locales/ja-4…31d8c116b17a08664c7.js (11.3 minutes)
https://static.zdassets.com/hc/assets/theming_v1_s…fe398d782b729b53ac.css (11.3 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 1Minify 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.5KiB (18% reduction).

Minifying https://static.zdassets.com/hc/assets/application-…8fe3c4f62d8d644bc6.css could save 3.4KiB (19% reduction) after compression.
Minifying https://p19.zdassets.com/hc/theming_assets/759768/…ss?digest=360420895233 could save 3.1KiB (17% reduction) after compression.

priority - 0Reduce server response time

In our test, your server responded in 0.24 seconds.

priority - 0Minify 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 2.6KiB (49% reduction).

Minifying https://p19.zdassets.com/hc/theming_assets/759768/…js?digest=360420895233 could save 2.6KiB (49% reduction) after compression.

backlog.jp Desktop Resource Breakdown

Total Resources32
Number of Hosts11
Static Resources21
JavaScript Resources9
CSS Resources3

backlog.jp mobile page speed rank

Last tested: 2017-06-06


Mobile Speed Bad
56/100

backlog.jp Mobile Speed Test Quick Summary


priority - 40Eliminate 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.

Remove render-blocking JavaScript:

http://www.backlog.jp/wp-includes/js/jquery/jquery.js?ver=1.12.4
http://www.backlog.jp/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
http://www.backlog.jp/js/jquery.url.js?ver=4.7.2
http://www.backlog.jp/js/common.backlog.js?ver=4.7.2
https://use.typekit.net/zkw7fsx.js
http://www.backlog.jp/js/google.analytics.js
http://www.backlog.jp/js/mixpanel.js

Optimize CSS Delivery of the following:

http://www.backlog.jp/css/generic.css
http://www.backlog.jp/css/home.css?ver=4.7.2
http://fonts.googleapis.com/css?family=Cabin:400,700
http://www.backlog.jp/wp-content/plugins/contact-f…s/styles.css?ver=4.6.1

priority - 29Leverage 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://www.backlog.jp/css/generic.css (expiration not specified)
http://www.backlog.jp/img/common/content/btn_backTop.png (expiration not specified)
http://www.backlog.jp/img/common/footer/btn_langPickDown.png (expiration not specified)
http://www.backlog.jp/img/common/footer/ico_world.png (expiration not specified)
http://www.backlog.jp/img/common/footer/mark_breadcrumbs_home.png (expiration not specified)
http://www.backlog.jp/img/common/footer/mark_privacy.png (expiration not specified)
http://www.backlog.jp/img/common/footer/new/icon_facebook.png (expiration not specified)
http://www.backlog.jp/img/common/footer/new/icon_googleplus.png (expiration not specified)
http://www.backlog.jp/img/common/footer/new/icon_linkedin.png (expiration not specified)
http://www.backlog.jp/img/common/footer/new/icon_twitter.png (expiration not specified)
http://www.backlog.jp/img/common/footer/new/logo_cacoo.png (expiration not specified)
http://www.backlog.jp/img/common/footer/new/logo_typetalk.png (expiration not specified)
http://www.backlog.jp/img/common/header/logo_site@2x.png (expiration not specified)
http://www.backlog.jp/img/common/icon/icon_close@2x.png (expiration not specified)
http://www.backlog.jp/img/common/px.gif (expiration not specified)
http://www.backlog.jp/img/home/bg_hero_balloon.png (expiration not specified)
http://www.backlog.jp/img/home/bg_hero_ja.png (expiration not specified)
http://www.backlog.jp/img/home/btn_register_arrow.png (expiration not specified)
http://www.backlog.jp/img/home/ico_burndown.png (expiration not specified)
http://www.backlog.jp/img/home/ico_gantt.png (expiration not specified)
http://www.backlog.jp/img/home/ico_management.png (expiration not specified)
http://www.backlog.jp/img/home/ico_mobile.png (expiration not specified)
http://www.backlog.jp/img/home/ico_versionControl.png (expiration not specified)
http://www.backlog.jp/img/home/ico_wiki.png (expiration not specified)
http://www.backlog.jp/img/home/img_component1.png (expiration not specified)
http://www.backlog.jp/img/home/img_component2.png (expiration not specified)
http://www.backlog.jp/img/home/img_component3.png (expiration not specified)
http://www.backlog.jp/img/home/logo/gungho.png (expiration not specified)
http://www.backlog.jp/img/home/logo/his.png (expiration not specified)
http://www.backlog.jp/img/home/logo/idom.png (expiration not specified)
http://www.backlog.jp/img/home/logo/omron.png (expiration not specified)
http://www.backlog.jp/img/home/logo/softbank_robotics.png (expiration not specified)
http://www.backlog.jp/img/support/ico_faq@2x.png (expiration not specified)
http://www.backlog.jp/img/tour/ico_paging_next.png (expiration not specified)
http://www.backlog.jp/js/google.analytics.js (expiration not specified)
http://www.backlog.jp/js/mixpanel.js (expiration not specified)
https://use.typekit.net/zkw7fsx.js (10 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-C9J9 (15 minutes)
http://www.google-analytics.com/ga.js (2 hours)

priority - 12Enable 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 116.3KiB (67% reduction).

Compressing http://www.backlog.jp/wp-includes/js/jquery/jquery.js?ver=1.12.4 could save 61.9KiB (65% reduction).
Compressing http://www.backlog.jp/css/generic.css could save 21.5KiB (77% reduction).
Compressing http://www.backlog.jp/wp-content/plugins/contact-f…?ver=3.51.0-2014.06.20 could save 9.2KiB (61% reduction).
Compressing http://www.backlog.jp/wp-content/plugins/contact-f…s/scripts.js?ver=4.6.1 could save 8.6KiB (73% reduction).
Compressing http://www.backlog.jp/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1 could save 5.9KiB (60% reduction).
Compressing http://www.backlog.jp/css/home.css?ver=4.7.2 could save 5.3KiB (74% reduction).
Compressing http://www.backlog.jp/js/jquery.config.js?ver%5B0%5D=jquery could save 1.3KiB (56% reduction).
Compressing http://www.backlog.jp/js/jquery.url.js?ver=4.7.2 could save 1.1KiB (57% reduction).
Compressing http://www.backlog.jp/wp-content/plugins/contact-f…s/styles.css?ver=4.6.1 could save 961B (60% reduction).
Compressing http://www.backlog.jp/wp-includes/js/wp-embed.min.js?ver=4.7.2 could save 647B (47% reduction).

priority - 1Optimize images

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

Optimize the following images to reduce their size by 12.6KiB (24% reduction).

Compressing http://www.backlog.jp/img/home/img_component2.png could save 2KiB (13% reduction).
Compressing http://www.backlog.jp/img/home/logo/softbank_robotics.png could save 1.4KiB (29% reduction).
Compressing http://www.backlog.jp/img/common/footer/new/logo_typetalk.png could save 1.3KiB (37% reduction).
Compressing http://www.backlog.jp/img/common/footer/new/icon_twitter.png could save 1.3KiB (41% reduction).
Compressing http://www.backlog.jp/img/home/img_component1.png could save 1.2KiB (19% reduction).
Compressing http://www.backlog.jp/img/common/footer/new/icon_googleplus.png could save 1.2KiB (38% reduction).
Compressing http://www.backlog.jp/img/common/footer/new/logo_cacoo.png could save 1KiB (38% reduction).
Compressing http://www.backlog.jp/img/common/footer/new/icon_linkedin.png could save 1KiB (43% reduction).
Compressing http://www.backlog.jp/img/common/footer/new/icon_facebook.png could save 910B (45% reduction).
Compressing http://www.backlog.jp/img/common/header/logo_site@2x.png could save 872B (12% reduction).
Compressing http://www.backlog.jp/img/home/logo/his.png could save 523B (30% reduction).

priority - 0Minify 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 2KiB (18% reduction).

Minifying http://www.backlog.jp/wp-content/plugins/contact-f…s/scripts.js?ver=4.6.1 could save 2KiB (18% reduction).

priority - 0Minify 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 1.8KiB (24% reduction).

Minifying http://www.backlog.jp/ could save 1.8KiB (24% reduction) after compression.

backlog.jp Mobile Resource Breakdown

Total Resources67
Number of Hosts13
Static Resources43
JavaScript Resources18
CSS Resources4

backlog.jp mobile page usability

Last tested: 2017-06-06


Mobile Usability Medium
68/100

backlog.jp Mobile Usability Test Quick Summary


priority - 21Use 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.

Backlogの初心者向け無料セミナーを開催します。 renders only 5 pixels tall (13 CSS pixels).

東京会場:6/20(火)・2…:6/27(火)・28(木) renders only 5 pixels tall (13 CSS pixels).

エンタープライズ and 3 others render only 5 pixels tall (13 CSS pixels).

ログイン renders only 5 pixels tall (12 CSS pixels).

Backlogは、毎日の仕事…に、チームを、もっと明るく、 and 1 others render only 6 pixels tall (16 CSS pixels).

バーンダウンチャート and 5 others render only 5 pixels tall (12 CSS pixels).

全プラン無料お試し30日間!お申込み後すぐにお使い頂けます。 renders only 6 pixels tall (16 CSS pixels).

操作が簡単で分かりやすい and 5 others render only 7 pixels tall (18 CSS pixels).

Backlogは、プロジェク…ト管理&課題管理ができます。 and 2 others render only 5 pixels tall (14 CSS pixels).

ツアーを見る renders only 6 pixels tall (15 CSS pixels).

ホーム renders only 5 pixels tall (12 CSS pixels).

ヌーラボのサービス and 2 others render only 5 pixels tall (14 CSS pixels).

サルでもわかるプロジェクト管理入門 and 27 others render only 5 pixels tall (13 CSS pixels).

Backlogについて and 1 others render only 5 pixels tall (14 CSS pixels).

日本語 renders only 5 pixels tall (12 CSS pixels).
プライバシーポリシー and 1 others render only 5 pixels tall (13 CSS pixels).
Nulab Inc. is…ered in Japan. and 1 others render only 5 pixels tall (13 CSS pixels).

priority - 13Size 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://www.bac…ur/?ref=footer">ツアー</a> and 26 others are close to other tap targets.

The tap target <a href="http://www.bac…rt/?ref=footer">サポート</a> and 1 others are close to other tap targets.

The tap target <a href="https://cacoo.com/">オンライン作図ツール</a> is close to 1 other tap targets.

The tap target <a href="https://typetalk.in/">チームメッセージアプリ</a> is close to 1 other tap targets.

The tap target <a href="https://typetalk.in/">チームメッセージアプリ</a> is close to 1 other tap targets.

The tap target <a href="https://www.fa…om/Backlogapp/"></a> and 3 others are close to other tap targets.

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 3Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,005 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <h4>スペースIDを入力してください</h4> falls outside the viewport.
The element <p class="faq-link">スペースIDとは?</p> falls outside the viewport.
The element <a id="closeDropdown" href="javascript:void(0)" class="close-dropdown"> falls outside the viewport.

backlog.jp HTML validation

Errors

Attribute “xmlns:og” not allowed here.

Line: 6 Column: 31 - 152
"...IE)]><!--> <html lang="ja" prefix="og: http://ogp.me/ns#" xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml"> <!--<..."

Attribute “xmlns:fb” not allowed here.

Line: 6 Column: 31 - 152
"...IE)]><!--> <html lang="ja" prefix="og: http://ogp.me/ns#" xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml"> <!--<..."

Bad value “https://api.w.org/” for attribute “rel” on element “link”: The string “https://api.w.org/” is not a registered keyword.

Line: 48 Column: 1 - 72
"...</script> <link rel='https://api.w.org/' href='https://www.backlog.jp/wp-json/' /> ..."

Stray end tag “head”.

Line: 66 Column: 5 - 11
"...l --> </head> <..."

Start tag “body” seen but an element of the same type was already open.

Line: 67 Column: 5 - 53
"...head> <body class="home blog two-column right-sidebar"> ..."

Cannot recover after last error. Any further errors will be ignored.

Line: 67 Column: 5 - 53
"...head> <body class="home blog two-column right-sidebar"> ..."

Warnings

Attribute with the local name “xmlns:og” is not serializable as XML 1.0.

Line: 6 Column: 31 - 152
"...IE)]><!--> <html lang="ja" prefix="og: http://ogp.me/ns#" xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml"> <!--<..."

Attribute with the local name “xmlns:fb” is not serializable as XML 1.0.

Line: 6 Column: 31 - 152
"...IE)]><!--> <html lang="ja" prefix="og: http://ogp.me/ns#" xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml"> <!--<..."

Consider avoiding viewport values that prevent users from resizing documents.

Line: 9 Column: 9 - 114
"...> <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=0"> ..."

backlog.jp similar domains

Similar domains:
www.backlog.com
www.backlog.net
www.backlog.org
www.backlog.info
www.backlog.biz
www.backlog.us
www.backlog.mobi
www.acklog.jp
www.backlog.jp
www.vacklog.jp
www.bvacklog.jp
www.vbacklog.jp
www.gacklog.jp
www.bgacklog.jp
www.gbacklog.jp
www.hacklog.jp
www.bhacklog.jp
www.hbacklog.jp
www.nacklog.jp
www.bnacklog.jp
www.nbacklog.jp
www.bcklog.jp
www.bqcklog.jp
www.baqcklog.jp
www.bqacklog.jp
www.bwcklog.jp
www.bawcklog.jp
www.bwacklog.jp
www.bscklog.jp
www.bascklog.jp
www.bsacklog.jp
www.bzcklog.jp
www.bazcklog.jp
www.bzacklog.jp
www.baklog.jp
www.baxklog.jp
www.bacxklog.jp
www.baxcklog.jp
www.badklog.jp
www.bacdklog.jp
www.badcklog.jp
www.bafklog.jp
www.bacfklog.jp
www.bafcklog.jp
www.bavklog.jp
www.bacvklog.jp
www.bavcklog.jp
www.baclog.jp
www.bacjlog.jp
www.backjlog.jp
www.bacjklog.jp
www.bacilog.jp
www.backilog.jp
www.baciklog.jp
www.bacmlog.jp
www.backmlog.jp
www.bacmklog.jp
www.bacllog.jp
www.backllog.jp
www.baclklog.jp
www.bacolog.jp
www.backolog.jp
www.bacoklog.jp
www.backog.jp
www.backpog.jp
www.backlpog.jp
www.backplog.jp
www.backoog.jp
www.backloog.jp
www.backkog.jp
www.backlkog.jp
www.backklog.jp
www.backlg.jp
www.backlig.jp
www.backloig.jp
www.backliog.jp
www.backlkg.jp
www.backlokg.jp
www.backllg.jp
www.backlolg.jp
www.backlpg.jp
www.backlopg.jp
www.backlo.jp
www.backlof.jp
www.backlogf.jp
www.backlofg.jp
www.backlov.jp
www.backlogv.jp
www.backlovg.jp
www.backlot.jp
www.backlogt.jp
www.backlotg.jp
www.backlob.jp
www.backlogb.jp
www.backlobg.jp
www.backloy.jp
www.backlogy.jp
www.backloyg.jp
www.backloh.jp
www.backlogh.jp
www.backlohg.jp

backlog.jp Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


backlog.jp TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.