Access momilux.jp. 【公式】かんたん・やさしい・きもちいい MOMiLUX

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value15.6 s

0/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value320 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.36

30/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

momilux.jp

901 ms

import.min.css

522 ms

slick.css

392 ms

slick-theme.css

406 ms

top.min.css

404 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 95% of them (59 requests) were addressed to the original Momilux.jp, 3% (2 requests) were made to Googletagmanager.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Momilux.jp.

Content Size

5.6 MB

After Optimization

5.4 MB

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

HTML Optimization

-82%

Potential reduce by 30.3 kB

Original 36.9 kB
After minification 33.7 kB
After compression 6.6 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 30.3 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 81.6 kB

Original 5.4 MB
After minification 5.3 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. MOMiLUX images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 54.8 kB

Original 108.6 kB
After minification 108.4 kB
After compression 53.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 54.8 kB or 50% of the original size.

CSS Optimization

-80%

Potential reduce by 29.9 kB

Original 37.5 kB
After minification 36.2 kB
After compression 7.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. Momilux.jp needs all CSS files to be minified and compressed as it can save up to 29.9 kB or 80% of the original size.

Requests Now

After Optimization

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MOMiLUX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 4 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-*] 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 toggle 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 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

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

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

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

JA
Encoding

UTF-8

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

momilux.jp

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

【公式】かんたん・やさしい・きもちいい MOMiLUX

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

momilux.jp

import.min.css

slick.css

slick-theme.css

top.min.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

momilux.jp

import.min.css

slick.css

slick-theme.css

top.min.css

jquery.min.js

common.js

slick.min.js

gtm.js

head_logo.png

doshisha_logo.png

sp_menu.png

sp_menu_close.png

gnav_top_off.png

gnav_products_off.png

gnav_about_non.png

gnav_shop_off.png

mv_pc_dmg-2301.png

mv_pc_dtb-2201.png

pc_dmg-2201.png

pc_ods-2201.jpg

pc_drb-2101.png

pc_dmg-2101.jpg

mv_dkm_2001_pc.jpg

mv_dms_2001_pc.jpg

mv_sp_dmg-2301.png

mv_sp_dtb-2201.png

sp_dmg-2201.png

sp_ods-2201.jpg

sp_drb-2101.png

sp_dmg-2101.jpg

mv_dkm_2001_sp.jpg

mv_dms_2001_sp.jpg

slide_next1.png

slide_prev1.png

top_logo_pc.png

banner_dmg-2301.png

banner_dtb-2201.png

banner_dmg-2201.png

banner_ods-2201.jpg

banner_drb-2101.png

banner_dmg-2101sub.jpg

gtm.js