13.2 sec in total
508 ms
11.8 sec
867 ms
Welcome to recall-plus.jp homepage info - get ready to check Recall Plus best content for Japan right away, or after learning these important things about recall-plus.jp
リコール/回収/不具合を知り暮らしに安全安心をプラス!自主回収情報11311件!会員には無料でリコール情報配信。ケータイ、スマートフォンも「リコール」検索
Visit recall-plus.jpWe analyzed Recall-plus.jp page load time and found that the first response time was 508 ms and then it took 12.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
recall-plus.jp performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value11.8 s
0/100
25%
Value12.1 s
3/100
10%
Value510 ms
57/100
30%
Value0.001
100/100
15%
Value11.7 s
18/100
10%
508 ms
3285 ms
397 ms
1812 ms
1199 ms
Our browser made a total of 216 requests to load all elements on the main page. We found that 59% of them (127 requests) were addressed to the original Recall-plus.jp, 6% (12 requests) were made to Chart.apis.google.com and 5% (10 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Recall-plus.jp.
Page size can be reduced by 784.1 kB (62%)
1.3 MB
479.8 kB
In fact, the total size of Recall-plus.jp main page is 1.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 771.5 kB which makes up the majority of the site volume.
Potential reduce by 142.1 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 33.8 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 142.1 kB or 83% of the original size.
Potential reduce by 88.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. Obviously, Recall Plus needs image optimization as it can save up to 88.3 kB or 40% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 473.2 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 473.2 kB or 61% of the original size.
Potential reduce by 80.4 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. Recall-plus.jp needs all CSS files to be minified and compressed as it can save up to 80.4 kB or 81% of the original size.
Number of requests can be reduced by 124 (60%)
207
83
The browser has sent 207 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Recall Plus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
recall-plus.jp
508 ms
www.recall-plus.jp
3285 ms
common.css
397 ms
prototype.js
1812 ms
effects.js
1199 ms
dragdrop.js
1009 ms
controls.js
1061 ms
application.js
592 ms
leftbar.js
791 ms
rightbar.js
989 ms
jquery.js
1979 ms
highslide.js
1614 ms
hs_conf.js
1263 ms
AC_RunActiveContent.js
1397 ms
jquery.innerfade.js
1434 ms
jq-lib.js
1465 ms
jquery.cookie.js
1589 ms
wz_tooltip.js
1452 ms
tip_balloon.js
1476 ms
thickbox.js
1604 ms
thickbox.css
1620 ms
element.js
48 ms
reset.css
1467 ms
layout.css
1696 ms
print.css
1610 ms
dwalk.css
1618 ms
adsbygoogle.js
7 ms
646 ms
reward-lang.js
1203 ms
sortinfo.js
1039 ms
api
17 ms
gsearch.css
28 ms
google-news.js
1074 ms
index.js
337 ms
845 ms
analytics.js
93 ms
btnXSLogin.gif
1001 ms
chart
86 ms
small-logo.png
80 ms
chart
186 ms
chart
187 ms
chart
235 ms
chart
187 ms
chart
186 ms
chart
187 ms
chart
188 ms
chart
234 ms
chart
232 ms
chart
232 ms
chart
228 ms
header_data.gif
249 ms
share.jpg
246 ms
header_regist.gif
245 ms
header_login.gif
245 ms
logo.gif
252 ms
header_search01.gif
251 ms
header_search02.gif
565 ms
bestcard_top.gif
563 ms
banner_jprs.gif
4253 ms
recall_pub.gif
542 ms
maximum.png
564 ms
minimum.png
541 ms
rss.gif
869 ms
camera.png
868 ms
pet_banner_0701.gif
863 ms
maximum.png
862 ms
minimum.png
863 ms
bestcard_new_card.gif
1123 ms
heater.gif
1122 ms
battery.gif
1143 ms
allergie.png
1597 ms
fcp-200_50white.gif
1142 ms
ps_award.gif
1593 ms
addgg.gif
1589 ms
open_search.jpg
1649 ms
exitemylink105x20-10.gif
1589 ms
add_yahoo.gif
1911 ms
add_hatena.gif
1916 ms
add_nifty.gif
1916 ms
add_iza.gif
1886 ms
add_buzzurl.gif
1900 ms
qr.png
2278 ms
clipboard_plus.png
2303 ms
noritz13207.gif
2318 ms
addtomy1.gif
878 ms
inf_type_18.gif
2289 ms
noritz2.gif
2288 ms
translateelement.css
181 ms
main.js
364 ms
collect
93 ms
daikin_ani_7d.gif
4017 ms
banner01.gif
4207 ms
inf_type_13.gif
2316 ms
to_en.gif
2306 ms
to_jp.gif
2305 ms
17409_1_s.gif
2446 ms
widgets.js
177 ms
plusone.js
292 ms
element_main.js
110 ms
danger.gif
2156 ms
inf_type_41.gif
2135 ms
17575_1_s.gif
2767 ms
17573_1_s.gif
2768 ms
qr.png
2767 ms
ca-pub-6186399580079325.js
393 ms
zrt_lookup.html
1065 ms
show_ads_impl.js
555 ms
cb=gapi.loaded_0
462 ms
cb=gapi.loaded_1
960 ms
fastbutton
957 ms
clipboard_plus.png
2871 ms
plus_comment_16.png
2871 ms
inf_type_43.gif
2870 ms
camera.png
3355 ms
28920_1_s.jpg
3354 ms
28934_1_s.jpg
3312 ms
28205_1_s.gif
3295 ms
26605_2_s.jpg
3293 ms
ads
489 ms
inf_type_10.gif
2938 ms
osd.js
175 ms
cb=gapi.loaded_0
317 ms
cb=gapi.loaded_1
296 ms
28181_1_s.gif
2863 ms
inf_type_44.gif
3122 ms
27356_1_s.jpg
3119 ms
29094_1_s.jpg
3065 ms
inf_type_20.gif
3029 ms
ads
700 ms
inf_type_12.gif
2803 ms
pm25_title.gif
2798 ms
inf_category_105.gif
3198 ms
inf_category_1.gif
3197 ms
1748708676781993521
1003 ms
abg.js
757 ms
m_js_controller.js
755 ms
googlelogo_color_112x36dp.png
1448 ms
rone.gif
3151 ms
postmessageRelay
1130 ms
chintaistyle.gif
2802 ms
p_mark.gif
2787 ms
qr2.gif
2783 ms
gooddesign.gif
2995 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
1791 ms
stemb.gif
2894 ms
suggestion_autolayout_V2_10.css
805 ms
suggestion_autolayout_V2_10.js
791 ms
layout_engine.js
811 ms
stemt.gif
2784 ms
l.gif
2782 ms
ads
696 ms
lb.gif
2674 ms
b.gif
2639 ms
rb.gif
2896 ms
r.gif
2885 ms
x_button_blue2.png
665 ms
ads
855 ms
s
474 ms
2530
1463 ms
api.js
913 ms
core:rpc:shindig.random:shindig.sha1.js
1401 ms
2536007149-postmessagerelay.js
1243 ms
rt.gif
2279 ms
t.gif
2279 ms
lt.gif
2278 ms
aclk
1338 ms
pixel
744 ms
adj
1338 ms
beacon
1267 ms
background.gif
1871 ms
close.gif
2024 ms
container_bg_ffcc99.jpg
2007 ms
5405968357433652555
390 ms
hnav_bg.jpg
1512 ms
sub_ttlbg.gif
1510 ms
sub-icon.gif
1502 ms
AUrdvhejKSJD2XN0WEoLkNJn8VW-ISfFFTHwdQR0Ws4.js
227 ms
ttlbg_attention.gif
1370 ms
pixel
562 ms
pixel
543 ms
gradient.png
1476 ms
ttlbg_lookfor.gif
1687 ms
comp.gif
1483 ms
ttlbg_reward.gif
1689 ms
reward_amount.gif
1475 ms
ttlbg_news.gif
1655 ms
default+en.I.js
206 ms
f001648d69a9c188d78a231cd179ca8f_6.html
529 ms
icon_clock.gif
1396 ms
ttlbg.gif
1410 ms
uh.js
830 ms
button.b059c0eb61ea902a882e5c5b3c66a17a.js
253 ms
hnav_bgr.jpg
1136 ms
loading.gif
1309 ms
MHI_RR_1045_DP_Mobile_320x50.jpg
355 ms
lidar.js
144 ms
sbhK2lTE.js
120 ms
translate_24dp.png
153 ms
l
243 ms
cleardot.gif
199 ms
cTrvNaRi.html
146 ms
st.v2.js
382 ms
te_ctrl3.gif
62 ms
tweet_button.baa54ded21a982344c4ced326592f3de.ja.html
46 ms
tweet_button.baa54ded21a982344c4ced326592f3de.en.html
35 ms
activeview
99 ms
sd
243 ms
e2f34c617fdf27280259dd4bb1e1a3cc.jpg
97 ms
cvo.gif
85 ms
gr
37 ms
pixel_details.html
39 ms
jot.html
2 ms
GnewsSearch
374 ms
rounded-orange.png
619 ms
zoomout.cur
202 ms
ui
12 ms
recall-plus.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
<frame> or <iframe> elements do not have a title
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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.
recall-plus.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
Page has valid source maps
recall-plus.jp 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 Recall-plus.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 Recall-plus.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.
recall-plus.jp
Open Graph description is not detected on the main page of Recall Plus. 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: