3.3 sec in total
323 ms
2.3 sec
715 ms
Welcome to efbr.com homepage info - get ready to check EFBR best content right away, or after learning these important things about efbr.com
Visit efbr.comWe analyzed Efbr.com page load time and found that the first response time was 323 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
efbr.com performance score
name
value
score
weighting
Value1.7 s
92/100
10%
Value1.9 s
98/100
25%
Value2.2 s
99/100
10%
Value10 ms
100/100
30%
Value0.101
89/100
15%
Value1.8 s
100/100
10%
323 ms
825 ms
311 ms
314 ms
316 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that all of those requests were addressed to Efbr.com and no external sources were called. The less responsive or slowest element that took the longest time to load (825 ms) belongs to the original domain Efbr.com.
Page size can be reduced by 96.4 kB (17%)
561.5 kB
465.1 kB
In fact, the total size of Efbr.com main page is 561.5 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. 35% of websites need less resources to load. Images take 460.0 kB which makes up the majority of the site volume.
Potential reduce by 86.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. This page needs HTML code to be minified as it can gain 25.2 kB, which is 25% 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 86.7 kB or 85% of the original size.
Potential reduce by 9.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. EFBR images are well optimized though.
We found no issues to fix!
55
55
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EFBR. According to our analytics all requests are already optimized.
efbr.com
323 ms
efbr.com
825 ms
headline2003.gif
311 ms
Prisma_Bild_End.jpg
314 ms
Schaltflaeche-Home%20DR_r2_c2.gif
316 ms
Schaltflaeche-Unser%20Unternehmen%20DR_r2_c2.gif
315 ms
Schaltflaeche-%20PublikationenDR_r2_c2.gif
317 ms
Schaltflaeche-ProjekteDR_r2_c2.gif
413 ms
Schaltflaeche-PatenteDR_r2_c2.gif
416 ms
Schaltflaeche-KontaktDR_r2_c2.gif
417 ms
Schaltflaeche-Speakers_r2_c2.gif
417 ms
Schaltflaeche-RecordingDR_r2_c2.gif
417 ms
Photonshock.gif
494 ms
logo_header_panosound_small.jpg
421 ms
cd_pres_3_small_2.JPG
522 ms
cd_pres_2_small_2.JPG
623 ms
cd_pres_1_small_2.JPG
523 ms
cd_pres_4_small_2.JPG
525 ms
be_small2.jpg
302 ms
praesention_freudenstadt_2.gif
419 ms
praesention_freudenstadt.gif
404 ms
Hoerraum-small.gif
456 ms
Hoertest-2.gif
472 ms
Hoertest-1.gif
573 ms
ErlangerNr_banner.gif
573 ms
131203_Foto_LS_Web.JPG
677 ms
Kirche_3.gif
558 ms
Kirche_2.gif
574 ms
spacer.gif
573 ms
Formel.gif
662 ms
spacer.gif
675 ms
frank_04%20small.JPG
628 ms
Gebrauchmuster_LS-DR-Compact.JPG
726 ms
Schaltflaeche-Speakers_r2_c2_f3.gif
105 ms
Schaltflaeche-Speakers_r2_c2_f2.gif
105 ms
Schaltflaeche-Speakers_r2_c2_f4.gif
106 ms
Schaltflaeche-Home%20DR_r2_c2_f3.gif
106 ms
Schaltflaeche-Home%20DR_r2_c2_f2.gif
107 ms
Schaltflaeche-Home%20DR_r2_c2_f4.gif
106 ms
Schaltflaeche-Unser%20Unternehmen%20DR_r2_c2_f3.gif
217 ms
Schaltflaeche-Unser%20Unternehmen%20DR_r2_c2_f2.gif
218 ms
Schaltflaeche-Unser%20Unternehmen%20DR_r2_c2_f4.gif
218 ms
Schaltflaeche-%20PublikationenDR_r2_c2_f3.gif
219 ms
Schaltflaeche-%20PublikationenDR_r2_c2_f2.gif
219 ms
Schaltflaeche-%20PublikationenDR_r2_c2_f4.gif
218 ms
Schaltflaeche-ProjekteDR_r2_c2_f3.gif
320 ms
Schaltflaeche-ProjekteDR_r2_c2_f2.gif
319 ms
Schaltflaeche-ProjekteDR_r2_c2_f4.gif
320 ms
Schaltflaeche-PatenteDR_r2_c2_f3.gif
320 ms
Schaltflaeche-PatenteDR_r2_c2_f2.gif
321 ms
Schaltflaeche-PatenteDR_r2_c2_f4.gif
321 ms
Schaltflaeche-KontaktDR_r2_c2_f3.gif
421 ms
Schaltflaeche-KontaktDR_r2_c2_f2.gif
422 ms
Schaltflaeche-KontaktDR_r2_c2_f4.gif
423 ms
Schaltflaeche-RecordingDR_r2_c2_f3.gif
424 ms
Schaltflaeche-RecordingDR_r2_c2_f2.gif
423 ms
Schaltflaeche-RecordingDR_r2_c2_f4.gif
423 ms
efbr.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
efbr.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
efbr.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
DE
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Efbr.com can be misinterpreted by Google and other search engines. Our service has detected that German 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 Efbr.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
efbr.com
Open Graph description is not detected on the main page of EFBR. 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: