Tools & Wizards About Us
yumehome.co.jp screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

yumehome.co.jp

【夢ホーム】倉敷を中心とした不動産売買。住宅用地、戸建や倉庫・事務所などの建物もお任せ！　有限会社夢ホーム

Page Load Speed

5.3 sec in total

First Response

522 ms

Resources Loaded

3.7 sec

Page Rendered

998 ms

yumehome.co.jp screenshot

About Website

Welcome to yumehome.co.jp homepage info - get ready to check Yumehome best content for Japan right away, or after learning these important things about yumehome.co.jp

夢ホームは売買メインの不動産会社です。倉敷・早島を中心に土地は住宅用地、分譲地から事業用まで、中古住宅や新築戸建を販売しています。岡山県内の空家管理、建物解体や片付け、売却のご相談を承っています。不動産の困ったなを解決しましょう。

Visit yumehome.co.jp

Key Findings

We analyzed Yumehome.co.jp page load time and found that the first response time was 522 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

yumehome.co.jp performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.21

59/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

yumehome.co.jp

522 ms

yumehome.co.jp

837 ms

embed

88 ms

cl_txt.css

327 ms

rollover.js

492 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 97% of them (67 requests) were addressed to the original Yumehome.co.jp, 1% (1 request) were made to Knowledgetags.yextpages.net and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Yumehome.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.4 kB (16%)

Content Size

236.6 kB

After Optimization

199.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yumehome.co.jp main page is 236.6 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. 40% of websites need less resources to load. Images take 202.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 20.6 kB

  • Original 24.4 kB
  • After minification 15.5 kB
  • After compression 3.9 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 8.9 kB, which is 36% 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 20.6 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 9.1 kB

  • Original 202.8 kB
  • After minification 193.7 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. Yumehome images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 2.2 kB

  • Original 3.1 kB
  • After minification 2.0 kB
  • After compression 881 B

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 2.2 kB or 71% of the original size.

CSS Optimization

-88%

Potential reduce by 5.5 kB

  • Original 6.3 kB
  • After minification 2.3 kB
  • After compression 749 B

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. Yumehome.co.jp needs all CSS files to be minified and compressed as it can save up to 5.5 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (4%)

Requests Now

67

After Optimization

64

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yumehome.co.jp

yumehome.co.jp

522 ms

yumehome.co.jp

yumehome.co.jp

837 ms

embed

embed

88 ms

cl_txt.css

cl_txt.css

327 ms

rollover.js

rollover.js

492 ms

bukken_count.js

bukken_count.js

495 ms

dream_redirect.js

dream_redirect.js

517 ms

js

js

75 ms

bg.gif

bg.gif

166 ms

logo.gif

logo.gif

261 ms

company.gif

company.gif

173 ms

t_e_telephone.png

t_e_telephone.png

264 ms

t_e_company.gif

t_e_company.gif

166 ms

t_e_kanban.png

t_e_kanban.png

330 ms

t_b_toiawase.gif

t_b_toiawase.gif

331 ms

t_b_kaisya.gif

t_b_kaisya.gif

342 ms

t_e_bg.gif

t_e_bg.gif

431 ms

t_b_index_off.gif

t_b_index_off.gif

435 ms

t_b_bukken01_off.gif

t_b_bukken01_off.gif

495 ms

t_b_whatiskj_off.gif

t_b_whatiskj_off.gif

514 ms

t_b_c_kibou01_off.gif

t_b_c_kibou01_off.gif

513 ms

t_b_kaisha_off.gif

t_b_kaisha_off.gif

514 ms

t_b_map_off.gif

t_b_map_off.gif

607 ms

l_b_baibaiall01_off.gif

l_b_baibaiall01_off.gif

606 ms

l_b_baibaiall02_off.gif

l_b_baibaiall02_off.gif

658 ms

l_b_toiawase.gif

l_b_toiawase.gif

679 ms

l_b_kibou.gif

l_b_kibou.gif

684 ms

l_b_whatismb.gif

l_b_whatismb.gif

678 ms

l_e_chiiki.png

l_e_chiiki.png

775 ms

l_b_chiiki%20kurashiki.gif

l_b_chiiki%20kurashiki.gif

776 ms

l_b_chiiki%20tsukubogunn.gif

l_b_chiiki%20tsukubogunn.gif

822 ms

l_b_chiiki%20soujya.gif

l_b_chiiki%20soujya.gif

842 ms

l_b_baikyaku.gif

l_b_baikyaku.gif

1008 ms

l_b_keitai.gif

l_b_keitai.gif

853 ms

l_b_mp.gif

l_b_mp.gif

946 ms

r_e_whatsnew.png

r_e_whatsnew.png

948 ms

r_e_osusume.png

r_e_osusume.png

986 ms

r_e_tokusen.png

r_e_tokusen.png

1005 ms

tokusen1.gif

tokusen1.gif

1023 ms

tokusen2.gif

tokusen2.gif

1116 ms

tokusen%20souko.gif

tokusen%20souko.gif

1120 ms

tokusen%20eki.gif

tokusen%20eki.gif

1156 ms

tokusen%20tiku.gif

tokusen%20tiku.gif

1169 ms

tokusen6.gif

tokusen6.gif

1134 ms

rireki.htm

rireki.htm

1060 ms

picturetable.htm

picturetable.htm

1130 ms

tokusen7.gif

tokusen7.gif

1126 ms

tokusen8.gif

tokusen8.gif

1067 ms

tokusen%20bun.gif

tokusen%20bun.gif

1076 ms

r_e_map.png

r_e_map.png

1013 ms

map_top.gif

map_top.gif

1210 ms

r_b_returntop_off.png

r_b_returntop_off.png

1121 ms

up-down.gif

up-down.gif

181 ms

pic_syodan.gif

pic_syodan.gif

203 ms

k5582p4.jpg

k5582p4.jpg

216 ms

k5702p4.jpg

k5702p4.jpg

218 ms

k5720p4.jpg

k5720p4.jpg

341 ms

k5733p4.jpg

k5733p4.jpg

352 ms

t5729p4.jpg

t5729p4.jpg

367 ms

i5723p4.jpg

i5723p4.jpg

380 ms

t_b_index_on.gif

t_b_index_on.gif

167 ms

t_b_bukken01_on.gif

t_b_bukken01_on.gif

172 ms

t_b_whatiskj_on.gif

t_b_whatiskj_on.gif

172 ms

t_b_c_kibou01_on.gif

t_b_c_kibou01_on.gif

172 ms

t_b_kaisha_on.gif

t_b_kaisha_on.gif

165 ms

t_b_map_on.gif

t_b_map_on.gif

166 ms

l_b_baibaiall01_on.gif

l_b_baibaiall01_on.gif

330 ms

l_b_baibaiall02_on.gif

l_b_baibaiall02_on.gif

330 ms

r_b_returntop_on.png

r_b_returntop_on.png

331 ms

Accessibility Review

yumehome.co.jp accessibility score

75

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

yumehome.co.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

yumehome.co.jp SEO score

100

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

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 Yumehome.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 Yumehome.co.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

yumehome.co.jp

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