Access onair-blog.jp. おんえあ KCT@nsk公式ブログサービス

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

19/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.056

98/100

15%

TTI (Time to Interactive)

Value8.0 s

42/100

10%

onair-blog.jp

3121 ms

jquery.js

1153 ms

jquery.rollover.js

404 ms

smooth.pack.js

410 ms

jquery-1.2.6.js

1501 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 76% of them (69 requests) were addressed to the original Onair-blog.jp, 12% (11 requests) were made to Blog.nsk.ne.jp and 9% (8 requests) were made to Control.onair-blog.jp. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Blog.nsk.ne.jp.

Content Size

917.3 kB

After Optimization

697.6 kB

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

HTML Optimization

-85%

Potential reduce by 31.7 kB

Original 37.4 kB
After minification 27.4 kB
After compression 5.7 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 10.1 kB, which is 27% 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 31.7 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 20.9 kB

Original 652.5 kB
After minification 631.6 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. Onair Blog images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 140.3 kB

Original 195.7 kB
After minification 140.3 kB
After compression 55.4 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 140.3 kB or 72% of the original size.

CSS Optimization

-85%

Potential reduce by 26.8 kB

Original 31.7 kB
After minification 16.5 kB
After compression 4.9 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. Onair-blog.jp needs all CSS files to be minified and compressed as it can save up to 26.8 kB or 85% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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

[id] attributes on active, focusable elements are not unique

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

Displays images with incorrect aspect ratio

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

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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 Onair-blog.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 Onair-blog.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

onair-blog.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

おんえあ KCT@nsk公式ブログサービス

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

onair-blog.jp

jquery.js

jquery.rollover.js

smooth.pack.js

jquery-1.2.6.js

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

onair-blog.jp

jquery.js

jquery.rollover.js

smooth.pack.js

jquery-1.2.6.js

ui.core.js

ui.tabs.js

common.css

home.css

contents.css

regis.css

checker.css

ui.tabs.css

guide.css

ranking.css

base.css

textsettings.css

logo.gif

menu_1.gif

menu_2.gif

menu_3.gif

menu_4.gif

menu_5.gif

ds1.gif

profile.jpg

profile.jpg

profile.JPG

profile.gif

profile.gif

profile.jpg

profile.jpg

profile.jpg

profile.gif

profile.jpg

profile.JPG

link_point.gif

menu_boder.gif

bg_entry.jpg

entry_logo.gif

bt_entry.jpg

bt_guide.jpg

bg_login.gif

title_login.gif