Tools & Wizards About Us
e-koyama.com screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

e-koyama.com

オンデマンド印刷・スピード印刷 東京｜株式会社コーヤマ－HOME

Page Load Speed

4.6 sec in total

First Response

696 ms

Resources Loaded

3.6 sec

Page Rendered

310 ms

e-koyama.com screenshot

About Website

Welcome to e-koyama.com homepage info - get ready to check E Koyama best content for Japan right away, or after learning these important things about e-koyama.com

東京都｜千代田区｜株式会社コーヤマは、オンデマンド印刷・スピード印刷の他、同人誌をはじめとするご注文をお受けする東京の印刷会社です。

Visit e-koyama.com

Key Findings

We analyzed E-koyama.com page load time and found that the first response time was 696 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

e-koyama.com performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.361

30/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

e-koyama.com

696 ms

top.css

332 ms

style.css

493 ms

top.css

496 ms

koyama-exp.css

339 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 80% of them (84 requests) were addressed to the original E-koyama.com, 6% (6 requests) were made to Cdnjs.cloudflare.com and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain E-koyama.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 373.4 kB (28%)

Content Size

1.3 MB

After Optimization

972.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-koyama.com main page is 1.3 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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 35.2 kB

  • Original 44.3 kB
  • After minification 38.2 kB
  • After compression 9.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 6.2 kB, which is 14% 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 35.2 kB or 79% of the original size.

Image Optimization

-21%

Potential reduce by 217.0 kB

  • Original 1.1 MB
  • After minification 833.5 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, E Koyama needs image optimization as it can save up to 217.0 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 4.3 kB

  • Original 113.8 kB
  • After minification 112.8 kB
  • After compression 109.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. This website has mostly compressed JavaScripts.

CSS Optimization

-85%

Potential reduce by 116.9 kB

  • Original 137.3 kB
  • After minification 105.6 kB
  • After compression 20.4 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. E-koyama.com needs all CSS files to be minified and compressed as it can save up to 116.9 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

103

After Optimization

77

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Koyama. 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

e-koyama.com

e-koyama.com

696 ms

top.css

top.css

332 ms

style.css

style.css

493 ms

top.css

top.css

496 ms

koyama-exp.css

koyama-exp.css

339 ms

drawer.css

drawer.css

349 ms

default.js

default.js

345 ms

page.css

page.css

499 ms

front.css

front.css

683 ms

sp2.css

sp2.css

683 ms

iscroll.min.js

iscroll.min.js

28 ms

slick.css

slick.css

37 ms

slick-theme.css

slick-theme.css

48 ms

jquery.min.js

jquery.min.js

29 ms

slick.min.js

slick.min.js

44 ms

widgets.js

widgets.js

17 ms

sdk.js

sdk.js

21 ms

pc_logo.png

pc_logo.png

178 ms

pc_tel.png

pc_tel.png

177 ms

cotact_banner.png

cotact_banner.png

180 ms

sp_logo.png

sp_logo.png

179 ms

sp_tel.png

sp_tel.png

176 ms

top_c.png

top_c.png

178 ms

top_line.png

top_line.png

332 ms

head_menu1.png

head_menu1.png

335 ms

head_menu2.png

head_menu2.png

335 ms

head_menu3.png

head_menu3.png

340 ms

head_menu4.png

head_menu4.png

341 ms

topmain1.jpg

topmain1.jpg

863 ms

topmain2.jpg

topmain2.jpg

822 ms

insatsunew.gif

insatsunew.gif

661 ms

katsuyougaido.gif

katsuyougaido.gif

666 ms

top_line.png

top_line.png

509 ms

side_banner3.png

side_banner3.png

510 ms

side_banner1.png

side_banner1.png

678 ms

side_banner2.png

side_banner2.png

679 ms

side_m1_head.png

side_m1_head.png

826 ms

side_m1_foot.png

side_m1_foot.png

833 ms

side_m2_head.png

side_m2_head.png

847 ms

side_m2_foot.png

side_m2_foot.png

849 ms

side_access_head.png

side_access_head.png

987 ms

side_access_foot.png

side_access_foot.png

992 ms

bottan_list.png

bottan_list.png

1000 ms

sp_bottan1.png

sp_bottan1.png

1017 ms

sp_banner1.png

sp_banner1.png

1017 ms

sp_banner2.png

sp_banner2.png

1207 ms

icon_banner1_1.png

icon_banner1_1.png

1152 ms

icon_banner1_2.png

icon_banner1_2.png

1157 ms

icon_banner1_3.png

icon_banner1_3.png

1166 ms

icon_banner1_4.png

icon_banner1_4.png

1186 ms

icon_banner1_5.png

icon_banner1_5.png

1187 ms

icon_banner1_6.png

icon_banner1_6.png

1318 ms

ajax-loader.gif

ajax-loader.gif

28 ms

embed

embed

224 ms

icon_banner1_1.png

icon_banner1_1.png

1253 ms

slick.woff

slick.woff

13 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

37 ms

sdk.js

sdk.js

37 ms

settings

settings

95 ms

32 ms

icon_banner1_2.png

icon_banner1_2.png

1165 ms

icon_banner1_3.png

icon_banner1_3.png

1182 ms

icon_banner1_4.png

icon_banner1_4.png

1182 ms

icon_banner1_5.png

icon_banner1_5.png

1205 ms

icon_banner1_6.png

icon_banner1_6.png

1307 ms

icon_banner2_1.png

icon_banner2_1.png

1308 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

3 ms

embeds

embeds

27 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

16 ms

js

js

37 ms

search.js

search.js

4 ms

geometry.js

geometry.js

7 ms

main.js

main.js

12 ms

icon_banner2_2.png

icon_banner2_2.png

1175 ms

icon_banner2_4.png

icon_banner2_4.png

1194 ms

icon_banner2_5.png

icon_banner2_5.png

1195 ms

icon_banner2_6.png

icon_banner2_6.png

1217 ms

icon_banner2_7.png

icon_banner2_7.png

1310 ms

icon_banner2_8.png

icon_banner2_8.png

1147 ms

icon_banner2_9.png

icon_banner2_9.png

1165 ms

icon_banner2_10.png

icon_banner2_10.png

1038 ms

icon_banner2_11.png

icon_banner2_11.png

1034 ms

icon_banner2_1.png

icon_banner2_1.png

1051 ms

icon_banner2_2.png

icon_banner2_2.png

1135 ms

icon_banner2_4.png

icon_banner2_4.png

999 ms

icon_banner2_5.png

icon_banner2_5.png

1016 ms

icon_banner2_6.png

icon_banner2_6.png

1035 ms

icon_banner2_7.png

icon_banner2_7.png

1020 ms

icon_banner2_8.png

icon_banner2_8.png

1053 ms

icon_banner2_9.png

icon_banner2_9.png

1117 ms

icon_banner2_10.png

icon_banner2_10.png

1000 ms

icon_banner2_11.png

icon_banner2_11.png

1017 ms

footer_logo.png

footer_logo.png

1038 ms

privacy.png

privacy.png

1021 ms

pagetop.png

pagetop.png

1058 ms

footer_tel.png

footer_tel.png

990 ms

footer_shopping.png

footer_shopping.png

995 ms

footer_mail.png

footer_mail.png

1008 ms

footer_menu.png

footer_menu.png

1020 ms

side_m1_bg.png

side_m1_bg.png

1019 ms

side_m2_bg.png

side_m2_bg.png

1041 ms

side_access_bg.png

side_access_bg.png

990 ms

top_news.png

top_news.png

996 ms

p_m_bg2.png

p_m_bg2.png

1005 ms

footer_tel.png

footer_tel.png

1020 ms

Accessibility Review

e-koyama.com accessibility score

83

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

Best Practices

e-koyama.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

e-koyama.com SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 E-koyama.com 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 E-koyama.com 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

e-koyama.com

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