6 sec in total
721 ms
5 sec
300 ms
Click here to check amazing Pioneer Communication content for Japan. Otherwise, check out these important facts you probably never knew about pioneer-communication.com
オンキヨー&パイオニア株式会社のホームページです。生活機器などを掲載しています。
Visit pioneer-communication.comWe analyzed Pioneer-communication.com page load time and found that the first response time was 721 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
pioneer-communication.com performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value10.4 s
0/100
25%
Value10.0 s
9/100
10%
Value60 ms
100/100
30%
Value0.198
62/100
15%
Value8.2 s
40/100
10%
721 ms
332 ms
507 ms
407 ms
488 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 93% of them (70 requests) were addressed to the original Pioneer-communication.com, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Rt.rtoaster.jp. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Pioneer-communication.com.
Page size can be reduced by 540.5 kB (27%)
2.0 MB
1.5 MB
In fact, the total size of Pioneer-communication.com main page is 2.0 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. 20% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 30.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. This page needs HTML code to be minified as it can gain 5.3 kB, which is 14% 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 30.2 kB or 81% of the original size.
Potential reduce by 27.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. Pioneer Communication images are well optimized though.
Potential reduce by 268.1 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 268.1 kB or 70% of the original size.
Potential reduce by 214.9 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. Pioneer-communication.com needs all CSS files to be minified and compressed as it can save up to 214.9 kB or 88% of the original size.
Number of requests can be reduced by 35 (48%)
73
38
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pioneer Communication. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
pioneer-communication.com
721 ms
media_change.css
332 ms
reset.css
507 ms
module.css
407 ms
module2.css
488 ms
layout.css
899 ms
form.css
374 ms
import.css
495 ms
jquery-1.9.1.min.js
1121 ms
jquery.easing.1.3.js
573 ms
num_list.js
661 ms
jquery.flatheights.js
658 ms
msm.js
672 ms
navi_change.js
741 ms
responsive-nav.js
822 ms
loadbar.js
834 ms
require.js
841 ms
Rtoaster.js
1165 ms
responsive_slide.css
906 ms
responsive_slide.js
995 ms
googleAnalytics.js
1011 ms
common.js
851 ms
red_line_global_navi.js
917 ms
global_navi_layer.js
1082 ms
jquery.leanModal.min.js
1002 ms
main.js
172 ms
navi_cycle_life.css
178 ms
contents.css
166 ms
jquery-1.9.1.min.js
345 ms
analytics.js
77 ms
bg.png
177 ms
logo.png
166 ms
navi_l3_bic2.png
182 ms
navi_l3_bic5.png
169 ms
navi_l3_bic4.png
188 ms
navi_l3_bic3.png
332 ms
gnavi_li_bg.jpg
336 ms
4_2_1.png
530 ms
4_3_1.png
362 ms
4_4_1.png
380 ms
4_4_2.png
478 ms
4_4_3.png
821 ms
z_slide_btn_up.png
505 ms
z_slide_btn_down.png
543 ms
icon_search_sp.png
567 ms
close_btn_modal.png
648 ms
close_btn.png
672 ms
main01.jpg
1585 ms
main02.jpg
1625 ms
main03.jpg
1134 ms
main04.jpg
1159 ms
main_thumb01.jpg
1006 ms
main_thumb02.jpg
1149 ms
main_thumb03.jpg
1177 ms
main_thumb04.jpg
1353 ms
img_tel.jpg
1479 ms
img_femimi.jpg
1332 ms
img_kaitelekun.jpg
1511 ms
img_hochouki.jpg
1502 ms
img_femimi02.jpg
1543 ms
img_kaitelekun02.jpg
1647 ms
bread_bg.png
1673 ms
icon_arrow_op.png
1681 ms
btn_pageTop.png
1096 ms
collect
2 ms
collect
65 ms
jquery.easing.1.3.js
1415 ms
jquery.bxslider.min.js
1445 ms
common.js
172 ms
reset.css
175 ms
module.css
172 ms
module2.css
171 ms
layout.css
174 ms
print.css
171 ms
mosaictile.css
172 ms
pioneer-communication.com accessibility score
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.
pioneer-communication.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
pioneer-communication.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pioneer-communication.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 Pioneer-communication.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.
pioneer-communication.com
Open Graph data is detected on the main page of Pioneer Communication. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: