Tools & Wizards About Us
tokai-house.co.jp screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

tokai-house.co.jp

東海ハウス｜住宅･不動産･店舗･賃貸・リフォーム・リノベーション

Page Load Speed

6.3 sec in total

First Response

519 ms

Resources Loaded

4.9 sec

Page Rendered

886 ms

tokai-house.co.jp screenshot

About Website

Click here to check amazing Tokai House content. Otherwise, check out these important facts you probably never knew about tokai-house.co.jp

愛知県安城市、豊田市、岡崎市の東海ハウスの公式サイトです。住宅、不動産、店舗、賃貸、リフォーム、リノベーションなど建物に関することをトータルにサポートします。

Visit tokai-house.co.jp

Key Findings

We analyzed Tokai-house.co.jp page load time and found that the first response time was 519 ms and then it took 5.8 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

tokai-house.co.jp performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value1.537

0/100

15%

TTI (Time to Interactive)

Value13.0 s

12/100

10%

Network Requests Diagram

tokai-house.co.jp

519 ms

www.tokai-house.co.jp

1631 ms

reset.css

322 ms

style.css

328 ms

top.css

333 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 85% of them (50 requests) were addressed to the original Tokai-house.co.jp, 5% (3 requests) were made to Tokai-house.work and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Tokai-house.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 363.0 kB (6%)

Content Size

6.4 MB

After Optimization

6.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-72%

Potential reduce by 14.9 kB

  • Original 20.6 kB
  • After minification 19.6 kB
  • After compression 5.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. 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 14.9 kB or 72% of the original size.

Image Optimization

-4%

Potential reduce by 239.7 kB

  • Original 6.2 MB
  • After minification 6.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. Tokai House images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 87.1 kB

  • Original 152.3 kB
  • After minification 152.1 kB
  • After compression 65.3 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 87.1 kB or 57% of the original size.

CSS Optimization

-81%

Potential reduce by 21.3 kB

  • Original 26.5 kB
  • After minification 20.9 kB
  • After compression 5.1 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. Tokai-house.co.jp needs all CSS files to be minified and compressed as it can save up to 21.3 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

56

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tokai-house.co.jp

tokai-house.co.jp

519 ms

www.tokai-house.co.jp

www.tokai-house.co.jp

1631 ms

reset.css

reset.css

322 ms

style.css

style.css

328 ms

top.css

top.css

333 ms

jquery.bxslider.css

jquery.bxslider.css

336 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

675 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

343 ms

instafeed.js

instafeed.js

482 ms

insta-tokaihouse.js

insta-tokaihouse.js

490 ms

4-1-e1716596862637.jpg

4-1-e1716596862637.jpg

1215 ms

embed

embed

245 ms

1.jpg

1.jpg

1228 ms

1-2.jpg

1-2.jpg

1083 ms

tel.png

tel.png

174 ms

logo.png

logo.png

169 ms

nav1.png

nav1.png

167 ms

nav2.png

nav2.png

162 ms

nav3.png

nav3.png

177 ms

nav4.png

nav4.png

173 ms

nav7.png

nav7.png

321 ms

nav6.png

nav6.png

330 ms

nav5.png

nav5.png

336 ms

facebook.svg

facebook.svg

338 ms

instagram.svg

instagram.svg

351 ms

blog.svg

blog.svg

350 ms

smLogo.png

smLogo.png

480 ms

smMenu.png

smMenu.png

495 ms

mainImg05.jpg

mainImg05.jpg

1169 ms

mainImg06.jpg

mainImg06.jpg

992 ms

mainImg02.jpg

mainImg02.jpg

1038 ms

mainImg07.jpg

mainImg07.jpg

1190 ms

mainImg08.jpg

mainImg08.jpg

1270 ms

mainImg09.jpg

mainImg09.jpg

1313 ms

mainImg04.jpg

mainImg04.jpg

1486 ms

con01.jpg

con01.jpg

1558 ms

con02.jpg

con02.jpg

1510 ms

con03.jpg

con03.jpg

1525 ms

con04.jpg

con04.jpg

1595 ms

ban01.jpg

ban01.jpg

2132 ms

ban02.jpg

ban02.jpg

1651 ms

ban03.jpg

ban03.jpg

1677 ms

works57_1_1630714606.jpg

works57_1_1630714606.jpg

1867 ms

works58_1_1685782723.jpg

works58_1_1685782723.jpg

1908 ms

works59_1_1699344845.jpg

works59_1_1699344845.jpg

1914 ms

corpImg.jpg

corpImg.jpg

1978 ms

corpImg_sp1.png

corpImg_sp1.png

1849 ms

corpImg_sp2.png

corpImg_sp2.png

2023 ms

mail.png

mail.png

2036 ms

analytics.js

analytics.js

16 ms

recent

recent

87 ms

totop.svg

totop.svg

2008 ms

collect

collect

25 ms

js

js

72 ms

footBg.png

footBg.png

1917 ms

bottomLogo.png

bottomLogo.png

1981 ms

bx_loader.gif

bx_loader.gif

2032 ms

controls.png

controls.png

2036 ms

js

js

58 ms

Accessibility Review

tokai-house.co.jp accessibility score

86

Accessibility Issues

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

tokai-house.co.jp 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

tokai-house.co.jp SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Tokai-house.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 Tokai-house.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

tokai-house.co.jp

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