Tools & Wizards About Us
commerce21.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

commerce21.co.jp

Commerce21｜コーポレートサイト

Page Load Speed

11.5 sec in total

First Response

1.7 sec

Resources Loaded

9.2 sec

Page Rendered

589 ms

commerce21.co.jp screenshot

About Website

Welcome to commerce21.co.jp homepage info - get ready to check Commerce21 best content for Japan right away, or after learning these important things about commerce21.co.jp

コマース21は、ビジネス構想策定・データベースデザイン・システム開発・運用まで、一気通貫のソリューションサービス企業としてクライアントの事業を成長させるパートナーです。

Visit commerce21.co.jp

Key Findings

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

Performance Metrics

commerce21.co.jp performance score

0

Network Requests Diagram

commerce21.co.jp

1673 ms

reset.css

354 ms

slick.css

109 ms

common.css

557 ms

top.css

579 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 86% of them (90 requests) were addressed to the original Commerce21.co.jp, 4% (4 requests) were made to Cdn.jsdelivr.net and 2% (2 requests) were made to Seal.globalsign.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Commerce21.co.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.6 MB

After Optimization

963.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Commerce21.co.jp main page is 1.6 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. 20% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 57.8 kB

  • Original 76.9 kB
  • After minification 67.6 kB
  • After compression 19.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 9.2 kB, which is 12% 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 57.8 kB or 75% of the original size.

Image Optimization

-35%

Potential reduce by 472.9 kB

  • Original 1.3 MB
  • After minification 860.3 kB

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. Obviously, Commerce21 needs image optimization as it can save up to 472.9 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 112.5 kB

  • Original 190.2 kB
  • After minification 179.9 kB
  • After compression 77.8 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 112.5 kB or 59% of the original size.

CSS Optimization

-79%

Potential reduce by 23.9 kB

  • Original 30.3 kB
  • After minification 24.8 kB
  • After compression 6.3 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. Commerce21.co.jp needs all CSS files to be minified and compressed as it can save up to 23.9 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (45%)

Requests Now

101

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

commerce21.co.jp

commerce21.co.jp

1673 ms

reset.css

reset.css

354 ms

slick.css

slick.css

109 ms

common.css

common.css

557 ms

top.css

top.css

579 ms

btn_recruit.png

btn_recruit.png

400 ms

btn_material.png

btn_material.png

401 ms

img_logo.png

img_logo.png

739 ms

img_tel.png

img_tel.png

754 ms

nav_service_off.png

nav_service_off.png

763 ms

nav_works_off.png

nav_works_off.png

877 ms

nav_review_off.png

nav_review_off.png

902 ms

nav_sminar_off.png

nav_sminar_off.png

940 ms

nav_news_off.png

nav_news_off.png

1120 ms

nav_company_off.png

nav_company_off.png

1123 ms

nav_concept_off.png

nav_concept_off.png

1145 ms

nav_fact_off.png

nav_fact_off.png

1219 ms

nav_history_off.png

nav_history_off.png

1309 ms

btn_contact_off.png

btn_contact_off.png

1314 ms

nav_material.png

nav_material.png

1503 ms

up.png

up.png

1509 ms

top1.jpg

top1.jpg

2312 ms

img_retention.jpg

img_retention.jpg

2390 ms

2015TOP2.jpg

2015TOP2.jpg

2048 ms

img_banner01.jpg

img_banner01.jpg

2289 ms

img_banner02.jpg

img_banner02.jpg

2416 ms

img_strong1.png

img_strong1.png

1936 ms

img_strong_under1.png

img_strong_under1.png

2324 ms

img_strong2.png

img_strong2.png

2418 ms

img_strong_under2.png

img_strong_under2.png

2674 ms

img_strong3.png

img_strong3.png

2660 ms

img_strong_under3.png

img_strong_under3.png

2689 ms

img_catch1.png

img_catch1.png

2744 ms

img_catch2.png

img_catch2.png

2960 ms

544f299213973_180x120_2.png

544f299213973_180x120_2.png

3185 ms

5448ebf034364_142x120_1.gif

5448ebf034364_142x120_1.gif

2871 ms

5448ebf03537f.jpg

5448ebf03537f.jpg

3060 ms

544f29a71cfbe_180x120_2.png

544f29a71cfbe_180x120_2.png

3262 ms

5448ecb3e7880_142x120_1.gif

5448ecb3e7880_142x120_1.gif

2724 ms

5448ecb3e8823.jpg

5448ecb3e8823.jpg

3107 ms

gs_noscript_100-50_ja.gif

gs_noscript_100-50_ja.gif

12 ms

gs_image_100-50_ja.js

gs_image_100-50_ja.js

13 ms

slick.min.js

slick.min.js

55 ms

conversion.js

conversion.js

13 ms

s_retargeting.js

s_retargeting.js

523 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

3446 ms

common.js

common.js

2981 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

2956 ms

jquery.film_roll.js

jquery.film_roll.js

3146 ms

top.js

top.js

3109 ms

544f2ae325c13_180x120_2.png

544f2ae325c13_180x120_2.png

3660 ms

544a01d65bd18_142x120_1.gif

544a01d65bd18_142x120_1.gif

3108 ms

544a01d65cc8f.jpg

544a01d65cc8f.jpg

3297 ms

544f2aa70e193_180x120_2.png

544f2aa70e193_180x120_2.png

3795 ms

5448f38deea4d_142x120_1.gif

5448f38deea4d_142x120_1.gif

3142 ms

5448f38deff0c.jpg

5448f38deff0c.jpg

3369 ms

544f2b1c99cfb_180x120_2.png

544f2b1c99cfb_180x120_2.png

3744 ms

559a42bf6e888_142x120_1.jpg

559a42bf6e888_142x120_1.jpg

3553 ms

544a090001b5e.jpg

544a090001b5e.jpg

3529 ms

547d69e99f84d_180x120_2.png

547d69e99f84d_180x120_2.png

3989 ms

54fd2b553dd14_142x120_1.jpg

54fd2b553dd14_142x120_1.jpg

3349 ms

5448f0636bd93.jpg

5448f0636bd93.jpg

3796 ms

img_customize01.png

img_customize01.png

3215 ms

img_customize02.png

img_customize02.png

3150 ms

img_customize03.png

img_customize03.png

2926 ms

img_customize04.png

img_customize04.png

2942 ms

img_customize05.png

img_customize05.png

3210 ms

img_customize06.png

img_customize06.png

3156 ms

img_customize07.png

img_customize07.png

3149 ms

img_customize08.png

img_customize08.png

3203 ms

img_customize09.png

img_customize09.png

3021 ms

img_customize10.png

img_customize10.png

3012 ms

img_customize11.png

img_customize11.png

3214 ms

img_customize12.png

img_customize12.png

3155 ms

img_customize13.png

img_customize13.png

2982 ms

img_customize14.png

img_customize14.png

2944 ms

img_customize15.png

img_customize15.png

2933 ms

img_customize16.png

img_customize16.png

2847 ms

img_customize17.png

img_customize17.png

2978 ms

img_customize18.png

img_customize18.png

2823 ms

img_sell.png

img_sell.png

2798 ms

btn_s5.png

btn_s5.png

2736 ms

img_search.png

img_search.png

2796 ms

img_recommend.png

img_recommend.png

2568 ms

img_mobile.png

img_mobile.png

2823 ms

analytics.js

analytics.js

63 ms

75 ms

img_recommend-1.png

img_recommend-1.png

2730 ms

siteSeal.do

siteSeal.do

490 ms

ajax-loader.gif

ajax-loader.gif

83 ms

ico_pdf.gif

ico_pdf.gif

2682 ms

slick.woff

slick.woff

104 ms

collect

collect

12 ms

35 ms

collect

collect

49 ms

btn_under_tel.png

btn_under_tel.png

2522 ms

btn_under_contact.png

btn_under_contact.png

2532 ms

btn_under_material.png

btn_under_material.png

2362 ms

siteSealImage.do

siteSealImage.do

182 ms

btn_under_seminar.png

btn_under_seminar.png

2590 ms

img_banner01.jpg

img_banner01.jpg

2343 ms

img_banner03.jpg

img_banner03.jpg

2320 ms

background.png

background.png

2268 ms

background3.jpg

background3.jpg

3175 ms

common.css

common.css

2504 ms

SEO Factors

commerce21.co.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 Commerce21.co.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 Commerce21.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

commerce21.co.jp

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