Tools & Wizards About Us
hoyotokyo.jp screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

hoyotokyo.jp

ホーヨー東京 ｜ 不動産のことならお任せください

Page Load Speed

8.5 sec in total

First Response

1 sec

Resources Loaded

7.1 sec

Page Rendered

288 ms

hoyotokyo.jp screenshot

About Website

Visit hoyotokyo.jp now to see the best up-to-date Hoyotokyo content and also check out these interesting facts you probably never knew about hoyotokyo.jp

困ったときのホーヨー東京。不動産のことなら当社にお任せください。賃貸、売買、管理、リフォーム、任意売却、投資、法律・税務相談等々。お気軽にご連絡ください。

Visit hoyotokyo.jp

Key Findings

We analyzed Hoyotokyo.jp page load time and found that the first response time was 1 sec and then it took 7.4 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

hoyotokyo.jp performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value15.6 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

www.hoyotokyo.jp

1044 ms

styles.css

1172 ms

styles.css

314 ms

css

23 ms

style.css

316 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 92% of them (48 requests) were addressed to the original Hoyotokyo.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Hoyotokyo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 379.2 kB (18%)

Content Size

2.1 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 10.7 kB

  • Original 14.7 kB
  • After minification 13.1 kB
  • After compression 4.0 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 1.6 kB, which is 11% 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 10.7 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 18.4 kB

  • Original 1.6 MB
  • After minification 1.6 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. Hoyotokyo images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 315.1 kB

  • Original 427.4 kB
  • After minification 357.6 kB
  • After compression 112.2 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 315.1 kB or 74% of the original size.

CSS Optimization

-85%

Potential reduce by 35.0 kB

  • Original 41.2 kB
  • After minification 31.5 kB
  • After compression 6.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. Hoyotokyo.jp needs all CSS files to be minified and compressed as it can save up to 35.0 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

51

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.hoyotokyo.jp

www.hoyotokyo.jp

1044 ms

styles.css

styles.css

1172 ms

styles.css

styles.css

314 ms

css

css

23 ms

style.css

style.css

316 ms

jquery.js

jquery.js

837 ms

jquery-migrate.min.js

jquery-migrate.min.js

499 ms

reset.css

reset.css

341 ms

base.css

base.css

623 ms

lightbox.css

lightbox.css

473 ms

jquery.min.js

jquery.min.js

7 ms

smoothRollOver.js

smoothRollOver.js

507 ms

rollover.js

rollover.js

632 ms

scrollsmoothly.js

scrollsmoothly.js

666 ms

prototype.js

prototype.js

1336 ms

scriptaculous.js

scriptaculous.js

779 ms

lightbox.js

lightbox.js

942 ms

jquery.form.min.js

jquery.form.min.js

999 ms

scripts.js

scripts.js

939 ms

scripts.js

scripts.js

1003 ms

navigation.js

navigation.js

1098 ms

effects.js

effects.js

174 ms

builder.js

builder.js

162 ms

analytics.js

analytics.js

39 ms

bg_containerIndex.jpg

bg_containerIndex.jpg

340 ms

blank.gif

blank.gif

161 ms

logo_headerLogo.jpg

logo_headerLogo.jpg

334 ms

icon_listIcon01.jpg

icon_listIcon01.jpg

162 ms

btn_headerContact.jpg

btn_headerContact.jpg

497 ms

bg_topImageIndex.jpg

bg_topImageIndex.jpg

1656 ms

blank.gif

blank.gif

320 ms

boxBtn01.jpg

boxBtn01.jpg

1238 ms

boxBtn02.jpg

boxBtn02.jpg

1396 ms

boxBtn03.jpg

boxBtn03.jpg

1160 ms

boxBtn04.jpg

boxBtn04.jpg

1329 ms

boxCenter.jpg

boxCenter.jpg

1326 ms

boxBtn05.jpg

boxBtn05.jpg

1661 ms

boxBtn06.jpg

boxBtn06.jpg

1701 ms

boxBtn07.jpg

boxBtn07.jpg

1993 ms

boxBtn08.jpg

boxBtn08.jpg

2178 ms

h2_indexInfo.jpg

h2_indexInfo.jpg

1555 ms

bnr_simulation.jpg

bnr_simulation.jpg

1716 ms

bnr_howTo.jpg

bnr_howTo.jpg

1825 ms

bnr_re-words.jpg

bnr_re-words.jpg

1834 ms

bg_footerWrapper.jpg

bg_footerWrapper.jpg

1860 ms

btn_pageTopLink.jpg

btn_pageTopLink.jpg

1876 ms

logo_footerLogo.png

logo_footerLogo.png

1993 ms

bg_footerInfo.jpg

bg_footerInfo.jpg

2004 ms

btn_footerContact.jpg

btn_footerContact.jpg

2018 ms

loading.gif

loading.gif

2011 ms

closelabel.gif

closelabel.gif

2132 ms

collect

collect

13 ms

Accessibility Review

hoyotokyo.jp accessibility score

100

Accessibility Issues

Best Practices

hoyotokyo.jp best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

hoyotokyo.jp SEO score

71

Search Engine Optimization Advices

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 Hoyotokyo.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 Hoyotokyo.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

hoyotokyo.jp

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