Tools & Wizards About Us
hotflops.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

hotflops.jp

ホットフロップス オンラインショップ｜hotflops・ホットフロップス・公式ホームページ

Page Load Speed

5.6 sec in total

First Response

796 ms

Resources Loaded

4.7 sec

Page Rendered

133 ms

hotflops.jp screenshot

About Website

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

hotflops（ホットフロップス）のサンダルは世界中で販売され、多彩なデザインで多くの反響を呼んでいます。通販もフルラインナップで展開中です。

Visit hotflops.jp

Key Findings

We analyzed Hotflops.jp page load time and found that the first response time was 796 ms and then it took 4.8 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

hotflops.jp performance score

0

Network Requests Diagram

hotflops.jp

796 ms

page.css

401 ms

style.css

391 ms

common.css

581 ms

lightbox.css

421 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 169.6 kB (81%)

Content Size

208.7 kB

After Optimization

39.1 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Hotflops.jp main page is 208.7 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. Javascripts take 190.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 6.5 kB

  • Original 8.6 kB
  • After minification 7.6 kB
  • After compression 2.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 993 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 6.5 kB or 76% of the original size.

JavaScript Optimization

-82%

Potential reduce by 156.3 kB

  • Original 190.9 kB
  • After minification 136.8 kB
  • After compression 34.7 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 156.3 kB or 82% of the original size.

CSS Optimization

-75%

Potential reduce by 6.8 kB

  • Original 9.2 kB
  • After minification 5.9 kB
  • After compression 2.3 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. Hotflops.jp needs all CSS files to be minified and compressed as it can save up to 6.8 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (21%)

Requests Now

33

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hotflops.jp

hotflops.jp

796 ms

page.css

page.css

401 ms

style.css

style.css

391 ms

common.css

common.css

581 ms

lightbox.css

lightbox.css

421 ms

prototype.js

prototype.js

1605 ms

scriptaculous.js

scriptaculous.js

434 ms

lightbox.js

lightbox.js

824 ms

back.jpg

back.jpg

192 ms

effects.js

effects.js

788 ms

builder.js

builder.js

220 ms

spc.gif

spc.gif

193 ms

2_base_01.gif

2_base_01.gif

193 ms

collection_topbg.gif

collection_topbg.gif

192 ms

collection_top.gif

collection_top.gif

551 ms

base_03.gif

base_03.gif

386 ms

link_01.gif

link_01.gif

191 ms

link_02.gif

link_02.gif

382 ms

link_03.gif

link_03.gif

383 ms

link_04.gif

link_04.gif

384 ms

link_05.gif

link_05.gif

385 ms

link_06.gif

link_06.gif

572 ms

link_07.gif

link_07.gif

572 ms

link_09.gif

link_09.gif

576 ms

link_10.gif

link_10.gif

578 ms

link_11.gif

link_11.gif

577 ms

collection.gif

collection.gif

731 ms

collection_list_01.gif

collection_list_01.gif

1330 ms

collection_list_03.gif

collection_list_03.gif

1409 ms

collection_list_02.gif

collection_list_02.gif

957 ms

collection_list_04.gif

collection_list_04.gif

1342 ms

collection_list_05.gif

collection_list_05.gif

960 ms

base_10.gif

base_10.gif

915 ms

loading.gif

loading.gif

197 ms

closelabel.gif

closelabel.gif

196 ms

SEO Factors

hotflops.jp SEO score

0

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

hotflops.jp

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