Tools & Wizards About Us
kagoshima-athome.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

kagoshima-athome.jp

鹿児島県の不動産・住宅情報を探す【アットホーム】｜不動産・物件・住宅情報

Page Load Speed

6.9 sec in total

First Response

802 ms

Resources Loaded

5.7 sec

Page Rendered

366 ms

kagoshima-athome.jp screenshot

About Website

Welcome to kagoshima-athome.jp homepage info - get ready to check Kagoshima Athome best content right away, or after learning these important things about kagoshima-athome.jp

鹿児島県から不動産・住宅・物件情報を探すページ。鹿児島県の不動産・住宅・物件情報を探すならアットホーム。鹿児島県の不動産物件を賃貸・購入からエリアや価格などこだわりの条件に絞り込んで検索が可能！その他、鹿児島県に関する詳細情報やおすすめの特集も盛り沢山なのであなたの希望に合った物件情報を検索・比較できます。

Visit kagoshima-athome.jp

Key Findings

We analyzed Kagoshima-athome.jp page load time and found that the first response time was 802 ms and then it took 6.1 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

kagoshima-athome.jp performance score

0

Network Requests Diagram

802 ms

master.css

178 ms

top.css

392 ms

feature.css

352 ms

jquery-1.8.3.min.js

530 ms

Our browser made a total of 131 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Kagoshima-athome.jp, 5% (7 requests) were made to Tag.ladsp.com and 3% (4 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Athome.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 546.4 kB (48%)

Content Size

1.1 MB

After Optimization

589.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kagoshima-athome.jp main page is 1.1 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. 45% of websites need less resources to load. Javascripts take 574.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 60.1 kB

  • Original 73.3 kB
  • After minification 55.5 kB
  • After compression 13.3 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 17.9 kB, which is 24% 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 60.1 kB or 82% of the original size.

Image Optimization

-12%

Potential reduce by 52.4 kB

  • Original 425.3 kB
  • After minification 372.8 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. Obviously, Kagoshima Athome needs image optimization as it can save up to 52.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 385.1 kB

  • Original 574.5 kB
  • After minification 573.2 kB
  • After compression 189.4 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 385.1 kB or 67% of the original size.

CSS Optimization

-77%

Potential reduce by 48.8 kB

  • Original 63.1 kB
  • After minification 53.0 kB
  • After compression 14.2 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. Kagoshima-athome.jp needs all CSS files to be minified and compressed as it can save up to 48.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (53%)

Requests Now

126

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

802 ms

master.css

master.css

178 ms

top.css

top.css

392 ms

feature.css

feature.css

352 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

530 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

349 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

347 ms

common_functions.js

common_functions.js

354 ms

common_functions_ext.js

common_functions_ext.js

524 ms

cookie.js

cookie.js

605 ms

personal_functions.js

personal_functions.js

549 ms

personal_cond.js

personal_cond.js

529 ms

html5shiv.min.js

html5shiv.min.js

565 ms

respond.min.js

respond.min.js

698 ms

dfcc905e69e940.js

dfcc905e69e940.js

53 ms

ojs

ojs

491 ms

base.css

base.css

531 ms

jquery.bxslider_custom.css

jquery.bxslider_custom.css

531 ms

custom.css

custom.css

565 ms

fontsize-default.css

fontsize-default.css

568 ms

parts.css

parts.css

615 ms

global.css

global.css

699 ms

analytics.js

analytics.js

102 ms

bg_fixed_bar.gif

bg_fixed_bar.gif

178 ms

logo_fixedbar.png

logo_fixedbar.png

178 ms

sprite_fixedbar.png

sprite_fixedbar.png

190 ms

logo_header.gif

logo_header.gif

190 ms

sprite_header_nav_common.png

sprite_header_nav_common.png

185 ms

sprite_header_func.png

sprite_header_func.png

186 ms

stit_link_rent.gif

stit_link_rent.gif

351 ms

stit_link_sell.gif

stit_link_sell.gif

461 ms

bt_link_estate.gif

bt_link_estate.gif

357 ms

bt_link_assess.gif

bt_link_assess.gif

357 ms

hitori_tn.gif

hitori_tn.gif

364 ms

shinkon_tn.gif

shinkon_tn.gif

367 ms

ldk15_tn.gif

ldk15_tn.gif

551 ms

chiku10nen_tn.gif

chiku10nen_tn.gif

531 ms

wooddeck_tn.gif

wooddeck_tn.gif

533 ms

kitchen_tn.gif

kitchen_tn.gif

542 ms

ritchi_tn.gif

ritchi_tn.gif

544 ms

shinchaku_tn.gif

shinchaku_tn.gif

684 ms

image_moyamoya.gif

image_moyamoya.gif

722 ms

image_tv_spot.gif

image_tv_spot.gif

743 ms

image_machicolle.gif

image_machicolle.gif

833 ms

image_uturn_iturn.gif

image_uturn_iturn.gif

833 ms

image_landmark.gif

image_landmark.gif

727 ms

img_link_souba.gif

img_link_souba.gif

917 ms

img_link_favorite.gif

img_link_favorite.gif

919 ms

220_164.jpg

220_164.jpg

1077 ms

LNEAPI_220_164.jpg

LNEAPI_220_164.jpg

952 ms

01_F5WC_220_164.jpg

01_F5WC_220_164.jpg

1118 ms

souba_220_164.gif

souba_220_164.gif

1119 ms

img_side_hikkoshi.gif

img_side_hikkoshi.gif

1033 ms

img_side_resort.gif

img_side_resort.gif

1075 ms

img_side_gakuseikaikan.gif

img_side_gakuseikaikan.gif

1145 ms

img_side_monthly.gif

img_side_monthly.gif

1229 ms

15062101_Athome_Vox_Bnr.jpg

15062101_Athome_Vox_Bnr.jpg

1344 ms

bn_tieup01.jpg

bn_tieup01.jpg

1607 ms

r-column_tieup03.jpg

r-column_tieup03.jpg

1277 ms

collect

collect

18 ms

ojs2

ojs2

336 ms

read_iframe_m.html

read_iframe_m.html

1140 ms

img_side_mobile_smp.jpg

img_side_mobile_smp.jpg

1170 ms

img_side_mobile_qr.gif

img_side_mobile_qr.gif

1310 ms

bt_to_pagetop.png

bt_to_pagetop.png

1312 ms

logo_footer.gif

logo_footer.gif

1318 ms

bg_shadow.gif

bg_shadow.gif

1315 ms

bg_yrhere.gif

bg_yrhere.gif

1305 ms

bg_gradient.jpg

bg_gradient.jpg

1316 ms

ico_link_arrow.gif

ico_link_arrow.gif

1319 ms

ico_arrow_red.gif

ico_arrow_red.gif

1338 ms

ico_opener_s.gif

ico_opener_s.gif

1316 ms

ico_blank.gif

ico_blank.gif

1332 ms

segmentation.js

segmentation.js

431 ms

82A

82A

362 ms

bg_pref_links.png

bg_pref_links.png

1312 ms

bg_globak_links.gif

bg_globak_links.gif

1311 ms

bg_global_links.png

bg_global_links.png

1311 ms

ico_blank_global.gif

ico_blank_global.gif

1317 ms

ico_arrow_red.gif

ico_arrow_red.gif

1480 ms

gtm.js

gtm.js

68 ms

tag.js

tag.js

64 ms

cnt

cnt

302 ms

tag

tag

16 ms

jquery.min.js

jquery.min.js

5 ms

logo-middle.gif

logo-middle.gif

629 ms

main-m.jpg

main-m.jpg

828 ms

main-m.jpg

main-m.jpg

685 ms

main-m.jpg

main-m.jpg

694 ms

main-m.jpg

main-m.jpg

710 ms

main-m.jpg

main-m.jpg

805 ms

main-m.jpg

main-m.jpg

864 ms

main-m.jpg

main-m.jpg

868 ms

main-m.jpg

main-m.jpg

871 ms

main-m.jpg

main-m.jpg

887 ms

main-m.jpg

main-m.jpg

983 ms

btn-up.png

btn-up.png

1002 ms

btn-down.png

btn-down.png

1054 ms

beacon.html

beacon.html

91 ms

pixel.js

pixel.js

19 ms

pixel

pixel

25 ms

cs

cs

301 ms

setuid

setuid

25 ms

Pug

Pug

27 ms

set

set

306 ms

sd

sd

5 ms

tap.php

tap.php

5 ms

sync

sync

6 ms

pixel

pixel

15 ms

sync

sync

380 ms

pixel

pixel

152 ms

mapuser

mapuser

149 ms

sync

sync

296 ms

sync

sync

260 ms

pixel

pixel

16 ms

sd

sd

10 ms

Pug

Pug

18 ms

sync.ad-stir.com

sync.ad-stir.com

302 ms

sync

sync

12 ms

sync

sync

443 ms

is

is

359 ms

mapuser

mapuser

208 ms

pixel

pixel

148 ms

google

google

295 ms

sync

sync

4 ms

pixel

pixel

158 ms

setuid

setuid

12 ms

pixel

pixel

15 ms

xrost

xrost

150 ms

google

google

150 ms

adfunnel

adfunnel

150 ms

SEO Factors

kagoshima-athome.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 Kagoshima-athome.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 Kagoshima-athome.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

kagoshima-athome.jp

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