9.2 sec in total
542 ms
8.2 sec
459 ms
Click here to check amazing Tokyooffice content. Otherwise, check out these important facts you probably never knew about tokyooffice.jp
東京をはじめ全国の賃貸オフィス探しは、全物件、仲介手数料無料のofficee(オフィシー)にお任せください。東京・大阪・福岡など全国主要11都市の賃貸オフィス・賃貸事務所情報サービスです。
Visit tokyooffice.jpWe 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.
tokyooffice.jp performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value8.8 s
1/100
25%
Value14.0 s
1/100
10%
Value18,890 ms
0/100
30%
Value0.119
85/100
15%
Value32.7 s
0/100
10%
542 ms
855 ms
454 ms
474 ms
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 size can be reduced by 308.0 kB (11%)
2.8 MB
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.
Potential reduce by 25.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 25.7 kB or 73% of the original size.
Potential reduce by 16.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. Tokyooffice images are well optimized though.
Potential reduce by 186.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.
Potential reduce by 79.9 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.
Number of requests can be reduced by 46 (45%)
103
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.
officee.jp
542 ms
officee.jp
855 ms
import.css
454 ms
search.css
474 ms
index.css
520 ms
jquery.js
1108 ms
jquery.mousewheel.js
588 ms
common.js
737 ms
search.js
1201 ms
jquery.easing.1.3.js
952 ms
index.js
997 ms
header.css
1028 ms
TweenMax.min.js
2017 ms
navifix.js
1459 ms
navimenu.js
1581 ms
conversion.js
63 ms
default.css
1088 ms
common.css
1419 ms
ga.js
67 ms
logo.png
345 ms
nav_search.png
239 ms
nav_btn_fb.png
619 ms
nav_btn_twt.png
597 ms
nav_btn_mail.png
619 ms
nav_txt_tell.png
711 ms
nav_tell.png
801 ms
searcharea_tit.gif
990 ms
searchbtn_text01.png
1159 ms
searchbtn_text02.png
1170 ms
searchbtn_text03.png
1176 ms
searchbtn_text04.png
1233 ms
searchbtn_text05.png
1329 ms
searchbtn_text06.png
1455 ms
searchbtn_bg.png
1593 ms
cont01_tit.gif
1649 ms
cont01_img_01.gif
1749 ms
cont01_img_02.gif
1805 ms
cont01_text.gif
1867 ms
cont02_tit.gif
1928 ms
cont02_text.gif
2022 ms
cont02_img.jpg
2505 ms
cont03_tit.gif
2250 ms
ft_banner_request.gif
2297 ms
ft_logo_s.gif
2385 ms
ft_btn_facebook.gif
2510 ms
ft_btn_twitter.gif
2534 ms
pagetop.png
2803 ms
all.js
321 ms
__utm.gif
12 ms
nav_area.png
2696 ms
nav_line.png
2692 ms
nav_favorite.png
2803 ms
nav_number_bg.png
2850 ms
nav_history.png
2962 ms
nav_other.png
3132 ms
arrow_icon_03.png
3134 ms
arrow_icon_02.gif
3132 ms
arrow_icon_01.gif
3251 ms
widgets.js
224 ms
bi.js
910 ms
access.php
3201 ms
146 ms
148 ms
xd_arbiter.php
333 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
62 ms
syndication
101 ms
402995684153884673
162 ms
access.php
2985 ms
cont01_btn.gif
3129 ms
cont02_btn.gif
3236 ms
cont03_btn_on.gif
3179 ms
proxy.jpg
80 ms
proxy.jpg
70 ms
proxy.jpg
69 ms
proxy.jpg
66 ms
proxy.jpg
67 ms
proxy.jpg
67 ms
proxy.jpg
99 ms
proxy.jpg
83 ms
proxy.jpg
83 ms
proxy.jpg
95 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
42 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
79 ms
cont3_more.gif
3176 ms
uNkfnSzs_normal.png
253 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
40 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
36 ms
ft_banner_request_on.gif
3064 ms
proxy.jpg
9 ms
proxy.jpg
18 ms
proxy.jpg
7 ms
proxy.jpg
14 ms
proxy.jpg
6 ms
proxy.jpg
5 ms
proxy.jpg
8 ms
proxy.jpg
6 ms
proxy.jpg
8 ms
proxy.jpg
8 ms
ft_btn_facebook_on.gif
2972 ms
ft_btn_twitter_on.gif
3128 ms
pagetop_on.png
3199 ms
701 ms
accordion_close.gif
3198 ms
accordion_open.gif
3123 ms
jot.html
27 ms
tokyooffice.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
tokyooffice.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
tokyooffice.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
JA
JA
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.
tokyooffice.jp
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: