Tools & Wizards About Us
thomashummel.net screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% 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.7 sec in total

First Response

333 ms

Resources Loaded

2.3 sec

Page Rendered

91 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 333 ms and then it took 2.4 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

thomashummel.net performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value6.5 s

38/100

10%

TBT (Total Blocking Time)

Value1,210 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.039

100/100

15%

TTI (Time to Interactive)

Value9.0 s

34/100

10%

Network Requests Diagram

de

333 ms

de

671 ms

1675678832_5e9d1b5783c840a30b3251592213d634.css

233 ms

digitest.css

336 ms

stylesheet.css

334 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Thomashummel.net, 22% (5 requests) were made to Gstatic.com and 17% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (692 ms) relates to the external source Contimbre.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 53.3 kB (9%)

Content Size

614.8 kB

After Optimization

561.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thomashummel.net main page is 614.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. 45% of websites need less resources to load. Javascripts take 383.8 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 24.4 kB

  • Original 32.6 kB
  • After minification 32.6 kB
  • After compression 8.3 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 24.4 kB or 75% of the original size.

Image Optimization

-11%

Potential reduce by 15.5 kB

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

JavaScript Optimization

-3%

Potential reduce by 10.4 kB

  • Original 383.8 kB
  • After minification 383.8 kB
  • After compression 373.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 3.0 kB

  • Original 61.6 kB
  • After minification 61.6 kB
  • After compression 58.6 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (59%)

Requests Now

17

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 17 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 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

de

de

333 ms

de

de

671 ms

1675678832_5e9d1b5783c840a30b3251592213d634.css

1675678832_5e9d1b5783c840a30b3251592213d634.css

233 ms

digitest.css

digitest.css

336 ms

stylesheet.css

stylesheet.css

334 ms

uc.js

uc.js

29 ms

1675678832_5e9d1b5783c840a30b3251592213d634.js

1675678832_5e9d1b5783c840a30b3251592213d634.js

692 ms

api.js

api.js

106 ms

conTimbre_website_background3_opt.jpg

conTimbre_website_background3_opt.jpg

279 ms

payment_logos.jpg

payment_logos.jpg

279 ms

auvst_logos.jpg

auvst_logos.jpg

278 ms

shopware.woff

shopware.woff

398 ms

recaptcha__de.js

recaptcha__de.js

22 ms

anchor

anchor

39 ms

styles__ltr.css

styles__ltr.css

4 ms

recaptcha__de.js

recaptcha__de.js

12 ms

Gar3GNXyGuEFKrsdSCNgV3EULqB3zePQrsysOZqpo_s.js

Gar3GNXyGuEFKrsdSCNgV3EULqB3zePQrsysOZqpo_s.js

42 ms

webworker.js

webworker.js

76 ms

logo_48.png

logo_48.png

29 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

55 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

56 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

60 ms

recaptcha__de.js

recaptcha__de.js

40 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

83

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

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 data is detected on the main page of Thomashummel. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: