13.4 sec in total
478 ms
12.3 sec
631 ms
Click here to check amazing Yume J content. Otherwise, check out these important facts you probably never knew about yume-j.co.jp
富士見市・ふじみ野市の一戸建てや土地、マンションなど不動産情報をお探しなら夢住宅にお任せください。夢住宅では富士見市・ふじみ野市・新座市・三芳町・志木市の不動産情報を網羅し、お客様のご希望に合った住まい選びをサポートいたします!
Visit yume-j.co.jpWe analyzed Yume-j.co.jp page load time and found that the first response time was 478 ms and then it took 12.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
yume-j.co.jp performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value12.1 s
0/100
25%
Value12.1 s
3/100
10%
Value1,820 ms
9/100
30%
Value0.364
30/100
15%
Value10.7 s
22/100
10%
478 ms
1172 ms
502 ms
1111 ms
593 ms
Our browser made a total of 173 requests to load all elements on the main page. We found that 71% of them (122 requests) were addressed to the original Yume-j.co.jp, 9% (15 requests) were made to Img-asp.jp and 5% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Yume-j.co.jp.
Page size can be reduced by 206.9 kB (8%)
2.7 MB
2.5 MB
In fact, the total size of Yume-j.co.jp main page is 2.7 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 2.5 MB which makes up the majority of the site volume.
Potential reduce by 43.7 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 7.7 kB, which is 14% 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 43.7 kB or 79% of the original size.
Potential reduce by 77.9 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. Yume J images are well optimized though.
Potential reduce by 58.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 58.6 kB or 55% of the original size.
Potential reduce by 26.7 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. Yume-j.co.jp needs all CSS files to be minified and compressed as it can save up to 26.7 kB or 85% of the original size.
Number of requests can be reduced by 35 (21%)
166
131
The browser has sent 166 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yume J. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
yume-j.co.jp
478 ms
www.yume-j.co.jp
1172 ms
index.css
502 ms
jquery-1.4.2.min.js
1111 ms
index.js
593 ms
yugaAutoLine.js
989 ms
widgets.js
83 ms
plusone.js
57 ms
flash.js
667 ms
402 ms
common.css
583 ms
345 ms
3064 ms
ga.js
60 ms
141_58448_1_1000_1000.jpg
438 ms
27268547_1_150_150_3.jpg
965 ms
18660002_1_280_210_2.jpg
400 ms
141_58955_1_1000_1000.jpg
463 ms
141_67799_1_1000_1000.jpg
1658 ms
141_67100_1_1000_1000.jpg
2231 ms
23840602_1_280_210_2.jpg
405 ms
22152446_1_280_210_2.jpg
406 ms
26316392_1_280_210_2.jpg
431 ms
25923976_1_280_210_2.jpg
453 ms
27056302_1_280_210_2.jpg
453 ms
16208_1_80_80_3.jpg
453 ms
27062986_1_150_150_3.jpg
1431 ms
4859_1_80_80_3.jpg
520 ms
27123138_1_150_150_3.jpg
759 ms
25802744_1_150_150_3.jpg
747 ms
26321933_1_150_150_3.jpg
757 ms
26327513_1_150_150_3.jpg
805 ms
1835_1_200_200_2.jpg
1261 ms
bg_body.jpg
339 ms
bg_header.jpg
406 ms
clearfix.gif
413 ms
logo.jpg
805 ms
tel.jpg
596 ms
bt_favorite.jpg
396 ms
bt_2_company.jpg
856 ms
bt_2_accessmap.jpg
908 ms
bt_2_sitemap.jpg
904 ms
bt_2_bknRequest.jpg
915 ms
bt_2_contact.jpg
1089 ms
ttl_house.jpg
1260 ms
bt_house_area.jpg
1181 ms
bt_house_line.jpg
1250 ms
ttl_land.jpg
1262 ms
bt_land_area.jpg
1255 ms
bt_land_line.jpg
1450 ms
ttl_mansion.jpg
1749 ms
bt_mansion_area.jpg
1569 ms
bt_mansion_line.jpg
1591 ms
bt_map_search.jpg
2278 ms
original_member.jpg
2281 ms
ttl_kodawari_buy.jpg
1777 ms
img_kodawari_buy01.jpg
2250 ms
img_kodawari_buy02.jpg
2235 ms
img_kodawari_buy03.jpg
2237 ms
img_kodawari_buy04.jpg
2287 ms
img_kodawari_buy05.jpg
2955 ms
ttl_topic.jpg
2598 ms
ttl_new.jpg
2586 ms
img_bkn_top03.jpg
2621 ms
icon_new.gif
2639 ms
icon_comment.gif
2666 ms
bt_detail03.jpg
2912 ms
ttl_osusume.jpg
2916 ms
__utm.gif
20 ms
cb=gapi.loaded_0
12 ms
cb=gapi.loaded_1
11 ms
fastbutton
127 ms
like.php
155 ms
postmessageRelay
145 ms
cb=gapi.loaded_0
66 ms
cb=gapi.loaded_1
68 ms
grlryt2bdKIyfMSOhzd1eA.woff
78 ms
qeKvIRsJabD.js
571 ms
LVx-xkvaJ0b.png
563 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
136 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
162 ms
3193398744-postmessagerelay.js
45 ms
rpc:shindig_random.js
43 ms
cb=gapi.loaded_0
4 ms
2725 ms
img_bkn_top02.jpg
2639 ms
icon_osusume.gif
2900 ms
bt_station_search.jpg
2879 ms
141_58448_1_1000_1000.jpg
1594 ms
syndication
90 ms
387131488895901697
201 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
43 ms
141_58955_1_1000_1000.jpg
1955 ms
ttl_side_contents.jpg
2721 ms
proxy.jpg
73 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
37 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
67 ms
baa8eb518e53e3ade58c1b536b0941dd_normal.jpeg
206 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
47 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
53 ms
bnr_member.jpg
3007 ms
proxy.jpg
31 ms
bt_member.jpg
2535 ms
bt_side_original1.jpg
3007 ms
bt_side_staff.jpg
3103 ms
bt_side_voice.jpg
3100 ms
jot.html
30 ms
bt_side_original2.jpg
3159 ms
bt_side_original3.jpg
2827 ms
bt_side_spot.jpg
3241 ms
bt_side_satei.jpg
3276 ms
bt_side_original4.jpg
3396 ms
bt_side_original5.jpg
3429 ms
bt_side_original6.jpg
3105 ms
bt_side_original7.jpg
3303 ms
ttl_side_company.jpg
3224 ms
icn_company.jpg
3167 ms
icn_contact.jpg
3132 ms
icn_map.jpg
2728 ms
bnr_ielove.jpg
3106 ms
txt_buy.jpg
3465 ms
eliminator.jpg
2930 ms
bt_follow.jpg
3133 ms
bt_follow_login.jpg
2992 ms
contact_blue_remove.gif
2717 ms
new_3.gif
2947 ms
marker_rounded_blue.gif
2995 ms
comment_question.gif
3024 ms
icon_new_update.gif
2987 ms
icn_koshin.jpg
2965 ms
bg_osusume.jpg
3004 ms
bg_station_search.jpg
3156 ms
bt_favorite_on.jpg
2984 ms
bt_2_company_on.jpg
3228 ms
bt_2_accessmap_on.jpg
2977 ms
bt_2_sitemap_on.jpg
3134 ms
bt_2_bknRequest_on.jpg
3188 ms
bt_2_contact_on.jpg
3136 ms
bt_house_area_on.jpg
2705 ms
bt_house_line_on.jpg
2680 ms
bt_land_area_on.jpg
2659 ms
bt_land_line_on.jpg
2808 ms
bt_mansion_area_on.jpg
2822 ms
bt_mansion_line_on.jpg
2577 ms
bt_map_search_on.jpg
3172 ms
original_member_on.jpg
3138 ms
img_kodawari_buy01_on.jpg
2731 ms
img_kodawari_buy02_on.jpg
2799 ms
img_kodawari_buy03_on.jpg
2846 ms
img_kodawari_buy04_on.jpg
2549 ms
img_kodawari_buy05_on.jpg
3059 ms
bt_detail03_on.jpg
2793 ms
bnr_member_on.jpg
3357 ms
bt_member_on.jpg
2914 ms
bt_side_original1_on.jpg
3311 ms
bt_side_staff_on.jpg
3136 ms
bt_side_voice_on.jpg
3078 ms
bt_side_original2_on.jpg
3460 ms
bt_side_original3_on.jpg
3229 ms
bt_side_spot_on.jpg
3407 ms
bt_side_satei_on.jpg
3485 ms
bt_side_original4_on.jpg
3407 ms
bt_side_original5_on.jpg
3501 ms
bt_side_original6_on.jpg
3438 ms
3582 ms
bt_side_original7_on.jpg
3603 ms
icn_company_on.jpg
3484 ms
icn_contact_on.jpg
3455 ms
icn_map_on.jpg
3318 ms
bnr_ielove_on.jpg
3612 ms
eliminator_on.jpg
3357 ms
bt_follow_on.jpg
3523 ms
bt_follow_login_on.jpg
3328 ms
yume-j.co.jp accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
yume-j.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
yume-j.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yume-j.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 Yume-j.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.
yume-j.co.jp
Open Graph description is not detected on the main page of Yume J. 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: