Tools & Wizards About Us
nixus.jp screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 50

    SEO

    Google-friendlier than
    19% of websites

nixus.jp

NIXUS -放送・映像システムのニクサス 日興通信株式会社-

Page Load Speed

7.9 sec in total

First Response

1.8 sec

Resources Loaded

5.9 sec

Page Rendered

188 ms

nixus.jp screenshot

About Website

Welcome to nixus.jp homepage info - get ready to check NIXUS best content for Japan right away, or after learning these important things about nixus.jp

日興通信株式会社 NIXUSは映像の力をキーワードに、放送用テロップシステム、コンテンツデータベースなどを扱うブランドです。

Visit nixus.jp

Key Findings

We analyzed Nixus.jp page load time and found that the first response time was 1.8 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

nixus.jp performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.062

97/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

nixus.jp

1842 ms

reset.css

593 ms

text.css

592 ms

kube.css

950 ms

kube2.css

2816 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 93% of them (54 requests) were addressed to the original Nixus.jp, 2% (1 request) were made to Ajax.googleapis.com and 2% (1 request) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Nixus.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (38%)

Content Size

2.7 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 29.5 kB

  • Original 36.9 kB
  • After minification 28.0 kB
  • After compression 7.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 8.9 kB, which is 24% 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 29.5 kB or 80% of the original size.

Image Optimization

-35%

Potential reduce by 859.6 kB

  • Original 2.4 MB
  • After minification 1.6 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. Obviously, NIXUS needs image optimization as it can save up to 859.6 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-58%

Potential reduce by 66.9 kB

  • Original 115.7 kB
  • After minification 84.9 kB
  • After compression 48.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 66.9 kB or 58% of the original size.

CSS Optimization

-83%

Potential reduce by 65.2 kB

  • Original 78.6 kB
  • After minification 61.7 kB
  • After compression 13.4 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. Nixus.jp needs all CSS files to be minified and compressed as it can save up to 65.2 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

56

After Optimization

41

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nixus.jp

nixus.jp

1842 ms

reset.css

reset.css

593 ms

text.css

text.css

592 ms

kube.css

kube.css

950 ms

kube2.css

kube2.css

2816 ms

design-resp.css

design-resp.css

2384 ms

flexslider.css

flexslider.css

565 ms

jquery.min.js

jquery.min.js

21 ms

jquery.flexslider.js

jquery.flexslider.js

3822 ms

jquery.corner.js

jquery.corner.js

1155 ms

jquery.lazyload.js

jquery.lazyload.js

947 ms

heightLine.js

heightLine.js

1166 ms

jquery.fitvids.js

jquery.fitvids.js

1134 ms

jquery.horizontalNav.js

jquery.horizontalNav.js

1323 ms

colorbox.css

colorbox.css

564 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

854 ms

addthis_widget.js

addthis_widget.js

12 ms

js

js

59 ms

b-logo.png

b-logo.png

1125 ms

b-products_off.png

b-products_off.png

2339 ms

b-event_off.png

b-event_off.png

2346 ms

b-support_off.png

b-support_off.png

540 ms

b-toiawase_off.png

b-toiawase_off.png

638 ms

69.png

69.png

1857 ms

53.png

53.png

1922 ms

45.png

45.png

2404 ms

34.png

34.png

2065 ms

33_1.png

33_1.png

3175 ms

19.png

19.png

2562 ms

11.png

11.png

3204 ms

thumb-69.png

thumb-69.png

2525 ms

thumb-53.png

thumb-53.png

2769 ms

thumb-45.png

thumb-45.png

2605 ms

thumb-34.png

thumb-34.png

2714 ms

thumb-27.png

thumb-27.png

2775 ms

thumb-19.png

thumb-19.png

2818 ms

thumb-11.png

thumb-11.png

3089 ms

top_cgn_off.png

top_cgn_off.png

3469 ms

top_sg-ljio_off.png

top_sg-ljio_off.png

2991 ms

top_vision3_off.png

top_vision3_off.png

3471 ms

top_pc_off.png

top_pc_off.png

3205 ms

top_apras_off.png

top_apras_off.png

3651 ms

top_tc4_off.png

top_tc4_off.png

3155 ms

top_bj_off.png

top_bj_off.png

3186 ms

pta.js

pta.js

14 ms

footertop.png

footertop.png

214 ms

b-products_on.png

b-products_on.png

214 ms

b-event_on.png

b-event_on.png

188 ms

b-support_on.png

b-support_on.png

214 ms

b-toiawase_on.png

b-toiawase_on.png

189 ms

top_cgn_on.png

top_cgn_on.png

431 ms

top_sg-ljio_on.png

top_sg-ljio_on.png

747 ms

top_vision3_on.png

top_vision3_on.png

388 ms

top_pc_on.png

top_pc_on.png

391 ms

top_apras_on.png

top_apras_on.png

430 ms

top_tc4_on.png

top_tc4_on.png

428 ms

top_bj_on.png

top_bj_on.png

578 ms

bg_direction_nav.png

bg_direction_nav.png

215 ms

Accessibility Review

nixus.jp accessibility score

70

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

nixus.jp SEO score

50

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

nixus.jp

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