6.6 sec in total
285 ms
6.1 sec
155 ms
Visit unaxis.com now to see the best up-to-date Unaxis content and also check out these interesting facts you probably never knew about unaxis.com
Welcome to Oerlikon - one of the world's leading high-tech industrial groups.
Visit unaxis.comWe analyzed Unaxis.com page load time and found that the first response time was 285 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
unaxis.com performance score
285 ms
1626 ms
197 ms
299 ms
637 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Unaxis.com, 73% (74 requests) were made to Oerlikon.com and 7% (7 requests) were made to Use.typekit.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Oerlikon.com.
Page size can be reduced by 1.4 MB (68%)
2.0 MB
656.1 kB
In fact, the total size of Unaxis.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. 55% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 51.9 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 11.0 kB, which is 17% 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 51.9 kB or 81% of the original size.
Potential reduce by 18.5 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, Unaxis needs image optimization as it can save up to 18.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 993.2 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 993.2 kB or 68% of the original size.
Potential reduce by 309.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. Unaxis.com needs all CSS files to be minified and compressed as it can save up to 309.9 kB or 84% of the original size.
Number of requests can be reduced by 44 (48%)
92
48
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Unaxis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
unaxis.com
285 ms
www.oerlikon.com
1626 ms
screen.css
197 ms
libraries.js
299 ms
plugins.js
637 ms
functions.js
217 ms
e.js
235 ms
kuj6zvt.js
157 ms
require.js
218 ms
cookiechoices.js
218 ms
screen-blessed1.css
375 ms
jquery-1.8.3.min.js
475 ms
365 ms
t.js
364 ms
1f
134 ms
print.css
96 ms
oerlikon_bg_logo_oerlikon_corporate.png
335 ms
oerlikon_ANIGIF_porsche.gif
1147 ms
oerlikon_pi_stageNav_thumb-1.jpg&w=100
482 ms
oerlikon_pi_stageNav_thumb-5.jpg&w=100
477 ms
oerlikon_pi_stageNav_thumb-2.jpg&w=100
481 ms
oerlikon_pi_stageNav_thumb-3.jpg&w=100
415 ms
oerlikon_pi_stageNav_thumb-4.jpg&w=100
768 ms
gtm.js
205 ms
javascript.js
436 ms
bg_navTop.png
456 ms
navMeta_arrow.gif
461 ms
arrow_02.png
478 ms
bg_search.png
562 ms
bg_stage_shadow.jpg
624 ms
bg_welcome-slider-top-shadow.jpg
643 ms
bg_stageNav_shadow.jpg
660 ms
pi_welcome_teaser_pageBtn_bg.png
727 ms
bg_pageBtn-hover.png
770 ms
oerlikon_InternetBlog.png
957 ms
oerlikon_pi_teaser_e-report.png
919 ms
oerlikon_pi_teaser_play.png
1015 ms
oerlikon_pi_teaser_weltkarte.png
1049 ms
oerlikon_pi_teaser_fragezeichen.png
1084 ms
oerlikon_pi_teaser_group.png
1206 ms
bg_footer.png
1111 ms
bg_footer_stock.png
1152 ms
pi_social_footer_facebook.png
1196 ms
pi_social_footer_twitter.png
1231 ms
pi_social_footer_youtube.png
1262 ms
pi_social_footer_googleplus.png
1278 ms
pi_social_footer_xing.png
1320 ms
pi_social_footer_linkedin.png
1363 ms
pi_social_footer_rss.png
1386 ms
bg_loading.gif
1411 ms
arrow_11.png
1444 ms
bg_close.png
1462 ms
en.png
1501 ms
analytics.js
15 ms
gtmext.min.js
73 ms
_SZwhL9WATCugwB7SNRQDsJOButwL8mB9TpMQzU48V6ffHObMUM-eMI6MK6fw6NuSh90iY83ZAlTifoRdhXtgM.eot
35 ms
vDrebYyHeq13NJfGuxsjh4j6fQv107Cs6IYiObkpEYtffHdbMUM-eMI6MK6fw6NuSh90iY83ZAlTifoRdhXtg3.eot
142 ms
_jPVZ1TiiWCsAn3Wmf80OsNyFKnWTRrBjfjo-FmeFv6ffHVbMUM-eMI6MK6fw6NuSh90iY83ZAlTifoRdhXt26.eot
205 ms
GmaP2UQRlgeFx1XnpJWX3A2yE62sn2tZKrX3t1zSegjffHLbMUM-eMI6MK6fw6NuSh90iY83ZAlTifoRdhXtIb.eot
208 ms
GBTSh-NWrw_jQKxqOBqWo-aFK2_HdZ_xTmNMjMCmDItffOhUggM-eMI6MK6gw6NuSh90iY83ZAlTifoRdhXtg3.eot
245 ms
linkid.js
34 ms
collect
57 ms
collect
188 ms
collect
66 ms
collect
106 ms
collect
105 ms
main_old.js
1805 ms
collect
135 ms
cnt_js.php
217 ms
cntcc
214 ms
vmpm.php
207 ms
fontawesome-webfont.woff
1516 ms
fontawesome-webfont.woff
1529 ms
de.png
1369 ms
cn.png
1361 ms
ga-audiences
36 ms
ga-audiences
45 ms
screen.css
1295 ms
arrow_07.png
1377 ms
bg_footer_toggle.png
1390 ms
bg_black.png
1383 ms
bg_filmstrip.png
1394 ms
bg_nav.png
1424 ms
bg_nav_switch.png
1448 ms
bg_thumb_toggle.png
1429 ms
bg_tooltip_bg.png
1410 ms
bg_tooltip_button.png
1448 ms
bg_tooltip_spike.png
1409 ms
bg_play_stop.png
1281 ms
bg_sound.png
1256 ms
bg_dyk2013_logo.png
1249 ms
bg_close_01.png
1210 ms
bg_close_02.png
1282 ms
oerlikon_oe_vorhang-auf-ANIGIF_01b_EN.GIF
929 ms
oerlikon_Mobility_Internet.jpg
719 ms
prev.png
219 ms
next.png
224 ms
ajax-loader.gif
214 ms
oerlikon-logo-white.png
337 ms
slick.woff
386 ms
bg_new_loader.gif
543 ms
unaxis.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Unaxis.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Unaxis.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.
unaxis.com
Open Graph data is detected on the main page of Unaxis. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: