6.8 sec in total
1.6 sec
4.7 sec
437 ms
Welcome to future-r.co.jp homepage info - get ready to check Future R best content right away, or after learning these important things about future-r.co.jp
千葉県・東京都を中心に太陽光発電をお考えの方はフューチャーリレーションにお任せください! 家庭向け・アパート向け・法人向けを取り扱っております。 地域密着で低価格高品質。ご提案から受注後のアフターフォローまで全力投球! 多数の取り扱いメーカーの中からピッタリなメーカーをベストチョイス! フューチャーリレーションの魅力はなんといっても"人間力"です。 メリットだけじゃなくデメリットまできちんとご説明...
Visit future-r.co.jpWe analyzed Future-r.co.jp page load time and found that the first response time was 1.6 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
future-r.co.jp performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value6.0 s
13/100
25%
Value10.1 s
9/100
10%
Value70 ms
99/100
30%
Value0.214
58/100
15%
Value7.6 s
46/100
10%
1632 ms
192 ms
357 ms
382 ms
378 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 89% of them (51 requests) were addressed to the original Future-r.co.jp, 4% (2 requests) were made to Ssl.google-analytics.com and 4% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Future-r.co.jp.
Page size can be reduced by 587.9 kB (16%)
3.7 MB
3.1 MB
In fact, the total size of Future-r.co.jp main page is 3.7 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. 35% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 26.0 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 26.0 kB or 74% of the original size.
Potential reduce by 401.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. Obviously, Future R needs image optimization as it can save up to 401.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 140.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 140.9 kB or 63% of the original size.
Potential reduce by 20.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. Future-r.co.jp needs all CSS files to be minified and compressed as it can save up to 20.0 kB or 78% of the original size.
Number of requests can be reduced by 15 (27%)
56
41
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Future R. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
future-r.co.jp
1632 ms
style.css
192 ms
styles.css
357 ms
flexslider.css
382 ms
jquery.fancybox-1.3.7.min.css
378 ms
jquery.js
544 ms
jquery-migrate.min.js
385 ms
jquery.flexslider-min.js
415 ms
jquery.form.min.js
523 ms
scripts.js
623 ms
jquery.easing.pack.js
622 ms
dynamic.to.top.min.js
623 ms
wp-embed.min.js
623 ms
jquery.fancybox-1.3.7.min.js
695 ms
jquery.mousewheel.min.js
712 ms
wp-emoji-release.min.js
540 ms
ga.js
8 ms
__utm.gif
47 ms
arrowSub.png
236 ms
TEL3.jpg
891 ms
cropped-toptst.jpg
887 ms
border.png
288 ms
11eac0d981b2c259a3dffaf3b17bf58c.jpg
1494 ms
b1fdbdcfb90a42451ebad47285666fcd.png
501 ms
5e5d540d18beeb31fa2eb65dfa0eab59.png
523 ms
dda2f154ecf89105be0b510c5dff5d59.png
605 ms
d4f88984a67986160012dbe34285667d.jpg
2541 ms
dc8fae56eee354bc7745af9c4dd606de.jpg
1513 ms
e6bb19a58006a1637e1ec21f4e1b1079.jpg
1384 ms
62f43d2203718c03a803d66b1534a088.jpg
1396 ms
e33ff36264eabe6809fe75012c4c05c6.jpg
1096 ms
d9469c625ee6bfd27ff8158642c0b750.jpg
1302 ms
a3813611cc425c5ced4438defa47aa41.jpg
1509 ms
a289b5d15ce40799725cc95fb7531953.jpg
1584 ms
95ad2cb644e0eb06f25f35051c00246f.jpg
1609 ms
bbce09d0a4857c7f935160547cea63c1.jpg
1698 ms
4a86ebe92f7aecb434c1a75b4e342ed0.jpg
1706 ms
19a0d9958043e4e8e7926657555eb41b.jpg
1716 ms
GWs.jpg
1783 ms
in1.jpg
1815 ms
tel_banar.jpg
1928 ms
03e54021b5e44a4e7c41cfbe9e64c720.png
1880 ms
8abb88c505a868a49f9a5d7b3102fb9f.jpg
1965 ms
3e0203e45f38be21ffe6b0ba48172a3f.png
1953 ms
0120-00-2399.png
1999 ms
694d786095307dd9f58681d00c44477e.jpg
2079 ms
7d0322a764258b70aa03c87055c1e30c.jpg
2089 ms
e100d55b97d8824c4957eb77fe9f5def.gif
2072 ms
j-pec.gif
2095 ms
recruit.jpg
2167 ms
__utm.gif
2 ms
c5eaf40197e7de09aa824b3852fa149a.jpg
2218 ms
like.php
182 ms
c5eaf40197e7de09aa824b3852fa149a.png
2340 ms
arrow.png
2138 ms
qeKvIRsJabD.js
491 ms
LVx-xkvaJ0b.png
555 ms
future-r.co.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.
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
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
Links do not have a discernible name
future-r.co.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
future-r.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Future-r.co.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 Future-r.co.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.
future-r.co.jp
Open Graph description is not detected on the main page of Future R. 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: