3.4 sec in total
476 ms
2.8 sec
189 ms
Welcome to goettingen.de homepage info - get ready to check Goettingen best content for Germany right away, or after learning these important things about goettingen.de
Startseite Internet
Visit goettingen.deWe analyzed Goettingen.de page load time and found that the first response time was 476 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
goettingen.de performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value6.8 s
7/100
25%
Value11.2 s
5/100
10%
Value6,320 ms
0/100
30%
Value0.936
3/100
15%
Value13.4 s
11/100
10%
476 ms
381 ms
285 ms
381 ms
664 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 96% of them (46 requests) were addressed to the original Goettingen.de, 4% (2 requests) were made to Tagesforum.de. The less responsive or slowest element that took the longest time to load (862 ms) belongs to the original domain Goettingen.de.
Page size can be reduced by 327.5 kB (37%)
885.8 kB
558.3 kB
In fact, the total size of Goettingen.de main page is 885.8 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. 25% of websites need less resources to load. Images take 441.1 kB which makes up the majority of the site volume.
Potential reduce by 47.6 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 47.6 kB or 84% of the original size.
Potential reduce by 84 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. Goettingen images are well optimized though.
Potential reduce by 275.7 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 275.7 kB or 72% of the original size.
Potential reduce by 4.2 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. Goettingen.de needs all CSS files to be minified and compressed as it can save up to 4.2 kB or 70% of the original size.
Number of requests can be reduced by 21 (45%)
47
26
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Goettingen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
index.php
476 ms
screen.css.php
381 ms
standards.css
285 ms
mobileesp.min.js
381 ms
jquery.min.js
664 ms
jquery-ui.min.js
855 ms
jquery_functions.js
290 ms
jquery.easing.min.js
379 ms
jquery.cw.listslider.js
385 ms
jquery.bxslider.js
514 ms
img_image_11640972272291.jpeg
190 ms
image_12161315546390.gif
100 ms
image_12161315451993.gif
101 ms
image_12179256339195.gif
104 ms
image_1225118638856.gif
104 ms
image_1310709145431.gif
103 ms
start.gif
193 ms
pfeil.gif
191 ms
ex_link.gif
195 ms
pfeil_uv.gif
195 ms
ticker.php
468 ms
ozon.php
337 ms
minus.gif
171 ms
normal.gif
259 ms
plus.gif
261 ms
u_vmenu.jpg
261 ms
image_1366796905300.jpeg
359 ms
image_1366797044953.jpeg
262 ms
image_1343809110779.jpeg
262 ms
image_126467513824.jpeg
541 ms
image_1361893126599.jpeg
486 ms
image_1413879482282.jpeg
356 ms
container_lp.gif
360 ms
pfeil_green.gif
360 ms
image_1377692709191.jpeg
640 ms
image_1455188557343.jpeg
639 ms
image_144603978032.jpeg
585 ms
image_1420469666684.jpeg
454 ms
image_1290515150580.jpeg
550 ms
image_1430315280719.jpeg
673 ms
big_image_11688664478259.jpeg
862 ms
ex_link_schwarz.gif
646 ms
ex_link_weiss.gif
679 ms
footer.jpg
734 ms
anker.gif
735 ms
ozonalarm_nowarning.gif
191 ms
161184174759.gif
218 ms
print.css.php
98 ms
goettingen.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
goettingen.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
goettingen.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Goettingen.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 Goettingen.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.
goettingen.de
Open Graph description is not detected on the main page of Goettingen. 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: