JIG.JP スマホ(Android/iPhone)アプリ・携帯アプリならjig.jp(ジグジェイピー)

jig.jp Website Information

Daily Unique Visits: 11,111

Daily Page Views: 55,555

Income Per Day: $139

Estimated Value: $83,400

This website is located in Japan and is using following IP address 133.242.209.55. See the complete list of popular websites hosted in Japan.

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

Website jig.jp is using the following name servers:

  • dns3.jig.jp
  • dns4.jig.jp

and is probably hosted by SAKURA-A SAKURA Internet Inc., JP. See the full list of other websites hosted by SAKURA-A SAKURA Internet Inc., JP.

The highest website jig.jp position in Alexa rank database was 9937 and the lowest rank position was 982809. Current position of jig.jp in Alexa rank database is 122633.

Desktop speed score of jig.jp (65/100) is better than the results of 42.84% of other sites and shows that the page desktop performance can be improved.

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

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

Advertisement

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


jig.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] JIG.JP

[登録者名] 株式会社ジグジェイピー
[Registrant] jig.jp co.,ltd.

[Name Server] dns3.jig.jp
[Name Server] dns4.jig.jp
[Signing Key]

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

Contact Information: [公開連絡窓口]
[名前] 株式会社ジグジェイピー
[Name] jig.jp co., ltd.
[Email] domain-adm@jig.jp
[Web Page]
[郵便番号] 151-0051
[住所] 東京都渋谷区
千駄ヶ谷 5-23-5
代々木イースト 4F
[Postal Address] Shibuya-ku
5-23-5 Sendagaya
YOYOGI EAST 4F
[電話番号] 03-5367-3891
[FAX番号] 03-3350-1043

jig.jp server information

Servers Location

jig.jp desktop page speed rank

Last tested: 2017-05-20


Desktop Speed Medium
65/100

jig.jp Desktop Speed Test Quick Summary


priority - 33Optimize images

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

Optimize the following images to reduce their size by 324.6KiB (57% reduction).

Compressing http://jig.jp/wordpress/wp-content/uploads/2014/04…_image_kensakuplus.jpg could save 88.2KiB (70% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2014/04/slide_01.jpg could save 59.6KiB (61% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2014/04/sp_top_jigbrowser.jpg could save 42.5KiB (66% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2014/04/sp_top_kensakuplus.jpg could save 39.7KiB (67% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2014/04/top_jigbrowser.jpg could save 26.4KiB (66% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2014/04/top_kensakuplus.jpg could save 24.6KiB (67% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2017/05/slide_jigtwi.jpg could save 23.8KiB (43% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2016/06/sp_top_jigtwi_3.jpg could save 6KiB (23% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2016/06…jig_browser_plus_2.jpg could save 5.8KiB (21% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2016/06…jig_browser_plus_2.jpg could save 4.1KiB (22% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2016/06/top_jigtwi_3.jpg could save 3.8KiB (23% reduction).

priority - 18Enable 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 175.4KiB (65% reduction).

Compressing http://jig.jp/wordpress/wp-includes/js/jquery/jquery.js?ver=1.12.4 could save 61.9KiB (65% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/js/jquery-1.11.0.min.js could save 61.5KiB (65% reduction).
Compressing http://jig.jp/ could save 13.1KiB (71% reduction).
Compressing http://jig.jp/wordpress/wp-content/plugins/contact…?ver=3.51.0-2014.06.20 could save 9.2KiB (61% reduction).
Compressing http://jig.jp/wordpress/wp-content/plugins/contact…/js/scripts.js?ver=4.6 could save 8.6KiB (73% reduction).
Compressing http://jig.jp/wordpress/wp-includes/js/wp-emoji-release.min.js?ver=4.5.9 could save 5.9KiB (61% reduction).
Compressing http://jig.jp/wordpress/wp-includes/js/jquery/jque…grate.min.js?ver=1.4.1 could save 5.9KiB (60% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/style.css could save 4.7KiB (72% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/style-top.css could save 2KiB (69% reduction).
Compressing http://jig.jp/wordpress/wp-content/plugins/contact…css/styles.css?ver=4.6 could save 961B (60% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/css/reset.css could save 928B (54% reduction).
Compressing http://jig.jp/wordpress/wp-includes/js/wp-embed.min.js?ver=4.5.9 could save 653B (47% reduction).

priority - 2Reduce server response time

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

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

http://jig.jp/wordpress/wp-content/themes/jig/style.css

priority - 0Leverage 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.google-analytics.com/ga.js (2 hours)

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

Minifying http://jig.jp/wordpress/wp-content/themes/jig/style.css could save 1.5KiB (23% reduction).
Minifying http://jig.jp/wordpress/wp-content/themes/jig/style-top.css could save 615B (21% 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 2.2KiB (13% reduction).

Minifying http://jig.jp/ could save 2.2KiB (13% 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://jig.jp/wordpress/wp-content/plugins/contact…/js/scripts.js?ver=4.6 could save 2KiB (18% reduction).

jig.jp Desktop Resource Breakdown

Total Resources44
Number of Hosts2
Static Resources42
JavaScript Resources8
CSS Resources5

jig.jp mobile page speed rank

Last tested: 2018-06-30


Mobile Speed Medium
67/100

jig.jp Mobile Speed Test Quick Summary


priority - 18Optimize images

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

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

Compressing http://jig.jp/wordpress/wp-content/uploads/2014/04/slide_01.jpg could save 59.6KiB (61% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2017/09/site_top_slide_ainc2.png could save 32.2KiB (14% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2017/05/slide_jigtwi.jpg could save 23.8KiB (43% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2017/09/sp_top_otamart.png could save 19.7KiB (13% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2017/09/top_otamart.png could save 14.9KiB (19% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2017/09/sp_top_sabarepo.png could save 6.3KiB (22% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2016/06/sp_top_jigtwi_3.jpg could save 6KiB (23% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2017/09/sp_top_odp.png could save 4.6KiB (23% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2016/06/top_jigtwi_3.jpg could save 3.8KiB (23% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2017/09/top_sabarepo.png could save 3.6KiB (39% reduction).
Compressing http://jig.jp/wordpress/wp-content/uploads/2017/09/top_odp.png could save 2.6KiB (34% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/images/bt_news_more.png could save 378B (28% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/images/h1_logo.png could save 312B (28% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/images/icon_rss.png could save 295B (31% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/images/navi_recruit_off.png could save 203B (23% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/images/navi_company_off.png could save 176B (21% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/images/navi_support_off.png could save 175B (19% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/images/h2_latest_info.png could save 149B (19% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/images/bt_next.png could save 132B (27% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/images/sp_navi.png could save 126B (18% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/images/navi_service_off.png could save 120B (21% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/images/bt_prev.png could save 116B (24% reduction).

priority - 17Enable 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 170.8KiB (66% reduction).

Compressing http://jig.jp/wordpress/wp-includes/js/jquery/jquery.js?ver=1.12.4 could save 61.9KiB (65% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/js/jquery-1.11.0.min.js could save 61.5KiB (65% reduction).
Compressing http://jig.jp/ could save 14.3KiB (72% reduction).
Compressing http://jig.jp/wordpress/wp-content/plugins/contact…s/scripts.js?ver=5.0.1 could save 10.3KiB (72% reduction).
Compressing http://jig.jp/wordpress/wp-includes/js/wp-emoji-release.min.js?ver=4.9.6 could save 7.3KiB (64% reduction).
Compressing http://jig.jp/wordpress/wp-includes/js/jquery/jque…grate.min.js?ver=1.4.1 could save 5.9KiB (60% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/style.css could save 4.8KiB (72% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/style-top.css could save 2.1KiB (70% reduction).
Compressing http://jig.jp/wordpress/wp-content/plugins/contact…s/styles.css?ver=5.0.1 could save 1KiB (61% reduction).
Compressing http://jig.jp/wordpress/wp-content/themes/jig/css/reset.css could save 928B (54% reduction).
Compressing http://jig.jp/wordpress/wp-includes/js/wp-embed.min.js?ver=4.9.6 could save 647B (47% reduction).

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

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

http://jig.jp/wordpress/wp-content/themes/jig/style.css

priority - 4Reduce server response time

priority - 1Leverage 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.google-analytics.com/ga.js (2 hours)

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 3.5KiB (25% reduction).

Minifying http://jig.jp/wordpress/wp-content/plugins/contact…s/scripts.js?ver=5.0.1 could save 3.5KiB (25% reduction).

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

Minifying http://jig.jp/wordpress/wp-content/themes/jig/style.css could save 1.2KiB (18% reduction).
Minifying http://jig.jp/wordpress/wp-content/themes/jig/style-top.css could save 647B (21% reduction).
Minifying http://jig.jp/wordpress/wp-content/themes/jig/css/reset.css could save 445B (27% reduction).
Minifying http://jig.jp/wordpress/wp-content/plugins/contact…s/styles.css?ver=5.0.1 could save 204B (13% reduction).
Minifying http://jig.jp/wordpress/wp-content/themes/jig/css/clearfix.css could save 109B (45% 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 2.5KiB (13% reduction).

Minifying http://jig.jp/ could save 2.5KiB (13% reduction).

jig.jp Mobile Resource Breakdown

Total Resources50
Number of Hosts2
Static Resources48
JavaScript Resources7
CSS Resources5

jig.jp mobile page usability

Last tested: 2018-06-30


Mobile Usability Good
100/100

jig.jp HTML validation

Errors

Attribute “xmlns:og” not allowed here.

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

Attribute “xmlns:fb” not allowed here.

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

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Line: 10 Column: 1 - 62
"...e-width"> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> <meta..."

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

Line: 57 Column: 1 - 63
"...</script> <link rel='https://api.w.org/' href='http://jig.jp/wp-json/' /> <link..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 130 Column: 46 - 110
"...a href=""><img src="/wordpress/wp-content/themes/jig/images/sp_navi.png" /></a></..." Line: 209 Column: 9 - 80
"...> <h2><img src="/wordpress/wp-content/themes/jig/images/h2_latest_info.png" /></h2> ..." Line: 210 Column: 37 - 102
"...&cat=-4"><img src="/wordpress/wp-content/themes/jig/images/icon_rss.png" /></a></p..." Line: 261 Column: 47 - 116
"...ws_list/"><img src="/wordpress/wp-content/themes/jig/images/bt_news_more.png" /></a></..."

Duplicate ID “slide_prev”.

Line: 289 Column: 9 - 27
"...> </ul> <p id="slide_prev"><a><im..."

Duplicate ID “slide_next”.

Line: 290 Column: 4 - 22
"...a></p> <p id="slide_next"><a><im..."

End tag for “body” seen, but there were unclosed elements.

Line: 368 Column: 1 - 7
"...pre> --> </body> </htm..."

Unclosed element “div”.

Line: 206 Column: 2 - 27
"...cript> <div id="content_wrapper"><div i..."

Warnings

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

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

Empty heading.

Line: 209 Column: 5 - 8
"...fix"> <h2><img s..."

The first occurrence of ID “slide_prev” was here.

Line: 277 Column: 9 - 27
"...> </ul> <p id="slide_prev"><a><im..."

The first occurrence of ID “slide_next” was here.

Line: 278 Column: 4 - 22
"...a></p> <p id="slide_next"><a><im..."

jig.jp similar domains

Similar domains:
www.jig.com
www.jig.net
www.jig.org
www.jig.info
www.jig.biz
www.jig.us
www.jig.mobi
www.ig.jp
www.jig.jp
www.nig.jp
www.jnig.jp
www.njig.jp
www.hig.jp
www.jhig.jp
www.hjig.jp
www.uig.jp
www.juig.jp
www.ujig.jp
www.iig.jp
www.jiig.jp
www.ijig.jp
www.kig.jp
www.jkig.jp
www.kjig.jp
www.mig.jp
www.jmig.jp
www.mjig.jp
www.jg.jp
www.jug.jp
www.jiug.jp
www.jjg.jp
www.jijg.jp
www.jjig.jp
www.jkg.jp
www.jikg.jp
www.jog.jp
www.jiog.jp
www.joig.jp
www.ji.jp
www.jif.jp
www.jigf.jp
www.jifg.jp
www.jiv.jp
www.jigv.jp
www.jivg.jp
www.jit.jp
www.jigt.jp
www.jitg.jp
www.jib.jp
www.jigb.jp
www.jibg.jp
www.jiy.jp
www.jigy.jp
www.jiyg.jp
www.jih.jp
www.jigh.jp
www.jihg.jp

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


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