Tools & Wizards About Us
stylecom.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

stylecom.jp

ブランドクローズのお知らせ ｜ NEWS ｜ 東京スタイル

Page Load Speed

3.5 sec in total

First Response

475 ms

Resources Loaded

2.8 sec

Page Rendered

172 ms

stylecom.jp screenshot

About Website

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

株式会社東京スタイルは1949年創立の婦人服総合メーカーです。ヤングからミセスまで幅広いお客様にファッションをご提案します。東京スタイルのニュースページです。

Visit stylecom.jp

Key Findings

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

Performance Metrics

stylecom.jp performance score

0

Network Requests Diagram

post_16.php

475 ms

base.css

300 ms

jquery.js

769 ms

jquery.easing.js

311 ms

rollover.js

313 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Stylecom.jp, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Tokyostyle.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.4 kB (24%)

Content Size

488.7 kB

After Optimization

369.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stylecom.jp main page is 488.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. 20% of websites need less resources to load. Images take 330.8 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 12.4 kB

  • Original 15.7 kB
  • After minification 12.5 kB
  • After compression 3.2 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.1 kB, which is 20% 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 12.4 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 19.8 kB

  • Original 330.8 kB
  • After minification 311.1 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. Stylecom images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 72.2 kB

  • Original 124.2 kB
  • After minification 117.8 kB
  • After compression 52.0 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 72.2 kB or 58% of the original size.

CSS Optimization

-83%

Potential reduce by 15.0 kB

  • Original 18.0 kB
  • After minification 14.6 kB
  • After compression 3.0 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. Stylecom.jp needs all CSS files to be minified and compressed as it can save up to 15.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (61%)

Requests Now

41

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

post_16.php

post_16.php

475 ms

base.css

base.css

300 ms

jquery.js

jquery.js

769 ms

jquery.easing.js

jquery.easing.js

311 ms

rollover.js

rollover.js

313 ms

common.js

common.js

313 ms

scroller.js

scroller.js

336 ms

news.css

news.css

448 ms

bg_sub_col.jpg

bg_sub_col.jpg

153 ms

ga.js

ga.js

52 ms

logo.png

logo.png

155 ms

icon_home.gif

icon_home.gif

156 ms

arrow_br.gif

arrow_br.gif

178 ms

h1_corporate.gif

h1_corporate.gif

157 ms

bt_news_top.gif

bt_news_top.gif

156 ms

brandclose-thumb-280xauto-10126.jpg

brandclose-thumb-280xauto-10126.jpg

253 ms

bg_nav_corporate.gif

bg_nav_corporate.gif

307 ms

pagetop.gif

pagetop.gif

308 ms

copyright.gif

copyright.gif

307 ms

bg_sub_col_inn.jpg

bg_sub_col_inn.jpg

1075 ms

dot_01.png

dot_01.png

352 ms

gn.png

gn.png

856 ms

ln_news_b.png

ln_news_b.png

459 ms

ln_news.png

ln_news.png

460 ms

nav_top.png

nav_top.png

459 ms

bnr_02.png

bnr_02.png

526 ms

tl_gnav_02.png

tl_gnav_02.png

614 ms

tl_gnav_03.png

tl_gnav_03.png

614 ms

tl_gnav_04.png

tl_gnav_04.png

614 ms

tl_gnav_05.png

tl_gnav_05.png

706 ms

tl_gnav_06.png

tl_gnav_06.png

768 ms

tl_copyright.png

tl_copyright.png

766 ms

sp_arrow_04.png

sp_arrow_04.png

768 ms

sp_bnr_01.gif

sp_bnr_01.gif

887 ms

sp_bnr_02.gif

sp_bnr_02.gif

919 ms

__utm.gif

__utm.gif

12 ms

icon_home_on.gif

icon_home_on.gif

153 ms

bt_news_top_on.gif

bt_news_top_on.gif

155 ms

pagetop_on.gif

pagetop_on.gif

156 ms

nav_top_on.png

nav_top_on.png

190 ms

bnr_02_on.png

bnr_02_on.png

157 ms

fn.png

fn.png

156 ms

SEO Factors

stylecom.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

stylecom.jp

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