diff --git a/2/index.html b/2/index.html
index bcbaa8c..06b65a1 100644
--- a/2/index.html
+++ b/2/index.html
@@ -34,7 +34,7 @@ <h1>24 seconds to view the product images on Amazon’s website</h1>
 <p>I repeated the test a few more times across different product pages to confirm that it wasn’t just a fluke. Overall, it takes about 24 seconds from navigation start to product image render. That’s on the Nokia C02. I also performed a site performance test with an “emulated Motorola G4” on WebPageTest. The <a href="https://www.webpagetest.org/result/240130_AiDcSF_EAG/">test result</a> shows about 10 seconds of scripting on the main thread, and the first 30 seconds are riddled with long tasks. According to my browser’s devtools, a typical product page on Amazon’s website executes around 7 MB of JavaScript.</p>
 <p>While this is undoubtedly too much JavaScript (five times more than I would be comfortable with), users on low-end devices can still have a passable experience—at the expense of their device’s battery percentage—as long as they don’t have to wait too long for each individual event. But in this case, waiting 20+ seconds for the product images to load <em>is</em> too long.</p>
 <p>Since the first two product images load immediately, it could be that Amazon decided to eagerly load only those two images because they determined that by the time the user swipes to the third image, most if not all of the JavaScript has already been executed anyway, so there’s only a small delay. Amazon’s test devices must be more powerful than my Nokia. Amazon should consider eagerly loading <em>all</em> product images. After all, viewing these images is one of the first things the user does after checking the price, isn’t it? If that’s not possible, Amazon could probably reduce the image loading delay by prioritizing the JavaScript that is responsible for loading the images, and making sure that the images can load faster if needed, without being delayed by other resources.</p>
-<p>But those are just my surface-level thoughts. I don’t have the whole picture. I’m sure Amazon knows how to fix this issue, assuming that it can be fixed without a major overhaul of the code. The only question is whether they consider this issue to be important enough to be prioritized. Meanwhile, I’ll stick to my admittedly simplistic rule: If it’s too slow on my Nokia, it’s unacceptable.</p>
+<p>But those are just my surface-level thoughts. I don’t have the whole picture. I’m sure Amazon knows how to fix this issue, assuming that it can be fixed without a major overhaul of the code. The only question is whether they consider this issue to be important enough to be prioritized. In the meantime, I’ll stick to my admittedly simplistic rule: If it’s too slow on my Nokia, it’s unacceptable.</p>
 
 <p><a href="https://mastodon.social/@simevidas/">Reply on Mastodon</a></p></main>
       <nav>
diff --git a/feed.xml b/feed.xml
index c1fc4f3..e822311 100644
--- a/feed.xml
+++ b/feed.xml
@@ -25,7 +25,7 @@
 &lt;p&gt;I repeated the test a few more times across different product pages to confirm that it wasn’t just a fluke. Overall, it takes about 24 seconds from navigation start to product image render. That’s on the Nokia C02. I also performed a site performance test with an “emulated Motorola G4” on WebPageTest. The &lt;a href=&quot;https://www.webpagetest.org/result/240130_AiDcSF_EAG/&quot;&gt;test result&lt;/a&gt; shows about 10 seconds of scripting on the main thread, and the first 30 seconds are riddled with long tasks. According to my browser’s devtools, a typical product page on Amazon’s website executes around 7 MB of JavaScript.&lt;/p&gt;
 &lt;p&gt;While this is undoubtedly too much JavaScript (five times more than I would be comfortable with), users on low-end devices can still have a passable experience—at the expense of their device’s battery percentage—as long as they don’t have to wait too long for each individual event. But in this case, waiting 20+ seconds for the product images to load &lt;em&gt;is&lt;/em&gt; too long.&lt;/p&gt;
 &lt;p&gt;Since the first two product images load immediately, it could be that Amazon decided to eagerly load only those two images because they determined that by the time the user swipes to the third image, most if not all of the JavaScript has already been executed anyway, so there’s only a small delay. Amazon’s test devices must be more powerful than my Nokia. Amazon should consider eagerly loading &lt;em&gt;all&lt;/em&gt; product images. After all, viewing these images is one of the first things the user does after checking the price, isn’t it? If that’s not possible, Amazon could probably reduce the image loading delay by prioritizing the JavaScript that is responsible for loading the images, and making sure that the images can load faster if needed, without being delayed by other resources.&lt;/p&gt;
-&lt;p&gt;But those are just my surface-level thoughts. I don’t have the whole picture. I’m sure Amazon knows how to fix this issue, assuming that it can be fixed without a major overhaul of the code. The only question is whether they consider this issue to be important enough to be prioritized. Meanwhile, I’ll stick to my admittedly simplistic rule: If it’s too slow on my Nokia, it’s unacceptable.&lt;/p&gt;
+&lt;p&gt;But those are just my surface-level thoughts. I don’t have the whole picture. I’m sure Amazon knows how to fix this issue, assuming that it can be fixed without a major overhaul of the code. The only question is whether they consider this issue to be important enough to be prioritized. In the meantime, I’ll stick to my admittedly simplistic rule: If it’s too slow on my Nokia, it’s unacceptable.&lt;/p&gt;
 </content>
   </entry>
   <entry>