Access nippon-olive.co.jp. 自然派オリーブ化粧品の日本オリーブ公式通販

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value330 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.28

43/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

nippon-olive.co.jp

554 ms

top.php

837 ms

corporate.css

158 ms

bgstretcher.css

296 ms

rollover.js

311 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 71% of them (44 requests) were addressed to the original Nippon-olive.co.jp, 6% (4 requests) were made to Xc520.xbit.jp and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Xc520.xbit.jp.

Content Size

1.6 MB

After Optimization

1.4 MB

In fact, the total size of Nippon-olive.co.jp main page is 1.6 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 7.7 kB

Original 10.8 kB
After minification 9.8 kB
After compression 3.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 7.7 kB or 71% of the original size.

Image Optimization

-5%

Potential reduce by 68.3 kB

Original 1.4 MB
After minification 1.4 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. Nippon Olive images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 104.2 kB

Original 188.2 kB
After minification 181.3 kB
After compression 84.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 104.2 kB or 55% of the original size.

CSS Optimization

-82%

Potential reduce by 15.4 kB

Original 18.8 kB
After minification 14.2 kB
After compression 3.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. Nippon-olive.co.jp needs all CSS files to be minified and compressed as it can save up to 15.4 kB or 82% of the original size.

Requests Now

After Optimization

The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nippon Olive. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts 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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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 the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

JA
Encoding

UTF-8

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

nippon-olive.co.jp

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

自然派オリーブ化粧品の日本オリーブ公式通販

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

nippon-olive.co.jp

top.php

corporate.css

bgstretcher.css

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

nippon-olive.co.jp

top.php

corporate.css

bgstretcher.css

rollover.js

jquery-1.5.2.min.js

bgstretcher.js

common.js

102_l.jpg

90_l.jpg

2_l.jpg

30_l.jpg

logo.png

img_top01.png

bg_top01.png

ttl_top01.gif

arrow01.png

txtLink_top01.gif

ttl_top02.gif

txtLink_top02.gif

bt_top01.png

btn_top01.jpg

btn_top02.jpg

bg_newTopics.png

fb_banner.png

ttl_top03.png

bnr_top01.gif

bnr_top02.gif

copyright.gif

ftLink01.gif

ftLink02.gif

ftLink03.gif

ftLink04.gif

ftLink05.gif

ga.js

tag.js

blade_track_jp.js

bg_img01.jpg

bg_img02.jpg

bg_img03.jpg

__utm.gif

__utm.gif

tag