6.8 sec in total
522 ms
5.4 sec
865 ms
Click here to check amazing R STORE content for Japan. Otherwise, check out these important facts you probably never knew about r-store.jp
R-STOREでは、デザイナーズ・リノベーション・広いバルコニー・DIY可能など、個性的でこだわりのある 賃貸・売買・事業用物件を紹介しています。
Visit r-store.jpWe analyzed R-store.jp page load time and found that the first response time was 522 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
r-store.jp performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value23.7 s
0/100
25%
Value11.5 s
5/100
10%
Value1,950 ms
8/100
30%
Value0.004
100/100
15%
Value19.6 s
2/100
10%
522 ms
1230 ms
190 ms
192 ms
675 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 63% of them (49 requests) were addressed to the original R-store.jp, 27% (21 requests) were made to Cf.r-store.jp and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain R-store.jp.
Page size can be reduced by 2.3 MB (34%)
6.8 MB
4.5 MB
In fact, the total size of R-store.jp main page is 6.8 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. 70% of websites need less resources to load. Images take 4.4 MB which makes up the majority of the site volume.
Potential reduce by 2.1 MB
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 357.7 kB, which is 16% 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 2.1 MB or 95% of the original size.
Potential reduce by 190.8 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. R STORE images are well optimized though.
Potential reduce by 50.4 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 50.4 kB or 36% of the original size.
Potential reduce by 5.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. R-store.jp needs all CSS files to be minified and compressed as it can save up to 5.5 kB or 23% of the original size.
Number of requests can be reduced by 9 (12%)
74
65
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of R STORE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
r-store.jp
522 ms
www.r-store.jp
1230 ms
MyFontsWebfontsKit.css
190 ms
swiper.min.css
192 ms
style.css
675 ms
js
61 ms
js
115 ms
lbformnew.js
566 ms
jquery.min.js
6 ms
jquery.easing.1.3.js
24 ms
swiper.min.js
9 ms
main.js
8 ms
jquery.cookie.js
5 ms
analytics.js
449 ms
slide1.jpg
1435 ms
logo.svg
1183 ms
sub-search-condition.png
1185 ms
sub-search-map.png
1199 ms
sub-search-new.png
1199 ms
sub-publish-owner.png
1368 ms
sub-publish-agents.png
1364 ms
sub-howto.png
1365 ms
sub-blogs.png
1366 ms
sub-townnavi.png
1364 ms
sub-column.png
1367 ms
sub-recruit.png
1527 ms
icon-select.png
1530 ms
235685_01_ip_normal.jpg
1861 ms
238079_01_ip_normal.jpg
2025 ms
170947_01_ip_normal.jpg
1863 ms
238076_01_ip_normal.jpg
1865 ms
35747_01_ip_normal.jpg
2018 ms
23188_01_ip_normal.jpg
2189 ms
238069_01_ip_normal.jpg
2190 ms
228175_01_ip_normal.jpg
2195 ms
224191_01_ip_normal.jpg
2364 ms
34368_01_ip_normal.jpg
2346 ms
142099_01_ip_normal.jpg
2191 ms
51727_01_ip_normal.jpg
2518 ms
148366_01_ip_normal.jpg
2520 ms
224515_01_ip_normal.jpg
2358 ms
231522_01_ip_normal.jpg
2693 ms
233922_01_ip_normal.jpg
2673 ms
229003_01_ip_normal.jpg
2523 ms
231610_01_ip_normal.jpg
2697 ms
title-blogs.png
2683 ms
6edd7d89565d6a66f06f2f2438deb421.png
2685 ms
2228a357b720f430a70b2f0e1c7674f9.png
2690 ms
f17ae7a29eaffbddb373ab3ac05a4ee4.png
2837 ms
a384f69828f86bbb33696697b8c2121d.png
2848 ms
slide14.jpg
1194 ms
slide15.jpg
207 ms
slide4.jpg
207 ms
slide2.jpg
1197 ms
slide3.jpg
1198 ms
howto-flow01.gif
1193 ms
merit1.gif
1193 ms
merit2.gif
1373 ms
merit3.gif
1371 ms
merit4.gif
1372 ms
app-image.png
1406 ms
title-townnavi.png
2708 ms
tracker.bundle.js
1068 ms
1AFA32_1_0.woff
1197 ms
1AFA32_0_0.woff
1168 ms
collect
932 ms
1899 ms
1910 ms
1d15921e9e144fd35e52736ae4085564.jpg
1669 ms
41490a36fc3ada25cbaf5f82fbafa228.jpg
1807 ms
collect
13 ms
ga-audiences
1234 ms
aebcea5c1b34aa4316912d62c0082c5f.jpg
1655 ms
a297a2f6c689a6f98c07c440020d67d0.jpg
1654 ms
app-bg.jpg
1669 ms
app-icon.png
1804 ms
app-store.png
1817 ms
google-play-badge.png
1817 ms
r-store.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
r-store.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
r-store.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
![]()
N/A
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise R-store.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that R-store.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.
r-store.jp
Open Graph data is detected on the main page of R STORE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: