2.5 sec in total
361 ms
2 sec
186 ms
Welcome to tinnitus.de homepage info - get ready to check Tinnitus best content for Germany right away, or after learning these important things about tinnitus.de
auric-direct bietet Ihnen die moderne Hörgeräteversorgung über den verkürzten Versorgungsweg. Finden Sie jetzt eine kooperierende HNO-Praxis!
Visit tinnitus.deWe analyzed Tinnitus.de page load time and found that the first response time was 361 ms and then it took 2.2 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.
tinnitus.de performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value7.1 s
5/100
25%
Value5.9 s
48/100
10%
Value1,600 ms
12/100
30%
Value0.021
100/100
15%
Value9.9 s
27/100
10%
361 ms
127 ms
99 ms
190 ms
357 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 67% of them (29 requests) were addressed to the original Tinnitus.de, 9% (4 requests) were made to Pagead2.googlesyndication.com and 7% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (379 ms) belongs to the original domain Tinnitus.de.
Page size can be reduced by 140.5 kB (53%)
264.9 kB
124.5 kB
In fact, the total size of Tinnitus.de main page is 264.9 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. Javascripts take 158.0 kB which makes up the majority of the site volume.
Potential reduce by 45.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 45.3 kB or 82% of the original size.
Potential reduce by 890 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. Tinnitus images are well optimized though.
Potential reduce by 94.3 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 94.3 kB or 60% of the original size.
Number of requests can be reduced by 27 (73%)
37
10
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tinnitus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
tinnitus.de
361 ms
forum.php
127 ms
yuiloader-dom-event.js
99 ms
connection-min.js
190 ms
vbulletin-core.js
357 ms
css.php
379 ms
css
68 ms
jquery.min.js
74 ms
vbulletin_read_marker.js
267 ms
css.php
285 ms
css.php
289 ms
cookieconsent.latest.min.js
60 ms
vbulletin_md5.js
277 ms
show_ads.js
33 ms
RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf
85 ms
DXI1ORHCpsQm3Vp6mXoaTfOEPOIfcPv-fZ-WyMUtx48.ttf
115 ms
MTP_ySUJH_bn48VBG8sNSvOEPOIfcPv-fZ-WyMUtx48.ttf
115 ms
analytics.js
73 ms
search-button-bg.png
108 ms
close_popup.png
107 ms
vbulletin4_logo.png
95 ms
nav-icons-bg.png
95 ms
black_downward_arrow.png
97 ms
navbit-home.png
96 ms
Werbebanner-HAS_2.jpg
245 ms
notice-exclamation.png
160 ms
collapse_40b.png
176 ms
forum_old-48.png
176 ms
lastpost-right.png
180 ms
users_online.png
182 ms
forum_stats.png
248 ms
legend.png
264 ms
forum_new-16.png
264 ms
forum_old-16.png
269 ms
category-16.png
273 ms
forum_link-16.png
332 ms
cron.php
345 ms
ca-pub-0155026572592782.js
115 ms
zrt_lookup.html
32 ms
show_ads_impl.js
70 ms
collect
30 ms
ads
294 ms
osd.js
3 ms
tinnitus.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
tinnitus.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
tinnitus.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 uses legible font sizes
DE
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tinnitus.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 Tinnitus.de main page’s claimed encoding is iso-8859-1. 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.
tinnitus.de
Open Graph description is not detected on the main page of Tinnitus. 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: