Tools & Wizards About Us
neribun.or.jp screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

neribun.or.jp

公益財団法人練馬区文化振興協会(練馬区立練馬文化センター/練馬区立大泉学園ゆめりあホール/練馬区立石神井公園ふるさと文化館・分室/練馬区立美術館)

Page Load Speed

4.9 sec in total

First Response

716 ms

Resources Loaded

4 sec

Page Rendered

196 ms

neribun.or.jp screenshot

About Website

Click here to check amazing Neribun content for Japan. Otherwise, check out these important facts you probably never knew about neribun.or.jp

練馬区立練馬文化センター、練馬区立大泉学園ゆめりあホール、練馬区立石神井公園ふるさと文化館・分室、練馬区立美術館のイベント情報

Visit neribun.or.jp

Key Findings

We analyzed Neribun.or.jp page load time and found that the first response time was 716 ms and then it took 4.2 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

neribun.or.jp performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.178

68/100

15%

TTI (Time to Interactive)

Value10.0 s

27/100

10%

Network Requests Diagram

neribun.or.jp

716 ms

zaidan_001.css

342 ms

styleswitcher.js

339 ms

styleswitcher.js

355 ms

swfobject.js

361 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 84% of them (76 requests) were addressed to the original Neribun.or.jp, 4% (4 requests) were made to Platform.twitter.com and 2% (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 Neribun.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 89.2 kB (16%)

Content Size

567.4 kB

After Optimization

478.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 27.3 kB

  • Original 34.6 kB
  • After minification 33.9 kB
  • After compression 7.3 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 27.3 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 12.7 kB

  • Original 442.2 kB
  • After minification 429.5 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. Neribun images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 47.4 kB

  • Original 87.2 kB
  • After minification 85.8 kB
  • After compression 39.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 47.4 kB or 54% of the original size.

CSS Optimization

-52%

Potential reduce by 1.8 kB

  • Original 3.4 kB
  • After minification 3.2 kB
  • After compression 1.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. Neribun.or.jp needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 52% of the original size.

Requests Breakdown

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

Requests Now

90

After Optimization

58

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

neribun.or.jp

neribun.or.jp

716 ms

zaidan_001.css

zaidan_001.css

342 ms

styleswitcher.js

styleswitcher.js

339 ms

styleswitcher.js

styleswitcher.js

355 ms

swfobject.js

swfobject.js

361 ms

z_wall_001.gif

z_wall_001.gif

197 ms

header_001.gif

header_001.gif

198 ms

f_large.gif

f_large.gif

214 ms

f_medium.gif

f_medium.gif

195 ms

f_small.gif

f_small.gif

197 ms

spacer.gif

spacer.gif

343 ms

search_001.gif

search_001.gif

349 ms

01_off.gif

01_off.gif

355 ms

02_off.gif

02_off.gif

359 ms

03_off.gif

03_off.gif

360 ms

04_off.gif

04_off.gif

418 ms

08_off.gif

08_off.gif

507 ms

05_off.gif

05_off.gif

522 ms

06_off.gif

06_off.gif

530 ms

07_off.gif

07_off.gif

538 ms

09_off.gif

09_off.gif

539 ms

waku_001.jpg

waku_001.jpg

621 ms

saishin_01.gif

saishin_01.gif

675 ms

kyoukai_rss.gif

kyoukai_rss.gif

694 ms

internet02_off.gif

internet02_off.gif

705 ms

b_001.jpg

b_001.jpg

894 ms

b_002.jpg

b_002.jpg

895 ms

b_003.jpg

b_003.jpg

1027 ms

b_005.gif

b_005.gif

842 ms

b_006.gif

b_006.gif

867 ms

b_007.gif

b_007.gif

881 ms

b_004.gif

b_004.gif

1011 ms

kanren.gif

kanren.gif

1040 ms

b_008.jpg

b_008.jpg

1409 ms

b_009.jpg

b_009.jpg

1281 ms

b_012.jpg

b_012.jpg

1282 ms

b_013.jpg

b_013.jpg

1347 ms

b_010.gif

b_010.gif

1228 ms

kyoritz.gif

kyoritz.gif

1213 ms

sign_003.gif

sign_003.gif

1388 ms

sdk.js

sdk.js

158 ms

tf.html

tf.html

1427 ms

f_zaidan.cgi

f_zaidan.cgi

1016 ms

ga.js

ga.js

6 ms

__utm.gif

__utm.gif

12 ms

zaidan.html

zaidan.html

1248 ms

zaidan.cgi

zaidan.cgi

1410 ms

header_002.gif

header_002.gif

1379 ms

62 ms

wall_002.gif

wall_002.gif

1372 ms

xd_arbiter.php

xd_arbiter.php

139 ms

xd_arbiter.php

xd_arbiter.php

266 ms

wall_001.gif

wall_001.gif

1382 ms

line_001.gif

line_001.gif

1276 ms

line_003.gif

line_003.gif

1298 ms

zaidan_001.css

zaidan_001.css

366 ms

swfwrite_ver8.js

swfwrite_ver8.js

401 ms

5193_01.jpg

5193_01.jpg

244 ms

spacer.gif

spacer.gif

184 ms

5196_01.jpg

5196_01.jpg

452 ms

5194_01.jpg

5194_01.jpg

428 ms

5202_01.jpg

5202_01.jpg

364 ms

5195_01.jpg

5195_01.jpg

1450 ms

other_event_off.gif

other_event_off.gif

1453 ms

atrium_off.gif

atrium_off.gif

446 ms

wall_002.gif

wall_002.gif

550 ms

sign_002.gif

sign_002.gif

602 ms

sign_003.gif

sign_003.gif

648 ms

_web.css

_web.css

309 ms

style.css

style.css

304 ms

mootools-1.2-core.js

mootools-1.2-core.js

506 ms

_class.noobSlide.packed.js

_class.noobSlide.packed.js

340 ms

tweet_button.html

tweet_button.html

25 ms

widgets.js

widgets.js

26 ms

jot

jot

102 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

15 ms

like.php

like.php

67 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

22 ms

TY3MhkXpWJ-.js

TY3MhkXpWJ-.js

295 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

328 ms

swfwrite_ver8.js

swfwrite_ver8.js

197 ms

jot

jot

26 ms

kyoukai_02.gif

kyoukai_02.gif

177 ms

kyoukai_rss_002.gif

kyoukai_rss_002.gif

206 ms

new_001.gif

new_001.gif

171 ms

01.jpg

01.jpg

531 ms

02.jpg

02.jpg

540 ms

03.jpg

03.jpg

361 ms

zaidan_large.css

zaidan_large.css

176 ms

zaidan_medium.css

zaidan_medium.css

176 ms

zaidan_small.css

zaidan_small.css

176 ms

Accessibility Review

neribun.or.jp accessibility score

90

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

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

High

Links do not have a discernible name

Best Practices

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

neribun.or.jp SEO score

86

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 uses legible font sizes

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 Neribun.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 Neribun.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

neribun.or.jp

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