7.6 sec in total
409 ms
6.1 sec
1.1 sec
Click here to check amazing Ge Ne Me content. Otherwise, check out these important facts you probably never knew about geneme.de
The GeNeMe 2023 will take place in Dresden from 13 to 15 September 2023 and will focus on online communities at the interface or from the point of view of several disciplines.
Visit geneme.deWe analyzed Geneme.de page load time and found that the first response time was 409 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
geneme.de performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value5.8 s
15/100
25%
Value9.8 s
10/100
10%
Value390 ms
69/100
30%
Value0.081
94/100
15%
Value5.5 s
70/100
10%
409 ms
870 ms
2229 ms
106 ms
317 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Geneme.de, 89% (42 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 (2.2 sec) relates to the external source Tu-dresden.de.
Page size can be reduced by 153.6 kB (37%)
411.9 kB
258.3 kB
In fact, the total size of Geneme.de main page is 411.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. 35% of websites need less resources to load. Images take 248.5 kB which makes up the majority of the site volume.
Potential reduce by 84.2 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 38.9 kB, which is 40% 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 84.2 kB or 86% of the original size.
Potential reduce by 25.0 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. Ge Ne Me 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 (41%)
37
22
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ge Ne Me. 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.
geneme.de
409 ms
870 ms
geneme
2229 ms
resourcejquery-cachekey-903596d734d9e891147108d415f0e53f.css
106 ms
themetud.theme.webcms2cssanonymous.min-cachekey-45eab503abd206b48144b97a1f13c9c1.css
317 ms
resourcecollective.js.leafletleaflet-cachekey-e7eb005aa8b37c67889af790f6e74de9.css
316 ms
resourceplone.formwidget.contenttreecontenttree-cachekey-32bd20fcd068b73b88de8e4a5467ec09.css
314 ms
themedefaultstyle-cachekey-5187e6a18c26bbe27f955e25790b9aa8.css
331 ms
resourcetud.addons.ma_lscr_mb_erunhide-cachekey-b9c8ec981d1d6d20676d7349a3a60017.css
333 ms
themetud.theme.webcms2jslibs.min-cachekey-f7b6be037412e86b2bbcdac15514583a.js
734 ms
jquery.highlightsearchterms-cachekey-af283690ac387083271da0b7fbfe8d8e.js
431 ms
resourcetud.boxes.webcmsjsboard-cachekey-dff5c0cf673e1a1eb99e93df3f0fdac9.js
536 ms
OpenLayers-cachekey-97cf23daebe895942a7f0f1a39460599.js
645 ms
themetud.theme.webcms2jsmodules.min-cachekey-54d560d08f375dd30d76d1d95a49317f.js
549 ms
resourcetud.datafilter.basemap_switch-cachekey-c5563c74a62075a8ee5d1eeba12d4173.js
446 ms
popupforms-cachekey-b604896962ffcb6cbce672343fe91c6e.js
537 ms
formUnload-cachekey-0cd309420e4ff95099a83af89f52a485.js
557 ms
unlockOnFormUnload-cachekey-e34aeb01a98e545173ae18749522be98.js
641 ms
flag-en.svg
189 ms
flag-de.svg
220 ms
tud-logo-white.svg
191 ms
border-main.png
218 ms
6b5d8ddf-9bad-4307-8eb5-676b2da4c82b.png
234 ms
61601873-59d1-4919-86f2-2d554533134f.png
226 ms
dbf78d7e-6124-4fbf-8c76-3729694d296e.jpeg
393 ms
da5a11fb-f140-42a9-ae85-8228dd9cf9d2.jpeg
279 ms
6b4bf5e0-daf6-4576-aa9f-f3acbe4097fd.jpeg
1240 ms
0a996cf7-ace6-4f05-972e-cfca1937adc1.png
1477 ms
0d557959-c64b-4d9d-9f9e-e96201f0db6b.jpeg
354 ms
782b7fc9-6398-4ccc-a712-43a90f57cc75.png
360 ms
be86c649-6b0e-4f87-a3c3-a444c70601d4.png
1593 ms
3c536c8e-5de7-438e-a6ad-0845f68e1ded.png
487 ms
5fa980b1-45b6-4d1e-805c-4cd8bb208a62.jpeg
490 ms
4540d7cf-68b5-40aa-8aa3-a59bb64f6f88.jpeg
514 ms
ef9dcba1-7b3c-4125-a36b-c15e99579e2b.jpeg
609 ms
tud-logo.svg
612 ms
sachsen-signet-gruen.svg
1520 ms
opensans-regular.woff
639 ms
opensans-light.woff
667 ms
opensans-semibold.woff
761 ms
opensans-bold.woff
815 ms
tud-icons.woff
880 ms
piwik.js
629 ms
piwik.js
670 ms
piwik.php
104 ms
piwik.php
133 ms
themetud.theme.webcms2cssprint.min-cachekey-475737b10d85af3c8d6bdaf1431704f7.css
108 ms
geneme.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
geneme.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
geneme.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 Geneme.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 Geneme.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.
geneme.de
Open Graph data is detected on the main page of Ge Ne Me. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: