diff --git a/README.md b/README.md
index 3031556..508c0ce 100644
--- a/README.md
+++ b/README.md
@@ -26,7 +26,7 @@ Building and deploying such a RJSVM powered website with a client-based renderin
 
 An lot of engineering with [webpack](https://www.npmjs.com/package/webpack) later a functional prototype was created, and the very first fully blockchain-sourced website went live. You can view it under [caisar.github.io](https://caisar.github.io).
 
-<img src="https://i.imgur.com/7xH7oVX.jpg" alt="httXrp shoutbox" style="width:50%;height:50%"/>
+<img src="https://i.imgur.com/7xH7oVX.jpg" alt="httXrp shoutbox" style="width:400px"/>
 
 ## Next steps
 
@@ -34,7 +34,7 @@ The above proof of concept has one obvious weakness: browsers don't natively spe
 
 A prototype is available here: [The Tür browser](https://gitea.nitowa.xyz/nitowa/tur-browser/src/branch/master). 
 
-<img src="https://i.imgur.com/s1iuQme.png" alt="httXrp shoutbox" style="width:50%;height:50%"/>
+<img src="https://i.imgur.com/s1iuQme.png" alt="httXrp shoutbox" style="width:400px"/>
 
 As the name heavily implies, the project is somewhat inspired by Tor. While Tor allows traffic to be masked completely, the hidden services themselves are a undeniable weakpoint, that once compromised allow an attacker to turn them into honeypots. Tür on the other hand makes very little effort to mask traffic (it is readable via the blockchanin by anyone) but the "server" is replicated on each Ripple (history)node, making it effectively uncensorable/impossible to capture without breaking the promises the blockchain itself makes (i.e. immutability of persisted transactions).