6 sec in total
400 ms
4.7 sec
912 ms
Welcome to madpotato.de homepage info - get ready to check Madpotato best content right away, or after learning these important things about madpotato.de
I unlock the potential of Creative Coding and Generative Design for brands, agencies and cultural institutions.
Visit madpotato.deWe analyzed Madpotato.de page load time and found that the first response time was 400 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
madpotato.de performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value3.0 s
78/100
25%
Value3.5 s
88/100
10%
Value0 ms
100/100
30%
Value0.027
100/100
15%
Value3.0 s
95/100
10%
400 ms
1334 ms
214 ms
337 ms
221 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Madpotato.de, 81% (74 requests) were made to Patrik-huebner.com and 13% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Patrik-huebner.com.
Page size can be reduced by 2.3 MB (47%)
5.0 MB
2.6 MB
In fact, the total size of Madpotato.de main page is 5.0 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. 70% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 61.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. 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 61.8 kB or 86% of the original size.
Potential reduce by 26.1 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. Madpotato images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 70% of the original size.
Potential reduce by 1.1 MB
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. Madpotato.de needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 90% of the original size.
Number of requests can be reduced by 44 (59%)
75
31
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Madpotato. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
madpotato.de
400 ms
www.patrik-huebner.com
1334 ms
wp-emoji-release.min.js
214 ms
styles.css
337 ms
style.css
221 ms
plugins.min.css
263 ms
modules.min.css
384 ms
font-awesome.min.css
331 ms
style.min.css
381 ms
ionicons.min.css
340 ms
style.css
408 ms
simple-line-icons.css
576 ms
dripicons.css
438 ms
blog.min.css
445 ms
mediaelementplayer.min.css
579 ms
wp-mediaelement.css
576 ms
style_dynamic.php
1086 ms
modules-responsive.min.css
542 ms
blog-responsive.min.css
548 ms
style_dynamic_responsive.php
1154 ms
js_composer.min.css
1029 ms
css
57 ms
style.css
677 ms
jquery.js
832 ms
jquery-migrate.min.js
706 ms
jquery.form.min.js
802 ms
scripts.js
810 ms
core.min.js
926 ms
widget.min.js
925 ms
tabs.min.js
1080 ms
accordion.min.js
1079 ms
mouse.min.js
1079 ms
slider.min.js
1132 ms
mediaelement-and-player.min.js
1497 ms
wp-mediaelement.js
1135 ms
third-party.min.js
1937 ms
isotope.pkgd.min.js
1466 ms
smoothPageScroll.js
1405 ms
js
46 ms
modules.min.js
1488 ms
blog.min.js
1049 ms
comment-reply.min.js
1149 ms
js_composer_front.js
1265 ms
like.js
1189 ms
wp-embed.min.js
1247 ms
waypoints.min.js
1402 ms
style.css
930 ms
Logo-03.jpg
247 ms
title-pattern.png
692 ms
howScannersWork-widescreen-04.jpg
245 ms
howScannersWork-cover-1000-03.jpg
690 ms
coverHighres-500x1000.jpg
690 ms
generativeCreatures-cover-poster-1000.jpg
691 ms
KoiSession-cover-1000.jpg
692 ms
3dinteractiveWave-cover.jpg
723 ms
cover-1000-4.jpg
715 ms
cover-1000.jpg
830 ms
audioLoop-1-cover-2.jpg
714 ms
generativePhysicsSystem-cover.jpg
730 ms
generativeStarWars-shapes-cover-1000.jpg
843 ms
mcccDecember-cover-1000.jpg
814 ms
experimentsIn3D-cover-1000.jpg
827 ms
blog-300x206.jpg
1038 ms
goodVibes-cover-1000.jpg
878 ms
muensterRehearsal-cover-1000.jpg
937 ms
theaterPaderborn-02-1.jpg
1047 ms
qA-respi.jpg
1213 ms
morphinVectorParticles-cover-1000-120x120.jpg
946 ms
mcccDecember-cover-1000-120x120.jpg
983 ms
codingInTheWoods-cover-1000-120x120.jpg
1042 ms
MCCC-02-cover-120x120.jpg
1052 ms
randomMovement-cover-1000-02-120x120.jpg
1087 ms
cover-1000-4-120x120.jpg
1141 ms
generativeShapePoster-cover-1000-1-120x120.jpg
1147 ms
generativeCreatures-cover-poster-1000-120x120.jpg
1149 ms
xjAJXh38I15wypJXxuGMBl02b4v3fUxqf9CZJ1qUoIA.ttf
55 ms
PRmiXeptR36kaC0GEAetxvqEJM-AK1nFUafhVdytxUY.ttf
130 ms
PRmiXeptR36kaC0GEAetxmYImPRL1w80NlYTQ8LOqf4.ttf
152 ms
PRmiXeptR36kaC0GEAetxiBnJMIPt0VoltfALX9gDFQ.ttf
154 ms
PRmiXeptR36kaC0GEAetxk7Gbs5Oj9RrfpUUQRHsz5w.ttf
153 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
153 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
154 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
151 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
155 ms
EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf
153 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
154 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
154 ms
fontawesome-webfont.woff
1164 ms
ElegantIcons.woff
1193 ms
analytics.js
164 ms
collect
25 ms
madpotato.de accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
madpotato.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
madpotato.de SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Madpotato.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 Madpotato.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.
madpotato.de
Open Graph description is not detected on the main page of Madpotato. 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: