Tools & Wizards About Us
e-street.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

e-street.jp

Page Load Speed

10.7 sec in total

First Response

4.8 sec

Resources Loaded

5.6 sec

Page Rendered

266 ms

e-street.jp screenshot

About Website

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

東京23区の商店街情報から探す、店舗物件情報サイト「マチキタ！」。東京都内でお店の出店を考えている方のための、店舗出店情報サイト。東京の商店街のファーストフードの出店数、コンビニ・スーパーの出店数など、詳細情報をまとめて発信しています。

Visit e-street.jp

Key Findings

We analyzed E-street.jp page load time and found that the first response time was 4.8 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

e-street.jp performance score

0

Network Requests Diagram

e-street.jp

4807 ms

default.css

304 ms

top.css

306 ms

jquery-1.3.2.min.js

597 ms

jquery_easingscroll.js

309 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 96% of them (49 requests) were addressed to the original E-street.jp, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain E-street.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.8 kB (15%)

Content Size

652.9 kB

After Optimization

557.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 14.7 kB

  • Original 18.4 kB
  • After minification 17.3 kB
  • After compression 3.7 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. 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 14.7 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 509.0 kB
  • After minification 509.0 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. E Street images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 43.3 kB

  • Original 81.3 kB
  • After minification 79.1 kB
  • After compression 38.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 43.3 kB or 53% of the original size.

CSS Optimization

-86%

Potential reduce by 37.9 kB

  • Original 44.2 kB
  • After minification 34.0 kB
  • After compression 6.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. E-street.jp needs all CSS files to be minified and compressed as it can save up to 37.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (46%)

Requests Now

48

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

e-street.jp

e-street.jp

4807 ms

default.css

default.css

304 ms

top.css

top.css

306 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

597 ms

jquery_easingscroll.js

jquery_easingscroll.js

309 ms

blank.js

blank.js

304 ms

common.css

common.css

152 ms

base.css

base.css

154 ms

parts-image.css

parts-image.css

155 ms

parts-product_details.css

parts-product_details.css

156 ms

parts-icons.css

parts-icons.css

299 ms

parts-route_icon.css

parts-route_icon.css

302 ms

parts-route_title.css

parts-route_title.css

301 ms

parts-ptstyle.css

parts-ptstyle.css

152 ms

parts-page_top.css

parts-page_top.css

290 ms

parts-input_btn.css

parts-input_btn.css

299 ms

parts-side-box.css

parts-side-box.css

300 ms

side.css

side.css

302 ms

bg_body.jpg

bg_body.jpg

152 ms

bg_header.jpg

bg_header.jpg

152 ms

logo.jpg

logo.jpg

155 ms

navi.jpg

navi.jpg

448 ms

bt_sitemap.jpg

bt_sitemap.jpg

155 ms

bg_main_column_body.jpg

bg_main_column_body.jpg

307 ms

bg_main_column_head.jpg

bg_main_column_head.jpg

303 ms

bg_main_column_tail.jpg

bg_main_column_tail.jpg

308 ms

image_main.jpg

image_main.jpg

1232 ms

title_pickup.jpg

title_pickup.jpg

462 ms

bg_pickup_tail.jpg

bg_pickup_tail.jpg

751 ms

title_area.jpg

title_area.jpg

298 ms

bg_top_tail.jpg

bg_top_tail.jpg

152 ms

ico_area.gif

ico_area.gif

186 ms

bg_ranking_tail.jpg

bg_ranking_tail.jpg

199 ms

title_ranking.jpg

title_ranking.jpg

302 ms

bg_up_ranking.jpg

bg_up_ranking.jpg

341 ms

title_up_rank.jpg

title_up_rank.jpg

349 ms

u_rank1.jpg

u_rank1.jpg

448 ms

u_rank2.jpg

u_rank2.jpg

451 ms

u_rank3.jpg

u_rank3.jpg

500 ms

bg_dw_ranking.jpg

bg_dw_ranking.jpg

499 ms

title_dw_rank.jpg

title_dw_rank.jpg

502 ms

l_rank1.jpg

l_rank1.jpg

598 ms

l_rank2.jpg

l_rank2.jpg

600 ms

l_rank3.jpg

l_rank3.jpg

647 ms

bg_tag.jpg

bg_tag.jpg

647 ms

twitter_top.gif

twitter_top.gif

648 ms

page_top.gif

page_top.gif

747 ms

bg_footer.jpg

bg_footer.jpg

748 ms

bn_dokoiku.jpg

bn_dokoiku.jpg

795 ms

ga.js

ga.js

5 ms

__utm.gif

__utm.gif

15 ms

SEO Factors

e-street.jp SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-street.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that E-street.jp main page’s claimed encoding is euc-jp. 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

e-street.jp

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