6.2 sec in total
1.2 sec
4.8 sec
238 ms
Click here to check amazing Aposs content. Otherwise, check out these important facts you probably never knew about aposs.com
zub machine control AG, your drive engineering partner: Motion controls, Positioning controls, Synchronization controls, CAN and EtherCAT networking,...
Visit aposs.comWe analyzed Aposs.com page load time and found that the first response time was 1.2 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
aposs.com performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value7.0 s
6/100
25%
Value6.2 s
43/100
10%
Value130 ms
96/100
30%
Value0.001
100/100
15%
Value6.2 s
62/100
10%
1175 ms
901 ms
220 ms
204 ms
223 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Aposs.com, 95% (72 requests) were made to Zub.ch and 3% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Aposs.com.
Page size can be reduced by 802.3 kB (34%)
2.4 MB
1.6 MB
In fact, the total size of Aposs.com main page is 2.4 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 1.7 MB which makes up the majority of the site volume.
Potential reduce by 47.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. This page needs HTML code to be minified as it can gain 19.5 kB, which is 35% 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 47.8 kB or 85% of the original size.
Potential reduce by 295.7 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, Aposs needs image optimization as it can save up to 295.7 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 367.0 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 367.0 kB or 72% of the original size.
Potential reduce by 91.7 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. Aposs.com needs all CSS files to be minified and compressed as it can save up to 91.7 kB or 80% of the original size.
Number of requests can be reduced by 48 (65%)
74
26
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aposs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
aposs.com
1175 ms
901 ms
rokbox.css
220 ms
grid-12.css
204 ms
joomla-ie7.css
223 ms
style1.css
210 ms
sizes.php
217 ms
normalize.css
206 ms
default.css
406 ms
prettyPhoto.css
309 ms
isotope.css
310 ms
template.css
420 ms
css
24 ms
fusionmenu.css
319 ms
nivo-slider.css
323 ms
nivo-slider.css
412 ms
template.css
413 ms
jquery.min.js
32 ms
jquerynoconflict.js
442 ms
jquery-ui.min.js
52 ms
mootools-core.js
731 ms
core.js
506 ms
mootools-more.js
923 ms
k2.js
512 ms
rokbox.js
621 ms
gantry-totop.js
521 ms
browser-engines.js
608 ms
tooltips.js
614 ms
jquery.tagcanvas.js
622 ms
jquery.prettyPhoto.js
711 ms
jquery.preloader.js
716 ms
jquery.easing.1.3.js
721 ms
scripts.js
725 ms
jquery.isotope.min.js
816 ms
fusion.js
982 ms
jquery.nivo.slider.js
823 ms
logo.png
215 ms
de.gif
106 ms
en.gif
105 ms
search_bg.png
108 ms
search_button.gif
109 ms
menu_bg.gif
109 ms
menu_line.gif
206 ms
menu_active.gif
208 ms
submenu_bg.gif
213 ms
loader.gif
209 ms
c5f7f8ba22bc61faa6aa803ae1139d1d_XL.jpg
651 ms
5fa21cd9e0d2531a2f1dfdffbab46f70_XL.jpg
615 ms
da8a96cfc8ca1dd33bc42677c8b9c7c6_XL.jpg
722 ms
56dab2b3675237b0ba79395c67ee9ae4_XL.jpg
418 ms
b1d237aad44a95e3871fc116e6241517_XL.jpg
725 ms
0d1fd34f22c9730e91eb5170fbddc114_XL.jpg
736 ms
thumb1.jpg
523 ms
thumb2.jpg
628 ms
thumb3.jpg
719 ms
thumb4.jpg
732 ms
thumb5.jpg
753 ms
thumb6.jpg
824 ms
Daten-sammeln-und-auswerten-mit-MasterMACS.jpg
826 ms
Buzibachstrasse31_Rothenburg_118x101px.png
827 ms
7a0c9d8bd9eadf879f0011817e8c2396_XS.jpg
835 ms
cdbf366d9f51982d2973fefc5c0ec9b1_XS.jpg
838 ms
9f9f79e544fb8eb705d18df3c18b9f0a_XS.jpg
856 ms
Danfoss_MotionControl-Partner.jpg
932 ms
logo-klein.png
931 ms
bg_box.gif
927 ms
button_bg.gif
933 ms
line_hor1.gif
926 ms
bg_date.gif
942 ms
marker2.gif
1016 ms
marker1.gif
1016 ms
footer_bg.gif
963 ms
loading.gif
941 ms
thumb_active.gif
104 ms
marker_thumb.png
105 ms
thumb.gif
106 ms
aposs.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.
aposs.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
aposs.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
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aposs.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Aposs.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.
aposs.com
Open Graph data is detected on the main page of Aposs. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: