Tools & Wizards About Us
asahishokuhin.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

asahishokuhin.co.jp

Parallels Operations Automation Default Page

Page Load Speed

8.1 sec in total

First Response

594 ms

Resources Loaded

7.1 sec

Page Rendered

460 ms

asahishokuhin.co.jp screenshot

About Website

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

旭食品株式会社は、介護治療食品、携帯・給食用ミニパック食品の老舗です。減塩・低塩食品、たんぱく質調整食品、栄養強化食品、水分補給食品、とろみ剤など、様々な病院、介護施設、学校などで使用されています。

Visit asahishokuhin.co.jp

Key Findings

We analyzed Asahishokuhin.co.jp page load time and found that the first response time was 594 ms and then it took 7.6 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

asahishokuhin.co.jp performance score

0

Network Requests Diagram

asahishokuhin.co.jp

594 ms

www.asahishokuhin.co.jp

1588 ms

version4.css

435 ms

import.css

447 ms

prototype.js

1618 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 96% of them (68 requests) were addressed to the original Asahishokuhin.co.jp, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Asahishokuhin.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 249.0 kB (17%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 23.1 kB

  • Original 29.2 kB
  • After minification 23.4 kB
  • After compression 6.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 5.8 kB, which is 20% 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 23.1 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 77.3 kB

  • Original 1.2 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. Asahishokuhin images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 125.7 kB

  • Original 172.2 kB
  • After minification 129.8 kB
  • After compression 46.5 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 125.7 kB or 73% of the original size.

CSS Optimization

-84%

Potential reduce by 22.8 kB

  • Original 27.3 kB
  • After minification 18.1 kB
  • After compression 4.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. Asahishokuhin.co.jp needs all CSS files to be minified and compressed as it can save up to 22.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (10%)

Requests Now

69

After Optimization

62

  • Images
  • JavaScript
  • CSS

The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Asahishokuhin. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

asahishokuhin.co.jp

asahishokuhin.co.jp

594 ms

www.asahishokuhin.co.jp

www.asahishokuhin.co.jp

1588 ms

version4.css

version4.css

435 ms

import.css

import.css

447 ms

prototype.js

prototype.js

1618 ms

rollover.js

rollover.js

457 ms

colorbox.css

colorbox.css

421 ms

jquery.min.js

jquery.min.js

29 ms

jquery.colorbox.js

jquery.colorbox.js

1253 ms

base.css

base.css

705 ms

bg.jpg

bg.jpg

603 ms

logo.jpg

logo.jpg

482 ms

head_img.jpg

head_img.jpg

850 ms

btn_shinki.jpg

btn_shinki.jpg

463 ms

btn_login.jpg

btn_login.jpg

288 ms

btn_fax2.jpg

btn_fax2.jpg

302 ms

btn_cart.jpg

btn_cart.jpg

585 ms

btn_regi.jpg

btn_regi.jpg

623 ms

bg_navi.jpg

bg_navi.jpg

697 ms

navi01_o.jpg

navi01_o.jpg

751 ms

navi02.jpg

navi02.jpg

828 ms

navi03.jpg

navi03.jpg

852 ms

navi04.jpg

navi04.jpg

882 ms

navi05.jpg

navi05.jpg

1108 ms

navi06.jpg

navi06.jpg

1015 ms

left_t1.jpg

left_t1.jpg

1096 ms

left_t2.jpg

left_t2.jpg

1108 ms

icon01.jpg

icon01.jpg

1071 ms

left_t3.jpg

left_t3.jpg

1351 ms

left_banner01.jpg

left_banner01.jpg

1504 ms

left_banner02.jpg

left_banner02.jpg

1462 ms

left_banner03.jpg

left_banner03.jpg

1349 ms

left_t4.jpg

left_t4.jpg

1368 ms

left_t5.jpg

left_t5.jpg

1358 ms

mainimage.jpg

mainimage.jpg

1994 ms

top_banner01.jpg

top_banner01.jpg

2036 ms

top_banner02.jpg

top_banner02.jpg

1979 ms

top_banner03.jpg

top_banner03.jpg

1833 ms

top_banner04.jpg

top_banner04.jpg

1844 ms

top_banner05.jpg

top_banner05.jpg

1959 ms

top_banner06.jpg

top_banner06.jpg

2292 ms

top_banner07.jpg

top_banner07.jpg

2230 ms

top_banner08.jpg

top_banner08.jpg

2433 ms

top02.jpg

top02.jpg

2432 ms

top03.jpg

top03.jpg

2272 ms

ga.js

ga.js

5 ms

355_160x195.jpeg

355_160x195.jpeg

2428 ms

__utm.gif

__utm.gif

11 ms

199_160x279.jpeg

199_160x279.jpeg

2300 ms

367_160x203.jpeg

367_160x203.jpeg

2178 ms

359_160x191.jpeg

359_160x191.jpeg

2232 ms

402_160x199.jpeg

402_160x199.jpeg

2338 ms

772_160x160.jpg

772_160x160.jpg

2060 ms

588_160x247.jpg

588_160x247.jpg

2285 ms

780_160x160.jpg

780_160x160.jpg

2062 ms

445_160x233.jpeg

445_160x233.jpeg

2238 ms

788_160x382.jpg

788_160x382.jpg

2292 ms

393_160x198.jpeg

393_160x198.jpeg

2056 ms

786_160x350.jpg

786_160x350.jpg

2246 ms

206_160x222.jpeg

206_160x222.jpeg

2340 ms

465_160x112.jpeg

465_160x112.jpeg

2204 ms

397_160x110.jpeg

397_160x110.jpeg

2083 ms

570_160x96.jpeg

570_160x96.jpeg

2039 ms

773_160x160.jpg

773_160x160.jpg

2151 ms

copy.jpg

copy.jpg

2265 ms

pagetop.jpg

pagetop.jpg

2272 ms

navi02_o.jpg

navi02_o.jpg

349 ms

navi03_o.jpg

navi03_o.jpg

374 ms

navi04_o.jpg

navi04_o.jpg

376 ms

navi05_o.jpg

navi05_o.jpg

337 ms

navi06_o.jpg

navi06_o.jpg

345 ms

SEO Factors

asahishokuhin.co.jp SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Asahishokuhin.co.jp can be misinterpreted by Google and other search engines. Our service has detected that English 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 Asahishokuhin.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

asahishokuhin.co.jp

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