Tools & Wizards About Us

Report Summary

  • 36

    Performance

    Renders faster than
    55% 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

  • 74

    SEO

    Google-friendlier than
    31% of websites

assetnavi.co.jp

東京都２３区の賃貸マンションで1人暮らしをするならアセットナビへお任せください！ - アセットナビ

Page Load Speed

1.3 sec in total

First Response

617 ms

Resources Loaded

618 ms

Page Rendered

52 ms

About Website

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

東京都の1人暮らし向け賃貸マンションを中心に物件情報を掲載。遠方の方にも便利なオンライン内見や初期費用サポート、自社ブランドマンションはセキュリティやペット可など設備に拘った「AXAS(アクサス)・ARK MARK（アークマーク）シリーズ」を掲載、サイト限定情報があり。

Visit assetnavi.co.jp

Key Findings

We analyzed Assetnavi.co.jp page load time and found that the first response time was 617 ms and then it took 670 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

assetnavi.co.jp performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

assetnavi.co.jp

617 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Assetnavi.co.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (617 ms) belongs to the original domain Assetnavi.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 275 B (45%)

Content Size

611 B

After Optimization

336 B

  • HTML

In fact, the total size of Assetnavi.co.jp main page is 611 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 611 B which makes up the majority of the site volume.

HTML Optimization

-45%

Potential reduce by 275 B

  • Original 611 B
  • After minification 557 B
  • After compression 336 B

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 275 B or 45% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Network Requests Diagram

Accessibility Review

assetnavi.co.jp accessibility score

86

Accessibility Issues

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

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

assetnavi.co.jp SEO score

74

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

Links do not have descriptive text

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Assetnavi.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 Assetnavi.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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