Tools & Wizards About Us
smatch.jp screenshot

Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

smatch.jp

不動産会社・不動産屋検索サイト【スマッチ】

Page Load Speed

2.3 sec in total

First Response

412 ms

Resources Loaded

1.5 sec

Page Rendered

367 ms

smatch.jp screenshot

About Website

Click here to check amazing Smatch content for Japan. Otherwise, check out these important facts you probably never knew about smatch.jp

不動産会社・不動産屋、不動産物件の検索ならスマッチ。都道府県ごとの住まいに関するアンケート結果や各駅のクチコミ情報など、住まい探しに役立つ情報満載。住まい探しのことは、街の頼れるプロフェッショナルへ。

Visit smatch.jp

Key Findings

We analyzed Smatch.jp page load time and found that the first response time was 412 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

smatch.jp performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

99/100

25%

SI (Speed Index)

Value3.0 s

93/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.9 s

100/100

10%

Network Requests Diagram

smatch.jp

412 ms

ga.js

31 ms

style.css

168 ms

loader.css

313 ms

jquery-1.8.3.min.js

473 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 60% of them (12 requests) were addressed to the original Smatch.jp, 30% (6 requests) were made to Img01.s-bs.jp and 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (599 ms) relates to the external source Img01.s-bs.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 112.5 kB (33%)

Content Size

341.8 kB

After Optimization

229.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Smatch.jp main page is 341.8 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. Only 10% of websites need less resources to load. Images take 173.0 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 18.2 kB

  • Original 24.9 kB
  • After minification 22.5 kB
  • After compression 6.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 18.2 kB or 73% of the original size.

Image Optimization

-5%

Potential reduce by 7.8 kB

  • Original 173.0 kB
  • After minification 165.1 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. Smatch images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 61.8 kB

  • Original 113.1 kB
  • After minification 112.0 kB
  • After compression 51.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 61.8 kB or 55% of the original size.

CSS Optimization

-80%

Potential reduce by 24.7 kB

  • Original 30.8 kB
  • After minification 23.7 kB
  • After compression 6.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. Smatch.jp needs all CSS files to be minified and compressed as it can save up to 24.7 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

19

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Smatch. 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

smatch.jp

smatch.jp

412 ms

ga.js

ga.js

31 ms

style.css

style.css

168 ms

loader.css

loader.css

313 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

473 ms

imageLoad.js

imageLoad.js

323 ms

outboundLink.js

outboundLink.js

324 ms

__utm.gif

__utm.gif

23 ms

1912914_28548ba054_pr_gazo_m.jpg

1912914_28548ba054_pr_gazo_m.jpg

546 ms

sp_common.png

sp_common.png

314 ms

img_top_map.jpg

img_top_map.jpg

489 ms

sp_top_btn.png

sp_top_btn.png

311 ms

img_top_company.jpg

img_top_company.jpg

326 ms

img_top_chara.jpg

img_top_chara.jpg

162 ms

img_top_site.jpg

img_top_site.jpg

304 ms

1912685_6cafcc1a24_pr_gazo_m.jpg

1912685_6cafcc1a24_pr_gazo_m.jpg

541 ms

1900544_5b5052e6a4_pr_gazo_m.jpg

1900544_5b5052e6a4_pr_gazo_m.jpg

552 ms

1894365_61f662bce6_pr_gazo_m.png

1894365_61f662bce6_pr_gazo_m.png

599 ms

1877234_45c0b61adb_pr_gazo_m.jpg

1877234_45c0b61adb_pr_gazo_m.jpg

571 ms

1894221_e68e0ec0ef_pr_gazo_m.png

1894221_e68e0ec0ef_pr_gazo_m.png

562 ms

Accessibility Review

smatch.jp accessibility score

63

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

Best Practices

smatch.jp best practices score

75

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

SEO Factors

smatch.jp SEO score

54

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

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

smatch.jp

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