Access nikinokashi.co.jp. 二木の菓子 | かつては初代林家三平師匠のＣＭ『ニキ、ニキ、ニキ、ニキ、二木の菓子！』でおなじみ！！

name

value

score

weighting

FCP (First Contentful Paint)

Value8.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.7 s

0/100

25%

SI (Speed Index)

Value23.2 s

0/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.439

21/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

www.nikinokashi.co.jp

3330 ms

analytics.js

46 ms

wp-emoji-release.min.js

184 ms

style.css

348 ms

styles.css

352 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 66% of them (69 requests) were addressed to the original Nikinokashi.co.jp, 17% (18 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 (3.3 sec) belongs to the original domain Nikinokashi.co.jp.

Content Size

798.2 kB

After Optimization

687.4 kB

In fact, the total size of Nikinokashi.co.jp main page is 798.2 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. 65% of websites need less resources to load. Images take 554.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 55.2 kB

Original 70.4 kB
After minification 67.8 kB
After compression 15.1 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 55.2 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 15.5 kB

Original 554.9 kB
After minification 539.4 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. Nikinokashi images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 34.7 kB

Original 132.4 kB
After minification 132.3 kB
After compression 97.7 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 34.7 kB or 26% of the original size.

CSS Optimization

-13%

Potential reduce by 5.4 kB

Original 40.6 kB
After minification 40.5 kB
After compression 35.2 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. Nikinokashi.co.jp needs all CSS files to be minified and compressed as it can save up to 5.4 kB or 13% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA input fields do not have accessible names

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

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

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.

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

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 Nikinokashi.co.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 Nikinokashi.co.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

nikinokashi.co.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

二木の菓子 | かつては初代林家三平師匠のＣＭ『ニキ、ニキ、ニキ、ニキ、二木の菓子！』でおなじみ！！

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

www.nikinokashi.co.jp

analytics.js

wp-emoji-release.min.js

style.css

styles.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

www.nikinokashi.co.jp

analytics.js

wp-emoji-release.min.js

style.css

styles.css

sb-instagram.min.css

font-awesome.min.css

screen.min.css

vkExUnit_style.css

masterslider.main.css

custom.css

jquery.js

jquery-migrate.min.js

flags.js

style.css

comment-style.css

japanese.css

jscript.js

scroll.js

comment.js

rollover.js

slick.css

widgets.js

jquery.form.min.js

scripts.js

sb-instagram.min.js

front.min.js

wp-embed.min.js

all.min.js

jquery.easing.js

slick.min.js

collect

element.js

js

style_pc.css

logo.jpg

arrow1.png

icon_rss.png

search_input.gif

search_button.gif

20170817-01.jpg

20160830-05.jpg

no_image1.jpg