Tools & Wizards About Us

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

niben.jp

第二東京弁護士会（法律相談・弁護士紹介等）

Page Load Speed

9.5 sec in total

First Response

594 ms

Resources Loaded

8.6 sec

Page Rendered

348 ms

About Website

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

第二東京弁護士会のWebサイトです。法律の問題について相談したい方、法教育をご希望の方、求人情報をお探しの方などへ向けて、様々なサービスを提供しています。

Visit niben.jp

Key Findings

We analyzed Niben.jp page load time and found that the first response time was 594 ms and then it took 8.9 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

niben.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value6,260 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.29

41/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

niben.jp

594 ms

jquery.min.js

28 ms

jquery.cookie.js

329 ms

jquery.page-scroller.js

327 ms

rollover.js

337 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 96% of them (106 requests) were addressed to the original Niben.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Niben.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 254.4 kB (15%)

Content Size

1.7 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 20.7 kB

  • Original 27.1 kB
  • After minification 22.9 kB
  • After compression 6.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 4.2 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 20.7 kB or 77% of the original size.

Image Optimization

-8%

Potential reduce by 115.5 kB

  • Original 1.5 MB
  • After minification 1.4 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. Niben images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 14.6 kB

  • Original 39.5 kB
  • After minification 32.4 kB
  • After compression 24.9 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 14.6 kB or 37% of the original size.

CSS Optimization

-84%

Potential reduce by 103.5 kB

  • Original 122.8 kB
  • After minification 105.2 kB
  • After compression 19.3 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. Niben.jp needs all CSS files to be minified and compressed as it can save up to 103.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (15%)

Requests Now

108

After Optimization

92

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

niben.jp accessibility score

91

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

Links do not have a discernible name

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

niben.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

niben.jp SEO score

84

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Niben.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Niben.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 description is not detected on the main page of Niben. 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: