Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

throm.de

Immobilien Throm GmbH · seit 1962 in Karlsruhe und Ettlingen

Page Load Speed

2.2 sec in total

First Response

334 ms

Resources Loaded

1.7 sec

Page Rendered

169 ms

throm.de screenshot

About Website

Click here to check amazing Throm content. Otherwise, check out these important facts you probably never knew about throm.de

Dieter und Oliver Throm, Ihre Immobilienmakler seit 1962 in Karlsruhe und Ettlingen | Immobilien Throm GmbH - Karlstraße 142 - D-76137 Karlsruhe

Visit throm.de

Key Findings

We analyzed Throm.de page load time and found that the first response time was 334 ms and then it took 1.9 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

throm.de performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

throm.de

334 ms

throm.de

531 ms

style.css

120 ms

logo.png

327 ms

logo-claim.png

675 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that all of those requests were addressed to Throm.de and no external sources were called. The less responsive or slowest element that took the longest time to load (675 ms) belongs to the original domain Throm.de.

Page Optimization Overview & Recommendations

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

Content Size

311.6 kB

After Optimization

283.2 kB

In fact, the total size of Throm.de main page is 311.6 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. Images take 244.5 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 11.9 kB

  • Original 15.8 kB
  • After minification 15.8 kB
  • After compression 3.9 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 11.9 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 9.7 kB

  • Original 244.5 kB
  • After minification 234.8 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. Throm images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 5.3 kB

  • Original 44.0 kB
  • After minification 44.0 kB
  • After compression 38.8 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 5.3 kB or 12% of the original size.

CSS Optimization

-21%

Potential reduce by 1.6 kB

  • Original 7.3 kB
  • After minification 7.3 kB
  • After compression 5.7 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. Throm.de needs all CSS files to be minified and compressed as it can save up to 1.6 kB or 21% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

15

After Optimization

15

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Throm. According to our analytics all requests are already optimized.

Accessibility Review

throm.de accessibility score

100

Accessibility Issues

Best Practices

throm.de best practices score

83

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

SEO Factors

throm.de SEO score

96

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

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