Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

tokyooffice.jp

officee|東京・全国の賃貸オフィス探し【仲介手数料無料】

Page Load Speed

9.2 sec in total

First Response

542 ms

Resources Loaded

8.2 sec

Page Rendered

459 ms

tokyooffice.jp screenshot

About Website

Click here to check amazing Tokyooffice content. Otherwise, check out these important facts you probably never knew about tokyooffice.jp

東京をはじめ全国の賃貸オフィス探しは、全物件、仲介手数料無料のofficee(オフィシー)にお任せください。東京・大阪・福岡など全国主要11都市の賃貸オフィス・賃貸事務所情報サービスです。

Visit tokyooffice.jp

Key Findings

We analyzed Tokyooffice.jp page load time and found that the first response time was 542 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

tokyooffice.jp performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value18,890 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.119

85/100

15%

TTI (Time to Interactive)

Value32.7 s

0/100

10%

Network Requests Diagram

officee.jp

542 ms

officee.jp

855 ms

import.css

454 ms

search.css

474 ms

index.css

520 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Tokyooffice.jp, 19% (20 requests) were made to O.twimg.com and 5% (5 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Officee.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 308.0 kB (11%)

Content Size

2.8 MB

After Optimization

2.5 MB

In fact, the total size of Tokyooffice.jp main page is 2.8 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 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 25.7 kB

  • Original 35.3 kB
  • After minification 32.6 kB
  • After compression 9.6 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 25.7 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 16.3 kB

  • Original 2.4 MB
  • After minification 2.3 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. Tokyooffice images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 186.1 kB

  • Original 314.2 kB
  • After minification 286.1 kB
  • After compression 128.1 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 186.1 kB or 59% of the original size.

CSS Optimization

-83%

Potential reduce by 79.9 kB

  • Original 96.0 kB
  • After minification 80.5 kB
  • After compression 16.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. Tokyooffice.jp needs all CSS files to be minified and compressed as it can save up to 79.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (45%)

Requests Now

103

After Optimization

57

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

Accessibility Review

tokyooffice.jp accessibility score

88

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.

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

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

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

tokyooffice.jp SEO score

86

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

Open Graph data is detected on the main page of Tokyooffice. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: