Tools & Wizards About Us
iload.de screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

iload.de

iLoad - award winning software, index search, fullspeed + SSL

Page Load Speed

2.6 sec in total

First Response

304 ms

Resources Loaded

2.1 sec

Page Rendered

151 ms

iload.de screenshot

About Website

Click here to check amazing ILoad content for Germany. Otherwise, check out these important facts you probably never knew about iload.de

Full service usenet provider with an award winning software free to all users.All plans include longest retention and highest completion available, as well as SSL encryption.

Visit iload.de

Key Findings

We analyzed Iload.de page load time and found that the first response time was 304 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

iload.de performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value370 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

iload.de

304 ms

home

578 ms

bundle.min.js

24 ms

css

39 ms

animate.min.css

119 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Iload.de, 67% (31 requests) were made to Iload-usenet.com and 9% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (670 ms) relates to the external source Stats.iload-usenet.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 94.3 kB (66%)

Content Size

142.0 kB

After Optimization

47.8 kB

  • HTML
  • JavaScript

In fact, the total size of Iload.de main page is 142.0 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. 35% of websites need less resources to load. Javascripts take 119.5 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 17.4 kB

  • Original 22.5 kB
  • After minification 16.3 kB
  • After compression 5.1 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 6.2 kB, which is 28% 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 17.4 kB or 77% of the original size.

JavaScript Optimization

-64%

Potential reduce by 76.9 kB

  • Original 119.5 kB
  • After minification 119.5 kB
  • After compression 42.6 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 76.9 kB or 64% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (58%)

Requests Now

36

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ILoad. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

iload.de

iload.de

304 ms

home

home

578 ms

bundle.min.js

bundle.min.js

24 ms

css

css

39 ms

animate.min.css

animate.min.css

119 ms

fontawesome-all.min.css

fontawesome-all.min.css

207 ms

paymentfont.min.css

paymentfont.min.css

341 ms

theme.css

theme.css

472 ms

frontend.css

frontend.css

341 ms

jquery.min.js

jquery.min.js

377 ms

jquery-migrate.min.js

jquery-migrate.min.js

344 ms

popper.min.js

popper.min.js

344 ms

bootstrap.min.js

bootstrap.min.js

460 ms

hs.core.js

hs.core.js

376 ms

svg-injector.min.js

svg-injector.min.js

397 ms

hs.header.js

hs.header.js

409 ms

hs.unfold.js

hs.unfold.js

575 ms

hs.svg-injector.js

hs.svg-injector.js

468 ms

jquery.cookie.js

jquery.cookie.js

576 ms

frontend.js

frontend.js

576 ms

gtm.js

gtm.js

70 ms

analytics.js

analytics.js

20 ms

collect

collect

14 ms

collect

collect

29 ms

js

js

46 ms

ga-audiences

ga-audiences

129 ms

logo-white.svg

logo-white.svg

107 ms

logo.svg

logo.svg

105 ms

circle-preloader.svg

circle-preloader.svg

96 ms

wave-6-top-left.svg

wave-6-top-left.svg

95 ms

feature-1.svg

feature-1.svg

97 ms

feature-2.svg

feature-2.svg

100 ms

feature-3.svg

feature-3.svg

187 ms

curved-2.svg

curved-2.svg

184 ms

de16.png

de16.png

188 ms

en16.png

en16.png

186 ms

piwik.js

piwik.js

670 ms

fbds.js

fbds.js

49 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

34 ms

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

38 ms

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

48 ms

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

52 ms

fa-solid-900.woff

fa-solid-900.woff

331 ms

fa-regular-400.woff

fa-regular-400.woff

327 ms

fa-light-300.woff

fa-light-300.woff

300 ms

paymentfont-webfont.woff

paymentfont-webfont.woff

391 ms

Accessibility Review

iload.de accessibility score

96

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

iload.de 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

iload.de SEO score

97

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iload.de 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 Iload.de 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

iload.de

Open Graph description is not detected on the main page of ILoad. 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: