Tools & Wizards About Us
billiton.de screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    64% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

billiton.de

Über 25 Jahre im Internet zuhause: Wer @ sagt, muss auch b sagen - billiton

Page Load Speed

3.5 sec in total

First Response

553 ms

Resources Loaded

2.7 sec

Page Rendered

238 ms

billiton.de screenshot

About Website

Visit billiton.de now to see the best up-to-date Billiton content for Romania and also check out these interesting facts you probably never knew about billiton.de

Egal ob Webseite oder Applikation, wir begleiten Sie auf dem Weg in die digitale Zukunft. Ihren Wünschen oder Ideen sind keine Grenzen gesetzt!

Visit billiton.de

Key Findings

We analyzed Billiton.de page load time and found that the first response time was 553 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

billiton.de performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value640 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

www.billiton.de

553 ms

stylesheet_91890b196a.css

100 ms

seminars_pi1.css

194 ms

onetimeaccount_pi1.css

195 ms

reset-min.css

197 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 71% of them (50 requests) were addressed to the original Billiton.de, 10% (7 requests) were made to Cm.g.doubleclick.net and 6% (4 requests) were made to Billiton.ladesk.com. The less responsive or slowest element that took the longest time to load (750 ms) belongs to the original domain Billiton.de.

Page Optimization Overview & Recommendations

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

Content Size

797.8 kB

After Optimization

389.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-69%

Potential reduce by 43.4 kB

  • Original 62.9 kB
  • After minification 61.0 kB
  • After compression 19.4 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 43.4 kB or 69% of the original size.

Image Optimization

-4%

Potential reduce by 8.3 kB

  • Original 207.5 kB
  • After minification 199.2 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. Billiton images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 282.7 kB

  • Original 440.4 kB
  • After minification 427.1 kB
  • After compression 157.7 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 282.7 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 73.5 kB

  • Original 87.1 kB
  • After minification 65.3 kB
  • After compression 13.5 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. Billiton.de needs all CSS files to be minified and compressed as it can save up to 73.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (69%)

Requests Now

61

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Billiton. 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 from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.billiton.de

www.billiton.de

553 ms

stylesheet_91890b196a.css

stylesheet_91890b196a.css

100 ms

seminars_pi1.css

seminars_pi1.css

194 ms

onetimeaccount_pi1.css

onetimeaccount_pi1.css

195 ms

reset-min.css

reset-min.css

197 ms

fonts-min.css

fonts-min.css

198 ms

main.css

main.css

200 ms

tx_seminars_pi1.js

tx_seminars_pi1.js

198 ms

jquery.min.js

jquery.min.js

36 ms

easySlider1.7.js

easySlider1.7.js

288 ms

main.js

main.js

289 ms

thickbox_de.js

thickbox_de.js

294 ms

thickbox.css

thickbox.css

295 ms

addthis_widget.js

addthis_widget.js

15 ms

body-bg.gif

body-bg.gif

99 ms

head-logo.gif

head-logo.gif

97 ms

ed.gif

ed.gif

100 ms

signature.gif

signature.gif

101 ms

0acb99c5e1.png

0acb99c5e1.png

288 ms

f5d3d281f4.jpg

f5d3d281f4.jpg

101 ms

de.gif

de.gif

196 ms

en.gif

en.gif

197 ms

ga.js

ga.js

18 ms

track.js

track.js

349 ms

main-bg.gif

main-bg.gif

188 ms

head-big-b.gif

head-big-b.gif

189 ms

menu-2-ul-li-act.gif

menu-2-ul-li-act.gif

189 ms

menu-2-ul-li-ul-li-no.gif

menu-2-ul-li-ul-li-no.gif

276 ms

menu-2-ul-li-no.gif

menu-2-ul-li-no.gif

281 ms

search-icon.gif

search-icon.gif

286 ms

submit-28px.gif

submit-28px.gif

285 ms

dt-callback.gif

dt-callback.gif

284 ms

dt-address.gif

dt-address.gif

369 ms

dt-phone.gif

dt-phone.gif

370 ms

dt-fax.gif

dt-fax.gif

390 ms

dt-mail.gif

dt-mail.gif

391 ms

pfeil_weg.gif

pfeil_weg.gif

389 ms

dt-sitemap.gif

dt-sitemap.gif

389 ms

whoson-link.png

whoson-link.png

465 ms

whoson-hover.png

whoson-hover.png

750 ms

menu-1-act.6.png

menu-1-act.6.png

488 ms

begruessung.jpg

begruessung.jpg

588 ms

teaser-row-tyle.png

teaser-row-tyle.png

487 ms

cms.jpg

cms.jpg

486 ms

link-icon.gif

link-icon.gif

560 ms

news-more-link.gif

news-more-link.gif

585 ms

webshop.jpg

webshop.jpg

586 ms

webentwicklung.jpg

webentwicklung.jpg

584 ms

news-press-sub-icon.gif

news-press-sub-icon.gif

654 ms

li.gif

li.gif

682 ms

footer-bg.gif

footer-bg.gif

684 ms

rss-icon.gif

rss-icon.gif

683 ms

300lo.json

300lo.json

28 ms

__utm.gif

__utm.gif

13 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

46 ms

loadingAnimation.gif

loadingAnimation.gif

607 ms

pixel

pixel

15 ms

pixel

pixel

19 ms

pixel

pixel

16 ms

pixel

pixel

17 ms

pixel

pixel

15 ms

pixel

pixel

16 ms

match-result

match-result

43 ms

match-result

match-result

43 ms

match-result

match-result

43 ms

pixel

pixel

13 ms

track.js

track.js

295 ms

print.css

print.css

400 ms

track_visit.php

track_visit.php

36 ms

track_visit.php

track_visit.php

607 ms

Accessibility Review

billiton.de accessibility score

85

Accessibility Issues

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

Buttons do not have an accessible name

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.

Best Practices

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

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

billiton.de SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

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

billiton.de

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