5.2 sec in total
720 ms
4.3 sec
233 ms
Welcome to richmore.jp homepage info - get ready to check Richmore best content for Japan right away, or after learning these important things about richmore.jp
楽しい手芸のハマナカの商品情報サイトです。 人気の手あみ糸をはじめ、小ものやあみぐるみの手芸キット、フェルト羊毛、エコクラフトなど幅広く取り揃えております。 お好みのアイテムを見つけて、手芸の時間を楽しみましょう!
Visit richmore.jpWe analyzed Richmore.jp page load time and found that the first response time was 720 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
richmore.jp performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value7.6 s
3/100
25%
Value14.2 s
1/100
10%
Value60 ms
100/100
30%
Value0.672
8/100
15%
Value13.7 s
11/100
10%
720 ms
1389 ms
875 ms
1583 ms
350 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 93% of them (37 requests) were addressed to the original Richmore.jp, 5% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Richmore.jp.
Page size can be reduced by 222.8 kB (15%)
1.5 MB
1.3 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. 30% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 7.5 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 1.3 kB, which is 13% 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 7.5 kB or 75% of the original size.
Potential reduce by 24.2 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. Richmore images are well optimized though.
Potential reduce by 124.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 124.0 kB or 66% of the original size.
Potential reduce by 67.1 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 67.1 kB or 89% of the original size.
Number of requests can be reduced by 16 (41%)
39
23
The browser has sent 39 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 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
richmore.jp
720 ms
page.css
1389 ms
top.css
875 ms
jquery.js
1583 ms
FeedEk.js
350 ms
jquery.cycle.all.js
1405 ms
jquery.maximage.js
1268 ms
google.js
896 ms
footerFixed.js
1049 ms
base.css
174 ms
common.css
187 ms
ga.js
5 ms
photo_top01.jpg
694 ms
btn_index_info02.png
179 ms
photo_top02.jpg
1120 ms
photo_top03.jpg
712 ms
photo_top04.jpg
2050 ms
bg_header_wall_01.gif
355 ms
logo01.png
176 ms
btn_head_contact_01.png
351 ms
bg_gnavi_wall_01.gif
534 ms
gnavi01.png
535 ms
gnavi02.png
710 ms
gnavi03.png
711 ms
gnavi04.png
861 ms
gnavi07.png
884 ms
gnavi08.png
885 ms
gnavi09.png
887 ms
gnavi05.png
1033 ms
txt_top01.png
1057 ms
bg_top_newsbox01.png
1061 ms
h3_top01.png
1062 ms
bg_top_arrow01.png
1205 ms
line03.png
1232 ms
load
400 ms
bg_footer_wall_01.gif
1192 ms
line02.gif
1193 ms
line01_02.gif
1256 ms
loader.gif
342 ms
__utm.gif
22 ms
richmore.jp accessibility score
Names and labels
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.
Impact
Issue
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
richmore.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
richmore.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
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/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
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 neither this language nor any other was claimed in <html> or <meta> tags. 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.
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: