Tools & Wizards About Us
nikaten.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

nikaten.com

二科展（二科展 公式ホームページ）

Page Load Speed

4.8 sec in total

First Response

625 ms

Resources Loaded

4 sec

Page Rendered

130 ms

nikaten.com screenshot

About Website

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

この二科展ドットコムは公益社団法人二科会が二科展（絵画部・彫刻部・デザイン部・写真部）に関する情報をお伝えするする公式ホームページです。

Visit nikaten.com

Key Findings

We analyzed Nikaten.com page load time and found that the first response time was 625 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

nikaten.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value8.4 s

19/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

nikaten.com

625 ms

style.css

211 ms

_else.css

345 ms

style.css

350 ms

index.css

355 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that all of those requests were addressed to Nikaten.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Nikaten.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 498.1 kB (75%)

Content Size

662.6 kB

After Optimization

164.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nikaten.com main page is 662.6 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. 20% of websites need less resources to load. CSS take 365.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 10.4 kB

  • Original 13.2 kB
  • After minification 13.1 kB
  • After compression 2.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. 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 10.4 kB or 79% of the original size.

Image Optimization

-9%

Potential reduce by 5.6 kB

  • Original 65.5 kB
  • After minification 59.9 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. Nikaten images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 158.2 kB

  • Original 218.2 kB
  • After minification 189.2 kB
  • After compression 60.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 158.2 kB or 72% of the original size.

CSS Optimization

-89%

Potential reduce by 324.0 kB

  • Original 365.7 kB
  • After minification 327.2 kB
  • After compression 41.7 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. Nikaten.com needs all CSS files to be minified and compressed as it can save up to 324.0 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (64%)

Requests Now

53

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nikaten. 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 from 27 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

nikaten.com

nikaten.com

625 ms

style.css

style.css

211 ms

_else.css

_else.css

345 ms

style.css

style.css

350 ms

index.css

index.css

355 ms

script.js

script.js

415 ms

common.css

common.css

228 ms

pagelayout.css

pagelayout.css

649 ms

printlayout.css

printlayout.css

314 ms

blockskin.css

blockskin.css

1062 ms

wp_style.css

wp_style.css

843 ms

overwrite.css

overwrite.css

275 ms

style.css

style.css

300 ms

theme.css

theme.css

626 ms

_else.css

_else.css

211 ms

_else.css

_else.css

173 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

874 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

175 ms

head.load.min.js

head.load.min.js

178 ms

movie.js

movie.js

192 ms

parts.js

parts.js

344 ms

fx.js

fx.js

695 ms

override.js

override.js

356 ms

load.js

load.js

382 ms

_area_header.css

_area_header.css

210 ms

_area_billboard.css

_area_billboard.css

173 ms

_area_main.css

_area_main.css

219 ms

_area_side_a.css

_area_side_a.css

175 ms

_area_side_b.css

_area_side_b.css

178 ms

_area_footer.css

_area_footer.css

192 ms

_block_header.css

_block_header.css

344 ms

_block_billboard.css

_block_billboard.css

348 ms

nikaten_index_h01.css

nikaten_index_h01.css

355 ms

nikaten_index_01.css

nikaten_index_01.css

382 ms

_block_side_a.css

_block_side_a.css

416 ms

_block_side_b.css

_block_side_b.css

435 ms

_block_footer.css

_block_footer.css

514 ms

front_art04.png

front_art04.png

687 ms

bo96060_01_02.png

bo96060_01_02.png

523 ms

bo6010_1m_01.png

bo6010_1m_01.png

564 ms

bo6010_1m_02.png

bo6010_1m_02.png

617 ms

bo6010_2m_02.png

bo6010_2m_02.png

646 ms

bo6010_1m_03.png

bo6010_1m_03.png

678 ms

bo6010_2m_03.png

bo6010_2m_03.png

698 ms

bo6010_1m_04.png

bo6010_1m_04.png

754 ms

bo6010_2m_04.png

bo6010_2m_04.png

825 ms

bo6010_1m_05.png

bo6010_1m_05.png

863 ms

bo6010_1m_06.png

bo6010_1m_06.png

850 ms

bo6010_2m_06.png

bo6010_2m_06.png

858 ms

bo6010_1m_07.png

bo6010_1m_07.png

874 ms

bo6010_2m_07.png

bo6010_2m_07.png

943 ms

bo6010_1m_08.png

bo6010_1m_08.png

1032 ms

bg40_40_05nikatencom3.png

bg40_40_05nikatencom3.png

1020 ms

hr.gif

hr.gif

1032 ms

Accessibility Review

nikaten.com accessibility score

100

Accessibility Issues

Best Practices

nikaten.com best practices score

75

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

SEO Factors

nikaten.com SEO score

77

Search Engine Optimization Advices

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 Nikaten.com 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 Nikaten.com 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

nikaten.com

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