Tools & Wizards About Us
thomashummel.net screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    40% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 90% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

thomashummel.net

Das Virtuelle Orchester der Neuen Musik, Sample Datenbank, Spieltechniken, mehr als 150 Orchesterinstrumente | conTimbre

Page Load Speed

2.6 sec in total

First Response

311 ms

Resources Loaded

2.2 sec

Page Rendered

125 ms

thomashummel.net screenshot

About Website

Welcome to thomashummel.net homepage info - get ready to check Thomashummel best content right away, or after learning these important things about thomashummel.net

Musikern und Informatikern, die Spezialisten im Bereich der Neuen Musik sind. Finale, Sibelius, Cubase kompatibilität. Für Apple Mac und für Windows …

Visit thomashummel.net

Key Findings

We analyzed Thomashummel.net page load time and found that the first response time was 311 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 40% of websites can load faster.

Performance Metrics

thomashummel.net performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value13,530 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

thomashummel.net

311 ms

www.thomashummel.net

448 ms

colorbox1.min.css

110 ms

template.css

195 ms

mootools-core.js

493 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 92% of them (35 requests) were addressed to the original Thomashummel.net, 5% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (792 ms) belongs to the original domain Thomashummel.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 381.2 kB (46%)

Content Size

829.2 kB

After Optimization

448.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thomashummel.net main page is 829.2 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 476.5 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 8.9 kB

  • Original 12.7 kB
  • After minification 11.7 kB
  • After compression 3.7 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 8.9 kB or 71% of the original size.

Image Optimization

-12%

Potential reduce by 37.1 kB

  • Original 316.7 kB
  • After minification 279.6 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, Thomashummel needs image optimization as it can save up to 37.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 316.4 kB

  • Original 476.5 kB
  • After minification 469.6 kB
  • After compression 160.1 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 316.4 kB or 66% of the original size.

CSS Optimization

-81%

Potential reduce by 18.7 kB

  • Original 23.3 kB
  • After minification 18.1 kB
  • After compression 4.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. Thomashummel.net needs all CSS files to be minified and compressed as it can save up to 18.7 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (44%)

Requests Now

36

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thomashummel.net

thomashummel.net

311 ms

www.thomashummel.net

www.thomashummel.net

448 ms

colorbox1.min.css

colorbox1.min.css

110 ms

template.css

template.css

195 ms

mootools-core.js

mootools-core.js

493 ms

core.js

core.js

205 ms

mootools-more.js

mootools-more.js

792 ms

ScrollSpy-yui-compressed.js

ScrollSpy-yui-compressed.js

212 ms

smoothscroll.js

smoothscroll.js

212 ms

topofthepage.js

topofthepage.js

286 ms

caption.js

caption.js

304 ms

jquery.min.js

jquery.min.js

719 ms

jquery-noconflict.js

jquery-noconflict.js

318 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

379 ms

script.min.js

script.min.js

411 ms

system.css

system.css

425 ms

layout.css

layout.css

575 ms

css

css

23 ms

system.css

system.css

104 ms

de.gif

de.gif

101 ms

en.gif

en.gif

136 ms

home-quad-1.jpg

home-quad-1.jpg

137 ms

home-quad-2.jpg

home-quad-2.jpg

311 ms

home-quad-3.jpg

home-quad-3.jpg

222 ms

home-quad-4.jpg

home-quad-4.jpg

198 ms

ico_facebook.png

ico_facebook.png

204 ms

ico_twitter.png

ico_twitter.png

208 ms

ico_google_plus.png

ico_google_plus.png

215 ms

ico_rss.png

ico_rss.png

299 ms

analytics.js

analytics.js

32 ms

color_top.jpg

color_top.jpg

470 ms

thomas_hummel.jpg

thomas_hummel.jpg

181 ms

home-sottoquad-1.jpg

home-sottoquad-1.jpg

186 ms

home-sottoquad-2.jpg

home-sottoquad-2.jpg

195 ms

home-sottoquad-3.jpg

home-sottoquad-3.jpg

351 ms

home-sottoquad-4.jpg

home-sottoquad-4.jpg

283 ms

overlay.png

overlay.png

289 ms

collect

collect

11 ms

Accessibility Review

thomashummel.net accessibility score

96

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

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.

Best Practices

thomashummel.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Browser errors were logged to the console

SEO Factors

thomashummel.net SEO score

98

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

thomashummel.net

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