3.9 sec in total
665 ms
3 sec
312 ms
Click here to check amazing Roifleur content for Japan. Otherwise, check out these important facts you probably never knew about roifleur.com
Visit roifleur.comWe analyzed Roifleur.com page load time and found that the first response time was 665 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
roifleur.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value6.0 s
13/100
25%
Value8.7 s
17/100
10%
Value680 ms
43/100
30%
Value0.097
90/100
15%
Value8.4 s
39/100
10%
665 ms
158 ms
321 ms
321 ms
326 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 72% of them (51 requests) were addressed to the original Roifleur.com, 7% (5 requests) were made to Image.rakuten.co.jp and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (969 ms) belongs to the original domain Roifleur.com.
Page size can be reduced by 441.2 kB (58%)
758.3 kB
317.1 kB
In fact, the total size of Roifleur.com main page is 758.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 467.6 kB which makes up the majority of the site volume.
Potential reduce by 23.6 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 6.5 kB, which is 20% 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 23.6 kB or 73% of the original size.
Potential reduce by 4.3 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. Roifleur images are well optimized though.
Potential reduce by 320.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 320.6 kB or 69% of the original size.
Potential reduce by 92.7 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. Roifleur.com needs all CSS files to be minified and compressed as it can save up to 92.7 kB or 84% of the original size.
Number of requests can be reduced by 47 (71%)
66
19
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Roifleur. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
roifleur.com
665 ms
common.css
158 ms
jquery.lightbox-0.5.css
321 ms
jquery-ui-1.8.22.custom.css
321 ms
jquery.bxslider.css
326 ms
main.js
335 ms
clone.js
335 ms
css.js
338 ms
navi.js
476 ms
win_op.js
477 ms
site.js
480 ms
jquery.js
676 ms
jquery.lightbox-0.5.min.js
498 ms
jquery.mouse.wheel.min.js
502 ms
tilescroller.js
630 ms
bestproducts.js.php
631 ms
jquery-ui-1.8.22.custom.min.js
969 ms
jquery.min.js
44 ms
jquery.bxslider.min.js
663 ms
import.css
514 ms
block.css
161 ms
btn.css
169 ms
footer.css
159 ms
frame.css
168 ms
guide.css
171 ms
header.css
315 ms
index.css
314 ms
main.css
332 ms
mypage.css
334 ms
news.css
334 ms
products.css
456 ms
shopping.css
469 ms
sub_function.css
471 ms
recommend.css
496 ms
ranking.css
496 ms
window.css
496 ms
media-queries.css
614 ms
design_controller.js.php
164 ms
gtm.js
71 ms
rogo.jpg
167 ms
0.jpg
823 ms
icon_login.png
158 ms
icon_id.png
168 ms
icon_pass.png
158 ms
icon_mini_kotira.png
299 ms
icon_category.png
318 ms
icon_arrow_b.png
318 ms
bg_arrow.gif
320 ms
icon_recomend.png
318 ms
resize_image.php
395 ms
resize_image.php
472 ms
adv.js
8 ms
dg_gateway.js
180 ms
adv_inner.js
5 ms
visa.gif
410 ms
atobarai_newbanner126x61.jpg
418 ms
mastercard.gif
257 ms
jcb.gif
416 ms
diners.gif
413 ms
amex.gif
403 ms
footer_title840.gif
429 ms
footer_point.gif
453 ms
e.js
666 ms
389 ms
ga.js
43 ms
analytics.js
106 ms
adv.aspx
567 ms
__utm.gif
33 ms
collect
16 ms
dgcore.js
3 ms
adSiteVisit.js
5 ms
roifleur.com 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
Image elements do not have [alt] attributes
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.
roifleur.com 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
Page has valid source maps
roifleur.com 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 doesn't use legible font sizes
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Roifleur.com 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), while the claimed language is Japanese. Our system also found out that Roifleur.com 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.
roifleur.com
Open Graph description is not detected on the main page of Roifleur. 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: