10.8 sec in total
346 ms
10 sec
446 ms
Visit fovog.de now to see the best up-to-date FOVOG content and also check out these interesting facts you probably never knew about fovog.de
Monasteries and religious orders have been pioneers of social change for centuries. Nuns and monks, hermits, canons and many other representatives of spiritual forms of life formed a social elite as …
Visit fovog.deWe analyzed Fovog.de page load time and found that the first response time was 346 ms and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fovog.de performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value6.9 s
6/100
25%
Value8.8 s
15/100
10%
Value210 ms
89/100
30%
Value0.002
100/100
15%
Value5.6 s
69/100
10%
346 ms
3983 ms
1304 ms
105 ms
321 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fovog.de, 90% (47 requests) were made to Tu-dresden.de and 4% (2 requests) were made to Piwik.mz.tu-dresden.de. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source Tu-dresden.de.
Page size can be reduced by 193.6 kB (20%)
960.2 kB
766.6 kB
In fact, the total size of Fovog.de main page is 960.2 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. 50% of websites need less resources to load. Images take 807.9 kB which makes up the majority of the site volume.
Potential reduce by 72.9 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 28.3 kB, which is 33% 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 72.9 kB or 84% of the original size.
Potential reduce by 76.3 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. FOVOG images are well optimized though.
Potential reduce by 44.4 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 44.4 kB or 67% of the original size.
Number of requests can be reduced by 15 (36%)
42
27
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FOVOG. 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 7 to 1 for CSS and as a result speed up the page load time.
fovog.de
346 ms
3983 ms
fovog
1304 ms
resourcejquery-cachekey-903596d734d9e891147108d415f0e53f.css
105 ms
themetud.theme.webcms2cssanonymous.min-cachekey-45eab503abd206b48144b97a1f13c9c1.css
321 ms
resourcecollective.js.leafletleaflet-cachekey-e7eb005aa8b37c67889af790f6e74de9.css
320 ms
resourceplone.formwidget.contenttreecontenttree-cachekey-32bd20fcd068b73b88de8e4a5467ec09.css
353 ms
themedefaultstyle-cachekey-5187e6a18c26bbe27f955e25790b9aa8.css
351 ms
resourcetud.addons.ma_lscr_mb_erunhide-cachekey-b9c8ec981d1d6d20676d7349a3a60017.css
356 ms
themetud.theme.webcms2jslibs.min-cachekey-f7b6be037412e86b2bbcdac15514583a.js
734 ms
jquery.highlightsearchterms-cachekey-af283690ac387083271da0b7fbfe8d8e.js
422 ms
resourcetud.boxes.webcmsjsboard-cachekey-dff5c0cf673e1a1eb99e93df3f0fdac9.js
530 ms
OpenLayers-cachekey-97cf23daebe895942a7f0f1a39460599.js
845 ms
themetud.theme.webcms2jsmodules.min-cachekey-54d560d08f375dd30d76d1d95a49317f.js
532 ms
resourcetud.datafilter.basemap_switch-cachekey-c5563c74a62075a8ee5d1eeba12d4173.js
445 ms
popupforms-cachekey-b604896962ffcb6cbce672343fe91c6e.js
528 ms
formUnload-cachekey-0cd309420e4ff95099a83af89f52a485.js
556 ms
unlockOnFormUnload-cachekey-e34aeb01a98e545173ae18749522be98.js
630 ms
flag-en.svg
1117 ms
flag-de.svg
319 ms
tud-logo-white.svg
1120 ms
border-main.png
132 ms
fee56f30-ee38-44d6-9c09-4e9f7a14d96a.jpeg
417 ms
bd178464-c640-4237-bccf-d65bd04722aa.png
780 ms
d638dbf4-34db-4b62-bbf4-111aa72a94de.png
566 ms
4760d8c4-475c-46ef-bc90-c4de6944ea98.jpeg
1396 ms
764b75b6-b848-4053-8c5c-e3dcccf5e4af.jpeg
1093 ms
389b78a6-5f3c-4792-b4e4-abde76f50324.jpeg
1802 ms
1effc83a-d7fc-4c5e-a5bb-c29ba133e890.jpeg
900 ms
d6c433fc-df7b-4bb3-8e52-3bf5423522f7.png
1127 ms
eb88dab8-b187-40de-9c38-d02959d456ad.png
3334 ms
ed2fae81-ad15-40a3-9ea1-1be50c679d9a.jpeg
1343 ms
0f802e98-128d-435e-9c18-1ee0c552307d.jpeg
1251 ms
b8157c52-0492-4d6e-88b0-44021496510c.jpeg
2589 ms
c0fa25b3-9eee-412f-a6ab-83d6a5a6eea0.jpeg
2505 ms
ba748c7c-988f-4daa-81c6-ca023388e0d5.jpeg
1857 ms
78b46d62-ab0c-475d-9ff7-481a3964de73.png
1518 ms
bd125ce7-2c64-4255-b5f7-4647e748ce30.png
1831 ms
d173df93-a77f-4b8a-9000-aef8842d20a4.png
2109 ms
ae51ba09-44ea-4bed-8b6c-f06ea1624c3c.jpeg
1954 ms
tud-logo.svg
2108 ms
sachsen-signet-gruen.svg
2087 ms
opensans-regular.woff
2097 ms
opensans-light.woff
2487 ms
opensans-semibold.woff
2837 ms
opensans-bold.woff
2230 ms
tud-icons.woff
2901 ms
piwik.js
643 ms
piwik.js
633 ms
piwik.php
107 ms
piwik.php
129 ms
themetud.theme.webcms2cssprint.min-cachekey-475737b10d85af3c8d6bdaf1431704f7.css
106 ms
fovog.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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
fovog.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
fovog.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fovog.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fovog.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.
fovog.de
Open Graph data is detected on the main page of FOVOG. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: