5.1 sec in total
595 ms
4.3 sec
231 ms
Click here to check amazing Reric content for Japan. Otherwise, check out these important facts you probably never knew about reric.jp
reric(レリック)の公式オンラインショップ。reric(レリック)はスタイリングと機能が両立するサイクルウェア、ランニングウェア、ゴルフウェアの日本ブランド。素材開発から人間工学に基づくパターン制作・縫製が生み出すプロダクツでサイクリストやランナーをサポートします。
Visit reric.jpWe analyzed Reric.jp page load time and found that the first response time was 595 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.
reric.jp performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value16.2 s
0/100
25%
Value13.3 s
2/100
10%
Value440 ms
63/100
30%
Value0.322
36/100
15%
Value11.7 s
17/100
10%
595 ms
702 ms
87 ms
64 ms
29 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 75% of them (24 requests) were addressed to the original Reric.jp, 6% (2 requests) were made to Googletagmanager.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Reric.jp.
Page size can be reduced by 48.5 kB (2%)
2.4 MB
2.3 MB
In fact, the total size of Reric.jp main page is 2.4 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. 20% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 15.3 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 3.8 kB, which is 18% 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 15.3 kB or 73% of the original size.
Potential reduce by 29.7 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. Reric images are well optimized though.
Potential reduce by 1.1 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. This website has mostly compressed JavaScripts.
Potential reduce by 2.5 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. Reric.jp needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 23% of the original size.
Number of requests can be reduced by 11 (38%)
29
18
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reric. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
reric.jp
595 ms
reric.jp
702 ms
gtm.js
87 ms
analytics.js
64 ms
fbevents.js
29 ms
css
86 ms
layout.css
516 ms
about.css
515 ms
slick.css
522 ms
jquery-2.1.1.min.js
709 ms
slick.min.js
538 ms
js
108 ms
top.js
553 ms
jquery.cookie.js
1051 ms
app_new.js
1064 ms
collect
16 ms
logo_reric.png
370 ms
btn_menu_sp.png
510 ms
logo_reric_small.png
508 ms
mainCatch_black.png
851 ms
top_mainVisual_pc.jpg
1884 ms
top_image_prologue.jpg
1700 ms
top_image_theory.jpg
1704 ms
about_btn_technology_pc.jpg
1384 ms
about_btn_technology_sp.jpg
1262 ms
icon_facebook.png
1384 ms
icon_instagram.png
1771 ms
icon_twitter.png
1912 ms
icon_line.png
1912 ms
btn_pageTop.png
2188 ms
font
19 ms
test_api
818 ms
reric.jp accessibility score
reric.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
reric.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reric.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 Reric.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.
reric.jp
Open Graph description is not detected on the main page of Reric. 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: