Tools & Wizards About Us
nopa.or.jp screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

nopa.or.jp

一般社団法人ニューオフィス推進協会

Page Load Speed

4.2 sec in total

First Response

561 ms

Resources Loaded

3.5 sec

Page Rendered

111 ms

nopa.or.jp screenshot

About Website

Visit nopa.or.jp now to see the best up-to-date Nopa content for Japan and also check out these interesting facts you probably never knew about nopa.or.jp

一般社団法人ニューオフィス推進協会(NOPA)のサイトです。クリエイティブ・オフィス運動を始め、オフィスセキュリティーマーク認証制度の普及や、調査研究事業のさらなる充実、積極的な広報事業等を推進してまいります。

Visit nopa.or.jp

Key Findings

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

Performance Metrics

nopa.or.jp performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

72/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value5.5 s

71/100

10%

Network Requests Diagram

nopa.or.jp

561 ms

import.css

338 ms

submenu.js

353 ms

AC_RunActiveContent.js

368 ms

widgets.js

83 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 80% of them (35 requests) were addressed to the original Nopa.or.jp, 7% (3 requests) were made to Platform.twitter.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Nopa.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 57.6 kB (30%)

Content Size

194.0 kB

After Optimization

136.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nopa.or.jp main page is 194.0 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. 30% of websites need less resources to load. Images take 103.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 16.0 kB

  • Original 20.9 kB
  • After minification 15.3 kB
  • After compression 4.8 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 5.5 kB, which is 26% 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 16.0 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 852 B

  • Original 103.9 kB
  • After minification 103.0 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. Nopa images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 4.0 kB

  • Original 26.0 kB
  • After minification 26.0 kB
  • After compression 22.0 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 4.0 kB or 15% of the original size.

CSS Optimization

-85%

Potential reduce by 36.7 kB

  • Original 43.2 kB
  • After minification 30.4 kB
  • After compression 6.6 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. Nopa.or.jp needs all CSS files to be minified and compressed as it can save up to 36.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (69%)

Requests Now

42

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nopa.or.jp

nopa.or.jp

561 ms

import.css

import.css

338 ms

submenu.js

submenu.js

353 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

368 ms

widgets.js

widgets.js

83 ms

base.css

base.css

323 ms

common2.css

common2.css

339 ms

common0.css

common0.css

358 ms

top.css

top.css

373 ms

mcont.css

mcont.css

373 ms

header_bg.gif

header_bg.gif

177 ms

logo.gif

logo.gif

324 ms

header_inquiry.gif

header_inquiry.gif

339 ms

navi_01.gif

navi_01.gif

370 ms

navi_02.gif

navi_02.gif

370 ms

navi_03.gif

navi_03.gif

378 ms

navi_04.gif

navi_04.gif

543 ms

navi_05.gif

navi_05.gif

672 ms

navi_06.gif

navi_06.gif

702 ms

news_title.gif

news_title.gif

703 ms

icon_new.gif

icon_new.gif

717 ms

topics_title.gif

topics_title.gif

713 ms

topics_newoffice2014.jpg

topics_newoffice2014.jpg

1088 ms

topics_fm.jpg

topics_fm.jpg

1153 ms

topics_cover28.jpg

topics_cover28.jpg

1194 ms

side_bnr_osm.jpg

side_bnr_osm.jpg

1048 ms

side_bnr_member.jpg

side_bnr_member.jpg

1050 ms

side_bnr_pub.jpg

side_bnr_pub.jpg

1068 ms

pagetop.gif

pagetop.gif

1384 ms

navi_bg.gif

navi_bg.gif

1366 ms

arw_gry_03.gif

arw_gry_03.gif

1342 ms

arw_lblue.gif

arw_lblue.gif

1371 ms

footer_bg.gif

footer_bg.gif

1414 ms

arw_gry_01.gif

arw_gry_01.gif

1453 ms

analytics.js

analytics.js

5 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

131 ms

collect

collect

11 ms

like.php

like.php

175 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

42 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

39 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

29 ms

jot

jot

93 ms

i_print.css

i_print.css

353 ms

print.css

print.css

321 ms

Accessibility Review

nopa.or.jp accessibility score

89

Accessibility Issues

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.

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

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

Best Practices

nopa.or.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

High

Browser errors were logged to the console

SEO Factors

nopa.or.jp SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nopa.or.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 Nopa.or.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

nopa.or.jp

Open Graph description is not detected on the main page of Nopa. 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: