3.3 sec in total
327 ms
2.4 sec
629 ms
Visit telefonbuch.de now to see the best up-to-date Telefon Buch content for Germany and also check out these interesting facts you probably never knew about telefonbuch.de
Rufnummern & Adressen finden ✓ über 30 Mio. Einträge ✓ von Personen, Firmen u. a. m. ✓ Deutschlands beliebtes Adressbuch. Jetzt Adressauskunft nutzen!
Visit telefonbuch.deWe analyzed Telefonbuch.de page load time and found that the first response time was 327 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.
telefonbuch.de performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value3.7 s
59/100
25%
Value5.7 s
51/100
10%
Value190 ms
91/100
30%
Value0
100/100
15%
Value6.1 s
63/100
10%
327 ms
255 ms
28 ms
529 ms
665 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Telefonbuch.de, 33% (18 requests) were made to Medien.dastelefonbuch.de and 31% (17 requests) were made to Image.dastelefonbuch.de. The less responsive or slowest element that took the longest time to load (665 ms) relates to the external source Medien.dastelefonbuch.de.
Page size can be reduced by 162.2 kB (21%)
771.6 kB
609.4 kB
In fact, the total size of Telefonbuch.de main page is 771.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. 40% of websites need less resources to load. Images take 313.7 kB which makes up the majority of the site volume.
Potential reduce by 156.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. 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 156.5 kB or 78% of the original size.
Potential reduce by 43 B
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. Telefon Buch images are well optimized though.
Potential reduce by 1.6 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.
Potential reduce by 4.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. Telefonbuch.de has all CSS files already compressed.
Number of requests can be reduced by 13 (25%)
52
39
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Telefon Buch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
telefonbuch.de
327 ms
www.dastelefonbuch.de
255 ms
application_desktop_start-4980c18abd95f0e3cf33bdb4839bfb69.css
28 ms
cms_flexbox.css
529 ms
offer.css
665 ms
tb_ladeanimation-f892ff65d22da0685ac71299c5331b52.js
48 ms
42-f540009893b5e6a80d384697b17e40f7.js
46 ms
localStorageHandler-73b27ca4c3a58f97e860881afa7586b7.js
35 ms
loader.js
604 ms
wa.js
561 ms
style-2e53b4f9d37c6352d776d9b43e83e4a0.css
46 ms
cmp.min.css
185 ms
bundle_desktop_start_below_the_fold_new-e3ddb2edf1c2377f684e4d8ba493a20c.js
53 ms
bundle.js
204 ms
login-fa15f99cced5791eb1331b694a725ea6.svg
83 ms
startstage_2.jpg
133 ms
tsg_icon_newsletter_new-68e5d4b73325b3f56c21cf0edd01d51b.png
83 ms
top-berlin.jpg
158 ms
top-bochum.jpg
181 ms
top-bremen.jpg
185 ms
top-dortmund.jpg
181 ms
top-dresden.jpg
176 ms
top-duesseldorf.jpg
188 ms
top-duisburg.jpg
177 ms
top-essen.jpg
206 ms
top-frankfurt-am-main.jpg
190 ms
top-hamburg.jpg
208 ms
top-hannover.jpg
209 ms
top-koeln.jpg
211 ms
top-leipzig.jpg
210 ms
top-muenchen.jpg
213 ms
top-nuernberg.jpg
213 ms
top-stuttgart.jpg
216 ms
TB_Start_ts1.jpg.webp
80 ms
TB_Start_ts2.jpg.webp
85 ms
TB_Start_Privateintrag.jpg.webp
129 ms
benzin.jpg.webp
108 ms
TB_Start_Firmeneintrag.jpg.webp
110 ms
TB_Start_ts3.jpg.webp
103 ms
TB_Start_ts4.jpg.webp
108 ms
huawei.jpg.webp
105 ms
TB_teaser_Apple.jpg.webp
131 ms
TB_teaser_Google.jpg.webp
130 ms
TB_teaser_Alexa.jpg.webp
154 ms
messenger_TB_mauritius_images_2H8JY1G_485x355_72ppi_icons.png.webp
153 ms
start_kachel_alle_apps_neu.jpg.webp
153 ms
tsg_icon_appleMessage_sw.svg
244 ms
tsg_icon_android_Logo_sw.svg
581 ms
tsg_icon_apple_Logo_sw.svg
579 ms
cmp.php
475 ms
cmp_final.min.js
108 ms
tb_font-6634ce4567e1ca5f2370bbbeaf37d984.ttf
100 ms
bV8xLndfMTUwOTcucl9HRFBSLmxfZGUuZF8zMDY1MS54XzgwLnYucC50XzMwNjUxLnh0Xzgw.js
14 ms
crossdomain.html
15 ms
101 ms
telefonbuch.de 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
telefonbuch.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Page has valid source maps
telefonbuch.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Telefonbuch.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 Telefonbuch.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.
telefonbuch.de
Open Graph data is detected on the main page of Telefon Buch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: