Tools & Wizards About Us
zao-press.jp screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

zao-press.jp

山形県上山市のプレス加工、金型製作会社「株式会社ザオウ製作所」

Page Load Speed

5.8 sec in total

First Response

783 ms

Resources Loaded

4.7 sec

Page Rendered

326 ms

zao-press.jp screenshot

About Website

Welcome to zao-press.jp homepage info - get ready to check Zao Press best content right away, or after learning these important things about zao-press.jp

株式会社ザオウ製作所は山形県上山市の金属プレス加工、金型製作会社です。金型の制作のみの承っておりますので、ご用命の際はお気軽にお問い合わせください。

Visit zao-press.jp

Key Findings

We analyzed Zao-press.jp page load time and found that the first response time was 783 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

zao-press.jp performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value15.2 s

1/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

zao-press.jp

783 ms

A.jqselectable.css+prettyphoto.css+popup.css+base.css+print.css+layout.css,,q20150708+jqtransform.css,Mcc._Rn03G5v2q.css.pagespeed.cf.d-C8lroREQ.css

878 ms

jquery_v2.1.4.js.pagespeed.jm.UWusawvZ2R.js

1085 ms

ajax_v2016.js.pagespeed.jm.IhMMOvTC75.js

543 ms

jcarousellite_v1.1.js.pagespeed.jm.wtlzVdCKLg.js

552 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 66% of them (27 requests) were addressed to the original Zao-press.jp, 32% (13 requests) were made to Web.xaas.jp and 2% (1 request) were made to M6203506.xaas.jp. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Zao-press.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 361.6 kB (27%)

Content Size

1.4 MB

After Optimization

996.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zao-press.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 902.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 19.1 kB

  • Original 25.8 kB
  • After minification 24.4 kB
  • After compression 6.7 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 19.1 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 6.1 kB

  • Original 902.7 kB
  • After minification 896.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. Zao Press images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 227.8 kB

  • Original 301.2 kB
  • After minification 282.8 kB
  • After compression 73.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 227.8 kB or 76% of the original size.

CSS Optimization

-85%

Potential reduce by 108.6 kB

  • Original 128.3 kB
  • After minification 118.0 kB
  • After compression 19.7 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. Zao-press.jp needs all CSS files to be minified and compressed as it can save up to 108.6 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

40

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zao-press.jp

zao-press.jp

783 ms

A.jqselectable.css+prettyphoto.css+popup.css+base.css+print.css+layout.css,,q20150708+jqtransform.css,Mcc._Rn03G5v2q.css.pagespeed.cf.d-C8lroREQ.css

A.jqselectable.css+prettyphoto.css+popup.css+base.css+print.css+layout.css,,q20150708+jqtransform.css,Mcc._Rn03G5v2q.css.pagespeed.cf.d-C8lroREQ.css

878 ms

jquery_v2.1.4.js.pagespeed.jm.UWusawvZ2R.js

jquery_v2.1.4.js.pagespeed.jm.UWusawvZ2R.js

1085 ms

ajax_v2016.js.pagespeed.jm.IhMMOvTC75.js

ajax_v2016.js.pagespeed.jm.IhMMOvTC75.js

543 ms

jcarousellite_v1.1.js.pagespeed.jm.wtlzVdCKLg.js

jcarousellite_v1.1.js.pagespeed.jm.wtlzVdCKLg.js

552 ms

mousewheel_v3.1.13.js.pagespeed.jm.wBwlG6vk-c.js

mousewheel_v3.1.13.js.pagespeed.jm.wBwlG6vk-c.js

554 ms

jscrollpane.js.pagespeed.jm.2wYEC_BNG3.js

jscrollpane.js.pagespeed.jm.2wYEC_BNG3.js

742 ms

treeview.js.pagespeed.jm.Ccxdh7coVu.js

treeview.js.pagespeed.jm.Ccxdh7coVu.js

716 ms

common_v2016.js.pagespeed.jm.6iGU-6_f5J.js

common_v2016.js.pagespeed.jm.6iGU-6_f5J.js

978 ms

prettyphoto_v3.1.6.js,q20150527.pagespeed.jm.w2fGLjjfmp.js

prettyphoto_v3.1.6.js,q20150527.pagespeed.jm.w2fGLjjfmp.js

932 ms

theme.css

theme.css

519 ms

addStyle.css

addStyle.css

406 ms

jquery.cycle.all.js

jquery.cycle.all.js

1014 ms

information.js.pagespeed.jm.95f-nsecLq.js

information.js.pagespeed.jm.95f-nsecLq.js

727 ms

hdr_bg2.jpg

hdr_bg2.jpg

361 ms

xspace.gif.pagespeed.ic.lRMfmktUso.png

xspace.gif.pagespeed.ic.lRMfmktUso.png

187 ms

hdr_bg.jpg

hdr_bg.jpg

1377 ms

logo.jpg

logo.jpg

964 ms

icn_home.gif

icn_home.gif

387 ms

top_img001.jpg

top_img001.jpg

759 ms

top_img002.jpg

top_img002.jpg

783 ms

seizoukyokasyou.jpg

seizoukyokasyou.jpg

710 ms

bnr_img008.gif

bnr_img008.gif

754 ms

image1.jpg

image1.jpg

1944 ms

image2.jpg

image2.jpg

2204 ms

image3.jpg

image3.jpg

2236 ms

image4.jpg

image4.jpg

2519 ms

bnr_img001.jpg

bnr_img001.jpg

1744 ms

bnr_img002.jpg

bnr_img002.jpg

1777 ms

bnr_img003.jpg

bnr_img003.jpg

2135 ms

bnr_img004.jpg

bnr_img004.jpg

2172 ms

bnr_img005.jpg

bnr_img005.jpg

2294 ms

bnr_img006.jpg

bnr_img006.jpg

2526 ms

bnr_img007.jpg

bnr_img007.jpg

2967 ms

icn_h_regist.gif

icn_h_regist.gif

2366 ms

index

index

2569 ms

loading_icon.gif

loading_icon.gif

370 ms

space.gif

space.gif

351 ms

bg_footer.gif

bg_footer.gif

2566 ms

icn_h_information.gif

icn_h_information.gif

182 ms

bg_border01.gif

bg_border01.gif

203 ms

Accessibility Review

zao-press.jp accessibility score

83

Accessibility Issues

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 input fields do not have accessible names

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.

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

High

Links do not have a discernible name

High

<object> elements do not have alternate text

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

zao-press.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

zao-press.jp SEO score

93

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zao-press.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 Zao-press.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

zao-press.jp

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