5 sec in total
919 ms
3.7 sec
382 ms
Click here to check amazing Solarbear content. Otherwise, check out these important facts you probably never knew about solarbear.jp
そらべあ基金は再生可能エネルギーの普及啓発と環境教育を行うNPO法人です
Visit solarbear.jpWe analyzed Solarbear.jp page load time and found that the first response time was 919 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
solarbear.jp performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value12.2 s
0/100
25%
Value13.0 s
2/100
10%
Value40 ms
100/100
30%
Value0.224
56/100
15%
Value11.6 s
18/100
10%
919 ms
733 ms
564 ms
567 ms
541 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 54% of them (58 requests) were addressed to the original Solarbear.jp, 19% (20 requests) were made to Static.xx.fbcdn.net and 8% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Solarbear.jp.
Page size can be reduced by 167.6 kB (15%)
1.1 MB
919.0 kB
In fact, the total size of Solarbear.jp main page is 1.1 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 916.4 kB which makes up the majority of the site volume.
Potential reduce by 12.5 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 12.5 kB or 74% of the original size.
Potential reduce by 56.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. Solarbear images are well optimized though.
Potential reduce by 60.9 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 60.9 kB or 57% of the original size.
Potential reduce by 38.2 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. Solarbear.jp needs all CSS files to be minified and compressed as it can save up to 38.2 kB or 83% of the original size.
Number of requests can be reduced by 46 (43%)
106
60
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Solarbear. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
solarbear.jp
919 ms
common.css
733 ms
style.css
564 ms
require.js
567 ms
jquery-1.4.4.min.js
541 ms
jquery.easing.1.3.js
370 ms
jquery.scrollTo-min.js
187 ms
script.js
362 ms
logo_header.gif
186 ms
bg_body.png
182 ms
bg_container.png
382 ms
bg_visual.png
381 ms
gnavi_01.gif
182 ms
gnavi_02.gif
342 ms
gnavi_03.gif
378 ms
gnavi_04.gif
379 ms
gnavi_05.gif
380 ms
gnavi_06.gif
659 ms
bg_news.gif
663 ms
border_news.gif
663 ms
border_event.gif
777 ms
DSC09439-thumb-350x232-534.jpg
1009 ms
DSC00422re.JPG
1169 ms
DSC09578.jpg
1182 ms
DSC09427.JPG
964 ms
DSC08833%20%282%29.JPG
1297 ms
CIMG4384.JPG
1109 ms
CIMG4106.JPG
1142 ms
bg_sns.gif
1195 ms
border_twitter.gif
1295 ms
bn_sien.png
1321 ms
bn_oentai.jpg
1353 ms
bn_supporter.jpg
1349 ms
bn_smile.jpg
1379 ms
bn_blog.jpg
1479 ms
bn_student.jpg
1476 ms
pagetop.gif
1501 ms
logo_footer.gif
1516 ms
copyright_shinzikatoh.gif
1536 ms
btn_search.gif
367 ms
visual.gif
876 ms
ttl_news.gif
370 ms
btn_more_news.gif
368 ms
ttl_event.gif
374 ms
btn_more_event.gif
402 ms
ttl_twitter.gif
654 ms
btn_twitter.gif
653 ms
ttl_facebook.gif
652 ms
btn_facebook.gif
768 ms
widgets.js
18 ms
border_facebook.gif
1539 ms
bg_bn_02.gif
1632 ms
bg_bn.gif
1639 ms
bg_footer.png
1655 ms
border_footer_s.gif
1660 ms
icon_footer.gif
1697 ms
ga.js
19 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
31 ms
__utm.gif
27 ms
syndication
83 ms
359968247455571968
209 ms
likebox.php
310 ms
arrow.gif
1575 ms
border_footer_l.jpg
1660 ms
pagetop_o.gif
1512 ms
proxy.jpg
67 ms
proxy.jpg
227 ms
proxy.jpg
218 ms
proxy.jpg
103 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
18 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
47 ms
kyEKgjk51ZE.css
58 ms
xgj7bXhJNEH.css
71 ms
kE_Z8j4XNUS.css
156 ms
q68gy-v_YMF.js
155 ms
FJmpeSpHpjS.js
176 ms
0wM5s1Khldu.js
155 ms
1bNoFZUdlYZ.js
175 ms
OloiM1PZafe.js
173 ms
LTv6ZK-5zxz.js
198 ms
1FCa-btixu2.js
191 ms
Oagsvfb4VWi.js
194 ms
pObvZSrFc_4.js
190 ms
HgJbVwzBr8E.js
189 ms
H3EKDTObx05.js
193 ms
OZFAYTv-ZUg.js
195 ms
_____________normal.jpg
258 ms
Mv4fgDci_normal.jpg
257 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
60 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
134 ms
398204_277677132306722_751486209_n.jpg
201 ms
381815_203673319707104_1833954891_n.jpg
194 ms
198991_188297771212983_5555234_n.jpg
183 ms
12108242_905728892837745_4845744584879936852_n.jpg
183 ms
10414839_1374227119545199_172985091637714038_n.jpg
182 ms
11066775_1563986800525121_1416642514280509915_n.jpg
184 ms
168613_149507078438855_7366259_n.jpg
183 ms
11429822_866751430063509_5712320699637335081_n.jpg
185 ms
1620978_10208250529757436_439812852965895608_n.jpg
294 ms
wL6VQj7Ab77.png
124 ms
s7jcwEQH7Sx.png
125 ms
proxy.jpg
156 ms
gxbPuQdXIZP.png
56 ms
proxy.jpg
89 ms
I6-MnjEovm5.js
3 ms
pQrUxxo5oQp.js
6 ms
jot.html
3 ms
solarbear.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.
solarbear.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
Page has valid source maps
solarbear.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
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 Solarbear.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 Solarbear.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.
solarbear.jp
Open Graph data is detected on the main page of Solarbear. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: