5.6 sec in total
728 ms
4.7 sec
160 ms
Welcome to jai.co.jp homepage info - get ready to check Jai best content for Japan right away, or after learning these important things about jai.co.jp
日本分析工業株式会社(Japan Analytical Industry Co.,Ltd)のオフィシャルサイトです。製品情報、企業情報、採用情報、サービス・サポート情報等をご覧いただけます。主要製品としては、リサイクル分取HPLC,GC・GC/MSの前処理として熱分解装置・加熱脱着装置・アウトガス捕集装置・冷凍粉砕機がございます。質問や資料請求等はお問い合わせよりご連絡ください。
Visit jai.co.jpWe analyzed Jai.co.jp page load time and found that the first response time was 728 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
jai.co.jp performance score
name
value
score
weighting
Value1.8 s
91/100
10%
Value26.4 s
0/100
25%
Value21.6 s
0/100
10%
Value1,180 ms
21/100
30%
Value0.763
5/100
15%
Value20.9 s
1/100
10%
728 ms
345 ms
374 ms
369 ms
376 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 90% of them (65 requests) were addressed to the original Jai.co.jp, 7% (5 requests) were made to Sync5-res.digitalstage.jp and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Jai.co.jp.
Page size can be reduced by 533.3 kB (52%)
1.0 MB
490.4 kB
In fact, the total size of Jai.co.jp main page is 1.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. 30% of websites need less resources to load. Images take 368.7 kB which makes up the majority of the site volume.
Potential reduce by 18.8 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 18.8 kB or 78% of the original size.
Potential reduce by 36.1 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. Jai images are well optimized though.
Potential reduce by 168.8 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 168.8 kB or 61% of the original size.
Potential reduce by 309.6 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. Jai.co.jp needs all CSS files to be minified and compressed as it can save up to 309.6 kB or 88% of the original size.
Number of requests can be reduced by 48 (68%)
71
23
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
jai.co.jp
728 ms
style.css
345 ms
_else.css
374 ms
style.css
369 ms
index.css
376 ms
script.js
385 ms
common.css
181 ms
pagelayout.css
579 ms
printlayout.css
210 ms
blockskin.css
1061 ms
wp_style.css
545 ms
overwrite.css
209 ms
style.css
340 ms
theme.css
339 ms
_else.css
195 ms
_else.css
176 ms
jquery-1.8.3.min.js
770 ms
jquery.easing.1.3.js
191 ms
head.load.min.js
204 ms
movie.js
352 ms
parts.js
343 ms
fx.js
757 ms
override.js
371 ms
load.js
407 ms
ga.js
68 ms
_area_header.css
180 ms
_area_billboard.css
170 ms
_area_main.css
196 ms
_area_side_a.css
191 ms
_area_side_b.css
182 ms
_area_footer.css
179 ms
_block_header.css
337 ms
_block_billboard.css
354 ms
_block_main.css
355 ms
top_ivent.css
361 ms
_block_side_a.css
378 ms
_block_side_b.css
386 ms
_block_footer.css
502 ms
sync.css
566 ms
json.js
564 ms
sync.js
768 ms
engine.js
539 ms
top_logo.jpg
874 ms
Dot_19.gif
536 ms
jhi-07.jpg
936 ms
laboace.jpg
885 ms
hr83j83898380top.jpg
1423 ms
slide_j3.jpg
1140 ms
sign.jpg
741 ms
indent_bubble.gif
931 ms
doticon_red_new.png
1070 ms
jasis2015.jpg
1108 ms
50th.jpg
1149 ms
doticon_red_right.png
1127 ms
sign.jpg
1282 ms
sign.jpg
1328 ms
1_bf2.png
1328 ms
top_lc.jpg
1345 ms
top_jci.jpg
1376 ms
top_jtd.jpg
1472 ms
top_jfc.jpg
1544 ms
top_og.jpg
1521 ms
sign.png
1700 ms
sign.png
1745 ms
__utm.gif
11 ms
1_ic_linktop.png
1486 ms
foot.gif
1499 ms
google-Logo_40wht.gif
354 ms
bg_search.png
361 ms
nivo-slider.css
853 ms
custom-nivo-slider.css
876 ms
jquery.nivo.slider.pack.js
939 ms
jai.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.
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
Links do not have a discernible name
jai.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
jai.co.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 doesn't use legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jai.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 Jai.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.
jai.co.jp
Open Graph description is not detected on the main page of Jai. 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: