Tools & Wizards About Us
asset-estate.jp screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

asset-estate.jp

不動産売買 賃貸は[不動産アセット]へどうぞ

Page Load Speed

7.3 sec in total

First Response

2.7 sec

Resources Loaded

4.4 sec

Page Rendered

225 ms

asset-estate.jp screenshot

About Website

Click here to check amazing Asset Estate content for Japan. Otherwise, check out these important facts you probably never knew about asset-estate.jp

山形市周辺の不動産売買･賃貸仲介を致します。宅地建物取引士　不動産コンサルティング　ＡＦＰ　証券二種外務員有資格者による相続対策等提案.その他、相談アドバイス経験豊富です。

Visit asset-estate.jp

Key Findings

We analyzed Asset-estate.jp page load time and found that the first response time was 2.7 sec and then it took 4.6 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

asset-estate.jp performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.05

99/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

Network Requests Diagram

asset-estate.jp

2721 ms

style.css

829 ms

jquery.fancybox.css

547 ms

styles.css

368 ms

slider.css

369 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 93% of them (42 requests) were addressed to the original Asset-estate.jp, 7% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Asset-estate.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 180.0 kB (41%)

Content Size

438.0 kB

After Optimization

258.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 23.7 kB

  • Original 29.8 kB
  • After minification 28.1 kB
  • After compression 6.2 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 23.7 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 3.5 kB

  • Original 186.8 kB
  • After minification 183.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. Asset Estate images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 107.6 kB

  • Original 167.3 kB
  • After minification 141.3 kB
  • After compression 59.7 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 107.6 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 45.2 kB

  • Original 54.1 kB
  • After minification 41.7 kB
  • After compression 8.8 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. Asset-estate.jp needs all CSS files to be minified and compressed as it can save up to 45.2 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

44

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

asset-estate.jp

asset-estate.jp

2721 ms

style.css

style.css

829 ms

jquery.fancybox.css

jquery.fancybox.css

547 ms

styles.css

styles.css

368 ms

slider.css

slider.css

369 ms

l10n.js

l10n.js

378 ms

jquery.js

jquery.js

877 ms

jquery.fancybox.js

jquery.fancybox.js

731 ms

jquery.easing.js

jquery.easing.js

731 ms

jquery.easing.js

jquery.easing.js

752 ms

script.js

script.js

909 ms

rov.js

rov.js

744 ms

to_top.js

to_top.js

745 ms

jquery.form.js

jquery.form.js

783 ms

scripts.js

scripts.js

656 ms

ga.js

ga.js

5 ms

__utm.gif

__utm.gif

12 ms

__utm.gif

__utm.gif

59 ms

bg.jpg

bg.jpg

179 ms

base.jpg

base.jpg

185 ms

head.gif

head.gif

185 ms

logo.gif

logo.gif

184 ms

li.gif

li.gif

231 ms

navi.gif

navi.gif

355 ms

navi_li.gif

navi_li.gif

365 ms

indicator.gif

indicator.gif

366 ms

top1.jpg

top1.jpg

728 ms

s2.jpg

s2.jpg

576 ms

top3.jpg

top3.jpg

724 ms

h3.gif

h3.gif

530 ms

014-150x150.jpg

014-150x150.jpg

545 ms

btn.gif

btn.gif

549 ms

CIMG0510-150x150.jpg

CIMG0510-150x150.jpg

706 ms

CIMG0501-150x150.jpg

CIMG0501-150x150.jpg

726 ms

%E5%8C%97%E4%B9%85%E9%87%8E%E6%9C%AC%EF%BC%A2-150x150.jpg

%E5%8C%97%E4%B9%85%E9%87%8E%E6%9C%AC%EF%BC%A2-150x150.jpg

730 ms

c-0002-022-150x150.jpg

c-0002-022-150x150.jpg

763 ms

CIMG03661-150x150.jpg

CIMG03661-150x150.jpg

881 ms

%E3%83%99%E3%83%AB%E3%83%8F%E3%82%A6%E3%82%B9A.%E5%A4%96%E8%A6%B3-150x150.jpg

%E3%83%99%E3%83%AB%E3%83%8F%E3%82%A6%E3%82%B9A.%E5%A4%96%E8%A6%B3-150x150.jpg

885 ms

%E5%9F%8E%E8%A5%BF%E8%B2%B8%E5%AE%B6.%E5%A4%96%E8%A6%B3.1-150x150.jpg

%E5%9F%8E%E8%A5%BF%E8%B2%B8%E5%AE%B6.%E5%A4%96%E8%A6%B3.1-150x150.jpg

905 ms

top-sub_01.jpg

top-sub_01.jpg

906 ms

sample_s.jpg

sample_s.jpg

907 ms

banner-baikyaku.gif

banner-baikyaku.gif

948 ms

side_btn_df.jpg

side_btn_df.jpg

1056 ms

side_box.gif

side_box.gif

1000 ms

foot.gif

foot.gif

1037 ms

Accessibility Review

asset-estate.jp accessibility score

77

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-*] attributes do not match their roles

High

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

asset-estate.jp best practices score

83

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

SEO Factors

asset-estate.jp SEO score

90

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

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 Asset-estate.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 Asset-estate.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

asset-estate.jp

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