4.2 sec in total
471 ms
3.6 sec
129 ms
Visit iloxx.at now to see the best up-to-date Iloxx content for Austria and also check out these interesting facts you probably never knew about iloxx.at
Sie suchen Transportlösungen für außergewöhnliche Versandstücke, besonders große oder schwere Pakete, Reifen oder Sperrgut? iloxx hat die Lösung! LOX Frachten. Die Spedition von iloxx organisiert maßg...
Visit iloxx.atWe analyzed Iloxx.at page load time and found that the first response time was 471 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
iloxx.at performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value9.3 s
1/100
25%
Value9.1 s
14/100
10%
Value1,770 ms
10/100
30%
Value0.001
100/100
15%
Value17.8 s
4/100
10%
471 ms
1110 ms
275 ms
465 ms
278 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Iloxx.at, 88% (66 requests) were made to Iloxx.de and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Iloxx.de.
Page size can be reduced by 350.6 kB (51%)
683.4 kB
332.8 kB
In fact, the total size of Iloxx.at main page is 683.4 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. 25% of websites need less resources to load. Javascripts take 292.0 kB which makes up the majority of the site volume.
Potential reduce by 110.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. 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 110.9 kB or 79% of the original size.
Potential reduce by 3.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. Iloxx images are well optimized though.
Potential reduce by 191.5 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 191.5 kB or 66% of the original size.
Potential reduce by 44.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. Iloxx.at needs all CSS files to be minified and compressed as it can save up to 44.7 kB or 83% of the original size.
Number of requests can be reduced by 37 (51%)
73
36
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iloxx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
home.aspx
471 ms
home.aspx
1110 ms
iloxx.css
275 ms
jquery-ui.custom.css
465 ms
iloxx.js
278 ms
jquery.min.js
648 ms
jquery.iloxxrotate.js
279 ms
09906ba31ca89a33a1b975e9716b1637db223577dd0609a6f26f12f98be295a4.js
353 ms
WebResource.axd
307 ms
iloxx_logo_129x64.gif
94 ms
icon-iloxx-Blog.gif
95 ms
iloxx-facebook-20x20.gif
95 ms
google-plus_20x20.gif
96 ms
twitter_20x20.gif
96 ms
youtube_20x20.gif
217 ms
xing_20x20.gif
217 ms
btn_login_90x17.gif
216 ms
btn-registrieren.gif
217 ms
1_0.gif
217 ms
1_1.gif
274 ms
2_0.gif
274 ms
2_1.gif
275 ms
3_0.gif
277 ms
3_1.gif
276 ms
0.gif
276 ms
0_1.gif
358 ms
0_2.gif
365 ms
0_3.gif
367 ms
0_0.gif
373 ms
service.jpg
375 ms
selector_1_18x17.gif
373 ms
selector_2_18x17-active.gif
448 ms
selector_3_18x17.gif
456 ms
selector_4_18x17.gif
458 ms
iloxx-Fracht-Landverkehr_653x258.jpg
554 ms
selector_2_18x17.gif
458 ms
selector_3_18x17-active.gif
459 ms
iloxx-Zweiradtransport-653x258.jpg
632 ms
selector_4_18x17-active.gif
547 ms
iloxx-Skiversand_653x258.jpg
641 ms
selector_1_18x17-active.gif
551 ms
iloxx-Paketversand-at_653x258.jpg
641 ms
ecke_10x10.gif
637 ms
btn_berechnen_115x17.gif
642 ms
ecke_beige_9x8.gif
561 ms
tracking_at_44x46.gif
642 ms
btn_tracking_115x17.gif
648 ms
ecke_start_8x8.gif
651 ms
icon_Paket_70x59.gif
652 ms
icon_Reifen_70x59.gif
535 ms
icon_Express_70x59.gif
534 ms
icon_Board_70x59.gif
638 ms
icon_Spedition_70x59.gif
637 ms
icon_Zweirad_70x59.gif
638 ms
userlike.min.js
579 ms
analytics.js
25 ms
icon_Paekte_70x59.gif
623 ms
collect
11 ms
icon_Container_70x59.gif
582 ms
icon_Landverkehr_70x59.gif
580 ms
icon_Seefracht_70x59.gif
644 ms
icon_Spezial_70x59.gif
659 ms
btn_angebotsanfrage_140x17.gif
659 ms
f_dpd.gif
658 ms
f_eBay.gif
575 ms
f_sage.gif
567 ms
f_motocargo.gif
640 ms
f_raben.gif
656 ms
f_ids.gif
654 ms
f_kno.gif
653 ms
line_dotted_1.gif
576 ms
webfont.js
68 ms
userlikelib.min.js
40 ms
488 ms
css
61 ms
iloxx.at 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
iloxx.at 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
Missing source maps for large first-party JavaScript
iloxx.at SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iloxx.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Iloxx.at 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.
iloxx.at
Open Graph description is not detected on the main page of Iloxx. 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: