7.7 sec in total
1.3 sec
4.7 sec
1.7 sec
Welcome to randsel.jp homepage info - get ready to check Randsel best content for Japan right away, or after learning these important things about randsel.jp
毎日が、ちょっと特別になる。職人が丁寧に作り上げたランドセル。2026年ご入学用ランドセルをお探しなら6年間無料保証付きの生田ランドセル。創業70年の大阪老舗「生田ランドセル」は完全自社工房生産、すべて職人の思いが込められた本革手作りランドセルです。
Visit randsel.jpWe analyzed Randsel.jp page load time and found that the first response time was 1.3 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
randsel.jp performance score
name
value
score
weighting
Value4.1 s
20/100
10%
Value8.9 s
1/100
25%
Value16.4 s
0/100
10%
Value2,390 ms
5/100
30%
Value0
100/100
15%
Value19.3 s
2/100
10%
1266 ms
49 ms
64 ms
200 ms
602 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 78% of them (49 requests) were addressed to the original Randsel.jp, 8% (5 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Wf.typesquare.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Randsel.jp.
Page size can be reduced by 132.3 kB (5%)
2.6 MB
2.5 MB
In fact, the total size of Randsel.jp main page is 2.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. 65% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 48.9 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 48.9 kB or 76% of the original size.
Potential reduce by 916 B
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. Randsel images are well optimized though.
Potential reduce by 48.6 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 48.6 kB or 11% of the original size.
Potential reduce by 33.8 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. Randsel.jp needs all CSS files to be minified and compressed as it can save up to 33.8 kB or 34% of the original size.
Number of requests can be reduced by 17 (31%)
54
37
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Randsel. 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 from 9 to 1 for CSS and as a result speed up the page load time.
www.randsel.jp
1266 ms
css2
49 ms
css2
64 ms
base.css,qv=20240207.pagespeed.ce.cij-WBfc8O.css
200 ms
bundle.css,qv=20240207.pagespeed.ce.mdSPAtiu2C.css
602 ms
extra.css,qv=20240207.pagespeed.ce.CaJjnS0Ilf.css
514 ms
wp_bundle.css,qv=20240207.pagespeed.ce.X_wgNH69cb.css
521 ms
typesquare.js
405 ms
common.js,qv=20240207.pagespeed.ce.irqVmWka9H.js
706 ms
sbi-styles.min.css,qver=6.4.2.pagespeed.ce.z50i8-4IS1.css
588 ms
style.min.css,qver=6.4.5.pagespeed.ce.AjTQp2ha76.css
792 ms
callout.css
683 ms
home.js
1230 ms
header.js,qv=20240207.pagespeed.ce.5WSLICxIQn.js
1194 ms
footer.js,qv=20240207.pagespeed.ce.2UoqfkJyku.js
1052 ms
jquery-3.7.1.min.js
29 ms
js
83 ms
acf-googlemap.js,qver=6.4.5.pagespeed.ce.bhjneD3Cgs.js
963 ms
sbi-scripts.min.js
966 ms
gtm.js
59 ms
1.JiBnMqyl6S.gif
254 ms
sbi-sprite.png
255 ms
xintro_01.jpg.pagespeed.ic.ylqeCw1pFI.jpg
459 ms
footer_bg-pc.jpg
826 ms
product_bg_02-pc.jpg
246 ms
product_bg_03-pc.jpg
585 ms
header_icon_ig.svg
628 ms
header_icon_fb.svg
443 ms
header_icon_tw.svg
603 ms
bg_default-pc.jpg
631 ms
icon_shop.svg
642 ms
icon_randsel.svg
753 ms
breadcrumb_bg-pc.jpg
778 ms
breadcrumb_icon_home.svg
824 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf
96 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf
246 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf
252 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAkJxhTg.ttf
148 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwARZthTg.ttf
154 ms
about_03.jpg.pagespeed.ce.i4U5h_T4Hc.jpg
201 ms
ts
688 ms
ts
527 ms
ab.woff
29 ms
xabout_01.jpg.pagespeed.ic.B0zL5ITqFm.jpg
203 ms
interest_02.jpg
344 ms
about_04.jpg
180 ms
452506899_18308563897082966_9067747737166476040_nfull.jpg
203 ms
451429760_18307701367082966_2857134842678952725_nfull.jpg
353 ms
interest_04.jpg
355 ms
451623814_1171005880770886_7331206752474564042_nfull.jpg
394 ms
452223013_18308305471082966_8610277409520658670_nfull.jpg
397 ms
interest_03.jpg
401 ms
about_02.jpg.pagespeed.ce.M4SendWrBV.jpg
518 ms
interest_01.jpg
534 ms
451025803_18307331938082966_4240828287853554419_nfull.jpg
535 ms
randsel_01.jpg
788 ms
product_bg_01-pc.jpg
787 ms
451949047_18308303956082966_7356172500221561751_nfull.jpg
599 ms
interest_05.jpg
694 ms
xintro_02.jpg.pagespeed.ic.cQHRxeA7gb.jpg
733 ms
xintro_03.jpg.pagespeed.ic.Cclo2SP-hR.jpg
733 ms
randsel_04.jpg
800 ms
randsel_02.jpg
863 ms
randsel.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
randsel.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
randsel.jp SEO score
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
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Randsel.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 Randsel.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.
randsel.jp
Open Graph description is not detected on the main page of Randsel. 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: