Tools & Wizards About Us
nextlife-machida.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

nextlife-machida.jp

町田店｜ネクストライフ

Page Load Speed

7.2 sec in total

First Response

429 ms

Resources Loaded

6 sec

Page Rendered

759 ms

nextlife-machida.jp screenshot

About Website

Click here to check amazing Nextlife Machida content. Otherwise, check out these important facts you probably never knew about nextlife-machida.jp

町田駅(町田市)・長津田駅(横浜市緑区)周辺の賃貸物件をお探しの方はネクストライフ町田店へ。

Visit nextlife-machida.jp

Key Findings

We analyzed Nextlife-machida.jp page load time and found that the first response time was 429 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

nextlife-machida.jp performance score

0

Network Requests Diagram

nextlife-machida.jp

429 ms

www.nextlife-machida.jp

420 ms

954 ms

common.css

340 ms

list.css

343 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Nextlife-machida.jp, 49% (58 requests) were made to Next-life.co.jp and 10% (12 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Next-life.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 658.2 kB (34%)

Content Size

1.9 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 110.1 kB

  • Original 127.6 kB
  • After minification 91.9 kB
  • After compression 17.5 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 35.7 kB, which is 28% 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 110.1 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 35.2 kB

  • Original 1.0 MB
  • After minification 992.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. Nextlife Machida images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 507.4 kB

  • Original 768.6 kB
  • After minification 759.1 kB
  • After compression 261.2 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 507.4 kB or 66% of the original size.

CSS Optimization

-75%

Potential reduce by 5.5 kB

  • Original 7.3 kB
  • After minification 6.2 kB
  • After compression 1.8 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. Nextlife-machida.jp needs all CSS files to be minified and compressed as it can save up to 5.5 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (50%)

Requests Now

109

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nextlife-machida.jp

nextlife-machida.jp

429 ms

www.nextlife-machida.jp

www.nextlife-machida.jp

420 ms

954 ms

common.css

common.css

340 ms

list.css

list.css

343 ms

search_common.css

search_common.css

347 ms

shop_sp.css

shop_sp.css

333 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

529 ms

yugaAutoLine.js

yugaAutoLine.js

501 ms

jquery.cookie.js

jquery.cookie.js

676 ms

jquery.page-scroller-306.js

jquery.page-scroller-306.js

685 ms

common.js

common.js

688 ms

list.js

list.js

718 ms

result.js

result.js

842 ms

jquery.lazyload.js

jquery.lazyload.js

878 ms

header.css

header.css

998 ms

conversion.js

conversion.js

33 ms

animationrollover.js

animationrollover.js

1018 ms

bookmark_button.js

bookmark_button.js

329 ms

jquery-ui.min.js

jquery-ui.min.js

36 ms

jquery-ui.css

jquery-ui.css

46 ms

footer.css

footer.css

862 ms

analytics.js

analytics.js

15 ms

fbds.js

fbds.js

148 ms

button-only.gif

button-only.gif

231 ms

logo.png

logo.png

407 ms

card.jpg

card.jpg

466 ms

tel.png

tel.png

528 ms

nav_01.jpg

nav_01.jpg

551 ms

nav_02.jpg

nav_02.jpg

550 ms

nav_03.jpg

nav_03.jpg

554 ms

nav_04.jpg

nav_04.jpg

724 ms

nav_05.jpg

nav_05.jpg

817 ms

img_shop_main.jpg

img_shop_main.jpg

1708 ms

ttl_shop_info.jpg

ttl_shop_info.jpg

872 ms

img_shop01.jpg

img_shop01.jpg

1226 ms

img_shop02.jpg

img_shop02.jpg

1046 ms

img_shop03.jpg

img_shop03.jpg

1226 ms

toiawase_tel.jpg

toiawase_tel.jpg

1319 ms

toiawase_mail.jpg

toiawase_mail.jpg

1378 ms

ttl_shop_kodawari.jpg

ttl_shop_kodawari.jpg

1394 ms

img_shop_kodawari01.jpg

img_shop_kodawari01.jpg

1698 ms

img_shop_kodawari02.jpg

img_shop_kodawari02.jpg

1719 ms

img_shop_kodawari03.jpg

img_shop_kodawari03.jpg

1808 ms

img_shop_kodawari04.jpg

img_shop_kodawari04.jpg

2024 ms

ttl_list_squeeze.gif

ttl_list_squeeze.gif

1705 ms

bt_list_side_search.gif

bt_list_side_search.gif

2027 ms

tti_erea_info.jpg

tti_erea_info.jpg

2036 ms

page_top.png

page_top.png

2051 ms

collect

collect

14 ms

bg_head_history.jpg

bg_head_history.jpg

2032 ms

bg_header_favorite.jpg

bg_header_favorite.jpg

2120 ms

clearfix.gif

clearfix.gif

2332 ms

110 ms

bg_header.gif

bg_header.gif

2396 ms

bg_h1.gif

bg_h1.gif

2242 ms

ttl_h1.jpg

ttl_h1.jpg

2253 ms

widgets.js

widgets.js

32 ms

281 ms

plusone.js

plusone.js

257 ms

maps

maps

282 ms

207 ms

like.php

like.php

177 ms

233 ms

bg_side_list.jpg

bg_side_list.jpg

2138 ms

2607 ms

25300494_1_138_142_3.jpg

25300494_1_138_142_3.jpg

435 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

76 ms

bg_footermenu.jpg

bg_footermenu.jpg

2100 ms

bg_footer_arw.jpg

bg_footer_arw.jpg

2338 ms

logo_on.png

logo_on.png

2560 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

531 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

594 ms

toiawase_mail_on.jpg

toiawase_mail_on.jpg

2564 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

15 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

42 ms

fastbutton

fastbutton

70 ms

embed

embed

506 ms

img_shop_kodawari01_on.jpg

img_shop_kodawari01_on.jpg

2719 ms

postmessageRelay

postmessageRelay

71 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

40 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

37 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

36 ms

img_shop_kodawari02_on.jpg

img_shop_kodawari02_on.jpg

2676 ms

img_shop_kodawari03_on.jpg

img_shop_kodawari03_on.jpg

2884 ms

img_shop_kodawari04_on.jpg

img_shop_kodawari04_on.jpg

2894 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

21 ms

rpc:shindig_random.js

rpc:shindig_random.js

34 ms

bt_list_side_search_on.gif

bt_list_side_search_on.gif

2737 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

3 ms

jot

jot

93 ms

loading.gif

loading.gif

2595 ms

js

js

73 ms

init_embed.js

init_embed.js

34 ms

common.js

common.js

63 ms

map.js

map.js

78 ms

google4.png

google4.png

30 ms

overlay.js

overlay.js

28 ms

util.js

util.js

85 ms

onion.js

onion.js

85 ms

search_impl.js

search_impl.js

105 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

272 ms

stats.js

stats.js

68 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

47 ms

transparent.png

transparent.png

40 ms

kh

kh

120 ms

controls.js

controls.js

33 ms

vt

vt

181 ms

vt

vt

133 ms

vt

vt

171 ms

vt

vt

176 ms

css

css

77 ms

mapcnt6.png

mapcnt6.png

20 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

25 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

39 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

45 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

49 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

14 ms

SEO Factors

nextlife-machida.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 Nextlife-machida.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 Nextlife-machida.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

nextlife-machida.jp

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