Tools & Wizards About Us
nextlife-sagamiono.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

nextlife-sagamiono.jp

相模大野店｜ネクストライフ

Page Load Speed

7.6 sec in total

First Response

481 ms

Resources Loaded

6.4 sec

Page Rendered

693 ms

nextlife-sagamiono.jp screenshot

About Website

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

相模大野駅(相模原市南区)・中央林間駅(大和市)周辺の賃貸物件をお探しの方はネクストライフ相模大野店へ。

Visit nextlife-sagamiono.jp

Key Findings

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

Performance Metrics

nextlife-sagamiono.jp performance score

0

Network Requests Diagram

nextlife-sagamiono.jp

481 ms

www.nextlife-sagamiono.jp

428 ms

1030 ms

common.css

367 ms

list.css

365 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Nextlife-sagamiono.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 (3.1 sec) relates to the external source Next-life.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 690.0 kB (35%)

Content Size

1.9 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nextlife-sagamiono.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. 60% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 104.9 kB

  • Original 122.8 kB
  • After minification 90.2 kB
  • After compression 17.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 32.5 kB, which is 26% 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 104.9 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 35.7 kB

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

JavaScript Optimization

-68%

Potential reduce by 543.9 kB

  • Original 805.3 kB
  • After minification 795.7 kB
  • After compression 261.3 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 543.9 kB or 68% 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-sagamiono.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 (49%)

Requests Now

110

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nextlife Sagamiono. 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-sagamiono.jp

nextlife-sagamiono.jp

481 ms

www.nextlife-sagamiono.jp

www.nextlife-sagamiono.jp

428 ms

1030 ms

common.css

common.css

367 ms

list.css

list.css

365 ms

search_common.css

search_common.css

374 ms

shop_sp.css

shop_sp.css

362 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

569 ms

yugaAutoLine.js

yugaAutoLine.js

547 ms

jquery.cookie.js

jquery.cookie.js

712 ms

jquery.page-scroller-306.js

jquery.page-scroller-306.js

707 ms

common.js

common.js

731 ms

list.js

list.js

737 ms

result.js

result.js

909 ms

jquery.lazyload.js

jquery.lazyload.js

911 ms

header.css

header.css

1049 ms

conversion.js

conversion.js

15 ms

animationrollover.js

animationrollover.js

1060 ms

bookmark_button.js

bookmark_button.js

343 ms

jquery-ui.min.js

jquery-ui.min.js

12 ms

jquery-ui.css

jquery-ui.css

15 ms

footer.css

footer.css

1014 ms

analytics.js

analytics.js

9 ms

fbds.js

fbds.js

8 ms

button-only.gif

button-only.gif

251 ms

logo.png

logo.png

406 ms

card.jpg

card.jpg

561 ms

tel.png

tel.png

561 ms

nav_01.jpg

nav_01.jpg

573 ms

nav_02.jpg

nav_02.jpg

635 ms

nav_03.jpg

nav_03.jpg

634 ms

nav_04.jpg

nav_04.jpg

800 ms

nav_05.jpg

nav_05.jpg

851 ms

img_shop_main.jpg

img_shop_main.jpg

1873 ms

ttl_shop_info.jpg

ttl_shop_info.jpg

982 ms

img_shop01.jpg

img_shop01.jpg

1361 ms

img_shop02.jpg

img_shop02.jpg

1226 ms

img_shop03.jpg

img_shop03.jpg

1307 ms

toiawase_tel.jpg

toiawase_tel.jpg

1385 ms

toiawase_mail.jpg

toiawase_mail.jpg

1521 ms

ttl_shop_kodawari.jpg

ttl_shop_kodawari.jpg

1588 ms

img_shop_kodawari01.jpg

img_shop_kodawari01.jpg

2067 ms

img_shop_kodawari02.jpg

img_shop_kodawari02.jpg

1843 ms

img_shop_kodawari03.jpg

img_shop_kodawari03.jpg

1915 ms

img_shop_kodawari04.jpg

img_shop_kodawari04.jpg

2176 ms

ttl_list_squeeze.gif

ttl_list_squeeze.gif

1914 ms

bt_list_side_search.gif

bt_list_side_search.gif

2204 ms

tti_erea_info.jpg

tti_erea_info.jpg

2211 ms

page_top.png

page_top.png

2239 ms

collect

collect

12 ms

104 ms

bg_head_history.jpg

bg_head_history.jpg

2274 ms

bg_header_favorite.jpg

bg_header_favorite.jpg

2410 ms

clearfix.gif

clearfix.gif

2533 ms

118 ms

bg_header.gif

bg_header.gif

2574 ms

bg_h1.gif

bg_h1.gif

2411 ms

ttl_h1.jpg

ttl_h1.jpg

2438 ms

widgets.js

widgets.js

35 ms

246 ms

plusone.js

plusone.js

185 ms

maps

maps

89 ms

embed

embed

182 ms

bg_side_list.jpg

bg_side_list.jpg

2363 ms

106 ms

2711 ms

24618924_1_138_142_3.jpg

24618924_1_138_142_3.jpg

420 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

68 ms

bg_footermenu.jpg

bg_footermenu.jpg

2570 ms

bg_footer_arw.jpg

bg_footer_arw.jpg

2604 ms

logo_on.png

logo_on.png

2763 ms

like.php

like.php

222 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

18 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

34 ms

fastbutton

fastbutton

105 ms

postmessageRelay

postmessageRelay

76 ms

toiawase_mail_on.jpg

toiawase_mail_on.jpg

2878 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

15 ms

js

js

93 ms

init_embed.js

init_embed.js

69 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

23 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

22 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

34 ms

rpc:shindig_random.js

rpc:shindig_random.js

29 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

2 ms

jot

jot

174 ms

img_shop_kodawari01_on.jpg

img_shop_kodawari01_on.jpg

2896 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

99 ms

img_shop_kodawari02_on.jpg

img_shop_kodawari02_on.jpg

2907 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

107 ms

img_shop_kodawari03_on.jpg

img_shop_kodawari03_on.jpg

2966 ms

common.js

common.js

50 ms

map.js

map.js

80 ms

google4.png

google4.png

52 ms

overlay.js

overlay.js

51 ms

util.js

util.js

48 ms

onion.js

onion.js

97 ms

search_impl.js

search_impl.js

49 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

172 ms

img_shop_kodawari04_on.jpg

img_shop_kodawari04_on.jpg

3091 ms

bt_list_side_search_on.gif

bt_list_side_search_on.gif

2824 ms

stats.js

stats.js

36 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

31 ms

transparent.png

transparent.png

17 ms

kh

kh

69 ms

controls.js

controls.js

22 ms

vt

vt

130 ms

vt

vt

122 ms

vt

vt

131 ms

vt

vt

124 ms

vt

vt

128 ms

css

css

81 ms

loading.gif

loading.gif

2865 ms

mapcnt6.png

mapcnt6.png

29 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

26 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

29 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

36 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

39 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

20 ms

SEO Factors

nextlife-sagamiono.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-sagamiono.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-sagamiono.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-sagamiono.jp

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