Tools & Wizards About Us
kproject.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

kproject.co.jp

Webシステム開発、技術者エンジニアリングサービスの株式会社ケープロジェクト

Page Load Speed

5.8 sec in total

First Response

571 ms

Resources Loaded

4.8 sec

Page Rendered

461 ms

kproject.co.jp screenshot

About Website

Click here to check amazing Kproject content. Otherwise, check out these important facts you probably never knew about kproject.co.jp

ホームページ作成から、スマートフォンアプリを使った業務のスリム化、コストパフォーマンスに優れたクラウドツールによる業務改善、システム開発の提案から運用保守作業までワンストップのサポート体制を実現する、株式会社ケープロジェクト。あらゆる分野の業種に対応する技術力でアプリケーション開発を提案いたします。

Visit kproject.co.jp

Key Findings

We analyzed Kproject.co.jp page load time and found that the first response time was 571 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

kproject.co.jp performance score

0

Network Requests Diagram

kproject.co.jp

571 ms

www.kproject.co.jp

1483 ms

style.css

1016 ms

shortcodes.css

806 ms

style.css

514 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 83% of them (50 requests) were addressed to the original Kproject.co.jp, 7% (4 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Kproject.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 499.2 kB (29%)

Content Size

1.7 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kproject.co.jp main page is 1.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 34.3 kB

  • Original 41.4 kB
  • After minification 25.6 kB
  • After compression 7.1 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 15.8 kB, which is 38% 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 34.3 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 78.9 kB

  • Original 1.1 MB
  • After minification 1.1 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Kproject images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 215.4 kB

  • Original 320.5 kB
  • After minification 313.9 kB
  • After compression 105.1 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 215.4 kB or 67% of the original size.

CSS Optimization

-85%

Potential reduce by 170.6 kB

  • Original 200.7 kB
  • After minification 172.9 kB
  • After compression 30.1 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. Kproject.co.jp needs all CSS files to be minified and compressed as it can save up to 170.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (48%)

Requests Now

52

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kproject.co.jp

kproject.co.jp

571 ms

www.kproject.co.jp

www.kproject.co.jp

1483 ms

style.css

style.css

1016 ms

shortcodes.css

shortcodes.css

806 ms

style.css

style.css

514 ms

prettyPhoto.css

prettyPhoto.css

854 ms

revolution.css

revolution.css

914 ms

responsive.css

responsive.css

1026 ms

font-awesome.min.css

font-awesome.min.css

800 ms

css

css

26 ms

css

css

40 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

445 ms

jquery.js

jquery.js

965 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

507 ms

jquery.viewport.js

jquery.viewport.js

579 ms

jquery.tabs.min.js

jquery.tabs.min.js

606 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

642 ms

jquery.carouFredSel-6.2.0-packed.js

jquery.carouFredSel-6.2.0-packed.js

1234 ms

jquery.tweet.min.js

jquery.tweet.min.js

679 ms

custom.js

custom.js

762 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

767 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

962 ms

reset.css

reset.css

354 ms

analytics.js

analytics.js

109 ms

phone-ico.png

phone-ico.png

363 ms

facebook.png

facebook.png

365 ms

facebook.png

facebook.png

364 ms

google.png

google.png

365 ms

google.png

google.png

364 ms

twitter.png

twitter.png

366 ms

twitter.png

twitter.png

367 ms

kp-logo_base-orng_ol.png

kp-logo_base-orng_ol.png

368 ms

sub-menu-bg.png

sub-menu-bg.png

506 ms

kv_01.jpg

kv_01.jpg

1091 ms

rev-caption-bg.png

rev-caption-bg.png

508 ms

kv_02.jpg

kv_02.jpg

1343 ms

kv_03.jpg

kv_03.jpg

1798 ms

introtext-border-top.png

introtext-border-top.png

517 ms

intro-text-border-bottom.png

intro-text-border-bottom.png

551 ms

splitter.png

splitter.png

559 ms

portfolio_01.png

portfolio_01.png

1370 ms

transparent-bg.png

transparent-bg.png

734 ms

portfolio_03.jpg

portfolio_03.jpg

721 ms

portfolio_04.png

portfolio_04.png

1043 ms

feeture_01.jpg

feeture_01.jpg

916 ms

feeture_02.jpg

feeture_02.jpg

1099 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

20 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

20 ms

F-uvpIj1hF17IDyvQvI50Q.ttf

F-uvpIj1hF17IDyvQvI50Q.ttf

21 ms

MViwy4K6e56oHcyeMzjbCQ.ttf

MViwy4K6e56oHcyeMzjbCQ.ttf

20 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1114 ms

collect

collect

252 ms

collect

collect

170 ms

responsive-nav-bg.png

responsive-nav-bg.png

743 ms

btn-small-gradient.png

btn-small-gradient.png

779 ms

loader.gif

loader.gif

860 ms

timer.png

timer.png

877 ms

ga-audiences

ga-audiences

40 ms

large_left.png

large_left.png

164 ms

large_right.png

large_right.png

163 ms

SEO Factors

kproject.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kproject.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Kproject.co.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

kproject.co.jp

Open Graph description is not detected on the main page of Kproject. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: