4.8 sec in total
325 ms
2.6 sec
1.9 sec
Welcome to tereg.de homepage info - get ready to check TEREG best content for Germany right away, or after learning these important things about tereg.de
Visit tereg.deWe analyzed Tereg.de page load time and found that the first response time was 325 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
tereg.de performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value3.3 s
69/100
25%
Value4.8 s
67/100
10%
Value200 ms
90/100
30%
Value0.014
100/100
15%
Value9.0 s
34/100
10%
325 ms
393 ms
618 ms
283 ms
373 ms
Our browser made a total of 21 requests to load all elements on the main page. We found that 86% of them (18 requests) were addressed to the original Tereg.de, 14% (3 requests) were made to Analyse.tereg.de. The less responsive or slowest element that took the longest time to load (618 ms) belongs to the original domain Tereg.de.
Page size can be reduced by 102.0 kB (46%)
220.9 kB
118.9 kB
In fact, the total size of Tereg.de main page is 220.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. HTML takes 115.4 kB which makes up the majority of the site volume.
Potential reduce by 101.8 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 32.7 kB, which is 28% 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 101.8 kB or 88% of the original size.
Potential reduce by 0 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. TEREG images are well optimized though.
Potential reduce by 187 B
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.
Number of requests can be reduced by 4 (31%)
13
9
The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TEREG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
tereg.de
325 ms
tereg.de
393 ms
www.tereg.de
618 ms
auw.bundle.css
283 ms
jquery.min.js
373 ms
vendor.bundle.js
561 ms
auw.bundle.js
188 ms
noncritical.bundle.css
469 ms
matomo.js
592 ms
container_G7cXWsCk.js
608 ms
logo-stage.svg
97 ms
logo.svg
94 ms
bg-schraege-blau.jpg
276 ms
Tereg_Logo.svg
185 ms
6fa0a8232f0352e4c0f8.ttf
394 ms
ba0c0a7588d6b4fc8fb7.ttf
385 ms
2006c9ff100617e95eb8.ttf
467 ms
881316d6d7081aee5419.ttf
577 ms
0601cf57e567a5aa17eb.ttf
292 ms
matomo.php
146 ms
print.bundle.css
94 ms
tereg.de accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[role] values are not valid
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
tereg.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
tereg.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
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 Tereg.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 Tereg.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.
tereg.de
Open Graph description is not detected on the main page of TEREG. 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: