Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

iloxx.at

Paketversand, Express, Sperrgut und Spedition | iloxx.de

Page Load Speed

4.2 sec in total

First Response

471 ms

Resources Loaded

3.6 sec

Page Rendered

129 ms

iloxx.at screenshot

About Website

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.at

Key Findings

We 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.

Performance Metrics

iloxx.at performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value1,770 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

home.aspx

471 ms

home.aspx

1110 ms

iloxx.css

275 ms

jquery-ui.custom.css

465 ms

iloxx.js

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 Optimization Overview & Recommendations

Page size can be reduced by 350.6 kB (51%)

Content Size

683.4 kB

After Optimization

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.

HTML Optimization

-79%

Potential reduce by 110.9 kB

  • Original 139.9 kB
  • After minification 130.5 kB
  • After compression 29.0 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.

Image Optimization

-2%

Potential reduce by 3.5 kB

  • Original 197.8 kB
  • After minification 194.3 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.

JavaScript Optimization

-66%

Potential reduce by 191.5 kB

  • Original 292.0 kB
  • After minification 283.9 kB
  • After compression 100.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.

CSS Optimization

-83%

Potential reduce by 44.7 kB

  • Original 53.7 kB
  • After minification 43.8 kB
  • After compression 9.0 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.

Requests Breakdown

Number of requests can be reduced by 37 (51%)

Requests Now

73

After Optimization

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.

Accessibility Review

iloxx.at accessibility score

76

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[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

High

Some elements have a [tabindex] value greater than 0

Best Practices

iloxx.at best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

iloxx.at SEO score

54

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    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.

Social Sharing Optimization

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: