7.3 sec in total
563 ms
2.3 sec
4.4 sec
Visit internetgenie.de now to see the best up-to-date Internetgenie content and also check out these interesting facts you probably never knew about internetgenie.de
Neuigkeiten, Trends und geniale Einfälle aus dem Internet.
Visit internetgenie.deWe analyzed Internetgenie.de page load time and found that the first response time was 563 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
internetgenie.de performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value3.7 s
58/100
25%
Value8.1 s
21/100
10%
Value3,060 ms
2/100
30%
Value0.015
100/100
15%
Value20.6 s
2/100
10%
563 ms
27 ms
37 ms
40 ms
32 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Internetgenie.de, 20% (25 requests) were made to 38.media.tumblr.com and 19% (23 requests) were made to 33.media.tumblr.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source 38.media.tumblr.com.
Page size can be reduced by 946.7 kB (13%)
7.3 MB
6.3 MB
In fact, the total size of Internetgenie.de main page is 7.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.2 MB which makes up the majority of the site volume.
Potential reduce by 72.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 72.6 kB or 70% of the original size.
Potential reduce by 211.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. Internetgenie images are well optimized though.
Potential reduce by 460.1 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 460.1 kB or 63% of the original size.
Potential reduce by 203.0 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. Internetgenie.de needs all CSS files to be minified and compressed as it can save up to 203.0 kB or 83% of the original size.
Number of requests can be reduced by 34 (30%)
115
81
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Internetgenie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
www.internetgenie.de
563 ms
pre_tumblelog.js
27 ms
css
37 ms
tumblr-endless-scroll.js
40 ms
tumblelog_post_message_queue.js
32 ms
stylesheet.css
33 ms
index.js
148 ms
tumblr_inline_mohghtubX81qz4rgp.jpg
397 ms
tumblr_inline_mohgiyoCJO1qz4rgp.jpg
224 ms
tumblr_inline_mohgk51haV1qz4rgp.jpg
252 ms
false
251 ms
tumblr_mi5nnxkZcH1qjl9gno1_500.jpg
875 ms
plusone.js
397 ms
ga.js
194 ms
impixu
416 ms
anonymous_avatar_24.gif
175 ms
tumblr_mggjru4irB1rdymz1o1_500.jpg
526 ms
tumblr_inline_mjr6a63cML1qz4rgp.jpg
210 ms
tumblr_inline_mjyobubs7W1qz4rgp.jpg
292 ms
tumblr_menognyHbT1qd5mwd.jpg
289 ms
tumblr_me0iipdeMg1qiwu42.jpg
292 ms
tumblr_me0hooY6j91qiwu42.jpg
292 ms
tumblr_me0g07R4Gz1qiwu42.jpg
289 ms
tumblr_inline_mohgc2gI8g1qz4rgp.jpg
415 ms
tumblr_inline_mohgj5vS0c1qz4rgp.jpg
396 ms
tumblr_inline_mjr687Te9J1qz4rgp.jpg
368 ms
tumblr_inline_mjr69hWiIh1qz4rgp.jpg
395 ms
tumblr_inline_mjyo25Gijk1qz4rgp.jpg
510 ms
tumblr_inline_mjyo39HRyw1qz4rgp.jpg
719 ms
tumblr_inline_mjyo64z2V51qz4rgp.jpg
509 ms
tumblr_inline_mjyoaibSsU1qz4rgp.jpg
713 ms
tumblr_inline_mjyp9jc8WM1qz4rgp.jpg
554 ms
tumblr_me056042JB1qiwu42.jpg
516 ms
tumblr_me0f6rRMZA1qiwu42.jpg
714 ms
tumblr_me0ija4lo21qiwu42.jpg
736 ms
tumblr_me0igrgR1o1qiwu42.jpg
928 ms
tumblr_me0hu8zaIJ1qiwu42.jpg
739 ms
tumblr_me0g3oGZDE1qiwu42.jpg
935 ms
tumblr_me0f2hNZkS1qiwu42.jpg
935 ms
tumblr_me0fdt7VNo1qiwu42.jpg
935 ms
tumblr_me0fcgwkhv1qiwu42.jpg
934 ms
tumblr_me0evfG1ZM1qiwu42.jpg
1404 ms
tumblr_me0fxdLBLl1qiwu42.jpg
983 ms
tumblr_me0f5je3vR1qiwu42.jpg
1069 ms
tumblr_maichhQufE1qiwu42.jpg
1011 ms
avatar_c38650a39e2a_48.png
1025 ms
tumblr_inline_mjr67mjG0t1qz4rgp.jpg
273 ms
tumblr_inline_mjr68tLPL61qz4rgp.jpg
276 ms
tumblr_inline_mjynus3FLL1qz4rgp.jpg
275 ms
tumblr_inline_mjynx7B16g1qz4rgp.jpg
361 ms
tumblr_inline_mjyo04Hp3x1qz4rgp.jpg
362 ms
tumblr_inline_mjyo1dzf8k1qz4rgp.jpg
323 ms
tumblr_inline_mjyo53uklf1qz4rgp.jpg
322 ms
tumblr_inline_mjyob5yNJM1qz4rgp.jpg
320 ms
tumblr_inline_mjyp8gdweb1qz4rgp.jpg
320 ms
tumblr_me0fviLjl31qiwu42.jpg
381 ms
tumblr_me0hkrlkPV1qiwu42.jpg
377 ms
tumblr_me0g6xLUtf1qiwu42.jpg
376 ms
tumblr_me0g5uAZWh1qiwu42.jpg
368 ms
tumblr_me0fyiLp7A1qiwu42.jpg
429 ms
tumblr_me0fnydCrX1qiwu42.jpg
996 ms
tumblr_me0frjJkTM1qiwu42.jpg
386 ms
tumblr_me0ewokI331qiwu42.jpg
389 ms
tumblr_me0iheVZ091qiwu42.jpg
389 ms
tumblr_me0ihyGhKt1qiwu42.jpg
497 ms
tumblr_me0ik5t5ar1qiwu42.jpg
441 ms
tumblr_me0ikt5FAz1qiwu42.jpg
422 ms
tumblr_mblbm2B4fH1qiwu42.jpg
420 ms
simplethings-header-bg.png
175 ms
simplethings-rss-btn.png
307 ms
simplethings-rss-icon.png
307 ms
simplethings-search-full.png
308 ms
simplethings-date-flag.png
307 ms
simplethings-clock.png
336 ms
simplethings-tags.png
257 ms
simplethings-question-top-blue.png
260 ms
simplethings-question-bg-blue.png
335 ms
simplethings-question-bottom-blue.png
337 ms
simplethings-reblogged.png
336 ms
simplethings-page-btn.png
335 ms
simplethings-user-pic.png
335 ms
impixu
371 ms
analytics.html
484 ms
rdIWKytq_q4
229 ms
QfV7lyOjR7g
343 ms
q6atTwPf2U4
342 ms
0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf
121 ms
FUDHvzEKSJww3kCxuiAo2A.ttf
122 ms
PIPMHY90P7jtyjpXuZ2cLKCWcynf_cDxXwCLxiixG1c.ttf
169 ms
lILlYDvubYemzYzN7GbLkInF5uFdDttMLvmWuJdhhgs.ttf
168 ms
login_check.html
36 ms
__utm.gif
97 ms
tumblr_mitmr5cPmM1qjl9gno10_500.jpg
141 ms
tumblr_mitmr5cPmM1qjl9gno2_250.jpg
523 ms
tumblr_mitmr5cPmM1qjl9gno3_250.jpg
523 ms
tumblr_mitmr5cPmM1qjl9gno4_500.jpg
737 ms
tumblr_mitmr5cPmM1qjl9gno5_250.jpg
179 ms
tumblr_mitmr5cPmM1qjl9gno9_250.jpg
177 ms
tumblr_mitmr5cPmM1qjl9gno8_250.jpg
633 ms
tumblr_mitmr5cPmM1qjl9gno1_250.jpg
248 ms
tumblr_mitmr5cPmM1qjl9gno7_250.jpg
248 ms
tumblr_mitmr5cPmM1qjl9gno6_250.jpg
521 ms
init
305 ms
avatar_c38650a39e2a_40.png
709 ms
iframe_logo.png
273 ms
cb=gapi.loaded_0
26 ms
www-embed-player-vflfNyN_r.css
61 ms
www-embed-player.js
84 ms
base.js
175 ms
ga.js
214 ms
rapid-3.36.js
230 ms
rapidworker-1.2.js
237 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
82 ms
ad_status.js
88 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
37 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
53 ms
__utm.gif
32 ms
analytics.js
181 ms
cs.js
183 ms
__utm.gif
148 ms
yql
227 ms
cedexis.radar.js
5 ms
internetgenie.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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
internetgenie.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
internetgenie.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Internetgenie.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Internetgenie.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.
internetgenie.de
Open Graph data is detected on the main page of Internetgenie. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: