Report Summary

  • 87

    Performance

    Renders faster than
    90% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

shinketsu.jp

知的財産審決データベース

Page Load Speed

3 sec in total

First Response

377 ms

Resources Loaded

2.5 sec

Page Rendered

124 ms

About Website

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

知的財産審決データベースでは、効率的に特許・商標・意匠の審決を検索することが出来ます!企業の商標管理実務者・特許庁審査官・審判官の方には最適なデータベースです。

Visit shinketsu.jp

Key Findings

We analyzed Shinketsu.jp page load time and found that the first response time was 377 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

shinketsu.jp performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

shinketsu.jp

377 ms

portalBase.css

186 ms

common.js

370 ms

portalBanner.js

392 ms

ScriptServlet

44 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 93% of them (13 requests) were addressed to the original Shinketsu.jp, 7% (1 request) were made to Srv1.wa.marketingsolutions.yahoo.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Shinketsu.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.7 kB (67%)

Content Size

14.4 kB

After Optimization

4.8 kB

In fact, the total size of Shinketsu.jp main page is 14.4 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 7.3 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 4.4 kB

  • Original 7.3 kB
  • After minification 6.8 kB
  • After compression 2.9 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 4.4 kB or 61% of the original size.

JavaScript Optimization

-71%

Potential reduce by 2.1 kB

  • Original 3.0 kB
  • After minification 2.2 kB
  • After compression 866 B

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 2.1 kB or 71% of the original size.

CSS Optimization

-75%

Potential reduce by 3.1 kB

  • Original 4.2 kB
  • After minification 3.6 kB
  • After compression 1.0 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. Shinketsu.jp needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 75% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

13

After Optimization

13

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shinketsu. According to our analytics all requests are already optimized.

Accessibility Review

shinketsu.jp accessibility score

84

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Best Practices

shinketsu.jp best practices score

75

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

SEO Factors

shinketsu.jp SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shinketsu.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 Shinketsu.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

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