Tools & Wizards About Us
ajieng.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ajieng.co.jp

食品工場建設・改修のAJEC 味の素エンジニアリング株式会社

Page Load Speed

8.5 sec in total

First Response

2.6 sec

Resources Loaded

5.8 sec

Page Rendered

171 ms

ajieng.co.jp screenshot

About Website

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

味の素エンジニアリング（AJEC）の公式ウェブサイトです。早わかり！食品工場建設のキホン、AJECを知る、AJECが選ばれる理由、実績とお客様の声、AJECの技術、企業情報、採用情報をご紹介します。

Visit ajieng.co.jp

Key Findings

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

Performance Metrics

ajieng.co.jp performance score

0

Network Requests Diagram

ajieng.co.jp

2596 ms

basic.css

327 ms

swap.js

335 ms

scroll.js

886 ms

saiyou_aec.js

155 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 97% of them (60 requests) were addressed to the original Ajieng.co.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Ajieng.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 70.2 kB (8%)

Content Size

931.1 kB

After Optimization

860.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 41.3 kB

  • Original 48.4 kB
  • After minification 33.7 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 14.6 kB, which is 30% 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 41.3 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 24 B

  • Original 825.6 kB
  • After minification 825.6 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. Ajieng images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 27.0 kB

  • Original 54.8 kB
  • After minification 44.8 kB
  • After compression 27.9 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 27.0 kB or 49% of the original size.

CSS Optimization

-83%

Potential reduce by 1.9 kB

  • Original 2.3 kB
  • After minification 1.5 kB
  • After compression 402 B

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. Ajieng.co.jp needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

61

After Optimization

50

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ajieng.co.jp

ajieng.co.jp

2596 ms

basic.css

basic.css

327 ms

swap.js

swap.js

335 ms

scroll.js

scroll.js

886 ms

saiyou_aec.js

saiyou_aec.js

155 ms

head_bg.jpg

head_bg.jpg

158 ms

search_t.jpg

search_t.jpg

173 ms

space.gif

space.gif

167 ms

navi_05.jpg

navi_05.jpg

176 ms

navi_06.jpg

navi_06.jpg

305 ms

ajec_logo_l.jpg

ajec_logo_l.jpg

638 ms

head_shadow.jpg

head_shadow.jpg

327 ms

bg_01.jpg

bg_01.jpg

338 ms

globalnavi_01_in.jpg

globalnavi_01_in.jpg

350 ms

globalnavi_02.jpg

globalnavi_02.jpg

358 ms

globalnavi_03.jpg

globalnavi_03.jpg

455 ms

globalnavi_04.jpg

globalnavi_04.jpg

488 ms

globalnavi_05.jpg

globalnavi_05.jpg

503 ms

globalnavi_06.jpg

globalnavi_06.jpg

524 ms

top_bu_01.jpg

top_bu_01.jpg

933 ms

top_aj_01.jpg

top_aj_01.jpg

1065 ms

top_ad_01.jpg

top_ad_01.jpg

1463 ms

ind_tb.jpg

ind_tb.jpg

1672 ms

ind_01.jpg

ind_01.jpg

699 ms

new_icon.gif

new_icon.gif

793 ms

dot_01.gif

dot_01.gif

874 ms

ind_02.jpg

ind_02.jpg

952 ms

ind_03.jpg

ind_03.jpg

1049 ms

ind_04.jpg

ind_04.jpg

1290 ms

ind_05.jpg

ind_05.jpg

1116 ms

pagetop.jpg

pagetop.jpg

1223 ms

copyright.jpg

copyright.jpg

1213 ms

foot_shadow.jpg

foot_shadow.jpg

1198 ms

bg_01_end.jpg

bg_01_end.jpg

1288 ms

foot_bg.jpg

foot_bg.jpg

1319 ms

analytics.js

analytics.js

11 ms

collect

collect

23 ms

navi_05_on.jpg

navi_05_on.jpg

153 ms

navi_04_on.jpg

navi_04_on.jpg

170 ms

top3_r2_c2_f2.jpg

top3_r2_c2_f2.jpg

165 ms

top3_r4_c2_f2.jpg

top3_r4_c2_f2.jpg

178 ms

top3_r6_c2_f2.jpg

top3_r6_c2_f2.jpg

183 ms

top3_r12_c2_f2.jpg

top3_r12_c2_f2.jpg

162 ms

top3_r16_c2_f2.jpg

top3_r16_c2_f2.jpg

303 ms

top_aj_01_on01.jpg

top_aj_01_on01.jpg

1127 ms

top_aj_01_on02.jpg

top_aj_01_on02.jpg

816 ms

top_ad_01_on01.jpg

top_ad_01_on01.jpg

504 ms

navi_06_on.jpg

navi_06_on.jpg

352 ms

globalnavi_01_on.jpg

globalnavi_01_on.jpg

360 ms

globalnavi_02_on.jpg

globalnavi_02_on.jpg

454 ms

globalnavi_03_on.jpg

globalnavi_03_on.jpg

539 ms

globalnavi_04_on.jpg

globalnavi_04_on.jpg

671 ms

globalnavi_05_on.jpg

globalnavi_05_on.jpg

674 ms

globalnavi_06_on.jpg

globalnavi_06_on.jpg

718 ms

top_bu_01_on01.jpg

top_bu_01_on01.jpg

1096 ms

top_bu_01_on02.jpg

top_bu_01_on02.jpg

841 ms

top_bu_01_on03.jpg

top_bu_01_on03.jpg

1168 ms

ind_02_on.jpg

ind_02_on.jpg

896 ms

ind_03_on.jpg

ind_03_on.jpg

985 ms

ind_04_on.jpg

ind_04_on.jpg

1009 ms

ind_05_on.jpg

ind_05_on.jpg

1076 ms

pagetop_on.jpg

pagetop_on.jpg

1150 ms

SEO Factors

ajieng.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ajieng.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ajieng.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

ajieng.co.jp

Open Graph description is not detected on the main page of Ajieng. 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: