LIGINC.CO.JP 株式会社LIG | 台東区上野にあるウェブ制作会社


liginc.co.jp website information.

liginc.co.jp website servers are located in Japan and are responding from following IP address 13.113.163.173. Check the full list of most visited websites located in Japan.

liginc.co.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 liginc.co.jp domain:

  • ns-1391.awsdns-45.org
  • ns-1712.awsdns-22.co.uk
  • ns-388.awsdns-48.com
  • ns-563.awsdns-06.net

and probably website liginc.co.jp is hosted by awsdns-45.org web hosting company. Check the complete list of other most popular websites hosted by awsdns-45.org hosting company.

According to Alexa traffic rank the highest website liginc.co.jp position was 2730 (in the world). The lowest Alexa rank position was 101096. Now website liginc.co.jp ranked in Alexa database as number 7979 (in the world).

Website liginc.co.jp Desktop speed measurement score (0/100) shows that the page desktop performance can be improved.

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

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

Weekly Rank Report

DateRankChange
May-20-2019 N/AN/A
May-19-2019 7,9792,566
May-18-2019 10,545-2,408
May-17-2019 8,137552
May-16-2019 8,6895,283
May-15-2019 13,972800
May-14-2019 14,772790

Advertisement

liginc.co.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.


liginc.co.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.


[ 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:
a. [Domain Name] LIGINC.CO.JP
g. [Organization] Lig
l. [Organization Type] corporation
m. [Administrative Contact] GY1812JP
n. [Technical Contact] TW101888JP
p. [Name Server] ns-388.awsdns-48.com
p. [Name Server] ns-1712.awsdns-22.co.uk
p. [Name Server] ns-1391.awsdns-45.org
p. [Name Server] ns-563.awsdns-06.net
s. [Signing Key]
[State] Connected (2015/12/31)
[Registered Date] 2011/12/07
[Connected Date] 2011/12/07
[Last Update] 2015/01/01 01:14:26 (JST)

[ 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'. ]

Contact Information:
a. [JPNIC Handle] GY1812JP
c. [Last, First] Yoshiwara, Go
d. [E-Mail] go@lifeisg.com
g. [Organization] Lig
l. [Division]
n. [Title]
o. [TEL]
p. [FAX]
y. [Reply Mail]
[Last Update] 2011/12/07 14:30:20 (JST)
form@dom.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 xxx/e'. ]

Contact Information:
a. [JPNIC Handle] TW101888JP
c. [Last, First] warita, taro
d. [E-Mail] admin@onamae.com
g. [Organization] GMO Internet Inc.
l. [Division] System Division Operation Department Network Team.
n. [Title]
o. [TEL] 03-5456-2555
p. [FAX] 03-5456-2556
y. [Reply Mail]
[Last Update] 2011/12/07 14:30:20 (JST)
form@dom.jprs.jp

liginc.co.jp server information

Servers Location

liginc.co.jp desktop page speed rank

Last tested: 2016-07-12


Desktop Speed Bad
0/100

liginc.co.jp Desktop Speed Test Quick Summary


priority - 1418 Optimize images

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

Optimize the following images to reduce their size by 13.5MiB (95% reduction).

Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/06…atch_160628_01_2_m.png could save 1.4MiB (93% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/06/eyecatch_160622_01_t.png could save 1.3MiB (98% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/07/eyecatch_160708_02_m.png could save 1.2MiB (87% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/07…1fa402ac3dc62cc91f.jpg could save 1.2MiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/06…atch_160630_02_m_1.png could save 961.6KiB (94% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/07/eyecatch.jpg could save 925.5KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/07/IGNIS-12.jpg could save 915.5KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/06/eyecatch_160629_01_t.png could save 865.5KiB (92% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/07/eyecatch_160709_01_m.png could save 461.9KiB (86% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/07/eyecatch_160707_02_m.png could save 390.5KiB (91% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/05/end.jpg could save 341.6KiB (97% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/07/20160708-29.jpg could save 317KiB (97% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/05/DSC_3677-2.jpg could save 236.8KiB (96% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/01…b1bbf9f8f9f12aa8dc.jpg could save 201.3KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2015/12…8567f5b7bacfbe9db7.jpg could save 178.5KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/02…0c1c833e2f5da5e100.jpg could save 176KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/02/bambino-22.jpg could save 175.6KiB (95% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2015/10…67f5b7bacfbe9db753.jpg could save 174.9KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/06…f64f769c36fec67b8d.jpg could save 162.5KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/06…550fc92044c52fd00a.jpg could save 161.3KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2015/11…67f5b7bacfbe9db726.jpg could save 158.5KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2015/12…567f5b7bacfbe9db78.jpg could save 157.9KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/06…0728b52422cc7d6cca.jpg could save 157.2KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/06…9e8e2f58315d2ac8ef.jpg could save 156.3KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/06/DSC00413.jpg could save 150.7KiB (94% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2015/11…67f5b7bacfbe9db712.jpg could save 147.7KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/06…4ef2814676d378054e.jpg could save 146.4KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/03…f33b69babe0a87aeed.jpg could save 133.1KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/07/eyecatch-2.png could save 121.6KiB (87% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/07/DSC00105.jpg could save 118.5KiB (95% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2015/10…67f5b7bacfbe9db715.jpg could save 113.9KiB (99% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/07…f789c27b264a6cb421.jpg could save 109.7KiB (94% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/07/20160708-1.jpg could save 90.7KiB (91% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2015/12/bambino-12.jpg could save 71.5KiB (98% reduction).
Compressing and resizing http://cdn.liginc.co.jp/wp-content/uploads/2016/07/160708_eyecatch.png could save 47.5KiB (82% reduction).
Compressing and resizing http://s3.feedly.com/img/follows/feedly-follow-rec…e-volume-medium_2x.png could save 5KiB (71% reduction).

priority - 12 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:

https://info.liginc.co.jp/data.json (expiration not specified)
http://js.fout.jp/segmentation.js (13.9 minutes)
http://liginc.co.jp/wp-content/themes/ligtheme/css/old.css?d=20160617 (15 minutes)
http://liginc.co.jp/wp-content/themes/ligtheme/css/style.css?d=20160617 (15 minutes)
http://liginc.co.jp/wp-includes/js/wp-embed.min.js?ver=4.4.2 (15 minutes)
http://liginc.co.jp/wp-includes/js/wp-emoji-release.min.js?ver=4.4.2 (15 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-PSHJDH (15 minutes)
http://connect.facebook.net/en_US/fbevents.js (20 minutes)
http://platform.twitter.com/oct.js (30 minutes)
http://js.ptengine.jp/10093f6f.js (60 minutes)
http://jsv2.ptengine.jp/pta.js (60 minutes)
http://jsv2.ptengine.jp/pts.js (60 minutes)
http://pagead2.googlesyndication.com/pagead/js/ads…gle.js?_=1468272774818 (60 minutes)
http://pagead2.googlesyndication.com/pagead/js/ads…gle.js?_=1468272774819 (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://liginc.co.jp/wp-content/themes/ligtheme/images/common/close.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme/ima…common/lig-service.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme/images/contact_a.jpg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme/images/icon/criage.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme/images/icon/iioffice.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme/images/icon/lamp.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme/images/icon/lig-id.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme/images/icon/lig-like.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme/images/icon/lig-studio.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme/images/icon/lig.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme/images/icon/poole.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme/images/svg/icon-new.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme/lib…eral/icon_general.woff (3 days)

priority - 6 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 60.5KiB (72% reduction).

Compressing http://liginc.co.jp/wp-content/themes/ligtheme/images/icon/lamp.svg could save 10.9KiB (72% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme/images/icon/criage.svg could save 9.1KiB (75% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme/images/icon/lig-studio.svg could save 8.1KiB (73% reduction).
Compressing http://js.fout.jp/segmentation.js could save 6.7KiB (74% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme/images/icon/iioffice.svg could save 6.1KiB (73% reduction).
Compressing https://info.liginc.co.jp/data.json could save 5.1KiB (81% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme/images/icon/poole.svg could save 4KiB (73% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme/images/icon/lig-id.svg could save 2.5KiB (68% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme/ima…common/lig-service.svg could save 2.4KiB (67% reduction).
Compressing http://platform.twitter.com/oct.js could save 2.2KiB (60% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme/images/icon/lig.svg could save 1.6KiB (55% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme/images/svg/icon-new.svg could save 986B (59% reduction).
Compressing http://jsv2.ptengine.jp/pta.js could save 680B (57% reduction).

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

Your page has 2 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://cdn.liginc.co.jp/wp-content/themes/ligtheme…modernizr/modernizr.js
http://cdn.liginc.co.jp/wp-content/themes/ligtheme…-1.11/jquery-1.11.0.js

Optimize CSS Delivery of the following:

http://liginc.co.jp/wp-content/themes/ligtheme/css/style.css?d=20160617
http://fonts.googleapis.com/css?family=Quicksand:400,700
http://liginc.co.jp/wp-content/themes/ligtheme/css/old.css?d=20160617

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 14.9KiB (53% reduction).

Minifying http://cdn.liginc.co.jp/wp-content/themes/ligtheme…modernizr/modernizr.js could save 10.2KiB (66% reduction) after compression.
Minifying http://js.fout.jp/segmentation.js could save 3.2KiB (36% reduction).
Minifying http://cdn.liginc.co.jp/wp-content/themes/ligtheme…e/jquery.stickyside.js could save 912B (46% reduction) after compression.
Minifying http://cdn.liginc.co.jp/wp-content/themes/ligtheme…ookie/jquery.cookie.js could save 594B (43% reduction) after compression.

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 5KiB (14% reduction).

Minifying http://liginc.co.jp/ could save 3.1KiB (15% reduction) after compression.
Minifying http://liginc.co.jp/undefined could save 1.9KiB (13% reduction) after compression.

liginc.co.jp Desktop Resources

Total Resources154
Number of Hosts24
Static Resources124
JavaScript Resources41
CSS Resources3

liginc.co.jp Desktop Resource Breakdown

liginc.co.jp mobile page speed rank

Last tested: 2016-07-12


Mobile Speed Bad
50/100

liginc.co.jp Mobile Speed Test Quick Summary


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

Your page has 19 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://cdn.liginc.co.jp/wp-content/themes/ligtheme…1/jquery-1.11.0.min.js
http://cdn.liginc.co.jp/wp-content/themes/ligtheme_sp/js/load.js
http://cdn.liginc.co.jp/wp-content/themes/ligtheme…oad/jquery.lazyload.js
http://cdn.liginc.co.jp/wp-content/themes/ligtheme_sp/js/service_bar.js
http://cdn.liginc.co.jp/wp-content/themes/ligtheme_sp/js/global_navi.js
http://cdn.liginc.co.jp/wp-content/themes/ligtheme…scroll_fixed_header.js
http://cdn.liginc.co.jp/wp-content/themes/ligtheme_sp/js/common.js
http://cdn.liginc.co.jp/wp-content/themes/ligtheme_sp/js/smooth_scroll.js
http://cdn.liginc.co.jp/wp-content/themes/ligtheme_sp/js/social.js
http://cdn.liginc.co.jp/wp-content/themes/ligtheme_sp/js/text_ellipsis.js
https://info.liginc.co.jp/data.json
http://cdn.liginc.co.jp/wp-content/themes/ligtheme_sp/js/special_info.js
http://cdn.liginc.co.jp/wp-content/themes/ligtheme_sp/js/info_new.js
http://www.googleadservices.com/pagead/conversion.js
http://platform.twitter.com/oct.js
http://cdn.liginc.co.jp/wp-content/themes/ligtheme…r/swiper.jquery.min.js
http://cdn.liginc.co.jp/wp-content/themes/ligtheme…e/jquery.heightLine.js
http://cdn.liginc.co.jp/wp-content/themes/ligtheme_sp/js/article-slider.js
http://liginc.co.jp/wp-includes/js/wp-embed.min.js?ver=4.4.2

Optimize CSS Delivery of the following:

http://liginc.co.jp/wp-content/themes/ligtheme_sp/css/style.css?d=20160617
http://liginc.co.jp/wp-content/themes/ligtheme_sp/…_mobile.css?d=20160617
http://liginc.co.jp/wp-content/themes/ligtheme_sp/css/old.css?d=20160617
http://fonts.googleapis.com/css?family=Quicksand:400,700

priority - 27 Optimize images

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

Optimize the following images to reduce their size by 265.9KiB (21% reduction).

Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/05/DSC_3677-2.jpg could save 42.4KiB (18% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/07/jack_sp.png could save 29.7KiB (13% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/06…630_02_m_1-300x200.png could save 24.7KiB (24% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/07…60707_02_m-300x200.png could save 18.3KiB (27% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/06…620_03_2_m-300x200.png could save 17.2KiB (29% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/06…60628_03_m-300x200.png could save 14.2KiB (34% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/04…60602_01_t-300x200.png could save 14KiB (27% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/07/eyecatch-2-300x200.png could save 13.9KiB (27% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/05/banner-ad-1.png could save 11.5KiB (25% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/07…60630_01_m-300x200.png could save 11.5KiB (28% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/05…50506_01_n-300x200.png could save 10.6KiB (23% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/02…pritesheet-300x200.png could save 9.8KiB (20% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/07…60704_01_m-300x200.png could save 8.8KiB (15% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/07…8_eyecatch-300x200.png could save 8.4KiB (29% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/05…60531_01_m-300x200.png could save 8.2KiB (17% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/06…60608_03_m-300x200.png could save 7.9KiB (20% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/02…60704_02_m-300x200.png could save 6.5KiB (27% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/07…60706_01_m-300x200.png could save 6.4KiB (22% reduction).
Losslessly compressing http://cdn.liginc.co.jp/wp-content/uploads/2016/03/eyecatch172-300x200.jpg could save 1.5KiB (11% reduction).
Losslessly compressing http://liginc.co.jp/wp-content/themes/ligtheme_sp/images/logo_lig_black.png could save 686B (23% reduction).

priority - 19 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:

https://info.liginc.co.jp/data.json (expiration not specified)
http://js.fout.jp/prefs.js (9.2 minutes)
http://js.fout.jp/segmentation.js (14.2 minutes)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/css/old.css?d=20160617 (15 minutes)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/…_mobile.css?d=20160617 (15 minutes)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/css/style.css?d=20160617 (15 minutes)
http://liginc.co.jp/wp-includes/js/wp-embed.min.js?ver=4.4.2 (15 minutes)
http://liginc.co.jp/wp-includes/js/wp-emoji-release.min.js?ver=4.4.2 (15 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-PSHJDH (15 minutes)
http://connect.facebook.net/en_US/fbevents.js (20 minutes)
http://connect.facebook.net/ja_JP/sdk.js (20 minutes)
http://apis.google.com/js/platform.js (30 minutes)
http://platform.twitter.com/oct.js (30 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
http://js.ptengine.jp/10093f6f.js (60 minutes)
http://jsv2.ptengine.jp/pta.js (60 minutes)
http://jsv2.ptengine.jp/pts.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/…close-service-menu.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/images/lig-service-sp.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/images/logo_lig_black.png (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/…ervice_logo/criage.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/…vice_logo/iioffice.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/…/service_logo/lamp.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/…ervice_logo/lig-id.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/…vice_logo/lig-like.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/…ce_logo/lig-studio.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/…s/service_logo/lig.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/…service_logo/poole.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/images/svg/icon-new.svg (3 days)
http://liginc.co.jp/wp-content/themes/ligtheme_sp/…onts/icon_general.woff (3 days)

priority - 11 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 108.3KiB (69% reduction).

Compressing http://staticxx.facebook.com/connect/xd_arbiter.php?version=42 could save 21.7KiB (66% reduction).
Compressing https://staticxx.facebook.com/connect/xd_arbiter.php?version=42 could save 21.7KiB (66% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme_sp/…/service_logo/lamp.svg could save 10.9KiB (72% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme_sp/…ervice_logo/criage.svg could save 9.1KiB (75% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme_sp/…ce_logo/lig-studio.svg could save 8.1KiB (73% reduction).
Compressing http://js.fout.jp/segmentation.js could save 6.7KiB (74% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme_sp/…vice_logo/iioffice.svg could save 6.1KiB (73% reduction).
Compressing http://js.fout.jp/prefs.js could save 5.5KiB (61% reduction).
Compressing https://info.liginc.co.jp/data.json could save 5.1KiB (81% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme_sp/…service_logo/poole.svg could save 4KiB (73% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme_sp/…ervice_logo/lig-id.svg could save 2.5KiB (68% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme_sp/images/lig-service-sp.svg could save 2.3KiB (67% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme_sp/…s/service_logo/lig.svg could save 1.6KiB (55% reduction).
Compressing http://widgets.getpocket.com/v1/j/btn.js?v=1 could save 1.2KiB (55% reduction).
Compressing http://liginc.co.jp/wp-content/themes/ligtheme_sp/images/svg/icon-new.svg could save 986B (59% reduction).
Compressing http://jsv2.ptengine.jp/pta.js could save 680B (57% reduction).

priority - 8 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 68% of the final above-the-fold content could be rendered with the full HTML response.

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

Minifying http://cdn.liginc.co.jp/wp-content/themes/ligtheme…1/jquery-1.11.0.min.js could save 40.9KiB (50% reduction) after compression.
Minifying http://js.fout.jp/segmentation.js could save 3.2KiB (36% reduction).
Minifying https://b.hatena.ne.jp/js/bookmark_button.js could save 1.9KiB (23% reduction) after compression.
Minifying http://cdn.liginc.co.jp/wp-content/themes/ligtheme…oad/jquery.lazyload.js could save 925B (40% reduction) after compression.
Minifying http://widgets.getpocket.com/v1/j/btn.js?v=1 could save 545B (24% 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 2.3KiB (11% reduction).

Minifying http://liginc.co.jp/?utm_expid=76720523-3.k4iq65hMQua1mCePSGVLaw.0 could save 2.3KiB (11% reduction) after compression.

liginc.co.jp Mobile Resources

Total Resources206
Number of Hosts40
Static Resources157
JavaScript Resources34
CSS Resources4

liginc.co.jp Mobile Resource Breakdown

liginc.co.jp mobile page usability

Last tested: 2016-07-12


Mobile Usability Good
99/100

liginc.co.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 <div class="swiper-button-…swiper-custom"></div> and 1 others are close to other tap targets.

liginc.co.jp Mobile Resources

Total Resources206
Number of Hosts40
Static Resources157
JavaScript Resources34
CSS Resources4

liginc.co.jp Mobile Resource Breakdown

liginc.co.jp similar domains

Similar domains:
www.liginc.com
www.liginc.net
www.liginc.org
www.liginc.info
www.liginc.biz
www.liginc.us
www.liginc.mobi
www.iginc.co.jp
www.liginc.co.jp
www.piginc.co.jp
www.lpiginc.co.jp
www.pliginc.co.jp
www.oiginc.co.jp
www.loiginc.co.jp
www.oliginc.co.jp
www.kiginc.co.jp
www.lkiginc.co.jp
www.kliginc.co.jp
www.lginc.co.jp
www.luginc.co.jp
www.liuginc.co.jp
www.luiginc.co.jp
www.ljginc.co.jp
www.lijginc.co.jp
www.ljiginc.co.jp
www.lkginc.co.jp
www.likginc.co.jp
www.loginc.co.jp
www.lioginc.co.jp
www.liinc.co.jp
www.lifinc.co.jp
www.ligfinc.co.jp
www.lifginc.co.jp
www.livinc.co.jp
www.ligvinc.co.jp
www.livginc.co.jp
www.litinc.co.jp
www.ligtinc.co.jp
www.litginc.co.jp
www.libinc.co.jp
www.ligbinc.co.jp
www.libginc.co.jp
www.liyinc.co.jp
www.ligyinc.co.jp
www.liyginc.co.jp
www.lihinc.co.jp
www.lighinc.co.jp
www.lihginc.co.jp
www.lignc.co.jp
www.ligunc.co.jp
www.ligiunc.co.jp
www.liguinc.co.jp
www.ligjnc.co.jp
www.ligijnc.co.jp
www.ligjinc.co.jp
www.ligknc.co.jp
www.ligiknc.co.jp
www.ligkinc.co.jp
www.ligonc.co.jp
www.ligionc.co.jp
www.ligoinc.co.jp
www.ligic.co.jp
www.ligibc.co.jp
www.liginbc.co.jp
www.ligibnc.co.jp
www.ligihc.co.jp
www.liginhc.co.jp
www.ligihnc.co.jp
www.ligijc.co.jp
www.liginjc.co.jp
www.ligimc.co.jp
www.liginmc.co.jp
www.ligimnc.co.jp
www.ligin.co.jp
www.liginx.co.jp
www.ligincx.co.jp
www.liginxc.co.jp
www.ligind.co.jp
www.ligincd.co.jp
www.ligindc.co.jp
www.liginf.co.jp
www.ligincf.co.jp
www.liginfc.co.jp
www.liginv.co.jp
www.ligincv.co.jp
www.liginvc.co.jp

liginc.co.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.


liginc.co.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.