Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 78

    SEO

    Google-friendlier than
    40% of websites

office-navi.jp

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

Page Load Speed

11.5 sec in total

First Response

628 ms

Resources Loaded

10.3 sec

Page Rendered

592 ms

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 628 ms and then it took 10.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

office-navi.jp performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value29.1 s

0/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value2,400 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.333

34/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

office-navi.jp

628 ms

www.office-navi.jp

1965 ms

docodoco

688 ms

docodoco_ga_plugin.js

402 ms

base.css

400 ms

Our browser made a total of 269 requests to load all elements on the main page. We found that 68% of them (183 requests) were addressed to the original Office-navi.jp, 9% (23 requests) were made to Static.xx.fbcdn.net and 6% (16 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Office-navi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 380.5 kB (31%)

Content Size

1.2 MB

After Optimization

829.1 kB

In fact, the total size of Office-navi.jp main page is 1.2 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. 50% of websites need less resources to load. Images take 757.9 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 210.0 kB

  • Original 240.1 kB
  • After minification 225.8 kB
  • After compression 30.1 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 210.0 kB or 87% of the original size.

Image Optimization

-5%

Potential reduce by 34.4 kB

  • Original 757.9 kB
  • After minification 723.4 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. Office Navi images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 101.5 kB

  • Original 167.9 kB
  • After minification 157.3 kB
  • After compression 66.4 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 101.5 kB or 60% of the original size.

CSS Optimization

-79%

Potential reduce by 34.5 kB

  • Original 43.7 kB
  • After minification 34.0 kB
  • After compression 9.2 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 needs all CSS files to be minified and compressed as it can save up to 34.5 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 89 (34%)

Requests Now

262

After Optimization

173

The browser has sent 262 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 43 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

office-navi.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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

office-navi.jp 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

office-navi.jp SEO score

78

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

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

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: