Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 85

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

i-office.jp.net

吉祥寺駅から徒歩5分。登記可能な会員制コワーキングスペース/シェアオフィス「i-office吉祥寺」 – 起業/創業に必要なセミナーやビジネスサポート(会計入力・社会保険手続・税務申告等の支援)も充実!武蔵野市、商工会議所、金融機関等と連携しているのも強みです。

Page Load Speed

4.8 sec in total

First Response

775 ms

Resources Loaded

3.8 sec

Page Rendered

227 ms

i-office.jp.net screenshot

About Website

Visit i-office.jp.net now to see the best up-to-date I Office content for Japan and also check out these interesting facts you probably never knew about i-office.jp.net

起業/創業に必要なセミナーやビジネスサポート(会計入力・社会保険手続・税務申告等の支援)も充実!武蔵野市、商工会議所、金融機関等と連携しているのも強みです。

Visit i-office.jp.net

Key Findings

We analyzed I-office.jp.net page load time and found that the first response time was 775 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

i-office.jp.net performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value21.2 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value1,520 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value19.2 s

3/100

10%

Network Requests Diagram

i-office.jp.net

775 ms

cssreset-min.css

338 ms

cssbase-min.css

347 ms

cssfonts-min.css

348 ms

kichijoji.css

546 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 85% of them (23 requests) were addressed to the original I-office.jp.net, 7% (2 requests) were made to Ajax.googleapis.com and 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain I-office.jp.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.0 kB (4%)

Content Size

641.9 kB

After Optimization

615.9 kB

In fact, the total size of I-office.jp.net main page is 641.9 kB. 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 608.9 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 4.2 kB

  • Original 6.6 kB
  • After minification 5.6 kB
  • After compression 2.4 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.0 kB, which is 15% 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 4.2 kB or 63% of the original size.

Image Optimization

-2%

Potential reduce by 15.2 kB

  • Original 608.9 kB
  • After minification 593.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. I Office images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 665 B

  • Original 18.2 kB
  • After minification 17.9 kB
  • After compression 17.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-73%

Potential reduce by 6.0 kB

  • Original 8.2 kB
  • After minification 6.1 kB
  • After compression 2.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. I-office.jp.net needs all CSS files to be minified and compressed as it can save up to 6.0 kB or 73% of the original size.

Requests Breakdown

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

Requests Now

25

After Optimization

19

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

Accessibility Review

i-office.jp.net accessibility score

84

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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

<frame> or <iframe> elements do not have a title

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.

Best Practices

i-office.jp.net best practices score

85

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

i-office.jp.net SEO score

92

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

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 I-office.jp.net 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 I-office.jp.net 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 description is not detected on the main page of I Office. 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: