Tools & Wizards About Us
j-bld.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

j-bld.com

東京・渋谷区代々木のリノベーション（リフォーム）専門モデルルーム『ＲＥ創の家』運営、店舗公開物件が豊富！

Page Load Speed

5.4 sec in total

First Response

600 ms

Resources Loaded

4.4 sec

Page Rendered

401 ms

j-bld.com screenshot

About Website

Visit j-bld.com now to see the best up-to-date J Bld content for Japan and also check out these interesting facts you probably never knew about j-bld.com

中古マンション・賃貸マンションにリフォームをセットするなら、まずはジャパン・ビルドへ相談。中古マンションリフォーム・リフォーム付賃貸管理ならジャパン・ビルド株式会社が運営するRE創の家リノベーションギャラリーで実際リフォームしたお部屋を見学できます。

Visit j-bld.com

Key Findings

We analyzed J-bld.com page load time and found that the first response time was 600 ms and then it took 4.8 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

j-bld.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value550 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.354

31/100

15%

TTI (Time to Interactive)

Value7.5 s

48/100

10%

Network Requests Diagram

j-bld.com

600 ms

www.j-bld.com

1319 ms

reset.css

327 ms

main.css

819 ms

slick.css

494 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 82% of them (49 requests) were addressed to the original J-bld.com, 3% (2 requests) were made to Connect.facebook.net and 3% (2 requests) were made to Munchkin.marketo.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain J-bld.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 164.3 kB (13%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of J-bld.com main page is 1.2 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. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 32.9 kB

  • Original 41.8 kB
  • After minification 40.8 kB
  • After compression 8.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 32.9 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 31.3 kB

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

JavaScript Optimization

-41%

Potential reduce by 47.8 kB

  • Original 115.7 kB
  • After minification 111.1 kB
  • After compression 67.9 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 47.8 kB or 41% of the original size.

CSS Optimization

-85%

Potential reduce by 52.3 kB

  • Original 61.5 kB
  • After minification 44.1 kB
  • After compression 9.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. J-bld.com needs all CSS files to be minified and compressed as it can save up to 52.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (27%)

Requests Now

56

After Optimization

41

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

j-bld.com

j-bld.com

600 ms

www.j-bld.com

www.j-bld.com

1319 ms

reset.css

reset.css

327 ms

main.css

main.css

819 ms

slick.css

slick.css

494 ms

slick-theme.css

slick-theme.css

523 ms

common.css

common.css

526 ms

jquery.min.js

jquery.min.js

22 ms

slick.min.js

slick.min.js

876 ms

common.js

common.js

526 ms

scrollsmoothly.js

scrollsmoothly.js

656 ms

script.js

script.js

696 ms

sdk.js

sdk.js

17 ms

js

js

39 ms

munchkin.js

munchkin.js

80 ms

logo.png

logo.png

169 ms

Instagram_icon.svg

Instagram_icon.svg

176 ms

facebook_icon.svg

facebook_icon.svg

181 ms

slick01_slide1_pc.jpg

slick01_slide1_pc.jpg

526 ms

slick01_slide2_pc.jpg

slick01_slide2_pc.jpg

696 ms

slick01_slide3_pc.jpg

slick01_slide3_pc.jpg

489 ms

slick01_slide4_pc.jpg

slick01_slide4_pc.jpg

657 ms

slick01_slide5_pc.jpg

slick01_slide5_pc.jpg

700 ms

concept_title_01.png

concept_title_01.png

352 ms

concept_title_02.png

concept_title_02.png

527 ms

bannar_w50_spacer.png

bannar_w50_spacer.png

652 ms

bannar_w20_reform.jpg

bannar_w20_reform.jpg

701 ms

bannar_w20_study.png

bannar_w20_study.png

877 ms

bannar_w20_realinfo.png

bannar_w20_realinfo.png

816 ms

bannar_w20_yoyogi_benriya.jpg

bannar_w20_yoyogi_benriya.jpg

822 ms

banner_w20_actimethod.jpg

banner_w20_actimethod.jpg

870 ms

bannar_w20_posting.png

bannar_w20_posting.png

1050 ms

bannar_w20_ssm.png

bannar_w20_ssm.png

876 ms

pagetop_arrow.png

pagetop_arrow.png

978 ms

freedial.svg

freedial.svg

970 ms

top_box01_bkg.png

top_box01_bkg.png

1376 ms

top_unit_top.png

top_unit_top.png

1036 ms

top_unit_right.png

top_unit_right.png

1037 ms

top_unit_bottom.png

top_unit_bottom.png

1126 ms

top_unit_left.png

top_unit_left.png

1135 ms

new.png

new.png

1210 ms

bannar_w50_shibuya_txt.png

bannar_w50_shibuya_txt.png

1562 ms

bannar_w50_shibuya_img.jpg

bannar_w50_shibuya_img.jpg

1388 ms

bannar_w50_seikatsu_sien.jpg

bannar_w50_seikatsu_sien.jpg

1451 ms

bannar_w50_seikatsu_sien_bkg.jpg

bannar_w50_seikatsu_sien_bkg.jpg

1299 ms

logo.svg

logo.svg

1386 ms

bannar_w25_company.jpg

bannar_w25_company.jpg

1464 ms

bannar_w25_recruit.jpg

bannar_w25_recruit.jpg

1551 ms

bannar_w25_contact.jpg

bannar_w25_contact.jpg

1562 ms

sdk.js

sdk.js

60 ms

ga.js

ga.js

23 ms

70 ms

munchkin.js

munchkin.js

70 ms

t.js

t.js

633 ms

ajax-loader.gif

ajax-loader.gif

1414 ms

prev.svg

prev.svg

1465 ms

slick.woff

slick.woff

1475 ms

visitWebPage

visitWebPage

42 ms

next.svg

next.svg

1562 ms

t.gif

t.gif

162 ms

Accessibility Review

j-bld.com accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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.

Best Practices

j-bld.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

j-bld.com SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 J-bld.com 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 J-bld.com 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

j-bld.com

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