Tools & Wizards About Us
anken.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

anken.co.jp

会社の制服、ユニフォーム販売の株式会社安研

Page Load Speed

11.4 sec in total

First Response

516 ms

Resources Loaded

10.5 sec

Page Rendered

372 ms

anken.co.jp screenshot

About Website

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

会社の制服・ユニフォームのことなら何でもお気軽にお問い合わせください！ 会社制服、オリジナルユニフォーム、事務服、作業服・作業着、防塵服、オフィス制服、接客業向けユニフォームなど幅広く販売サポートしています。

Visit anken.co.jp

Key Findings

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

Performance Metrics

anken.co.jp performance score

0

Network Requests Diagram

anken.co.jp

516 ms

www.anken.co.jp

1852 ms

_import.css

377 ms

top.css

383 ms

_import.js

720 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 95% of them (72 requests) were addressed to the original Anken.co.jp, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Custom.search.yahoo.co.jp. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Anken.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 154.0 kB (11%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Anken.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. 25% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 15.5 kB

  • Original 21.6 kB
  • After minification 21.6 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 15.5 kB or 72% of the original size.

Image Optimization

-2%

Potential reduce by 21.6 kB

  • Original 1.2 MB
  • After minification 1.2 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. Anken images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 86.9 kB

  • Original 144.3 kB
  • After minification 128.0 kB
  • After compression 57.4 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 86.9 kB or 60% of the original size.

CSS Optimization

-80%

Potential reduce by 30.0 kB

  • Original 37.6 kB
  • After minification 31.0 kB
  • After compression 7.6 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. Anken.co.jp needs all CSS files to be minified and compressed as it can save up to 30.0 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (23%)

Requests Now

73

After Optimization

56

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

anken.co.jp

anken.co.jp

516 ms

www.anken.co.jp

www.anken.co.jp

1852 ms

_import.css

_import.css

377 ms

top.css

top.css

383 ms

_import.js

_import.js

720 ms

default.css

default.css

323 ms

common.css

common.css

518 ms

contents.css

contents.css

720 ms

clearfix.css

clearfix.css

369 ms

carousel.js

carousel.js

385 ms

jquery-1.6.min.js

jquery-1.6.min.js

1118 ms

jquery.cookie.js

jquery.cookie.js

585 ms

jquery.url.js

jquery.url.js

549 ms

jquery.browser.js

jquery.browser.js

391 ms

jquery.easing.js

jquery.easing.js

583 ms

jquery.flatheights.js

jquery.flatheights.js

415 ms

jquery.rollover.js

jquery.rollover.js

788 ms

jquery.scrollTo.js

jquery.scrollTo.js

787 ms

jquery.backgroundPosition.js

jquery.backgroundPosition.js

904 ms

common.js

common.js

1099 ms

ga.js

ga.js

16 ms

arrow.png

arrow.png

337 ms

7RQu5oUHDpxajhVA20UgAfMNAZQ6WoVDJdXJ.gif

7RQu5oUHDpxajhVA20UgAfMNAZQ6WoVDJdXJ.gif

1039 ms

logo.gif

logo.gif

397 ms

tel.gif

tel.gif

398 ms

hnav.gif

hnav.gif

415 ms

nav.gif

nav.gif

815 ms

tbnr_01.jpg

tbnr_01.jpg

1373 ms

tbnr_02.jpg

tbnr_02.jpg

1525 ms

tbnr_03.jpg

tbnr_03.jpg

1453 ms

tbnr_04.jpg

tbnr_04.jpg

1716 ms

tbnr_05.jpg

tbnr_05.jpg

1645 ms

tnav.gif

tnav.gif

1474 ms

bnr_collection.jpg

bnr_collection.jpg

2109 ms

lnav1.jpg

lnav1.jpg

2146 ms

lnav2.jpg

lnav2.jpg

2211 ms

lnav3.jpg

lnav3.jpg

2284 ms

lnav4.jpg

lnav4.jpg

2565 ms

lnav5.jpg

lnav5.jpg

2455 ms

lnav6.jpg

lnav6.jpg

2852 ms

lnav7.jpg

lnav7.jpg

2912 ms

lnav8.jpg

lnav8.jpg

2851 ms

lnav9.jpg

lnav9.jpg

2993 ms

bnr_selection.jpg

bnr_selection.jpg

3201 ms

bnr_voice.jpg

bnr_voice.jpg

3087 ms

bnr_flow.jpg

bnr_flow.jpg

3544 ms

img_information.jpg

img_information.jpg

3593 ms

illust_catalog.gif

illust_catalog.gif

3257 ms

illust_information.gif

illust_information.gif

3352 ms

illust_estimate.gif

illust_estimate.gif

3428 ms

freedial.gif

freedial.gif

3554 ms

search.png

search.png

3620 ms

inq_box.png

inq_box.png

3895 ms

inq_button_off.png

inq_button_off.png

3963 ms

inq_button_on.png

inq_button_on.png

3890 ms

closebutton.png

closebutton.png

3917 ms

__utm.gif

__utm.gif

20 ms

bg_catalogue.jpg

bg_catalogue.jpg

4198 ms

btn_catalogue.png

btn_catalogue.png

4109 ms

collect

collect

61 ms

btn_estimate01.png

btn_estimate01.png

4050 ms

btn_contact01.png

btn_contact01.png

4034 ms

fnav.gif

fnav.gif

3886 ms

bnr_collection_o.jpg

bnr_collection_o.jpg

4544 ms

lnav1_o.jpg

lnav1_o.jpg

4036 ms

lnav2_o.jpg

lnav2_o.jpg

3567 ms

lnav3_o.jpg

lnav3_o.jpg

3566 ms

lnav4_o.jpg

lnav4_o.jpg

3845 ms

lnav5_o.jpg

lnav5_o.jpg

3575 ms

lnav6_o.jpg

lnav6_o.jpg

3941 ms

lnav7_o.jpg

lnav7_o.jpg

3951 ms

lnav8_o.jpg

lnav8_o.jpg

3757 ms

lnav9_o.jpg

lnav9_o.jpg

3512 ms

bnr_selection_o.jpg

bnr_selection_o.jpg

3627 ms

bnr_voice_o.jpg

bnr_voice_o.jpg

3743 ms

bnr_flow_o.jpg

bnr_flow_o.jpg

3791 ms

SEO Factors

anken.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 Anken.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 Anken.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

anken.co.jp

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