Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

jusyo.jp

住所データ、住所マスタ、住所CSVの無料ダウンロードサイト!【住所.jp】

Page Load Speed

2.7 sec in total

First Response

620 ms

Resources Loaded

1.8 sec

Page Rendered

202 ms

jusyo.jp screenshot

About Website

Visit jusyo.jp now to see the best up-to-date Jusyo content for Japan and also check out these interesting facts you probably never knew about jusyo.jp

日本郵便CSVを元にしたスタンダードな住所コードマスタがダウンロードできます。

Visit jusyo.jp

Key Findings

We analyzed Jusyo.jp page load time and found that the first response time was 620 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

jusyo.jp performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

98/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.9 s

100/100

10%

Network Requests Diagram

jusyo.jp

620 ms

base.css

359 ms

logo-1.gif

536 ms

button-csv.gif

415 ms

button-tsv.gif

472 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 86% of them (12 requests) were addressed to the original Jusyo.jp, 14% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (893 ms) belongs to the original domain Jusyo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 27.1 kB (56%)

Content Size

48.9 kB

After Optimization

21.7 kB

In fact, the total size of Jusyo.jp main page is 48.9 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. 15% of websites need less resources to load. HTML takes 29.3 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 26.4 kB

  • Original 29.3 kB
  • After minification 25.8 kB
  • After compression 2.9 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 3.5 kB, which is 12% 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 26.4 kB or 90% of the original size.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

-28%

Potential reduce by 674 B

  • Original 2.4 kB
  • After minification 2.4 kB
  • After compression 1.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. Jusyo.jp needs all CSS files to be minified and compressed as it can save up to 674 B or 28% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

13

After Optimization

13

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jusyo. According to our analytics all requests are already optimized.

Accessibility Review

jusyo.jp accessibility score

70

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

jusyo.jp 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

SEO Factors

jusyo.jp SEO score

69

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

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 Jusyo.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 Jusyo.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

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