5 sec in total
565 ms
3.2 sec
1.2 sec
Visit rollcake.co now to see the best up-to-date Rollcake content for Japan and also check out these interesting facts you probably never knew about rollcake.co
楽しみを一緒につくるメンバー募集しています。ぜひお気軽にお問い合わせください!
Visit rollcake.coWe analyzed Rollcake.co page load time and found that the first response time was 565 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
rollcake.co performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value6.7 s
7/100
25%
Value5.7 s
51/100
10%
Value2,580 ms
4/100
30%
Value0.033
100/100
15%
Value6.9 s
54/100
10%
565 ms
870 ms
351 ms
361 ms
371 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 22% of them (15 requests) were addressed to the original Rollcake.co, 26% (18 requests) were made to Google.com and 19% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Rollcake.co.
Page size can be reduced by 606.8 kB (38%)
1.6 MB
996.2 kB
In fact, the total size of Rollcake.co main page is 1.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. 55% of websites need less resources to load. Javascripts take 828.6 kB which makes up the majority of the site volume.
Potential reduce by 15.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 15.2 kB or 68% of the original size.
Potential reduce by 16.0 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. Rollcake images are well optimized though.
Potential reduce by 567.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 567.5 kB or 68% of the original size.
Potential reduce by 8.0 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. Rollcake.co needs all CSS files to be minified and compressed as it can save up to 8.0 kB or 80% of the original size.
Number of requests can be reduced by 18 (29%)
63
45
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rollcake. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.
rollcake.co
565 ms
jquery.js
870 ms
stickUp.min.js
351 ms
main.js
361 ms
style.css
371 ms
analytics.js
62 ms
placeholder.png
409 ms
member_1.jpg
576 ms
member_2.jpg
575 ms
member_3.jpg
1385 ms
all.js
60 ms
embed
222 ms
logo.png
369 ms
service_letter.jpg
1516 ms
line_list.png
758 ms
icon_twitter.png
806 ms
icon_facebook.png
903 ms
icon_instagram.png
903 ms
collect
40 ms
74 ms
js
103 ms
init_embed.js
75 ms
xd_arbiter.php
38 ms
xd_arbiter.php
67 ms
common.js
141 ms
map.js
180 ms
google4.png
90 ms
overlay.js
88 ms
util.js
161 ms
onion.js
160 ms
search_impl.js
161 ms
stats.js
52 ms
openhand_8_8.cur
39 ms
ViewportInfoService.GetViewportInfo
87 ms
ViewportInfoService.GetViewportInfo
79 ms
transparent.png
74 ms
kh
207 ms
controls.js
122 ms
ViewportInfoService.GetViewportInfo
178 ms
vt
171 ms
vt
322 ms
vt
317 ms
vt
240 ms
vt
229 ms
vt
212 ms
vt
240 ms
vt
322 ms
vt
324 ms
vt
326 ms
vt
322 ms
vt
349 ms
vt
326 ms
vt
357 ms
vt
395 ms
vt
367 ms
vt
395 ms
css
182 ms
entity11.png
102 ms
mapcnt6.png
50 ms
tmapctrl.png
45 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
38 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
63 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
84 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
84 ms
AuthenticationService.Authenticate
19 ms
ping
49 ms
like.php
66 ms
LVx-xkvaJ0b.png
34 ms
rollcake.co accessibility score
rollcake.co 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
rollcake.co SEO score
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 Rollcake.co 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 Rollcake.co 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.
rollcake.co
Open Graph data is detected on the main page of Rollcake. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: