Tools & Wizards About Us
office-navi.jp screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

office-navi.jp

賃貸オフィス・賃貸事務所をお探しなら【オフィスナビ®】

Page Load Speed

8.5 sec in total

First Response

13 ms

Resources Loaded

7.3 sec

Page Rendered

1.3 sec

office-navi.jp screenshot

About Website

Click here to check amazing Office Navi content for Japan. Otherwise, check out these important facts you probably never knew about office-navi.jp

賃貸オフィス、貸事務所をお探しならオフィスナビ®。東京・大阪・名古屋・福岡・札幌・仙台など全国のオフィスや事務所の賃貸情報数は国内最大級！しかも毎日更新中。貸事務所をお探しの方は是非ご活用下さい。

Visit office-navi.jp

Key Findings

We analyzed Office-navi.jp page load time and found that the first response time was 13 ms and then it took 8.5 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

office-navi.jp performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value19.7 s

0/100

25%

SI (Speed Index)

Value20.9 s

0/100

10%

TBT (Total Blocking Time)

Value5,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.328

35/100

15%

TTI (Time to Interactive)

Value45.7 s

0/100

10%

Network Requests Diagram

office-navi.jp

13 ms

www.office-navi.jp

1842 ms

embed.js

424 ms

yakuhanjp.min.css

36 ms

app.css

1347 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 55% of them (60 requests) were addressed to the original Office-navi.jp, 11% (12 requests) were made to Static.xx.fbcdn.net and 5% (5 requests) were made to V1.chamo-chat.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Office-navi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 595.0 kB (23%)

Content Size

2.6 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Office-navi.jp main page is 2.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 542.4 kB

  • Original 721.4 kB
  • After minification 671.2 kB
  • After compression 179.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. 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 542.4 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 132 B

  • Original 1.3 MB
  • After minification 1.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. Office Navi images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 51.1 kB

  • Original 452.9 kB
  • After minification 448.3 kB
  • After compression 401.8 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 51.1 kB or 11% of the original size.

CSS Optimization

-2%

Potential reduce by 1.4 kB

  • Original 64.8 kB
  • After minification 64.8 kB
  • After compression 63.4 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. Office-navi.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (36%)

Requests Now

106

After Optimization

68

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

office-navi.jp

office-navi.jp

13 ms

www.office-navi.jp

www.office-navi.jp

1842 ms

embed.js

embed.js

424 ms

yakuhanjp.min.css

yakuhanjp.min.css

36 ms

app.css

app.css

1347 ms

all.css

all.css

35 ms

sdk.js

sdk.js

14 ms

app.js

app.js

1826 ms

index.js

index.js

1190 ms

top-recommend-tab.js

top-recommend-tab.js

842 ms

gtm.js

gtm.js

220 ms

logo01.png

logo01.png

569 ms

logo01-fix.png

logo01-fix.png

300 ms

icon-search-area01.svg

icon-search-area01.svg

301 ms

icon-search-station01.svg

icon-search-station01.svg

456 ms

icon-tel01.svg

icon-tel01.svg

801 ms

img06.png

img06.png

1102 ms

img02.png

img02.png

950 ms

img07.png

img07.png

1403 ms

img03.png

img03.png

1288 ms

img01.png

img01.png

1543 ms

img04.png

img04.png

1122 ms

img05.png

img05.png

1273 ms

mainimage_rentalofficesearch.jpg

mainimage_rentalofficesearch.jpg

1293 ms

mainslide_facility.jpg

mainslide_facility.jpg

2272 ms

mainslide_renewal.jpg

mainslide_renewal.jpg

2120 ms

mainslide_interview_vol47.jpg

mainslide_interview_vol47.jpg

1543 ms

mainimage_vol36.png

mainimage_vol36.png

1971 ms

mainslide_remote.jpg

mainslide_remote.jpg

2426 ms

mainslide_layout.jpg

mainslide_layout.jpg

1980 ms

mainslide_blog.jpg

mainslide_blog.jpg

2134 ms

mainslide_highgrade.jpg

mainslide_highgrade.jpg

2897 ms

mainslide_officemug.jpg

mainslide_officemug.jpg

2816 ms

img01.jpg

img01.jpg

2290 ms

building.svg

building.svg

2304 ms

04.jpg

04.jpg

2441 ms

rental-office-logo.svg

rental-office-logo.svg

2457 ms

01.jpg

01.jpg

3127 ms

logo_inuki01.png

logo_inuki01.png

2670 ms

03.jpg

03.jpg

2773 ms

05.jpg

05.jpg

2628 ms

06.jpg

06.jpg

3460 ms

07.jpg

07.jpg

2840 ms

08.jpg

08.jpg

2881 ms

fa-solid-900.woff

fa-solid-900.woff

84 ms

fa-regular-400.woff

fa-regular-400.woff

84 ms

sdk.js

sdk.js

48 ms

09.jpg

09.jpg

3181 ms

destination

destination

36 ms

ytag.js

ytag.js

743 ms

3vt0m00xdl

3vt0m00xdl

202 ms

chamovps.js

chamovps.js

913 ms

10.jpg

10.jpg

2695 ms

11.jpg

11.jpg

2627 ms

12.jpg

12.jpg

2660 ms

clarity.js

clarity.js

18 ms

voice.svg

voice.svg

2615 ms

news.svg

news.svg

2947 ms

handshake.svg

handshake.svg

2975 ms

service-bg.jpg

service-bg.jpg

2348 ms

star.svg

star.svg

2252 ms

staff-bg.jpg

staff-bg.jpg

2851 ms

widget.js.php

widget.js.php

1766 ms

staff.svg

staff.svg

2751 ms

member-bg.jpg

member-bg.jpg

2344 ms

img_bnr_inuki-guidebook.jpg

img_bnr_inuki-guidebook.jpg

2850 ms

img_bnr_seminar.jpg

img_bnr_seminar.jpg

2906 ms

rakulog_async.js

rakulog_async.js

1022 ms

js

js

60 ms

analytics.js

analytics.js

27 ms

tag.js

tag.js

280 ms

s_retargeting.js

s_retargeting.js

944 ms

page.php

page.php

257 ms

img_bnr_vr-blog.jpg

img_bnr_vr-blog.jpg

2365 ms

img_bnr_layout-sample.jpg

img_bnr_layout-sample.jpg

2903 ms

img_bnr_interview.jpg

img_bnr_interview.jpg

2531 ms

collect

collect

201 ms

collect

collect

176 ms

u2zNh1q5aWK.css

u2zNh1q5aWK.css

23 ms

SHojUHmeyWm.js

SHojUHmeyWm.js

41 ms

xjg1QNQguf-.js

xjg1QNQguf-.js

39 ms

eQ3e44cCeXh.js

eQ3e44cCeXh.js

74 ms

qnn7MVQZYOT.js

qnn7MVQZYOT.js

74 ms

7CmGfGBVS6H.js

7CmGfGBVS6H.js

79 ms

p55HfXW__mM.js

p55HfXW__mM.js

77 ms

G95XClHFDrT.js

G95XClHFDrT.js

78 ms

OWkNLphO4cA.js

OWkNLphO4cA.js

82 ms

304080580_734469704569597_1726524923836772370_n.png

304080580_734469704569597_1726524923836772370_n.png

70 ms

554t-O9EjCU.js

554t-O9EjCU.js

36 ms

4Za9TE_Wiy4.js

4Za9TE_Wiy4.js

34 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

30 ms

ga-audiences

ga-audiences

64 ms

img_bnr_vr-service.jpg

img_bnr_vr-service.jpg

2167 ms

img_bnr_remote-service.jpg

img_bnr_remote-service.jpg

2211 ms

bnr_first_step.jpg

bnr_first_step.jpg

2616 ms

bnr_car_parking.jpg

bnr_car_parking.jpg

2174 ms

fbevents.js

fbevents.js

5 ms

bat.js

bat.js

47 ms

283011997.js

283011997.js

11 ms

283011997

283011997

217 ms

loader.gif

loader.gif

172 ms

td_chm_access.js

td_chm_access.js

740 ms

chamo_sm.gif

chamo_sm.gif

330 ms

chamo_sm_offline.gif

chamo_sm_offline.gif

501 ms

td.min.js

td.min.js

22 ms

aid

aid

672 ms

chamo_access_log

chamo_access_log

24 ms

_analysis.rakulog

_analysis.rakulog

170 ms

chamo.pc.css

chamo.pc.css

173 ms

c.gif

c.gif

8 ms

Accessibility Review

office-navi.jp accessibility score

83

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

office-navi.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Missing source maps for large first-party JavaScript

SEO Factors

office-navi.jp SEO score

78

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Office-navi.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 Office-navi.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

office-navi.jp

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