diff --git a/layouts/css/_base.styl b/layouts/css/_base.styl
index 9c01c90cfd069..2b0d46b42ed18 100644
--- a/layouts/css/_base.styl
+++ b/layouts/css/_base.styl
@@ -34,8 +34,11 @@ a:hover
     background-color transparent
     color #fff
 
-a.imagelink:hover
-  background-color transparent
+a.imagelink
+  display inline-block
+
+  &:hover
+    background-color transparent
 
 strong,
 b
diff --git a/layouts/index.hbs b/layouts/index.hbs
index cda223ce0d3ac..f4c270c5863d9 100644
--- a/layouts/index.hbs
+++ b/layouts/index.hbs
@@ -12,6 +12,12 @@
 
         {{{ contents }}}
 
+        <p>
+          <a class="imagelink" href="https://events.linuxfoundation.org/events/js-interactive-2018/?utm_source=nodesite&utm_medium=homepagebanner&utm_campaign=jsint18&utm_term=eventpage">
+            <img src="/static/images/jsinteractive-2018-banner.png" alt="JS Interactive on October 10-12, 2018 in Vancouver, Canada">
+          </a>
+        </p>
+
         {{#if project.banner.visible}}
           <p class="home-version home-version-banner">
             <a href="{{ project.banner.link }}">{{#if project.banner.text}}{{{ project.banner.text }}}{{else}}{{{ labels.banner }}}{{/if}}</a>
diff --git a/layouts/partials/header.hbs b/layouts/partials/header.hbs
index 097ff3157de9f..d29e02b5ddb38 100644
--- a/layouts/partials/header.hbs
+++ b/layouts/partials/header.hbs
@@ -1,7 +1,7 @@
 <header>
   <div class="container">
 
-    <a href="/{{site.locale}}" id="logo">
+    <a href="/{{site.locale}}/" id="logo">
       <img src="/static/images/logo.svg" alt="node.js">
     </a>
 
diff --git a/locale/en/blog/uncategorized/profiling-node-js.md b/locale/en/blog/uncategorized/profiling-node-js.md
index c03b0b324827f..f23901f10fcdc 100644
--- a/locale/en/blog/uncategorized/profiling-node-js.md
+++ b/locale/en/blog/uncategorized/profiling-node-js.md
@@ -8,7 +8,7 @@ slug: profiling-node-js
 layout: blog-post.hbs
 ---
 
-It's incredibly easy to visualize where your Node program spends its time using DTrace and <a href="http://github.com/davepacheco/node-stackvis">node-stackvis</a> (a Node port of Brendan Gregg's <a href="http://github.com/brendangregg/FlameGraph/">FlameGraph</a> tool):
+It's incredibly easy to visualize where your Node program spends its time using DTrace and <a href="https://github.com/davepacheco/node-stackvis">node-stackvis</a> (a Node port of Brendan Gregg's <a href="https://github.com/brendangregg/FlameGraph/">FlameGraph</a> tool):
 
 <ol>
     <li>Run your Node.js program as usual.</li>
@@ -27,7 +27,7 @@ It's incredibly easy to visualize where your Node program spends its time using
 
 You'll be looking at something like this:
 
-<a href="https://www.cs.brown.edu/~dap/helloworld.svg" class="imagelink"><img src="https://www.cs.brown.edu/~dap/helloworld.svg" alt="'Hello World' HTTP server flame graph" /></a>
+<a href="https://cs.brown.edu/people/dapachec/helloworld.svg" class="imagelink"><img src="https://cs.brown.edu/people/dapachec/helloworld.svg" alt="'Hello World' HTTP server flame graph" /></a>
 
 This is a visualization of all of the profiled call stacks. This example is from the "hello world" HTTP server on the <a href="https://nodejs.org">Node.js</a> home page under load. Start at the bottom, where you have "main", which is present in most Node stacks because Node spends most on-CPU time in the main thread. Above each row, you have the functions called by the frame beneath it. As you move up, you'll see actual JavaScript function names. The boxes in each row are not in chronological order, but their width indicates how much time was spent there. When you hover over each box, you can see exactly what percentage of time is spent in each function. This lets you see at a glance where your program spends its time.
 
diff --git a/static/images/jsinteractive-2018-banner.png b/static/images/jsinteractive-2018-banner.png
new file mode 100644
index 0000000000000..d75a99f61e8bf
Binary files /dev/null and b/static/images/jsinteractive-2018-banner.png differ