6.3 sec in total
1.1 sec
4.7 sec
431 ms
Click here to check amazing Zoom Player content for Japan. Otherwise, check out these important facts you probably never knew about zoom-player.jp
どんな動画も高速かつ安定して再生する世界最高のメディアプレーヤー「ZOOM PLAYER」を販売しているInmatrix LTD.の日本公式サイトです。
Visit zoom-player.jpWe analyzed Zoom-player.jp page load time and found that the first response time was 1.1 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
zoom-player.jp performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value9.4 s
0/100
25%
Value10.3 s
8/100
10%
Value70 ms
99/100
30%
Value0.053
98/100
15%
Value8.3 s
40/100
10%
1134 ms
706 ms
891 ms
361 ms
1272 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 92% of them (45 requests) were addressed to the original Zoom-player.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Zoom-player.jp.
Page size can be reduced by 201.6 kB (28%)
709.0 kB
507.4 kB
In fact, the total size of Zoom-player.jp main page is 709.0 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. Images take 475.7 kB which makes up the majority of the site volume.
Potential reduce by 16.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 4.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 16.2 kB or 70% of the original size.
Potential reduce by 45.2 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. Zoom Player images are well optimized though.
Potential reduce by 114.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 114.1 kB or 64% of the original size.
Potential reduce by 26.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. Zoom-player.jp needs all CSS files to be minified and compressed as it can save up to 26.2 kB or 82% of the original size.
Number of requests can be reduced by 6 (13%)
47
41
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zoom Player. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
www.zoom-player.jp
1134 ms
wp-emoji-release.min.js
706 ms
common.css
891 ms
default.css
361 ms
jquery.js
1272 ms
jquery-migrate.min.js
546 ms
zoomplayer.js
504 ms
jquery.colorimazer.min.js
537 ms
gtm.js
119 ms
bg_header_home.jpg
178 ms
bg_header_wrap_home.jpg
367 ms
logo_zoomplayer.jpg
184 ms
bg_gloval_navi.jpg
178 ms
img_navHome.jpg
180 ms
img_navProduct.jpg
181 ms
img_navBuy.jpg
353 ms
img_navSupport.jpg
355 ms
bg_primaryDropDown.png
358 ms
bullet_dropdown.png
630 ms
img_navCompany.jpg
364 ms
img_navContact.jpg
530 ms
bg_billboard.jpg
531 ms
bg_billboard_wrap.jpg
900 ms
vector_300x300_160210.png
726 ms
img_billboard_copy.png
548 ms
img_billboard_h2_02.png
888 ms
button_buy_mainimage.png
710 ms
button_download_mainimage.png
735 ms
bg_homeMainColumn.jpg
808 ms
bg_h2_short.jpg
891 ms
img_home_screenshot.jpg
908 ms
img_home_interface.jpg
923 ms
bg_h2.jpg
992 ms
bullet_home_funclist.jpg
1068 ms
bg_home_productbox.jpg
1074 ms
img_free_pkg.png
1081 ms
button_download_m.png
1089 ms
bullet_product_list.png
1111 ms
img_pro_pkg.png
1176 ms
button_trial_m.png
1250 ms
button_buy_m.png
1256 ms
img_max_pkg.png
1265 ms
bg_sysReq.jpg
1270 ms
bg_sysReq_h3.jpg
1300 ms
bg_footer.jpg
1361 ms
analytics.js
5 ms
collect
4 ms
collect
67 ms
logo_footer.png
1267 ms
zoom-player.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.
zoom-player.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
Browser errors were logged to the console
zoom-player.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zoom-player.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 Zoom-player.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.
zoom-player.jp
Open Graph description is not detected on the main page of Zoom Player. 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: