Access tth-japanpost.jp. ホーム

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value1.0 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

tth-japanpost.jp

533 ms

symbol.gif

176 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Tth-japanpost.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (533 ms) belongs to the original domain Tth-japanpost.jp.

Content Size

5.4 kB

After Optimization

4.7 kB

In fact, the total size of Tth-japanpost.jp main page is 5.4 kB. This result falls within a big category (top 100 000) of medium weight web pages. Only a small number of websites need less resources to load. Images take 4.0 kB which makes up the majority of the site volume.

HTML Optimization

-47%

Potential reduce by 660 B

Original 1.4 kB
After minification 1.4 kB
After compression 759 B

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 660 B or 47% of the original size.

Image Optimization

-1%

Potential reduce by 30 B

Original 4.0 kB
After minification 3.9 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. Tth Japanpost images are well optimized though.

Requests Now

After Optimization

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

Accessibility Issues

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

High

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

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.

High

Image elements do not have [alt] attributes

These items highlight common accessibility best practices.

High

The document uses <meta http-equiv="refresh">

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

Language and Encoding

Language Detected

JA
Language Claimed

N/A
Encoding

SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tth-japanpost.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 Tth-japanpost.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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