Tools & Wizards About Us
gbf-estate.de screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

gbf-estate.de

Domain Default page

Page Load Speed

2.8 sec in total

First Response

398 ms

Resources Loaded

2.2 sec

Page Rendered

212 ms

gbf-estate.de screenshot

About Website

Click here to check amazing Gbf Estate content. Otherwise, check out these important facts you probably never knew about gbf-estate.de

Visit gbf-estate.de

Key Findings

We analyzed Gbf-estate.de page load time and found that the first response time was 398 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

gbf-estate.de performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value2.9 s

94/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

gbf-estate.de

398 ms

style.css

98 ms

analytics.js

12 ms

K_07baafbc2d1345b08e8ad5d8ff9f8296.jpg

447 ms

K_0cc839cc9fcc4af0a5e4a4913eb543ee.jpg

458 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 42% of them (10 requests) were addressed to the original Gbf-estate.de, 50% (12 requests) were made to Agbf.com and 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Agbf.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 118.3 kB (21%)

Content Size

553.1 kB

After Optimization

434.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 16.5 kB

  • Original 19.0 kB
  • After minification 13.9 kB
  • After compression 2.5 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 5.1 kB, which is 27% 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 16.5 kB or 87% of the original size.

Image Optimization

-14%

Potential reduce by 67.3 kB

  • Original 477.7 kB
  • After minification 410.4 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, Gbf Estate needs image optimization as it can save up to 67.3 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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 32.0 kB or 60% of the original size.

CSS Optimization

-70%

Potential reduce by 2.5 kB

  • Original 3.6 kB
  • After minification 3.1 kB
  • After compression 1.1 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. Gbf-estate.de needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 70% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

23

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gbf-estate.de

gbf-estate.de

398 ms

style.css

style.css

98 ms

analytics.js

analytics.js

12 ms

K_07baafbc2d1345b08e8ad5d8ff9f8296.jpg

K_07baafbc2d1345b08e8ad5d8ff9f8296.jpg

447 ms

K_0cc839cc9fcc4af0a5e4a4913eb543ee.jpg

K_0cc839cc9fcc4af0a5e4a4913eb543ee.jpg

458 ms

K_84e0db74781d4b1daa2f8955244e5356.jpg

K_84e0db74781d4b1daa2f8955244e5356.jpg

463 ms

K_e06fa059ebc1445abb72a06464c709d4.jpg

K_e06fa059ebc1445abb72a06464c709d4.jpg

688 ms

K_010d01caa29a4ada93afa039e9569cca.jpg

K_010d01caa29a4ada93afa039e9569cca.jpg

464 ms

K_ca94e520d19d44029b1b25c80259e188.jpg

K_ca94e520d19d44029b1b25c80259e188.jpg

1701 ms

K_572de3d95bc349fa8b7559336809fd88.jpg

K_572de3d95bc349fa8b7559336809fd88.jpg

535 ms

K_73b98e3b92dc4030aacd85f869b5e914.jpg

K_73b98e3b92dc4030aacd85f869b5e914.jpg

556 ms

K_f8e7cb40f9634cbaaae36e15d03850e0.jpg

K_f8e7cb40f9634cbaaae36e15d03850e0.jpg

657 ms

K_f40c8c8f248f4c69a2291c35171981f9.jpg

K_f40c8c8f248f4c69a2291c35171981f9.jpg

661 ms

K_ae86a6a74e0b4e3589bf920a04a48429.jpg

K_ae86a6a74e0b4e3589bf920a04a48429.jpg

718 ms

K_d637a42d88794d2d8ebbf513503d8c1d.JPG

K_d637a42d88794d2d8ebbf513503d8c1d.JPG

748 ms

header.jpg

header.jpg

192 ms

image-1.jpg

image-1.jpg

298 ms

image-2.jpg

image-2.jpg

201 ms

image-3.jpg

image-3.jpg

296 ms

image-4.jpg

image-4.jpg

297 ms

zoom_ico.png

zoom_ico.png

201 ms

luxury_portfolio.jpg

luxury_portfolio.jpg

288 ms

leading_real_estate.jpg

leading_real_estate.jpg

298 ms

collect

collect

11 ms

Accessibility Review

gbf-estate.de accessibility score

95

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.

Best Practices

gbf-estate.de best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

gbf-estate.de SEO score

92

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gbf-estate.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Gbf-estate.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

gbf-estate.de

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