Tools & Wizards About Us
stussylivin.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

stussylivin.jp

日本旅行

Page Load Speed

4 sec in total

First Response

470 ms

Resources Loaded

3.4 sec

Page Rendered

136 ms

stussylivin.jp screenshot

About Website

Click here to check amazing Stussylivin content for Hong Kong. Otherwise, check out these important facts you probably never knew about stussylivin.jp

日本は絶妙な異国情緒の宝庫です。日本の壮大な大都市と絵のように美しい田園地帯、沖縄本島の壮大なビーチ、古代の神社など、すべて日本についてです。 古代の寺院や精霊の門は、鏡張りの高層ビル、派手な「5人」（小さな旅館、誇大宣伝されたスパセンター）、反射するプールが温泉に並んでいます。この国の最も特徴的な特徴は、東洋の歴史と

Visit stussylivin.jp

Key Findings

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

Performance Metrics

stussylivin.jp performance score

0

Network Requests Diagram

stussylivin.jp

470 ms

fonts-min.css

21 ms

style-com.css

168 ms

supersized.css

333 ms

jquery.min.js

29 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 89% of them (17 requests) were addressed to the original Stussylivin.jp, 5% (1 request) were made to Yui.yahooapis.com and 5% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Stussylivin.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 13.1 kB (1%)

Content Size

1.7 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stussylivin.jp main page is 1.7 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. Only 5% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-57%

Potential reduce by 2.4 kB

  • Original 4.2 kB
  • After minification 3.7 kB
  • After compression 1.8 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 457 B, which is 11% 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 2.4 kB or 57% of the original size.

Image Optimization

-0%

Potential reduce by 1.1 kB

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

JavaScript Optimization

-80%

Potential reduce by 3.5 kB

  • Original 4.4 kB
  • After minification 2.4 kB
  • After compression 891 B

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 3.5 kB or 80% of the original size.

CSS Optimization

-79%

Potential reduce by 6.1 kB

  • Original 7.8 kB
  • After minification 5.7 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. Stussylivin.jp needs all CSS files to be minified and compressed as it can save up to 6.1 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (44%)

Requests Now

18

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stussylivin.jp

stussylivin.jp

470 ms

fonts-min.css

fonts-min.css

21 ms

style-com.css

style-com.css

168 ms

supersized.css

supersized.css

333 ms

jquery.min.js

jquery.min.js

29 ms

supersized.3.0.core.js

supersized.3.0.core.js

344 ms

jquery.newsticker.js

jquery.newsticker.js

370 ms

progress.gif

progress.gif

189 ms

index-logo_x4.png

index-logo_x4.png

555 ms

index-gnavi-bg.png

index-gnavi-bg.png

173 ms

index-gnavi_01.png

index-gnavi_01.png

190 ms

index-gnavi_02.png

index-gnavi_02.png

338 ms

index-gnavi_03.png

index-gnavi_03.png

345 ms

index-gnavi_04.png

index-gnavi_04.png

354 ms

index-gnavi_05.png

index-gnavi_05.png

378 ms

index-gnavi_06.png

index-gnavi_06.png

396 ms

copyright-bg-index.png

copyright-bg-index.png

505 ms

copyright.png

copyright.png

515 ms

WT_H1371-x-W1962_8.jpg

WT_H1371-x-W1962_8.jpg

2512 ms

SEO Factors

stussylivin.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stussylivin.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Stussylivin.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

stussylivin.jp

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