Access richmore.jp. リッチモアコンセプト

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.778

5/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

richmore.jp

523 ms

richmore

643 ms

style.css

341 ms

css

61 ms

richmore_index.css

343 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Richmore.jp, 83% (67 requests) were made to Hamanaka.jp and 4% (3 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Hamanaka.jp.

Content Size

1.5 MB

After Optimization

1.4 MB

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

HTML Optimization

-76%

Potential reduce by 19.7 kB

Original 25.8 kB
After minification 23.4 kB
After compression 6.2 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 19.7 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 16.5 kB

Original 1.2 MB
After minification 1.2 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. Richmore images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 32.0 kB

Original 225.5 kB
After minification 225.2 kB
After compression 193.5 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 32.0 kB or 14% of the original size.

CSS Optimization

-23%

Potential reduce by 7.9 kB

Original 33.8 kB
After minification 33.8 kB
After compression 25.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. Richmore.jp needs all CSS files to be minified and compressed as it can save up to 7.9 kB or 23% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

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

High

Page has valid source maps

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

richmore.jp

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

richmore.jp

richmore

style.css

css

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

richmore.jp

richmore

style.css

css

richmore_index.css

jquery.min.js

jquery.cookie.js

swView.js

imgchange.js

mobilyslider.js

smartrollover.js

rollover.js

scroll.js

matchMedia.js

modal.js

accordion.js

anime.min.js

jQueryAutoHeight.js

jQueryAutoHeight_setting.js

all.css

slick-theme.css

slick.css

demo.css

style-adsila.css

base.css

slick.min.js

richmore_index.js

seasontheme.js

lightbox.css

lightbox.min.js

se-styles.css

imagesloaded.pkgd.min.js

three.min.js

TweenMax.min.js

hover.js

slick.min.js

analytics.js

page_bg.jpg

close.png

loading.gif

prev.png

next.png

head_bg.jpg

リッチモアコンセプト | ハマナカ手芸糸