Tools & Wizards About Us
goodcomasset.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

goodcomasset.co.jp

ホーム - 株式会社グッドコムアセット

Page Load Speed

6.5 sec in total

First Response

1.2 sec

Resources Loaded

5.1 sec

Page Rendered

165 ms

goodcomasset.co.jp screenshot

About Website

Click here to check amazing Goodcomasset content for Japan. Otherwise, check out these important facts you probably never knew about goodcomasset.co.jp

株式会社グッドコムアセットは、分譲マンションの販売を通じて、お客様と一生涯のお付き合いを築きます。不動産の企画、開発、分譲、並びに建物管理に関するお問い合せは、弊社までお気軽にご相談ください。

Visit goodcomasset.co.jp

Key Findings

We analyzed Goodcomasset.co.jp page load time and found that the first response time was 1.2 sec and then it took 5.2 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

goodcomasset.co.jp performance score

0

Network Requests Diagram

goodcomasset.co.jp

1235 ms

import.css

358 ms

dw_common.js

369 ms

judge.js

370 ms

ie7_flash.js

390 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 97% of them (70 requests) were addressed to the original Goodcomasset.co.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Goodcomasset.co.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 53.5 kB

  • Original 61.8 kB
  • After minification 47.2 kB
  • After compression 8.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 14.6 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 53.5 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 9.7 kB

  • Original 1.0 MB
  • After minification 1.0 MB

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. Goodcomasset images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 104.3 kB

  • Original 159.8 kB
  • After minification 136.0 kB
  • After compression 55.6 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 104.3 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 30.0 kB

  • Original 35.9 kB
  • After minification 25.8 kB
  • After compression 5.9 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. Goodcomasset.co.jp needs all CSS files to be minified and compressed as it can save up to 30.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (30%)

Requests Now

71

After Optimization

50

  • Images
  • JavaScript
  • CSS

The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Goodcomasset. 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 from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

goodcomasset.co.jp

goodcomasset.co.jp

1235 ms

import.css

import.css

358 ms

dw_common.js

dw_common.js

369 ms

judge.js

judge.js

370 ms

ie7_flash.js

ie7_flash.js

390 ms

flexslider.css

flexslider.css

407 ms

jquery-2.1.1.js

jquery-2.1.1.js

1143 ms

jquery.flexslider.js

jquery.flexslider.js

940 ms

base.css

base.css

206 ms

top.css

top.css

208 ms

content.css

content.css

414 ms

form.css

form.css

252 ms

ga.js

ga.js

44 ms

bg_main.gif

bg_main.gif

193 ms

new_logo.jpg

new_logo.jpg

187 ms

new_contact.jpg

new_contact.jpg

384 ms

new_headnavi_01.jpg

new_headnavi_01.jpg

188 ms

new_headnavi_02.jpg

new_headnavi_02.jpg

183 ms

new_headnavi_03.jpg

new_headnavi_03.jpg

206 ms

new_headnavi_04.jpg

new_headnavi_04.jpg

368 ms

space.jpg

space.jpg

376 ms

new_gnavi_01.jpg

new_gnavi_01.jpg

378 ms

new_gnavi_02.jpg

new_gnavi_02.jpg

388 ms

new_gnavi_03.jpg

new_gnavi_03.jpg

407 ms

new_gnavi_04.jpg

new_gnavi_04.jpg

548 ms

new_gnavi_05.jpg

new_gnavi_05.jpg

562 ms

new_gnavi_06.jpg

new_gnavi_06.jpg

564 ms

top_1.jpg

top_1.jpg

1145 ms

top_2.jpg

top_2.jpg

947 ms

top_3.jpg

top_3.jpg

1034 ms

top_4.jpg

top_4.jpg

1984 ms

top_5.jpg

top_5.jpg

1745 ms

top_pict2.jpg

top_pict2.jpg

2416 ms

left_bg01.jpg

left_bg01.jpg

1137 ms

left_waku01.jpg

left_waku01.jpg

1236 ms

menu2.gif

menu2.gif

1326 ms

11th.png

11th.png

1338 ms

menu6.gif

menu6.gif

1436 ms

okyakusama2.png

okyakusama2.png

1516 ms

left_waku02.jpg

left_waku02.jpg

1532 ms

index_title01.jpg

index_title01.jpg

1640 ms

index_btn02.jpg

index_btn02.jpg

1707 ms

rss.jpg

rss.jpg

1726 ms

index_line01.jpg

index_line01.jpg

1841 ms

arrows.jpg

arrows.jpg

1898 ms

index_ico02.jpg

index_ico02.jpg

1923 ms

index_ico03.jpg

index_ico03.jpg

1930 ms

lifeplan.png

lifeplan.png

2042 ms

index_btn01.jpg

index_btn01.jpg

2064 ms

__utm.gif

__utm.gif

12 ms

index_title02.jpg

index_title02.jpg

1971 ms

index_ill02.jpg

index_ill02.jpg

1934 ms

index_ill03.jpg

index_ill03.jpg

1977 ms

index_btn03.jpg

index_btn03.jpg

2062 ms

index_ill04.jpg

index_ill04.jpg

2077 ms

index_ill05.jpg

index_ill05.jpg

1938 ms

footer_parts01.jpg

footer_parts01.jpg

1973 ms

footer_btn01.jpg

footer_btn01.jpg

1969 ms

footer_btn02.jpg

footer_btn02.jpg

2075 ms

footer_parts02.jpg

footer_parts02.jpg

2086 ms

17002245_01_75_JP.gif

17002245_01_75_JP.gif

2085 ms

get_flash_player.gif

get_flash_player.gif

1978 ms

navi1_on.gif

navi1_on.gif

191 ms

navi2_on.gif

navi2_on.gif

186 ms

navi3_on.gif

navi3_on.gif

197 ms

navi4_on.gif

navi4_on.gif

187 ms

navi5_on.gif

navi5_on.gif

182 ms

navi6_on.gif

navi6_on.gif

203 ms

menu1_on.gif

menu1_on.gif

359 ms

menu2_on.gif

menu2_on.gif

369 ms

menu3_on.gif

menu3_on.gif

370 ms

menu4_on.gif

menu4_on.gif

385 ms

SEO Factors

goodcomasset.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Goodcomasset.co.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 Goodcomasset.co.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

goodcomasset.co.jp

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