Tools & Wizards About Us
api.tokyo screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

api.tokyo

Luxury Real Estate for Rent & Sale in Tokyo | Asian Property Inc.

Page Load Speed

5.3 sec in total

First Response

524 ms

Resources Loaded

4.6 sec

Page Rendered

120 ms

api.tokyo screenshot

About Website

Click here to check amazing Api content. Otherwise, check out these important facts you probably never knew about api.tokyo

Asian Property Inc. is in the business of assisting well-to-do Japanese, international business people and corporation searching for a lease property and luxurious real estate in the area of Minato, S...

Visit api.tokyo

Key Findings

We analyzed Api.tokyo page load time and found that the first response time was 524 ms and then it took 4.8 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

api.tokyo performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

api.tokyo

524 ms

api.tokyo

939 ms

style.css

185 ms

jquery-1.7.1.min.js

870 ms

scroll.js

500 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 89% of them (24 requests) were addressed to the original Api.tokyo, 7% (2 requests) were made to Google-analytics.com and 4% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Api.tokyo.

Page Optimization Overview & Recommendations

Page size can be reduced by 180.3 kB (17%)

Content Size

1.0 MB

After Optimization

850.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Api.tokyo main page is 1.0 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. 20% of websites need less resources to load. Images take 884.5 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 5.8 kB

  • Original 7.8 kB
  • After minification 5.8 kB
  • After compression 2.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.9 kB, which is 25% 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 5.8 kB or 74% of the original size.

Image Optimization

-11%

Potential reduce by 93.8 kB

  • Original 884.5 kB
  • After minification 790.7 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. Obviously, Api needs image optimization as it can save up to 93.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-55%

Potential reduce by 68.7 kB

  • Original 124.2 kB
  • After minification 121.5 kB
  • After compression 55.5 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 68.7 kB or 55% of the original size.

CSS Optimization

-84%

Potential reduce by 12.1 kB

  • Original 14.4 kB
  • After minification 11.5 kB
  • After compression 2.3 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. Api.tokyo needs all CSS files to be minified and compressed as it can save up to 12.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (25%)

Requests Now

24

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Api. 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 as a result speed up the page load time.

Network Requests Diagram

api.tokyo

api.tokyo

524 ms

api.tokyo

api.tokyo

939 ms

style.css

style.css

185 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

870 ms

scroll.js

scroll.js

500 ms

gmenu.js

gmenu.js

514 ms

cont.js

cont.js

515 ms

photo_gallery.js

photo_gallery.js

533 ms

head_logo.png

head_logo.png

175 ms

btn_linkedin.png

btn_linkedin.png

181 ms

btn_twitter.png

btn_twitter.png

174 ms

btn_facebook.png

btn_facebook.png

176 ms

head_tel_ja.png

head_tel_ja.png

170 ms

head_contact.png

head_contact.png

179 ms

bg_main_image.jpg

bg_main_image.jpg

2299 ms

main_catch.png

main_catch.png

851 ms

gmenu_01.jpg

gmenu_01.jpg

350 ms

gmenu_02.jpg

gmenu_02.jpg

519 ms

gmenu_03.jpg

gmenu_03.jpg

535 ms

gmenu_04.jpg

gmenu_04.jpg

532 ms

top_areamap.png

top_areamap.png

526 ms

bnr_apartment_tokyo.jpg

bnr_apartment_tokyo.jpg

1199 ms

btn_totop.png

btn_totop.png

700 ms

foot_logo.png

foot_logo.png

709 ms

analytics.js

analytics.js

17 ms

collect

collect

13 ms

js

js

61 ms

Accessibility Review

api.tokyo accessibility score

88

Accessibility Issues

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

Best Practices

api.tokyo best practices score

67

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

api.tokyo SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Api.tokyo can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Api.tokyo 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

api.tokyo

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