diff --git a/README.md b/README.md
index dd21ca3868b85..d2a671d189c61 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,5 @@
+![headline](headline.png)
+
 # [Backstage](https://backstage.io)
 
 [![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
@@ -11,13 +13,11 @@ Backstage is an open platform for building developer portals.
 
 The philosophy behind Backstage is simple: Don't expose your engineers to the full complexity of your infrastructure tooling. Engineers should be shipping code — not figuring out a whole new toolset every time they want to implement the basics. Backstage allows you add "stuff" (tooling, services, features, etc.) by adding a plugin, instead of building a new tool. This saves you work and avoids the need of your team to learn how to use and support yet another tool.
 
-![headline](headline.png)
-
 For more information go to [backstage.io](https://backstage.io)
 
 ## What problem does Backstage solve?
 
-As companies grow, their infrastructure systems get messier. Backstage unifies all your infrastructure tooling, services, and documentation with a single, consistent UI. 
+As companies grow, their infrastructure systems get messier. Backstage unifies all your infrastructure tooling, services, and documentation with a single, consistent UI.
 
 This blog post provides more examples of how Backstage is used inside Spotify:
 
diff --git a/headline.png b/headline.png
index 063f5be00bd51..b0f9cb8b5c103 100644
Binary files a/headline.png and b/headline.png differ