Tools & Wizards About Us
logicom.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

logicom.jp

株式会社シーアールイー｜生活を支える物流不動産トータルサービス

Page Load Speed

6.3 sec in total

First Response

1.4 sec

Resources Loaded

4.6 sec

Page Rendered

316 ms

logicom.jp screenshot

About Website

Visit logicom.jp now to see the best up-to-date Logicom content and also check out these interesting facts you probably never knew about logicom.jp

世界の人とモノをつなぐ物流インフラプラットフォームとしてNO.1企業へ。物流不動産の開発、マスターリース、プロパティマネジメント、リーシング、アセットマネジメントまで、生活を支える物流不動産のトータルサービスを展開。

Visit logicom.jp

Key Findings

We analyzed Logicom.jp page load time and found that the first response time was 1.4 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

logicom.jp performance score

0

Network Requests Diagram

logicom.jp

1424 ms

reset.css

397 ms

style.css

780 ms

modernizr.js

582 ms

jquery.min.js

35 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 97% of them (37 requests) were addressed to the original Logicom.jp, 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Logicom.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.4 kB (41%)

Content Size

79.1 kB

After Optimization

46.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Logicom.jp main page is 79.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 48.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 10.7 kB

  • Original 14.3 kB
  • After minification 11.6 kB
  • After compression 3.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 2.6 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 10.7 kB or 75% of the original size.

JavaScript Optimization

-18%

Potential reduce by 8.9 kB

  • Original 48.6 kB
  • After minification 48.0 kB
  • After compression 39.7 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 8.9 kB or 18% of the original size.

CSS Optimization

-79%

Potential reduce by 12.7 kB

  • Original 16.2 kB
  • After minification 10.7 kB
  • After compression 3.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Logicom.jp needs all CSS files to be minified and compressed as it can save up to 12.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (11%)

Requests Now

37

After Optimization

33

  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Logicom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

logicom.jp

logicom.jp

1424 ms

reset.css

reset.css

397 ms

style.css

style.css

780 ms

modernizr.js

modernizr.js

582 ms

jquery.min.js

jquery.min.js

35 ms

common.js

common.js

397 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

397 ms

top.css

top.css

573 ms

top.js

top.js

582 ms

logo.png

logo.png

199 ms

nav.png

nav.png

197 ms

btn_objectinfo_off.png

btn_objectinfo_off.png

193 ms

btn_results_off.png

btn_results_off.png

196 ms

btn_language_off.png

btn_language_off.png

196 ms

img_main_01.png

img_main_01.png

2281 ms

img_main_02.png

img_main_02.png

2661 ms

img_main_03.png

img_main_03.png

1903 ms

text_main01.png

text_main01.png

384 ms

ttl_jigyou.png

ttl_jigyou.png

385 ms

ttl_chintai.png

ttl_chintai.png

389 ms

img_chintai.jpg

img_chintai.jpg

954 ms

ttl_pm.png

ttl_pm.png

577 ms

img_pm.jpg

img_pm.jpg

1165 ms

ttl_ir_news.png

ttl_ir_news.png

767 ms

pdf.png

pdf.png

959 ms

btn_detail.png

btn_detail.png

1143 ms

ttl_info.png

ttl_info.png

1151 ms

bnr_jpx.png

bnr_jpx.png

1525 ms

bnr_tokyoipo.png

bnr_tokyoipo.png

1344 ms

bnr_tokyoipo_irstreet.png

bnr_tokyoipo_irstreet.png

1554 ms

fnav.png

fnav.png

1729 ms

arrow02.png

arrow02.png

1716 ms

ttl_affiliate.png

ttl_affiliate.png

1750 ms

logo_lc_partners.png

logo_lc_partners.png

1907 ms

logo_lc_lending.png

logo_lc_lending.png

1923 ms

logo_logicom_re.png

logo_logicom_re.png

1945 ms

ttl_management.png

ttl_management.png

2089 ms

logo_yotsubako.png

logo_yotsubako.png

2098 ms

SEO Factors

logicom.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Logicom.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Logicom.jp main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

logicom.jp

Open Graph data is detected on the main page of Logicom. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: