From d54b1f8ad93a2dcf09e1609701d4ff050ee721cd Mon Sep 17 00:00:00 2001
From: Evorp <3vorpgaming@gmail.com>
Date: Mon, 1 Jul 2024 10:41:26 -0700
Subject: [PATCH] lazy load all images

---
 .vitepress/config.ts                        |   5 +
 pages/dungeons/alpha-img.md                 |   6 +-
 pages/dungeons/items-tutorial.md            | 110 ++++++++++----------
 pages/dungeons/loader-texture.md            |  22 ++--
 pages/manuals/branding-guidelines.md        |  34 +++---
 pages/mods/add-new-mod.md                   |   8 +-
 pages/mods/add-new-version.md               |   6 +-
 pages/mods/add-textures-commands.md         |   4 +-
 pages/mods/add-textures.md                  |  12 +--
 pages/textures/cf32-texturing-guidelines.md | 102 +++++++++---------
 pages/textures/f32-texturing-guidelines.md  |  95 +++++++++--------
 pages/textures/f64-texturing-guidelines.md  |  22 ++--
 12 files changed, 217 insertions(+), 209 deletions(-)

diff --git a/.vitepress/config.ts b/.vitepress/config.ts
index 0f8b0e2..c9ff63d 100644
--- a/.vitepress/config.ts
+++ b/.vitepress/config.ts
@@ -60,6 +60,11 @@ export default () => {
 		},
 		cleanUrls: true,
 		outDir: "./dist",
+		markdown: {
+			image: {
+				lazyLoading: true,
+			},
+		},
 		vite: {
 			resolve: {
 				alias: [
diff --git a/pages/dungeons/alpha-img.md b/pages/dungeons/alpha-img.md
index f54da7d..67d4e73 100644
--- a/pages/dungeons/alpha-img.md
+++ b/pages/dungeons/alpha-img.md
@@ -31,7 +31,7 @@ _If you find any bugs, please post a new issue on GitHub._
 <ul>
     <li>
         <code>remove_alpha.py</code><br><br>
-        <img src="/images/dungeons/alpha-img/remove_alpha.png" alt="remove alpha" width="192" height="64" loading="lazy">
+        <img src="/images/dungeons/alpha-img/remove_alpha.png" alt="remove alpha" width="192" height="64">
         <blockquote>From Alpha to Opaque.</blockquote>
         <p>Set <strong class="red-text">all pixels</strong> opaque.</p>
         <ul>
@@ -42,7 +42,7 @@ _If you find any bugs, please post a new issue on GitHub._
     <br>
     <li>
         <code>get_alpha.py</code><br><br>
-        <img src="/images/dungeons/alpha-img/get_alpha.png" alt="get alpha" width="192" height="64" loading="lazy">
+        <img src="/images/dungeons/alpha-img/get_alpha.png" alt="get alpha" width="192" height="64">
         <blockquote>From Opaque to Alpha.</blockquote>
         <p>Set <strong class="red-text">all pixels</strong> transparent.</p>
         <ul>
@@ -53,7 +53,7 @@ _If you find any bugs, please post a new issue on GitHub._
     <br>
     <li>
         <code>merge_alpha_layers.py</code><br><br>
-        <img src="/images/dungeons/alpha-img/merge_alpha_layers.png" alt="merge alpha layers" width="192" height="192" loading="lazy">
+        <img src="/images/dungeons/alpha-img/merge_alpha_layers.png" alt="merge alpha layers" width="192" height="192">
         <blockquote>Merge both types easily.</blockquote>
         <p>With this one, you have to set "masks", one with opaque pixels, one with transparent pixels.</p>
         <ul>
diff --git a/pages/dungeons/items-tutorial.md b/pages/dungeons/items-tutorial.md
index 5011834..dc24dda 100644
--- a/pages/dungeons/items-tutorial.md
+++ b/pages/dungeons/items-tutorial.md
@@ -5,7 +5,7 @@ date: "2020-09-09"
 archived: true
 ---
 
-<img class="center" src="/images/dungeons/items-tutorial/header.png" alt="header" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/header.png" alt="header">
 
 <h2>Introduction</h2>
 
@@ -21,9 +21,9 @@ When making a mod for Minecraft: Dungeons, it is important to know that most wea
 <h2>PART 0: Controls & Hotkeys</h2>
 
 <h3>Blockbench:</h3>
-<img class="center" src="/images/dungeons/items-tutorial/hotkey_blockbench.png" alt="hotkey blockbench" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/hotkey_blockbench.png" alt="hotkey blockbench">
 <h3>Blender:</h3>
-<img class="center" src="/images/dungeons/items-tutorial/hotkey_blender.png" alt="hotkey blender" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/hotkey_blender.png" alt="hotkey blender">
 
 > If you are on Mac: use `Cmd` instead of `Ctrl`
 
@@ -35,15 +35,15 @@ That's no problem! Blender allows you to emulate both of these, allowing you to
 Here's how to do it:
 
 1. Go to Edit tab up top, then select Preferences. A window should pop up.
-<img class="center" src="/images/dungeons/items-tutorial/no-3rd-mouse-emulation-1.png" alt="no 3rd mouse emulation 1" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/no-3rd-mouse-emulation-1.png" alt="no 3rd mouse emulation 1">
 
 2. In that window, go to the Input tab and check the `Emulate 3 Button Mouse` and `Emulate Numpad` boxes.
-<img class="center" src="/images/dungeons/items-tutorial/no-3rd-mouse-emulation-2.png" alt="no 3rd mouse emulation 2" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/no-3rd-mouse-emulation-2.png" alt="no 3rd mouse emulation 2">
 
 By default, `alt`+`LMB` will be registered as `MMB`. If you emulate the numpad, you can access the numpad hotkeys by pressing numbers in the top row of the keyboard (do NOT press shift!). The emulation will override some existing hotkeys placed on the numerical row, but we don't need them anyway, so don't worry about that.
 
 Additionally, if you've got an Apple Magic Mouse, on top of having to emulate a 3 button mouse the view controls are a bit different:
-<img class="center" src="/images/dungeons/items-tutorial/hotkey_mac.png" alt="hotkey mac" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/hotkey_mac.png" alt="hotkey mac">
 
 > All other controls are the same.
 
@@ -52,12 +52,12 @@ Additionally, if you've got an Apple Magic Mouse, on top of having to emulate a
 
 When you're finished making a texture for your item, it should look something like this:
 
-<img class="center" src="/images/dungeons/items-tutorial/prepare-a-texture-1.png" alt="prepare a texture 1" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/prepare-a-texture-1.png" alt="prepare a texture 1">
 
 This is the texture that you want to use in your mod. For our purposes we'll need another, slightly modified texture. Make a copy of your texture and modify that. For your texture to work properly with Blockbench, you need to get rid of all the parts that you do not want to be included in the model. In this case we need to remove the palette thingy, but depending on the texture you might also need to make the background transparent etc.
 This is how your texture should look before importing to Blockbench:
 
-<img class="center" src="/images/dungeons/items-tutorial/prepare-a-texture-2.png" alt="prepare a texture 2" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/prepare-a-texture-2.png" alt="prepare a texture 2">
 
 Now with that out of the way, let's get to modelling itself!
 
@@ -65,27 +65,27 @@ Now with that out of the way, let's get to modelling itself!
 
 Upon opening Blockbench you should get to this screen:
 
-<img class="center" src="/images/dungeons/items-tutorial/extrude-texture-1.png" alt="extrude texture 1" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/extrude-texture-1.png" alt="extrude texture 1">
 
 Make a new generic model and name it whatever you want. **DO NOT** change the texture dimensions in the window that pops up, it will break things!
 
-<img class="center" src="/images/dungeons/items-tutorial/extrude-texture-2.png" alt="extrude texture 2" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/extrude-texture-2.png" alt="extrude texture 2">
 
 Before importing the texture, make sure that your snapping grid resolution is 16x16. You can do that by going to `File > Settings...` and then the Snapping tab.
 
-<img class="center" src="/images/dungeons/items-tutorial/extrude-texture-3.png" alt="extrude texture 3" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/extrude-texture-3.png" alt="extrude texture 3">
 
 Now go to `File > Import` and select `Extrude Texture`. **Do not** change anything in the window that pops up. You should get something like this:
 
-<img class="center" src="/images/dungeons/items-tutorial/extrude-texture-4.png" alt="extrude texture 4" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/extrude-texture-4.png" alt="extrude texture 4">
 
 Now move the model so that it's centered on the grid.
 
-<img class="center" src="/images/dungeons/items-tutorial/extrude-texture-5.png" alt="extrude texture 5" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/extrude-texture-5.png" alt="extrude texture 5">
 
 Finally, right click on the texture under the Textures tab, and then change the file to your original, unmodified texture.
 
-<img class="center" src="/images/dungeons/items-tutorial/extrude-texture-6.png" alt="extrude texture 6" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/extrude-texture-6.png" alt="extrude texture 6">
 
 If you done that correctly, you shouldn't see a visual change.
 
@@ -93,7 +93,7 @@ If you done that correctly, you shouldn't see a visual change.
 
 You can do that by going to `File > Export` and then selecting `Export OBJ Model`.
 
-<img class="center" src="/images/dungeons/items-tutorial/export-as-obj.png" alt="export as obj" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/export-as-obj.png" alt="export as obj">
 Save the OBJ file somewhere you can find it - you'll need it in the next step:
 
 <h3>4) Import the model into Blender</h3>
@@ -104,19 +104,19 @@ Upon opening you should see small window pop up - don't change anything in there
 Next, delete the default cube by selecting it, right clicking and selecting `Delete`.
 Now you can import your OBJ model by going to `File > Import`, selecting `Wavefront (.obj)` and then navigating to your model.
 
-<img class="center" src="/images/dungeons/items-tutorial/import-model-to-blender-1.png" alt="import model to blender 1" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/import-model-to-blender-1.png" alt="import model to blender 1">
 
 You might notice that your model doesn't show any textures - that is completely normal, it's just blender's default view mode. Switch to Material mode (top right) to see the texture.
 
-<img class="center" src="/images/dungeons/items-tutorial/import-model-to-blender-2.png" alt="import model to blender 2" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/import-model-to-blender-2.png" alt="import model to blender 2">
 
 Your model should then look something like this:
 
-<img class="center" src="/images/dungeons/items-tutorial/import-model-to-blender-3.png" alt="import model to blender 3" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/import-model-to-blender-3.png" alt="import model to blender 3">
 
 Additionally, you can box select all the part of your model, shift-click on one of them and press `Ctrl` + `J` to merge all parts into one like so:
 
-<img class="center" src="/images/dungeons/items-tutorial/import-model-to-blender-4.png" alt="import model to blender 4" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/import-model-to-blender-4.png" alt="import model to blender 4">
 
 This will make it easier to edit the model all at once.
 We don't want the textures this blurry though! To fix that you'll need to
@@ -124,45 +124,45 @@ We don't want the textures this blurry though! To fix that you'll need to
 <h3>5) Set up a material</h3>
 You can edit your material by clicking on the red checkered circle in the tab on the right:
 
-<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-1.png" alt="set up a material 1" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-1.png" alt="set up a material 1">
 
 First you need to name your material correctly. Go to the location of the default texture in the Dungeons game files (assuming you've extracted them); you should see a bunch of files besides the texture. Locate the one with the .mat extension and copy its name (without the extension).
 
-<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-2.png" alt="set up a material 2" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-2.png" alt="set up a material 2">
 
 Next, copy the name into this field at the top of the Material Properties tab, and press Enter.
 
-<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-3.png" alt="set up a material 3" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-3.png" alt="set up a material 3">
 
 Now you can fix the texture filtering by going into this dropdown menu and selecting Closest.
 
-<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-4.png" alt="set up a material 4" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-4.png" alt="set up a material 4">
 
 If you've done everything correctly, your model should look roughly like this:
 
-<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-5.png" alt="set up a material 5" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-5.png" alt="set up a material 5">
 
 <h3>6) Position and scale your model</h3>
 Now it's time to position your model to fit the default scale and placement. To do that we're going to use the default item model.
 For importing Unreal skeletal meshes into Blender we're gonna need the Import Unreal Skeletal Mesh add-on. To install it, go to `Edit > Preferences`, then in the window that pops up go into the Add-ons tab, click the Install button and navigate to where you saved the .py file
 
-<img class="center" src="/images/dungeons/items-tutorial/position-and-scale-1.png" alt="position and scale 1" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/position-and-scale-1.png" alt="position and scale 1">
 
 When you've installed the add-on, make sure it's enabled by ticking the box below in the Add-ons tab and checking if the add-on is present in the list. (if it's not, untick the box, find the add-on and enable it manually.)
 
-<img class="center" src="/images/dungeons/items-tutorial/position-and-scale-2.png" alt="position and scale 2" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/position-and-scale-2.png" alt="position and scale 2">
 
 Now you can import the default model by going to File > Import, selecting Skeleton mesh (.psk) and navigating to the model.
 
-<img class="center" src="/images/dungeons/items-tutorial/position-and-scale-3.png" alt="position and scale 3" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/position-and-scale-3.png" alt="position and scale 3">
 
 Now that you've imported the model you can scale, move and rotate your custom one to fit the default like so:
 
-<img class="center" src="/images/dungeons/items-tutorial/position-and-scale-4.png" alt="position and scale 4" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/position-and-scale-4.png" alt="position and scale 4">
 
 **TIP:** You can use a present view (like topdown) by clicking any of these points on the top right corner  for more accurate positioning.
 
-<img class="center" src="/images/dungeons/items-tutorial/position-and-scale-5.png" alt="position and scale 5" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/position-and-scale-5.png" alt="position and scale 5">
 
 You don't have to be super precise though - just try to roughly match the position and size of the default model.
 
@@ -172,19 +172,19 @@ When you're finished, delete the default model by selecting it, right clicking i
 
 You can export your model into the FBX format by going to File > Export and then selecting FBX.
 
-<img class="center" src="/images/dungeons/items-tutorial/export-as-fbx-1.png" alt="export as fbx 1" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/export-as-fbx-1.png" alt="export as fbx 1">
 
 In the window that pops up you can navigate to your desired file location. That's not all though - we'll also need to change some settings in the tab on the right side. Set the scale in the Transform tab to 0.01 and then, in the Geometry tab, set Smoothing to Face.
 
-<img class="center" src="/images/dungeons/items-tutorial/export-as-fbx-2.png" alt="export as fbx 2" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/export-as-fbx-2.png" alt="export as fbx 2">
 
 Next, look at the model's name in the default game files and name your model that.
 
-<img class="center" src="/images/dungeons/items-tutorial/export-as-fbx-3.png" alt="export as fbx 3" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/export-as-fbx-3.png" alt="export as fbx 3">
 
 Finally, click the blue Export button to finish the process.
 
-<img class="center" src="/images/dungeons/items-tutorial/export-as-fbx-4.png" alt="export as fbx 4" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/export-as-fbx-4.png" alt="export as fbx 4">
 
 Congratulations! You've made it through the entire modelling process and now have a model that will function properly when put into a mod!
 
@@ -197,80 +197,80 @@ Congratulations! You've made it through the entire modelling process and now hav
 
 To import the model ripped from Minecraft: Dungeons we will need to install the Import Unreal Skeletal Mesh add-on for Blender. To do that, go to Edit > Preferences, then in the window that pops up go into the Add-ons tab, click the install button and navigate to where you saved the.py file.
 
-<img class="center" src="/images/dungeons/items-tutorial/rendering-import-model-1.png" alt="rendering import model 1" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/rendering-import-model-1.png" alt="rendering import model 1">
 
 When you've installed the add-on, make sure it's enabled by ticking the box below in the Add-ons tab and checking if the add-on is present in the list. (if it's not, untick the box, find the add-on and enable it manually.)
 
-<img class="center" src="/images/dungeons/items-tutorial/rendering-import-model-2.png" alt="rendering import model 2" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/rendering-import-model-2.png" alt="rendering import model 2">
 
 Now you can import the default model by going to File > Import, selecting Skeleton mesh (.psk) and navigating to the model.
 
-<img class="center" src="/images/dungeons/items-tutorial/rendering-import-model-3.png" alt="rendering import model 3" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/rendering-import-model-3.png" alt="rendering import model 3">
 
 <h3>2) Set up a material (again)</h3>
 First, check if the Use Nodes button in the red checkered circle tab is blue. If it's not, click on it to make it blue.
 
-<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-again-1.png" alt="set up a material again 1" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-again-1.png" alt="set up a material again 1">
 
 Then switch to the Shader Editor using this menu up top:
 
-<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-again-2.png" alt="set up a material again 2" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-again-2.png" alt="set up a material again 2">
 
 The tab should change into a node editor. Enlarge it so you can see it better and then make it look like this:
 
-<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-again-3.png" alt="set up a material again 3" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-again-3.png" alt="set up a material again 3">
 
 **TIP:** You can add a node by pressing Shift + A, selecting Search and then typing the node's name. You can also zoom in and out using Ctrl + scroll.
 TO connect two nodes together just click and drag from one point (as seen above) to another with your mouse.
 
-<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-again-4.png" alt="set up a material again 4" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/set-up-a-material-again-4.png" alt="set up a material again 4">
 
 <h3>3) Add a light</h3>
 
 First of all, your model is probably HUGE because Minecraft: Dungeons scales it down. This can cause some issues with lightning, so make your model smaller before doing anything.
 Next, delete any lights that might've been added by Blender when you created the model. Just select them, right click and select Delete. They look like this:
 
-<img class="center" src="/images/dungeons/items-tutorial/add-a-light-1.png" alt="add a light 1" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/add-a-light-1.png" alt="add a light 1">
 
 Before adding a light, switch to Render mode (the third circle in the top right menu) to see the changes properly.
 
-<img class="center" src="/images/dungeons/items-tutorial/add-a-light-2.png" alt="add a light 2" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/add-a-light-2.png" alt="add a light 2">
 
 Now you can add a light by pressing Shift + A while hovering above the model view, going to Light and selecting Sun.
 
-<img class="center" src="/images/dungeons/items-tutorial/add-a-light-3.png" alt="add a light 3" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/add-a-light-3.png" alt="add a light 3">
 
 Now move and rotate the sun while trying to roughly match the lightning of the default render. You can also move and rotate the model itself to help you out.
 **TIP:** You can adjust the strength of your sun on this slider in the right-side menu while having the sun selected:
 
-<img class="center" src="/images/dungeons/items-tutorial/add-a-light-4.png" alt="add a light 4" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/add-a-light-4.png" alt="add a light 4">
 
 When you're done you should get something that matches the default view and lightning pretty closely:
 
-<img class="center" src="/images/dungeons/items-tutorial/add-a-light-5.png" alt="add a light 5" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/add-a-light-5.png" alt="add a light 5">
 
 <h3>4) Set up a camera</h3>
 
 For Blender to actually know what to render, we need to set up a camera.
 First, we will enable an add-on that will make handling the camera easier. To do it, go to Edit > Preferences, open the Add-ons tab, find the add-on called "3D View: Stored views" and enable it like so:
 
-<img class="center" src="/images/dungeons/items-tutorial/set-up-a-camera-1.png" alt="set up a camera 1" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/set-up-a-camera-1.png" alt="set up a camera 1">
 
 Next, click this little arrow next to the axis cross thing:
 
-<img class="center" src="/images/dungeons/items-tutorial/set-up-a-camera-2.png" alt="set up a camera 2" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/set-up-a-camera-2.png" alt="set up a camera 2">
 
 A menu should pop up. Open the View tab and check the Lock Camera to View box.
 
-<img class="center" src="/images/dungeons/items-tutorial/set-up-a-camera-3.png" alt="set up a camera 3" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/set-up-a-camera-3.png" alt="set up a camera 3">
 
 Next, select a camera that should already be placed somewhere in your project. It should look like this:
 
-<img class="center" src="/images/dungeons/items-tutorial/set-up-a-camera-4.png" alt="set up a camera 4" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/set-up-a-camera-4.png" alt="set up a camera 4">
 
 Now rotate your view around so you get a view that looks the most like the default one. After that open the Stored Views tab, click Initialize and then click Camera to View. This will move the selected camera to your viewpoint.
 
-<img class="center" src="/images/dungeons/items-tutorial/set-up-a-camera-5.png" alt="set up a camera 5" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/set-up-a-camera-5.png" alt="set up a camera 5">
 
 Now press Numpad 0 to switch to camera view.
 
@@ -279,28 +279,28 @@ Now press Numpad 0 to switch to camera view.
 We're almost done! The only thing left to do is to configure the resolution and transparency of the output render.
 You can make the output transparent by going to this tab in the menu on the right side, opening the Film tab and checking the Transparent box.
 
-<img class="center" src="/images/dungeons/items-tutorial/configure-and-render-1.png" alt="configure and render 1" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/configure-and-render-1.png" alt="configure and render 1">
 
 For the resolution control, first get the default render and see how big it is. (There are usually 2 renders - and yes, you'll be rendering your model twice.)
 When you've located the resolution of the default render, go to the tab in Blender immediately below the one you just opened and set the resolution in the first two fields.
 
-<img class="center" src="/images/dungeons/items-tutorial/configure-and-render-2.png" alt="configure and render 2" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/configure-and-render-2.png" alt="configure and render 2">
 
 (You can then pan and zoom your view a bit so your model is roughly in the centre of the square.)
 
 
 Before we get to the render itself, select your sun, go to the tab with the lightbulb and uncheck the Shadow box.
 
-<img class="center" src="/images/dungeons/items-tutorial/configure-and-render-3.png" alt="configure and render 3" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/configure-and-render-3.png" alt="configure and render 3">
 
 Now you can finally initiate the render by pressing F12 (fn + F12 on mac).
 
 When the render is finished, you can save it by going to Image > Save as.
 
-<img class="center" src="/images/dungeons/items-tutorial/configure-and-render-4.png" alt="configure and render 4" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/configure-and-render-4.png" alt="configure and render 4">
 
 And there you have it! You have made yourself a model and render that is usable in Minecraft: Dungeons!
 
-<img class="center" src="/images/dungeons/items-tutorial/configure-and-render-5.png" alt="configure and render 5" loading="lazy">
+<img class="center" src="/images/dungeons/items-tutorial/configure-and-render-5.png" alt="configure and render 5">
 
 <p style="text-align: center;"><em>Thank you so much for reading this tutorial, and good luck with your mod!</em></p>
\ No newline at end of file
diff --git a/pages/dungeons/loader-texture.md b/pages/dungeons/loader-texture.md
index 0facdf3..a8864bc 100644
--- a/pages/dungeons/loader-texture.md
+++ b/pages/dungeons/loader-texture.md
@@ -21,18 +21,18 @@ All needed files for this tutorial can be found [here](https://github.com/Faithf
 
 1. Open `LoadingSpinnerBlock.blend` with Blender
 2. Drag the green bar at the bottom at the beginning of the animation
-<img class="center" src="/images/dungeons/loader-texture/1.png" alt="green bar" loading="lazy">
+<img class="center" src="/images/dungeons/loader-texture/1.png" alt="green bar">
 
 3. Go to the `Shading` tab at the top of the screen
-<img class="center" src="/images/dungeons/loader-texture/2.png" alt="shading tab" loading="lazy">
+<img class="center" src="/images/dungeons/loader-texture/2.png" alt="shading tab">
 
 4. Click on the blank face of the block in front of you (you get a green outline surrounding it)
-<img class="center" src="/images/dungeons/loader-texture/3.png" alt="block green outline" loading="lazy">
+<img class="center" src="/images/dungeons/loader-texture/3.png" alt="block green outline">
 
 5. In the bottom slide, in the Orange Area, click on the cross & import a new texture:
-    A. <img style="padding-left: 10px;" src="/images/dungeons/loader-texture/4.png" alt="import texture 1" loading="lazy"><br>
-    B. <img style="padding-left: 10px;" src="/images/dungeons/loader-texture/5.png" alt="import texture 2" loading="lazy"><br>
-    C. <img style="padding-left: 10px;" src="/images/dungeons/loader-texture/6.png" alt="import texture 3" loading="lazy"><br>
+    A. <img style="padding-left: 10px;" src="/images/dungeons/loader-texture/4.png" alt="import texture 1"><br>
+    B. <img style="padding-left: 10px;" src="/images/dungeons/loader-texture/5.png" alt="import texture 2"><br>
+    C. <img style="padding-left: 10px;" src="/images/dungeons/loader-texture/6.png" alt="import texture 3"><br>
 
 6. Drag the green slider until a new face
     - Remake the previous step & this one until all faces are done
@@ -40,17 +40,17 @@ All needed files for this tutorial can be found [here](https://github.com/Faithf
     > Optional: You can go to the `Texture Paint` tab & press the space bar to see your texture on the model.
 
 7. Return to the `Layout` tab, and in the bottom right, change the output path
-  <img class="center" src="/images/dungeons/loader-texture/7.png" alt="output path" loading="lazy">
+  <img class="center" src="/images/dungeons/loader-texture/7.png" alt="output path">
 
 8. Finally: at the top left, click on render, then render the animation, all screenshots should be in where you set the output path.
-  <img class="center" src="/images/dungeons/loader-texture/8.png" alt="render animation" loading="lazy">
+  <img class="center" src="/images/dungeons/loader-texture/8.png" alt="render animation">
 
 ## Step by step: Python
 ### Install Pillow:
 As said before, you will need the Pillow module, install it (if you haven't already installed it).
 1. Press `Windows` + `R` then type `cmd` then `enter`
 2. Write this command: `pip install pillow` then press `enter`
-    <img class="center" src="/images/dungeons/loader-texture/9.png" alt="pip install command" loading="lazy">
+    <img class="center" src="/images/dungeons/loader-texture/9.png" alt="pip install command">
 
 3. Once you have installed python & Pillow and that you have all the screenshots (with the right name), you can simply double click the `Merge.py` script to get the texture atlas.
     <strong class="red-text">⚠️ The script needs to be in the same file as screenshots took by Blender.</strong>
@@ -60,12 +60,12 @@ As said before, you will need the Pillow module, install it (if you haven't alre
 1. You need to put the `loader.png` file in this folder: `UE4Project\Content\UI\Materials\LoadingScreens\Misc`
 2. Open your `Dungeons.uproject` from `UE4Project/`
 3. Find the file in your project and open it:
-    <img class="center" src="/images/dungeons/loader-texture/10.png" alt="open file" loading="lazy">
+    <img class="center" src="/images/dungeons/loader-texture/10.png" alt="open file">
 
 4. Then you have to change settings on the right tab:
     - Compression Settings → BC7
     - Mip Gen Settings → NoMipmaps
     - Texture Group → UI
-    <img class="center" src="/images/dungeons/loader-texture/11.png" alt="settings" loading="lazy">
+    <img class="center" src="/images/dungeons/loader-texture/11.png" alt="settings">
 
 <p class="center"><em>Everything should be good, you now just have to package your files using the <a href="https://github.com/Dokucraft/Dungeons-Mod-Kit">Dokucraft Tool</a></em></p>
diff --git a/pages/manuals/branding-guidelines.md b/pages/manuals/branding-guidelines.md
index 2a5a73a..2139e2a 100644
--- a/pages/manuals/branding-guidelines.md
+++ b/pages/manuals/branding-guidelines.md
@@ -53,25 +53,25 @@ Logos work well for displaying our branding in places with limited space. This i
 
 For most general-purpose applications, use our plain logo. This logo additionally encompasses Classic Faithful, but if you specifically want to refer to Classic Faithful, you can use its respective plain logo as well.
 
-<img src="/images/manuals/branding-guidelines/main_logos.png" loading="lazy">
+<img src="/images/manuals/branding-guidelines/main_logos.png">
 <i class="center">Left: Plain logo. Right: Classic Faithful plain logo.</i>
 
 If you only want to refer to one project, such as in a card, use that project's respective logo. The Classic Faithful logos have different margins to the regular Faithful logo, so bear that in mind when adjusting sizes.
 
-<img src="/images/manuals/branding-guidelines/all_logos.png" class="center" loading="lazy">
+<img src="/images/manuals/branding-guidelines/all_logos.png" class="center">
 
 You can use a monochrome version of our logo in small spaces if using the regular logo would look visually noisy or be hard to read.
 
-<img src="/images/manuals/branding-guidelines/monochrome_logos.png" class="center" loading="lazy">
+<img src="/images/manuals/branding-guidelines/monochrome_logos.png" class="center">
 
 All our logos should always retain their pixel art form. Even when using the monochrome logo, don't simplify the shape into vectors.
 
-<img src="/images/manuals/branding-guidelines/no_vectors.png" class="center" loading="lazy">
+<img src="/images/manuals/branding-guidelines/no_vectors.png" class="center">
 <i class="center">Left: Correct depiction of the Faithful monochrome logo. Right: Incorrect depiction.</i>
 
 Finally, our logos should always be centered based on their main hexagonal part. The numbers and symbols in the bottom-right corner should not be taken into account when positioning.
 
-<img src="/images/manuals/branding-guidelines/centering.png" class="center" loading="lazy">
+<img src="/images/manuals/branding-guidelines/centering.png" class="center">
 <i class="center">Left: Correctly centered Faithful 32x logo. Right: An example of incorrect centering; Note that the logo on the right has been centered based on the whole image, and not just the hexagonal part.</i>
 
 ## Part 3: Logotexts
@@ -80,12 +80,12 @@ Finally, our logos should always be centered based on their main hexagonal part.
 
 Logotexts were designed for users to be able to use a logo and a wordmark at the same time without having a clash in resolution. Each logo has a corresponding logotext and this can be used if the Faithful name is not already well established.
 
-<img src="https://database.faithfulpack.net/images/branding/logotexts/plain_logotext.png" class="center" loading="lazy">
+<img src="https://database.faithfulpack.net/images/branding/logotexts/plain_logotext.png" class="center">
 <i class="center">The Faithful logotext.</i>
 
 Always make sure to put logotexts on plain or low-contrast backgrounds — readability can be negatively impacted with noisy backgrounds. Please also note that the text and the logo that make up the logotexts are inseparable, so don't use the pixel art text by itself.
 
-<img src="/images/manuals/branding-guidelines/logotext_comparison.png" class="center" loading="lazy">
+<img src="/images/manuals/branding-guidelines/logotext_comparison.png" class="center">
 <i class="center">Top: Correct placement of a logotext that ensures it's easily readable. Bottom: Poorly placed logotext.</i>
 
 ## Part 4: Wordmarks
@@ -94,24 +94,24 @@ Always make sure to put logotexts on plain or low-contrast backgrounds — read
 
 Wordmarks tend to be pretty big and bold, so use them sparingly for large banners and other big areas. They're usually the preferred branding when placed over busy backgrounds such as screenshots.
 
-<img src="https://database.faithfulpack.net/images/branding/social%20media/banners/universal_banner.png" class="center" loading="lazy">
+<img src="https://database.faithfulpack.net/images/branding/social%20media/banners/universal_banner.png" class="center">
 <i class="center">The Faithful banner.</i>
 
 The plain Faithful wordmark is preferred for most purposes, but specific projects also have their own wordmarks, similarly to the project logos.
 
 In addition, both cracked, flat, and outlined versions exist. As a rule of thumb, use the flat versions for referring to Faithful (or Classic Faithful) as a whole, the cracked versions for specific projects, and the outlined versions to help readability when necessary.
 
-<img src="/images/manuals/branding-guidelines/wordmarks.png" class="center" loading="lazy">
+<img src="/images/manuals/branding-guidelines/wordmarks.png" class="center">
 <i class="center">Each Faithful wordmark variation.</i>
 
 Wordmarks don't tend to scale well, so refrain from using them in small spaces — consider using the logo or simply typing out the name when space is limited.
 
-<img src="/images/manuals/branding-guidelines/bad_wordmark_scaling.png" class="center" loading="lazy">
+<img src="/images/manuals/branding-guidelines/bad_wordmark_scaling.png" class="center">
 <i class="center">An example of a wordmark not scaling well.</i>
 
 However, don't mix logos and wordmarks, since that's what the logotexts are for. The reasoning is because the pixelated logos don't mix well with the high-resolution wordmarks.
 
-<img src="/images/manuals/branding-guidelines/wordmark_vs_logotext.png" class="center" loading="lazy">
+<img src="/images/manuals/branding-guidelines/wordmark_vs_logotext.png" class="center">
 <i class="center">A logo next to a wordmark. A logotext is much better suited for this situation.</i>
 
 ## Part 5: Typography
@@ -122,12 +122,12 @@ The Faithful font should be used for titles and headings, while any neutral sans
 
 The individual pixels on a logotext also tend to blend at small resolutions so you're usually better off just typing the name out in a regular font.
 
-<img src="/images/manuals/branding-guidelines/bad_font.png" class="center" loading="lazy">
+<img src="/images/manuals/branding-guidelines/bad_font.png" class="center">
 <i class="center">Left: Good diversity in font sizing. Right: Blends together from the uniform size and font.</i>
 
 The semibold Faithful font should be used for large headings and the regular Faithful font for sub-headings. Only use the bold Faithful font for top-level titles when more than two levels of nested titles are required, due to its low readability and large horizontal footprint.
 
-<img src="/images/manuals/branding-guidelines/font_scaling.png" class="center" loading="lazy">
+<img src="/images/manuals/branding-guidelines/font_scaling.png" class="center">
 <i class="center">Each font weight and where it should be used.</i>
 
 ## Part 6: Scaling
@@ -138,12 +138,12 @@ In general, the hierarchy of branding elements to be used should be as following
 
 Always leave padding around the edges of any logo, logotext, and wordmark. Specific ratios don't really matter as long as the padding is even on all sides and the respective branding doesn't appear too large.
 
-<img src="/images/manuals/branding-guidelines/padding.png" class="center" loading="lazy">
+<img src="/images/manuals/branding-guidelines/padding.png" class="center">
 <i class="center">Left: Correct padding and scaling of the logo. Right: Incorrect padding and sizing.</i>
 
 Don't distort our branding to fit in a given space. Instead try using another suitable image or simply typing out the Faithful name using the format specified in part 1.
 
-<img src="/images/manuals/branding-guidelines/distortion.png" class="center" loading="lazy">
+<img src="/images/manuals/branding-guidelines/distortion.png" class="center">
 <i class="center">Do not.</i>
 
 ## Part 7: Colors and Backgrounds
@@ -152,12 +152,12 @@ Faithful has a fairly limited color palette used throughout most of the branding
 
 The main brand color is used for most accent colors, such as buttons or embeds. It works in combination with the "generic" background image.
 
-<img src="/images/manuals/branding-guidelines/faithful_color.png" class="center" loading="lazy">
+<img src="/images/manuals/branding-guidelines/faithful_color.png" class="center">
 <i class="center">The main Faithful brand color and image.</i>
 
 Each pack additionally has a unique color and background screenshot assigned to it.
 
-<img src="/images/manuals/branding-guidelines/colors.png" class="center" loading="lazy">
+<img src="/images/manuals/branding-guidelines/colors.png" class="center">
 <i class="center">All Faithful project colors with their respective images.</i>
 
 A background image works well with a wordmark, decently with a logo, and not very well with a logotext. This placement hierarchy should be used to determine an element to go on top of a background image. If you absolutely have to use a logo or a logotext on a background image, it is recommended to add a drop shadow and/or blur the background.
diff --git a/pages/mods/add-new-mod.md b/pages/mods/add-new-mod.md
index 164d42d..68460c9 100644
--- a/pages/mods/add-new-mod.md
+++ b/pages/mods/add-new-mod.md
@@ -16,18 +16,18 @@ deprecated: true
 
 *  If you want to add a new mod to our project, firstly check the mod list in our [GitHub](https://github.com/Faithful-Mods) **and** on our [Faithful Website](https://faithfulpack.net/mods) by typing the name of the mod or its assets folder name.
 
-<img src="/images/mods/add-new-mod/github-research.png" alt="github-research.png" class="center" loading="lazy">
+<img src="/images/mods/add-new-mod/github-research.png" alt="github-research.png" class="center">
 
 > ℹ️ **Info**
 > See [here](/pages/mods/add-textures) if the mod repository already exists.
 
 *  If the mod does not have any repository, then create a repository in your **own** profile (if you have access to the Faithful Mods organisation, then create it there). The repository needs to have the same name as the `assets` folder file (ex: `Actually Additions` mod repository would be named: `actuallyadditions`).
 
-<img src="/images/mods/add-new-mod/new-repo-img.png" alt="new-repo-img" class="center" loading="lazy">
+<img src="/images/mods/add-new-mod/new-repo-img.png" alt="new-repo-img" class="center">
 
 *  Keep the `main` branch empty (you can add a `readme.md` / `license.md` stuff but **no textures** on that branch) and make a new branch for each supported Minecraft version.
 
-<img src="/images/mods/add-new-mod/branches-list.png" alt="branches-list" class="center" loading="lazy">
+<img src="/images/mods/add-new-mod/branches-list.png" alt="branches-list" class="center">
 
 > ⚠️ **Warning**
 > - The `main` branch needs to be set as the **default branch**! Do not merge other branches into the main branch!
@@ -41,7 +41,7 @@ deprecated: true
 
 * Your repository now should look like this:
 
-<img src="/images/mods/add-new-mod/final-result.png" alt="final-result" class="center" loading="lazy">
+<img src="/images/mods/add-new-mod/final-result.png" alt="final-result" class="center">
 
 
 > ℹ️ **Info**
diff --git a/pages/mods/add-new-version.md b/pages/mods/add-new-version.md
index a1e44db..eb383e5 100644
--- a/pages/mods/add-new-version.md
+++ b/pages/mods/add-new-version.md
@@ -19,14 +19,14 @@ deprecated: true
 	#### **Using GitHub Website:**
 
 	Type the Minecraft version you want to add support for, then click on `Create a branch`.
-	<img src="/images/mods/add-new-version/github-add-branch.png" alt="github-add-branch.png" class="center" loading="lazy">
+	<img src="/images/mods/add-new-version/github-add-branch.png" alt="github-add-branch.png" class="center">
 
 	#### **Using GitHub Desktop:**
 
 	1. Click on the `current branch` button, then `New branch`, then type the Minecraft version you want to add support for, if `main` is not selected, click on it, then `create branch`.
-	<img src="/images/mods/add-new-version/github-desktop-add-branch-1st-step.png" alt="github-desktop-add-branch-1st-step.png" class="center" loading="lazy">
+	<img src="/images/mods/add-new-version/github-desktop-add-branch-1st-step.png" alt="github-desktop-add-branch-1st-step.png" class="center">
 	<br>
-	<img src="/images/mods/add-new-version/github-desktop-add-branch-2nd-step.png" alt="github-desktop-add-branch-2nd-step.png" class="center" loading="lazy">
+	<img src="/images/mods/add-new-version/github-desktop-add-branch-2nd-step.png" alt="github-desktop-add-branch-2nd-step.png" class="center">
 
 	2. Add those files to your new branch:
 		- **The pack.png and pack.mcmeta are not needed anymore, because that process is now automated. If you still find them, just delete them.**
diff --git a/pages/mods/add-textures-commands.md b/pages/mods/add-textures-commands.md
index 67123c4..0ea8ed3 100644
--- a/pages/mods/add-textures-commands.md
+++ b/pages/mods/add-textures-commands.md
@@ -15,7 +15,7 @@ deprecated: true
 ## Step by Step:
 
 1.  Firstly find your Mod repository in our [organization](https://github.com/Faithful-Mods), then find the repository `HTTPS` and use those commands in a shell:
-<img src="/images/mods/add-textures-commands/get-repository-https.png" alt="github get https" class="center" loading="lazy">
+<img src="/images/mods/add-textures-commands/get-repository-https.png" alt="github get https" class="center">
 ```shell
   $ git clone <git url>
 ```
@@ -29,7 +29,7 @@ deprecated: true
 > Note: If the branch doesn't exist, create a new one using `git branch <new-branch>` first, the new branch will be based on the actual branch
 
 3.  Your local repository should now looks like the image below, you can now edit/add textures locally.
-<img src="/images/mods/add-textures-commands/folder-example.png" alt="folder result" class="center" loading="lazy">
+<img src="/images/mods/add-textures-commands/folder-example.png" alt="folder result" class="center">
 
 4.  Once you are done with editing/adding textures, you can commit and push your changes to the online repository:
 ```shell
diff --git a/pages/mods/add-textures.md b/pages/mods/add-textures.md
index 4d47300..f0cceb0 100644
--- a/pages/mods/add-textures.md
+++ b/pages/mods/add-textures.md
@@ -18,16 +18,16 @@ deprecated: true
 > If the mod repository is not in the [Faithful Mods Organization](https://github.com/Faithful-Mods), check this [file](https://api.faithfulpack.net/v2/mods/raw) to see where is the repository located <kbd>CTRL</kbd> + <kbd>F</kbd> is the best way to find it.
 > If you can't find the repository, it may not exist yet, refer to [this](/pages/mods/add-new-mod) article then.
 
-<img src="/images/mods/add-textures/github-clone.png" alt="github clone repository" class="center" loading="lazy">
+<img src="/images/mods/add-textures/github-clone.png" alt="github clone repository" class="center">
 
 2. Select a file path to clone it on your computer (you can place it everywhere)
-<img src="/images/mods/add-textures/github-desktop-clone.png" alt="github desktop asking new cloned repository path" class="center" loading="lazy">
+<img src="/images/mods/add-textures/github-desktop-clone.png" alt="github desktop asking new cloned repository path" class="center">
 
 3. Then select the branch version for which you want to add textures (if the branch doesn't exist yet, see [here](/pages/mods/add-new-version)). Your local repository will update itself to the branch content (it has the content of the `main` branch by default → if you cloned the repository from the main branch).
-<img src="/images/mods/add-textures/github-desktop-select-branch.png" alt="github desktop choosing branch mc version" class="center" loading="lazy">
+<img src="/images/mods/add-textures/github-desktop-select-branch.png" alt="github desktop choosing branch mc version" class="center">
 
 4. Then go to your local repository folder and move your new/modified files in the `assets/` folder (like in any default resource pack).
-<img src="/images/mods/add-textures/folder-example.png" alt="local repository" class="center" loading="lazy">
+<img src="/images/mods/add-textures/folder-example.png" alt="local repository" class="center">
 
 > We recently made `pack.png` & `pack.mcmeta` dynamically generated, so they are no longer used and can be removed if they are still in the repository.
 
@@ -39,7 +39,7 @@ deprecated: true
 - ![(→)](/images/mods/add-textures/file-moved.png) File moved
 
 6. You can now add a title and a description to your commit (on the bottom left in GitHub Desktop) and press `Commit to <branch>`.
-<img src="/images/mods/add-textures/github-desktop-commit.png" alt="github desktop commit" class="center" loading="lazy">
+<img src="/images/mods/add-textures/github-desktop-commit.png" alt="github desktop commit" class="center">
 
 7. Finally: click on the `Push origin` button to send your commit to GitHub. You can now make a post in our [Discord](https://discord.gg/sN9YRQbBv7) to make an announcement about what you changed!
-<img src="/images/mods/add-textures/github-desktop-push.png" alt="github desktop push commit" class="center" loading="lazy">
+<img src="/images/mods/add-textures/github-desktop-push.png" alt="github desktop push commit" class="center">
diff --git a/pages/textures/cf32-texturing-guidelines.md b/pages/textures/cf32-texturing-guidelines.md
index d6daa99..329afdc 100644
--- a/pages/textures/cf32-texturing-guidelines.md
+++ b/pages/textures/cf32-texturing-guidelines.md
@@ -29,14 +29,14 @@ Over time, our community has adopted and come up with numerous terms regarding p
     <br>
     <li id="no-blending"><b>No blending</b> is a simple border between two or more colors, without any additional effects. A work in progress texture tends to have no blending, as other blending methods are usually added later on. However, this tends to have a "plasticky" effect or look flat, which is undesirable in most cases.</li>
     <br>
-    <img src="/images/textures/cf32-texturing-guidelines/1.png" alt="no blending" class="center" loading="lazy">
+    <img src="/images/textures/cf32-texturing-guidelines/1.png" alt="no blending" class="center">
     <i class="center"><b>Picture 1:</b> Example of a border between two colors, with no blending applied.</i>
     <br>
     <li id="antialiasing"><b>Antialiasing (AA)</b> is a technique used to smooth the jaggedness of a pixelated border between colors. It uses an additional in-between color to provide a smoother transition. This is particularly useful for smoother textures or getting rid of harsh color borders that may form.</li>
     <br>
-    <img src="/images/textures/cf32-texturing-guidelines/2.png" alt="aliased and antialiased" class="center" loading="lazy">
+    <img src="/images/textures/cf32-texturing-guidelines/2.png" alt="aliased and antialiased" class="center">
     <i class="center"><b>Picture 2:</b> A line with no antialiasing compared to a line with antialiasing applied to it.</i>
-    <img src="/images/textures/cf32-texturing-guidelines/3.png" alt="aa-example" class="center" loading="lazy">
+    <img src="/images/textures/cf32-texturing-guidelines/3.png" alt="aa-example" class="center">
     <i class="center"><b>Picture 3:</b> Example of antialiasing used in a texture featured in Classic Faithful.</i>
     <br>
     <li id="dithering"><b>Dithering</b> is where pixels of a color border are displaced in such a way that said border is no longer as sharply defined and has parts protruding in and out of the other color. Places where these can be used will be explained further in the material reference list, however in most cases using it gives it an overly noisy or sharp appearance which isn't desirable most of the time.
@@ -45,40 +45,40 @@ Over time, our community has adopted and come up with numerous terms regarding p
     <ol class="roman">
       <li id="checkerboard-dithering"><b>Checkerboard dithering</b> (also known as simply "checkerboarding") is not recommended in most cases, because it is too repetitive and usually doesn't fit the material. Special cases include chainmail and some particle effects. It looks, exactly as you'd expect, like a checkerboard of two colors.</li>
       <br>
-      <img src="/images/textures/cf32-texturing-guidelines/4.png" alt="checkerboard dithering transition" class="center" loading="lazy">
+      <img src="/images/textures/cf32-texturing-guidelines/4.png" alt="checkerboard dithering transition" class="center">
       <i class="center"><b>Picture 4:</b> Checkerboard dithering used as a transition between two colors.</i>
       <br>
       <li id="regular-dithering"><b>Regular dithering</b> (sometimes called "conventional dithering" or simply "dithering") consists of displacing pixels around the color border in such a way that little to no checkerboarding is created. These displaced pixels may look random, but oftentimes are cleverly laid out to avoid visual issues. Displaced pixels are usually a single pixel or sometimes a small cluster, but regular dithering should never convey any sense of directionality.</li>
       <br>
-      <img src="/images/textures/cf32-texturing-guidelines/5.png" alt="regular dithering textures" class="center" loading="lazy">
+      <img src="/images/textures/cf32-texturing-guidelines/5.png" alt="regular dithering textures" class="center">
       <i class="center"><b>Picture 5:</b> Examples of regular dithering being used on certain materials.</i>
       <br>
       <li id="linear-dithering"><b>Linear dithering (LD)</b> is exactly like regular dithering, but the displaced pixels are longer and face in a particular direction, as if regular dithering was stretched. This gives a streaky look to the texture in question, which is particularly useful for refined wood textures and certain types of stone.</li>
       <br>
-      <img src="/images/textures/cf32-texturing-guidelines/6.png" alt="linear dithering textures" class="center" loading="lazy">
+      <img src="/images/textures/cf32-texturing-guidelines/6.png" alt="linear dithering textures" class="center">
       <i class="center"><b>Picture 6:</b> Examples of linear dithering in wood and stone textures.</i>
       <br>
     </ol>
     <p>Do note that these methods can be mixed and matched in certain amounts to get a material looking as it should.</p>
     <li id="color-banding"><b>Color banding</b> describes the phenomenon of noticeable stripes of a single color appearing as a result of using multiple colors for a transition. This goes hand in hand with having no blending methods being employed, and just like using no blending it has a flat look which is generally undesirable. This can be prevented in many ways, such as through the usage of added colors, antialiasing, or simply reducing the amount or size of bands.</li>
     <br>
-    <img src="/images/textures/cf32-texturing-guidelines/7.png" alt="color banding" class="center" loading="lazy">
+    <img src="/images/textures/cf32-texturing-guidelines/7.png" alt="color banding" class="center">
     <i class="center"><b>Picture 7:</b> Left: An example of noticeable color banding. Right: Most of the color banding removed.</i>
     <br>
   </ol>
   <li id="upscaling-textures"><b>Upscaling (a texture)</b> refers to redrawing a vanilla resolution texture in a higher resolution (32x or 64x) according to these guidelines. In other contexts, it can refer to an image whose resolution has been increased. For example, all 1x1 pixels become 2x2 color areas using an image editing program, which is usually referred to as "nearest-neighbor" upscaling. There are other types of automatic upscaling (usually referred to as AI upscaling, despite having nothing to do with an AI) which can have varying levels of success such as bilinear and rotsprite. However, upscaling by hand will almost always look the best.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/8.png" alt="upscaled texture" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/8.png" alt="upscaled texture" class="center">
   <i class="center"><b>Picture 8:</b> Left: The vanilla 16x texture. Right: A 32x upscale of said texture.</i>
   <br>
   <li id="limited-palettes"><b>Limiting palettes (LP), indexing textures, or color quantizing</b> are names for the concept of reducing the amount of colors in a texture to only the necessary shades. This can either be done by hand or automatically using a program like GIMP or Aseprite. Limited palette textures generally have colors reused throughout the texture and noticeable color transitions, as opposed to a blurry texture where color transitions are fuzzy and hard to make out or noisy textures which will be covered directly below.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/9.png" alt="indexed textures" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/9.png" alt="indexed textures" class="center">
   <i class="center"><b>Picture 9:</b> Left: A "limited palette" texture. Center: A blurry texture. Right: A noisy texture.</i>
   <br>
   <li id="noise"><b>Noise</b>, as opposed to limited palette is a filter which randomly brightens and darkens pixels to give a grainer look, oftentimes used by novice pixel artists. In other contexts, it can mean a texture with no "definition", in that the detail has no meaning and is just a jumble of randomly placed pixels with no thought or reasoning behind them, oftentimes on materials that make no sense to be noisy.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/10.png" alt="noise" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/10.png" alt="noise" class="center">
   <i class="center"><b>Picture 10:</b> Left: A "noisy" texture with an excessively large palette. Right: A "noisy" texture with no definition and just a random mess of pixels.</i>
   <br>
   <li id="jappa"><b>Jasper "JAPPA" Boerstra</b> is the current art director for Minecraft, formerly working on the game's art from 2017 to 2022. In addition, he was mostly responsible for the 1.14 texture update.</li>
@@ -87,34 +87,34 @@ Over time, our community has adopted and come up with numerous terms regarding p
   <br>
   <li id="jappa-textures"><b>Jappa textures</b> directly oppose Programmer Art. They were made by dedicated pixel artists like Jappa and they have a consistent art style. They are featured in all versions after 1.14 inclusive.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/11.png" alt="jappa textures" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/11.png" alt="jappa textures" class="center">
   <i class="center"><b>Picture 11:</b> Left: Programmer art oak planks. Right: Jappa's oak planks.</i>
   <br>
   <li id="vattic"><b>Vattic</b> is the original creator of the Faithful 32x32 texture pack in 2010. In the following years, the pack exploded in popularity, but in 2016, Vattic disappeared from the internet following some unfortunate IRL circumstances, leaving his pack discontinued at the peak of its popularity. After being found again in 2020, he authorized the Faithful project to continue the pack officially. Classic Faithful is built on upscaling textures based on Vattic's original principles, and to emulate his original style with both the new, Jappa textures and updating legacy versions of the pack with later programmer art textures. All of Vattic's original art can be found unmodified in the <a href="https://web.archive.org/web/20170630235514/faithful32x32.com/dl/faithful32pack.zip/">Wayback Archive.</a></li>
   <br>
   <li id="false-lines"><b>False lines</b> are the occurrence of several elements and/or color areas of a texture lining up in such a way that they create an illusion of a straight line, even when there is none in reality.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/12.png" alt="mixel texture" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/12.png" alt="mixel texture" class="center">
   <i class="center"><b>Picture 12:</b> An example of false lines.</i>
   <br>
   <li id="mixels"><b>Mixels</b> describe pixels of clashing resolutions, for example if a texture uses 1x1 pixels and the other uses 2x2 pixels extensively, that would be considered mixels.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/13.png" alt="mixel texture" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/13.png" alt="mixel texture" class="center">
   <i class="center"><b>Picture 13:</b> Example of mixels in a texture.</i>
   <br>
   <li id="contrast"><b>Contrast</b> is a method of classifying a certain color palette. High contrast means that the colors look very different from each other, and low contrast means the colors look very similar to each other. In more technical terms, it's the distance from each color on the wheel, usually in brightness, but sometimes with a mix of saturation and hue differences as well.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/14.png" alt="contrast" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/14.png" alt="contrast" class="center">
   <i class="center"><b>Picture 14:</b> Left: Example of a texture with low contrast. Right: The same texture with higher contrast.</i>
   <br>
   <li id="depth-shading"><b>Depth shading</b> is an extremely versatile method of shading two or more pixel wide lines which can be employed in a multitude of scenarios. Essentially, one shades a thicker line to make one side lighter and one side darker, using some form of added color, or color from elsewhere in the texture. Depending on the material, the added color will either be lighter or darker than the base color, and this will go into more detail in the material reference list. While this term was initially used just for gaps, it has expanded over time to include any two pixel wide line that you want to shade in this method, including highlights and ridges.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/15.png" alt="depth shading" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/15.png" alt="depth shading" class="center">
   <i class="center"><b>Picture 15:</b> Examples of depth shading on gaps and highlights.</i>
   <br>
   <li id="stairing"><b>Stairing</b> is a method of making lines and curves, where each pixel moved up or down in the line is joined back to the previous one. This generally does not look the best in large amounts, and should be avoided in excess. However, it can be used in conjunction with thinner and thicker lines to give more natural gaps or lines to various textures.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/16.png" alt="stairing" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/16.png" alt="stairing" class="center">
   <i class="center"><b>Picture 16:</b> Left: An example of stairing being overused on a texture. Right: Stairing being used in small amounts alongside thicker and thinner lines.</i>
 </ol>
 
@@ -127,34 +127,34 @@ These requirements apply to all textures unless specified otherwise and must all
 <ol>
   <li id="follow-default"><b>Textures need to follow vanilla Minecraft textures whenever possible.</b> This should go without saying, but textures have to keep the same proportions, general coloration, and representation as vanilla. A good rule of thumb is to check how the texture looks from far away compared with vanilla; the less difference, the better.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/17.png" alt="default vs cf" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/17.png" alt="default vs cf" class="center">
   <i class="center"><b>Picture 17:</b> Right: A texture with vanilla color placement, proportions, and overall structure. Left: Its vanilla counterpart.</i>
   <br>
   <li id="reference-vattic"><b>When applicable, always reference <a href="https://web.archive.org/web/20170630235514/faithful32x32.com/dl/faithful32pack.zip/">Vattic's art</a>.</b> Another self explanatory one given the entire purpose of the pack. If the texture has a programmer art equivalent, or just generally fits into a similar material as one, always reference Vattic's original art when drawing textures. Not only does it make texturing much easier, but it also helps keep the stylistic cohesion of looking like Vattic's original Faithful 32x32.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/18.png" alt="vattic vs cf" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/18.png" alt="vattic vs cf" class="center">
   <i class="center"><b>Picture 18:</b> Left: Vattic's bricks. Right: Its Jappa equivalent.</i>
   <br>
   <li id="less-is-more"><b>With detailing, less is more.</b> Don’t overdo dithering or antialiasing, use the minimal amount of detail to keep textures from looking flat or ugly. Always ask yourself "could Jappa have done this in a 16x canvas" before adding additional detail; if large details are not present in vanilla there's probably a reason for it. If something genuinely could not fit in the vanilla texture and makes no sense to not add, such as gravel not containing actual rocks, then it can be acceptable to add. However, always get feedback before changing anything noticeable about any texture.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/19.png" alt="overdetailed textures" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/19.png" alt="overdetailed textures" class="center">
   <i class="center"><b>Picture 19:</b> Left: A texture with just enough detail. Right: An overdetailed texture.</i>
   <br>
   <li id="palette"><b>Don't overly change the vanilla palette.</b> Adding in-between colors is encouraged to eliminate a "plasticky" flat look, but don't overdo it by making the texture completely nonvanilla or blurry. Generally, between one and three added colors should suffice, and oftentimes none are even necessary to begin with. As well as this, ensure that the darkest and lightest colors of the texture are untouched to avoid the overall contrast being significantly altered; any added colors should just be used to blend contrasty and/or flat areas rather than create nonvanilla contrast in the palette. Another thing to note is to never change any already existing colors in a texture, only add to them. There are certain specific exceptions to this rule which will be covered later on.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/20.png" alt="constructive color use" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/20.png" alt="constructive color use" class="center">
   <i class="center"><b>Picture 20:</b> Left: Vanilla texture. Center: Unnecessary use of added colors. Right: Constructive use of added colors.</i>
   <br>
   <li id="1px-items"><b>When making item textures, thin out the borders to one pixel wide.</b> Pretty much exactly what it sounds like; two pixel wide outlines for items in 32x almost always look disproportionate and bloated. If the texture doesn't have a clear outline or the vanilla texture itself doesn't use a one pixel wide outline, then it can be acceptable to use more than one pixel, but nearly all of the time you should be thinning them out.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/21.png" alt="thinned outlines" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/21.png" alt="thinned outlines" class="center">
   <i class="center"><b>Picture 21:</b> Left: Examples of textures with two pixel wide outlines. Right: Textures with one pixel wide outlines.</i>
   <br>
   <li id="outdated-textures"><b>If a vanilla texture references an outdated texture, use the outdated texture as a base in the Classic Faithful counterpart.</b> Examples of this include the observer top using an outdated furnace base, the end crystal using an outdated bedrock texture, and smooth stone using an outdated stone texture.</li>
   <br>
   <li id="reuse-textures"><b>If a texture uses another texture as a base, use the already existing Classic Faithful rendition of it, if available.</b> An example of this would be planks and the crafting table. Don't make planks from scratch just for the crafting table texture, as not only would this cause inconsistencies if the two are used in conjunction, but it would also waste a lot of effort.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/22.png" alt="reusing textures" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/22.png" alt="reusing textures" class="center">
   <i class="center"><b>Picture 22:</b> A texture that directly references another. Note the identical plank background on the crafting table.</i>
   <br>
   <li id="useless-textures"><b>Don't upscale useless textures.</b> If a texture would end up looking identical to vanilla when upscaled, is unused, or is already so high resolution that there's no real need to upscale it, then just don't do it. It just bloats the file size of the pack and wastes your effort, pretty self explanatory.</li>
@@ -167,17 +167,17 @@ These are less specific ways to improve your textures, and unlike rules can be s
 <ol>
   <li id="mob-faces"><b>Mob faces</b> can be difficult to interpret. If making eyes, try to blend the corner of the eye into the next color over using an added color. This can be seen on a number of mob textures, as Vattic employed this method a lot. Try to upscale other features unless you cannot make it work (or it creates your new sleep paralysis demon), in which case leaving it the same as default is fine (a "mixel" face).</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/23.png" alt="mob faces" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/23.png" alt="mob faces" class="center">
   <i class="center"><b>Picture 23:</b> Left and center: Examples of "demixelled" mob faces. Right: A hard to interpret face left as mixels.</i>
   <br>
   <li id="jaggies-bad"><b>Smooth jagged lines whenever possible.</b> When upscaling lines and curves in a texture, you have to ensure jagged or lumpy edges (oftentimes referred to as "jaggies") do not form. Essentially, you want to ensure differing lengths of pixels within the curve don't alternate or repeat, rather curving it in a more natural way where the lengths of each section get longer or shorter consistently.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/24.png" alt="jaggies vs not jaggies" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/24.png" alt="jaggies vs not jaggies" class="center">
   <i class="center"><b>Picture 24:</b> Left: Examples of jagged edges and curves. Right: Examples of smooth edges and curves.</i>
   <br>
   <li id="overuse-2px"><b>Don't overuse undetailed two pixel wide lines.</b> Not only does it look mixelly or incomplete which is undesired, but it also makes the texture look flat. The best way to upscale these types of textures would be to add a color or use an existing color to depth shade the block to eliminate these straight two pixel wide lines, or to simply reduce the width of the band if necessary.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/25.png" alt="stairing pixels" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/25.png" alt="stairing pixels" class="center">
   <i class="center"><b>Picture 25:</b> Left: Improper interpretation of textures. Right: Utilizing the larger canvas size to remove unnecessarily thick lines.</i>
   <br>
   <li id="cross-reference"><b>Cross reference other similar textures.</b> This is one of the most important tips to make textures look like they fit in the pack in the first place. You don't just have to reference Vattic's art, but other pre-existing Classic Faithful textures as well. More information about how to shade specific materials can be found below, but this tip in particular will not only help you improve at getting the general style of Classic Faithful down, but improve at pixel art in general over time.</li>
@@ -192,133 +192,133 @@ This section goes into detail about how to shade materials that you shouldn't sh
 
 **Conventional/normal/painted upscaling** (used for basically everything not on this list) has no real special or unique way to shade these textures. Simply upscale them normally by smoothening out curves and shapes, taper off any lines and defined structures, add antialiasing and added colors to remove flat areas if and where needed, and keep stylistic cohesion present wherever possible by cross referencing existing textures as much as possible.
 
-<img src="/images/textures/cf32-texturing-guidelines/26.png" alt="conventionally upscaled textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/26.png" alt="conventionally upscaled textures" class="center">
 <i class="center"><b>Picture 26:</b> Examples of conventionally upscaled blocks.</i>
 
 <br id="gem-and-metals">
 
 **Gem and metal blocks** should be upscaled through a normal pass, and similar to the shading on large bricks if there are defined gaps and highlights, blend them. Added color usage is also encouraged to accurately portray a shiny material. For gaps, depth shade them by adding a lighter color(s) rather than a darker one, to give the texture an almost "glowy" look..
 
-<img src="/images/textures/cf32-texturing-guidelines/27.png" alt="gem and metal textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/27.png" alt="gem and metal textures" class="center">
 <i class="center"><b>Picture 27:</b> Examples of gem and metal blocks. Note the heavy usage of added colors and blended gaps.</i>
 
 <br id="contiguous-stones">
 
 **Contiguous stones** that are not broken up into defined shapes should not have any added colors, and should be upscaled in a highly "painted" style, meaning that blobs of color shouldn't have definition added to them where none exists, and it should be upscaled in a very literal sense of being closer to a simple "demixelling" pass. However, avoiding jagged edges and keeping stylistic cohesion present with the rest of the textures is still important.
 
-<img src="/images/textures/cf32-texturing-guidelines/28.png" alt="contiguous stone textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/28.png" alt="contiguous stone textures" class="center">
 <i class="center"><b>Picture 28:</b> Examples of contiguous stone textures. Note the lack of added detail and the plasticky look.</i>
 
 <br id="distinct-stones">
 
 **Rocky materials with distinct stones** should first use added colors to define what is a rock and what is a gap before doing anything else. After this, upscale normally while ensuring that the gaps and the rocks are visibly separated and don't overly blend into each other using added colors. Always shape based on the rocks, and the gaps will follow based on the rocks and look natural as a result. Otherwise, the rocks won't look anything like rocks!
 
-<img src="/images/textures/cf32-texturing-guidelines/29.png" alt="rocky textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/29.png" alt="rocky textures" class="center">
 <i class="center"><b>Picture 29:</b> Examples of textures with distinct rocks. Note the visible separation of the rounded rocks and gaps through added colors, particularly in comparison to their vanilla counterparts.</i>
 
 <br id="tiles">
 
 **Small bricks and tiles** should thin out the gaps to one pixel wide in the direction that looks best, and be upscaled normally from there. If the bricks have highlights or shadows, thin those out as well to one pixel wide. If the texture ends up looking flat due to the larger brick size after thinning out the gaps and highlights, added colors and even dithering sometimes may be helpful depending on the texture.
 
-<img src="/images/textures/cf32-texturing-guidelines/30.png" alt="small brick textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/30.png" alt="small brick textures" class="center">
 <i class="center"><b>Picture 30:</b> Examples of small bricks and tiles. Note the one pixel wide gaps/highlights and slight usage of dithering.</i>
 
 <br id="large-bricks">
 
 **Large bricks (and polished stones in certain situations)** should leave the gaps, highlights, and shadows two pixels wide, and be upscaled normally from there. Depth shade the gaps and highlights, and for the gaps add a darker color as opposed to gems which add a lighter color. This helps give the gaps a 3d effect and makes the gaps a lot less flat and "AI upscaled" looking. If the bricks have a linear pattern, small amounts of linear dithering may also be helpful.
 
-<img src="/images/textures/cf32-texturing-guidelines/31.png" alt="large brick textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/31.png" alt="large brick textures" class="center">
 <i class="center"><b>Picture 31:</b> Examples of larger bricks and polished stones. Note the usage of two pixel wide blended gaps, small amounts of linear dithering, but the overall painted look.</i>
 
 <br id="polished-stones">
 
 **Polished stone/wood** are the same as large bricks, only with the interior of the texture being tiled and the obvious tiling repetitions removed. However, only do this if it looks good, otherwise refer to the entry of large bricks if it has a "noisy" or nonvanilla appearance which is undesirable.
 
-<img src="/images/textures/cf32-texturing-guidelines/32.png" alt="polished stone textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/32.png" alt="polished stone textures" class="center">
 <i class="center"><b>Picture 32:</b> Examples of polished stone and wood blocks. Note how the detail looks tiled and much more fine compared to vanilla, and the usage of two pixel wide blended gaps.</i>
 
 <br id="logs-and-stems">
 
 **Tree bark and mushroom stems** should have heavy amounts of antialiasing in the direction the texture goes added manually using added colors. This is primarily done to preserve the aesthetic of Vattic's original logs, which had an extremely glossy, almost motion blurred appearance and had no real reasoning for being so.
 
-<img src="/images/textures/cf32-texturing-guidelines/33.png" alt="log and stem textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/33.png" alt="log and stem textures" class="center">
 <i class="center"><b>Picture 33:</b> Examples of heavily motion blurred logs. Note the usage of added colors going in the direction of the texture's linearity.</i>
 
 <br id="refined-wood">
 
 **Planks and other refined wood** should be upscaled with a lot of linear dithering and small amounts of antialiasing, to accurately portray a wood grain material. A method of doing this which is useful for planks involves stretching the vanilla texture, tiling it downwards, and fixing any awkward areas. Alternatively, if this method does not work well, simply extend out the detail to portray a linear look. Do not add colors unless absolutely necessary, and preserve default's contrast where possible.
 
-<img src="/images/textures/cf32-texturing-guidelines/34.png" alt="refined wood textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/34.png" alt="refined wood textures" class="center">
 <i class="center"><b>Picture 34:</b> Examples of refined wood. Note the detailed and linear look.</i>
 
 <br id="large-plants">
 
 **Leaves and larger plants** can use small amounts of dithering on the branches mixed in with a slightly increased usage of antialiasing and/or added colors. With thicker plants like cacti or bamboo, don't use any dithering and upscale conventionally.
 
-<img src="/images/textures/cf32-texturing-guidelines/35.png" alt="larger plant textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/35.png" alt="larger plant textures" class="center">
 <i class="center"><b>Picture 35:</b> Examples of larger plants. Note the lack of any blending method on stalks and stems.</i>
 
 <br id="foliage">
 
 **Flowers and other foliage** can use dithering more heavily than leaves or stalks. Similar to rocky stones, ensure that flowers have a defined shape and don't overly blend into the stems or leaves, and depending on the flower type either dither or antialias. For plant stems, antialias heavily and thin them out. Vines should be evenly conventionally dithered throughout the entire texture, and use heavy amounts of antialiasing in addition.
 
-<img src="/images/textures/cf32-texturing-guidelines/36.png" alt="foliage textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/36.png" alt="foliage textures" class="center">
 <i class="center"><b>Picture 36:</b> Examples of general foliage. Note the usage of dithering on the vines and on certain flowers, and how the flower stems were thinned out.</i>
 
 <br id="grass-fungi">
 
 **Grassy textures and certain fungi** should use a "jumble" or "scramble" filter if your editing program has that, with a few edits to fix mixels and other visual issues. If it doesn't, manually dither it to give it a coarse texture. Keep the palette as close to vanilla as possible to preserve the contrast, sometimes you may want to use additional effects and index it back to the vanilla palette.
 
-<img src="/images/textures/cf32-texturing-guidelines/37.png" alt="grassy textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/37.png" alt="grassy textures" class="center">
 <i class="center"><b>Picture 37:</b> Examples of grassy textures. Note the usage of patchy dithering.</i>
 
 <br id="sand">
 
 **Sand and other powdery materials** should tile the block in a 2x2 grid, then cut out random sections and rotate and/or flip them randomly to remove repetitions that stops the texture from looking just tiled on its own.
 
-<img src="/images/textures/cf32-texturing-guidelines/38.png" alt="powdery textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/38.png" alt="powdery textures" class="center">
 <i class="center"><b>Picture 38:</b> Examples of powdery materials. Note the fine detail and how it looks almost tiled but isn't.</i>
 
 <br id="sandstone">
 
 **Sandstone** should have large amounts of dithering present, a jumble tool may also suffice if necessary. Thin out natural gaps a lot more than otherwise, to give a more slate-like appearance. For more refined textures such as cut or chiseled sandstone antialiasing can also be used to properly convey smoothness.
 
-<img src="/images/textures/cf32-texturing-guidelines/39.png" alt="sandstone textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/39.png" alt="sandstone textures" class="center">
 <i class="center"><b>Picture 39:</b> Examples of sandstone textures. Note the heavy usage of dithering, and heavy usage of antialiasing on polished blocks.</i>
 
 <br id="prismarine">
 
 **Prismarine** should use added colors and antialiasing excessively to convey a smooth, shiny material. Thin out and curve highlights, and reduce gaps to one pixel wide.
 
-<img src="/images/textures/cf32-texturing-guidelines/40.png" alt="prismarine textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/40.png" alt="prismarine textures" class="center">
 <i class="center"><b>Picture 40:</b> Examples of prismarine textures. Note the heavy reliance on antialiasing to prevent flatness, and the one pixel wide gaps and highlights.</i>
 
 <br id="contrasty">
 
 **Contrasty dirt and stone textures** should soften the colors by using a translucent layer of the midtone color or manually editing the contrasty colors, and tile vanilla 16x on top of the texture at a low opacity using another different layer. However, only do this if the texture is particularly contrasty and the vanilla palette doesn't look good in any way even with added colors, as this method can add a lot of unnecessary colors and should be used as a last resort.
 
-<img src="/images/textures/cf32-texturing-guidelines/41.png" alt="tiled detail textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/41.png" alt="tiled detail textures" class="center">
 <i class="center"><b>Picture 41:</b> Examples of contrasty dirt and stone textures. Note the noisy look.</i>
 
 <br id="ice-glass">
 
 **Icy and glassy textures** should use antialiasing excessively. For items in particular, added colors should be used to properly convey a smooth surface. For textures with an obvious diagonal shine, thin out the shine marks and use antialiasing in the direction of the the marks to convey a streaky look, almost like diagonal linear dithering.
 
-<img src="/images/textures/cf32-texturing-guidelines/42.png" alt="ice and glass textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/42.png" alt="ice and glass textures" class="center">
 <i class="center"><b>Picture 42:</b> Examples of glassy and icy blocks. Note the usage of antialiasing and added colors.</i>
 
 <br id="fur-fabric">
 
 **Fur and fabric** should avoid false lines forming at all costs, which is very easy to happen given the spiky nature of these materials. Upscale it normally, and try to avoid having lines every two pixels from 16x by thickening and thinning out some of the spikes on the texture. Generally, the farther from the base color a spike gets, the thinner it should be. This creates a more natural effect and stops it from looking mindlessly upscaled.
 
-<img src="/images/textures/cf32-texturing-guidelines/43.png" alt="fabric and fur textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/43.png" alt="fabric and fur textures" class="center">
 <i class="center"><b>Picture 43:</b> Examples of fabric and fur textures. Note the heavy usage of tapering lines and spikes.</i>
 
 <br id="door-trapdoor">
 
 **Doors and trapdoors** should be upscaled like what they are made of. However, doors should always use one pixel wide borders, while trapdoors can use two pixel wide blended outlines for the outer border. This discrepancy is due to Vattic's original wooden door and trapdoor having this inconsistency present.
 
-<img src="/images/textures/cf32-texturing-guidelines/44.png" alt="door and trapdoor textures" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/44.png" alt="door and trapdoor textures" class="center">
 <i class="center"><b>Picture 44:</b> Examples of doors and trapdoors. Note the usage of depth shading on the trapdoors and one pixel wide lines on the doors.</i>
 
 <br>
@@ -339,7 +339,7 @@ While vanilla programmer art is deprecated and no longer updated, therefore lead
 
 Even though newer Jappa textures have a distinct style from programmer art, the exact way a developer would have gone about making a certain texture can't ever be known for sure, and it is not up to us to interpret. The aforementioned nylium and netherrack issue has a clear solution, to replace the Jappa netherrack with programmer art netherrack. However, a texture like blackstone has no clear programmer art equivalent, and as such shouldn't be touched and reuse the Jappa texture.
 
-<img src="/images/textures/cf32-texturing-guidelines/45.png" alt="progartification" class="center" loading="lazy">
+<img src="/images/textures/cf32-texturing-guidelines/45.png" alt="progartification" class="center">
 <i class="center"><b>Picture 45:</b> Left: Nylium, an example of a texture that should be "progartified" to fix an obvious oversight in the vanilla programmer art resource pack. Right: Blackstone, an example of a texture with no clear programmer art equivalent and as such should not be changed from its Jappa base.</i>
 
 That being said, here's a section to help upscale any of the most different aspects of programmer art and Jappa art.
@@ -354,27 +354,27 @@ Noise is usually present on textures because they are an original, programmer ar
 <ol>
   <li id="tiling-with-edits"><b>Tiling with edits</b> works very well if the texture is powdery or grainy, particularly when the texture is too chaotic and noisy to do it by hand. However, the most important part is to edit the texture after it's been tiled, or tiling repetitions will occur and it won't look good as a result.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/46.png" alt="tiling repetitions" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/46.png" alt="tiling repetitions" class="center">
   <i class="center"><b>Picture 46:</b> Left: The default texture. Center: The default texture tiled in a 2x2 grid. Right: Tiling repetitions removed.</i>
   <br>
   <li id="jumbling"><b>Jumbling</b>, sometimes also called "scrambling", "diffuse", or just "randomize", is a method of automatically upscaling textures with a lot of noise, which you may recall is how you should be upscaling grassy textures. Essentially, it gets demixelled by shuffling the pixels around randomly near, meaning that color placement stays similar to default. However, this method has a very rough and almost patchy look and not all materials will support it.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/47.png" alt="jumbling" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/47.png" alt="jumbling" class="center">
   <i class="center"><b>Picture 47:</b> Examples of texture upscaling via jumbling.</i>
   <br>
   <li id="tiled-detail"><b>Tiled detail</b>, which contrasty stone and dirt textures also use, however just without the contrast reduction. After doing a cursory upscale, likely using another method on this list such as bilinear or indexing, tile the same vanilla 16x texture you're upscaling on top of the texture at a low opacity using a different layer. This works best on dirty or very detailed textures however, as it has a very grainy appearance, similar to jumbling but even more detailed.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/48.png" alt="tiled detail" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/48.png" alt="tiled detail" class="center">
   <i class="center"><b>Picture 48:</b> Left: An automatically upscaled base. Center: The vanilla texture tiled. Right: The two overlaid on top of each other.</i>
   <br>
   <li id="softening"><b>Softening</b> is effectively the opposite effect of tiled detail, in that rather than making it more contrasty and grainy, it makes it less so. Basically, rather than tiling default on top you put a heavily blurred version of the texture on top at a very low opacity, decreasing the contrast on the colors and softening the overall texture to look less sharp.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/49.png" alt="softening" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/49.png" alt="softening" class="center">
   <i class="center"><b>Picture 49:</b> Left: A base upscale. Center: The base upscale blurred. Right: The two overlaid on top of each other.</i>
   <br>
   <li id="indexing"><b>Indexing and re-adding noise</b> is a method where you index the palette down to a more reasonable size, upscale like normal or however the material should be shaded, then adding noise back and approximating the palette to something similar to what it originally was. On textures with defined gaps or other visible structures this is oftentimes the most viable option.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/50.png" alt="indexing" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/50.png" alt="indexing" class="center">
   <i class="center"><b>Picture 50:</b> Top right: The default vanilla texture. Top left: Indexed down to essential colors. Bottom Left: An upscale of the indexed version. Bottom right: Added noise back in, finished version.</i>
   <br>
   <li id="native-upscale"><b>Natively upscaling</b> is pretty much exactly what it sounds like, and by far the most difficult on this list. Simply upscale the texture as usual, while keeping the noise present and avoiding mixelly areas.</li>
@@ -389,7 +389,7 @@ The majority of additional techniques for upscaling blurry textures are shared w
 <ol>
   <li id="automatic-upscale"><b>Automatic upscaling</b>, such as a bilinear or bicubic upscaling filter rather than nearest neighbor and doing it by hand can oftentimes do the trick. As it tends to add a lot of additional transition tones, it fits blurry textures very well.</li>
   <br>
-  <img src="/images/textures/cf32-texturing-guidelines/51.png" alt="indexing" class="center" loading="lazy">
+  <img src="/images/textures/cf32-texturing-guidelines/51.png" alt="indexing" class="center">
   <i class="center"><b>Picture 51:</b> Left: The programmer art bone block. Right: A bilinear upscale of said bone block.</i>
 </ol>
 
diff --git a/pages/textures/f32-texturing-guidelines.md b/pages/textures/f32-texturing-guidelines.md
index 86265db..c6732c3 100644
--- a/pages/textures/f32-texturing-guidelines.md
+++ b/pages/textures/f32-texturing-guidelines.md
@@ -29,15 +29,15 @@ Over time, our community has adopted and come up with numerous terms regarding p
     <li id="no-blending"><b>No blending</b> is a simple border between two or more colours, without any additional effects. An early in-development texture usually has no blending, which is added in later stages of the process.
     <br>This type of blending is discouraged in most cases, because it usually ends up making the texture look “plasticky” and fails to portray the material of the texture.</li>
     <br>
-    <img src="/images/textures/f32-texturing-guidelines/1.png" alt="no blending" class="center" loading="lazy">
+    <img src="/images/textures/f32-texturing-guidelines/1.png" alt="no blending" class="center">
     <i class="center"><b>Picture 1:</b> Example of a border between two colours, with no blending applied.</i>
     <br>
     <li id="anti-aliasing"><b>Anti-Aliasing (AA)</b> is a technique used to smooth the jaggedness of a pixelated border between colours. It uses an additional in-between colour (usually taken from somewhere else in the texture) to provide a smoother transition. This method is recommended to be used in conjunction with no blending on very smooth surfaces, like metal or plastic. It can also be used in small amounts on most other materials to eliminate drastic borders between light and dark colours.</li>
     <br>
-    <img src="/images/textures/f32-texturing-guidelines/2.png" alt="aliased and anti-aliased" class="center" loading="lazy">
+    <img src="/images/textures/f32-texturing-guidelines/2.png" alt="aliased and anti-aliased" class="center">
     <i class="center"><b>Picture 2:</b> A line with no anti-aliasing compared to a line with anti-aliasing applied to it.</i>
-    <img src="/images/textures/f32-texturing-guidelines/3.png" alt="anti-aliasing" class="center" loading="lazy">
-    <img src="/images/textures/f32-texturing-guidelines/4.png" alt="anti-aliasing" class="center" loading="lazy">
+    <img src="/images/textures/f32-texturing-guidelines/3.png" alt="anti-aliasing" class="center">
+    <img src="/images/textures/f32-texturing-guidelines/4.png" alt="anti-aliasing" class="center">
     <i class="center"><b>Picture 3:</b> Example of anti-aliasing used in a texture featured in Faithful.</i>
     <br>
     <li id="dithering"><b>Dithering</b> is perhaps the most used texturing term in the Faithful servers. The word describes a method used very commonly for the many textures of raw, unprocessed materials found in Minecraft, such as stone, wood and others. To achieve dithering, one is required to displace the pixels of a colour border in such a way that said border is no longer as defined and has parts protruding in and out of the other colour.
@@ -47,37 +47,37 @@ Over time, our community has adopted and come up with numerous terms regarding p
       <li id="checkerboard-dithering"><b>Checkerboard dithering</b> (AKA checkering/checkerboarding) is not recommended in most cases, because it is too repetitive and usually doesn’t fit the material.
       <br>Special cases include chainmail and sand (in small amounts). It looks like a checkerboard of two colours.</li>
       <br>
-      <img src="/images/textures/f32-texturing-guidelines/5.png" alt="checkerboard dithering transition" class="center" loading="lazy">
+      <img src="/images/textures/f32-texturing-guidelines/5.png" alt="checkerboard dithering transition" class="center">
       <i class="center"><b>Picture 4:</b> Checkerboard dithering used as a transition between two colours.</i>
       <br>
-      <img src="/images/textures/f32-texturing-guidelines/6.png" alt="checkerboard dithering texture" class="center" loading="lazy">
+      <img src="/images/textures/f32-texturing-guidelines/6.png" alt="checkerboard dithering texture" class="center">
       <i class="center"><b>Picture 5:</b> Example of checkerboard dithering in a texture.</i>
       <br>
       <li id="regular-dithering"><b>Regular dithering</b> is the single most used dithering method, as it can be utilised in the largest array of cases, and the vast majority of Faithful textures, be it in high or low levels. The technique consists of placing displaced pixels around the colour border (which look random, but oftentimes are cleverly laid out to avoid visual issues) in such a way that little to no checkerboarding/checkering is created. Displaced pixels usually take the shape of a single 1px square or a 2x1px rectangle, but never full-on intentional lines. Regular dithering doesn’t convey any sense of directionality!</li>
       <br>
-      <img src="/images/textures/f32-texturing-guidelines/7.png" alt="regular dithering texture" class="center" loading="lazy">
+      <img src="/images/textures/f32-texturing-guidelines/7.png" alt="regular dithering texture" class="center">
       <i class="center"><b>Picture 6:</b> Example of regular dithering in a texture.</i>
       <br>
       <li id="linear-dithering"><b>Linear dithering (LD)</b> is just like dithering, but with displaced pixels taking the shape of (usually) 1px wide lines that all go in the same direction, most of the time vertically or horizontally. This method is best used for textures that already have a linear pattern in vanilla, such as stone or wood.</li>
       <br>
-      <img src="/images/textures/f32-texturing-guidelines/8.png" alt="linear dithering texture" class="center" loading="lazy">
+      <img src="/images/textures/f32-texturing-guidelines/8.png" alt="linear dithering texture" class="center">
       <i class="center"><b>Picture 7:</b> Example of linear dithering in a texture.</i>
       <br>
     </ol>
     <p>Do note that all of these dithering methods can be mixed and matched at various intensities in a single texture. This is often required to accurately portray a desired material.</p>
-    <img src="/images/textures/f32-texturing-guidelines/9.png" alt="mixed dithering textures" class="center" loading="lazy">
+    <img src="/images/textures/f32-texturing-guidelines/9.png" alt="mixed dithering textures" class="center">
     <i class="center"><b>Picture 8:</b> Examples of mixed dithering methods: linear and regular on stone, regular and hints of checkerboard dithering on sand, respectively.</i>
     <br>
     <li id="colour-banding"><b>Colour banding</b> describes the phenomenon of noticeable stripes of a single colour appearing as a result of using multiple colours for a transition. This is generally unwanted, just because it doesn’t look the best. Colour banding can be reduced by narrowing the individual colour stripes to be 1 pixel thick or so, but this method often can and does look bad. If it doesn’t work, keep the colours banded, it’s not that much of an issue.</li>
     <br>
-    <img src="/images/textures/f32-texturing-guidelines/10.png" alt="colour banding" class="center" loading="lazy">
+    <img src="/images/textures/f32-texturing-guidelines/10.png" alt="colour banding" class="center">
     <i class="center"><b>Picture 9:</b> Left: An example of a texture with noticeable colour banding. Right: The same texture, with colour banding mostly eliminated.</i>
     <br>
   </ol>
   <li id="indexing-colours"><b>Indexing colours</b> refers to the process of reducing the colour count of an image. This is used when basing a texture off of its (usually) programmer art version, which oftentimes has needless amounts of colours. Since using too many colours would be against these guidelines, one is required to index them. This can be done automatically in an image editing program by using the Indexed Colours mode, but since that can cause problems, it’s recommended to either switch back to RGB/8 after indexing is done or to do the indexing manually.</li>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/11.png" alt="indexing" class="center" loading="lazy">
-  <img src="/images/textures/f32-texturing-guidelines/12.png" alt="indexing" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/11.png" alt="indexing" class="center">
+  <img src="/images/textures/f32-texturing-guidelines/12.png" alt="indexing" class="center">
   <i class="center"><b>Picture 10:</b> Left: An example of a texture with too many colours. Right: The same texture, with indexed colours.</i>
   <br>
   <li id="upscaling-a-texture"><b>Upscaling (a texture)</b> in Faithful's context refers to redrawing a vanilla-resolution texture in a higher resolution (32x or 64x) according to these guidelines. In other contexts, it can refer to an image whose resolution has been increased for example, all 1x1 pixels become 2x2 colour areas using an image editing program, and/or with an AI.</li>
@@ -88,22 +88,22 @@ Over time, our community has adopted and come up with numerous terms regarding p
   <br>
   <li id="jappa-textures"><b>Jappa textures</b> directly oppose Programmer Art. They were made by a single artist – JAPPA – and they have a consistent art style. They are featured in all versions after 1.14 inclusive.</li>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/13.png" alt="Jappa textures" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/13.png" alt="Jappa textures" class="center">
   <i class="center"><b>Picture 11:</b> Left: Programmer art oak planks. Right: Jappa oak planks.</i>
   <br>
   <li id="false-lines"><b>False lines</b> are the occurrence of several elements and/or colour areas of a texture lining up in such a way that they create an illusion of a straight line, even when there is none in reality.</li>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/14.png" alt="false lines" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/14.png" alt="false lines" class="center">
   <i class="center"><b>Picture 12:</b> An example of false lines.</i>
   <br>
   <li id="mixels"><b>Mixels</b> describe pixels of clashing resolutions, for example if a texture uses 1x1 pixels and the other uses 2x2 pixels extensively, that would be considered mixels.</li>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/15.png" alt="mixel texture" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/15.png" alt="mixel texture" class="center">
   <i class="center"><b>Picture 13:</b> Example of mixels in a texture.</i>
   <br>
   <li id="contrast-palette"><b>A contrasty colour palette</b> is a colour palette utilising colours which have high contrast between each other. Contrast in colour theory is defined as the difference in brightness or hue between two or more colours.</li>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/16.png" alt="false lines" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/16.png" alt="false lines" class="center">
   <i class="center"><b>Picture 14:</b> Left: example of a texture with low contrast. Right: example of a texture with high contrast.</i>
 </ol>
 
@@ -118,17 +118,17 @@ These requirements apply to all textures unless specified otherwise and must all
   <br>
   <li id="1px-wide"><b>Outlines, dividing lines and the like that would end up being 2 pixels wide when upscaled to double the resolution should almost always be 1 pixel wide.</b> Pretty straight-forward, most lines in Faithful should be 1 pixel wide (examples: glass, gold block, iron ingot, diamond). There are exceptions to this, especially if a line is not an outline/dividing line,  and/or is curvy, or would be off-centre if it was 1 pixel wide. In these cases it’s acceptable to make the line wider.</li>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/17.png" alt="outlines" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/17.png" alt="outlines" class="center">
   <i class="center"><b>Picture 15:</b> Top: Vanilla texture. Bottom left: Incorrect interpretation of lines present in the vanilla texture. Bottom right: Correct interpretation.</i>
   <br>
   <li id="shading"><b>All textures are required to be shaded correctly according to their material and shape.</b> Before shading a texture, define its material correctly (rough/smooth, shiny/non-reflective), and then use adequate shading methods. These are further described in the Material and Shape Reference List.</li>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/18.png" alt="shading" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/18.png" alt="shading" class="center">
   <i class="center"><b>Picture 16:</b> Left: Incorrectly shaded item (see the Material and Shape Reference List). Right: Correctly shaded item.</i>
   <br>
   <li id="meaning"><b>All elements of a texture need to have their meaning, and should look like actual things instead of just shapes.</b> Don’t just mindlessly upscale textures without paying attention to what they’re supposed to represent: When drawing an element of a texture, always think about what it’s supposed to represent in vanilla, and then draw the element according to this idea (while still keeping similarity to vanilla in mind, of course).</li>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/19.png" alt="correct upscaling" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/19.png" alt="correct upscaling" class="center">
   <i class="center"><b>Picture 17:</b> Top: Vanilla texture. Bottom left: Incorrect upscale. Bottom right: Correct interpretation (note the individual leaves, which are required in double the resolution but aren’t possible to be depicted in the vanilla resolution).</i>
   <br>
   <li id="vanilla-colour-palette"><b>Textures should stick to the vanilla colour palette.</b> Self-explanatory; try to only use the colours that the vanilla texture uses. If you’re trying to blend two colours together using anti-aliasing, you can usually re-use a colour from elsewhere in the texture. In difficult circumstances you can add colours to help you, but most of the time, one or two is enough. If the texture you’re upscaling already has many colours, you can use that to your advantage, but you should still keep the palette limited to more or less than 10 colours. Additionally, never change existing colours from the vanilla palette! If a vanilla texture uses 5 specific colours, make sure your texture uses these exact ones.
@@ -136,12 +136,12 @@ These requirements apply to all textures unless specified otherwise and must all
   <br>
   <li id="too-much-details"><b>Do not make up features/details that are not clearly present in the vanilla texture and don’t add them to your texture, unless not having them makes absolutely no sense in double the resolution.</b> While upscaling a texture, one might have the tendency to add significant elements that are not present in vanilla. This is discouraged, as it makes a texture look too distant from the vanilla look most of the time. This also applies to various details in a texture: If appropriate, a normal amount is encouraged, but don’t overdo it.</li>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/20.png" alt="texture details" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/20.png" alt="texture details" class="center">
   <i class="center"><b>Picture 18:</b> Top: Vanilla texture. Bottom left: A texture with too many added details. Bottom right: A texture with just enough details and features.</i>
   <br>
   <li id="blending-colours"><b>When blending colour using anti-aliasing or dithering, make sure that darkest colours never directly border the lightest ones and vice versa.</b> Dirt is an example of this. Always have a transition colour in between the colours. In some cases this is desired, but not in many. If you’re a beginner Faithful contributor, always follow this rule.</li>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/21.png" alt="colour borders" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/21.png" alt="colour borders" class="center">
   <i class="center"><b>Picture 19:</b> Left: Improper colour borders. Note the very harsh-looking colour borders caused by the lack of a transition colour. Right: Correct colour transitions.</i>
   <br>
   <li id="erase-colour-banding"><b>Try to eliminate colour banding, if possible.</b> As already described in previous sections, this can be done by cleverly reducing the width of each colour band to one or two pixels. Don’t brute force it though, in some cases where the colour palette is especially limited this can harm the texture overall. It’s certainly possible to do in most cases though.</li>
@@ -150,7 +150,7 @@ These requirements apply to all textures unless specified otherwise and must all
   <br>
   <li id="other-texture-as-base"><b>If a texture uses another texture as a base, use the already existing Faithful rendition of it, if available.</b> An example of this would be stone and ores. Don’t make stone from scratch just for the ore texture. Make your life simpler and re-use existing textures when you can.</li>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/22.png" alt="already existing texture" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/22.png" alt="already existing texture" class="center">
   <i class="center"><b>Picture 20:</b> An ore texture. Note how the already existing stone texture is used in the background.</i>
   <br>
   <li id="identical-when-upscaled"><b>If a texture would end up looking identical to vanilla when upscaled (while following all the above rules), it shall not be included in Faithful.</b> Self-explanatory. Textures like these look exactly the same as vanilla when used in-game, and so they only bloat the pack and needlessly increase the file size.</li>
@@ -159,30 +159,33 @@ These requirements apply to all textures unless specified otherwise and must all
   <br>
   <li id="noise"><b>Noise</b> that was clearly generated using a filter is only to be kept if removing it would alter the general look of the texture too significantly. If noise is upscaled, its palette should be reduced to a minimum.</li>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/23.png" alt="when to remove noise" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/23.png" alt="when to remove noise" class="center">
   <i class="center"><b>Picture 21:</b> In this particular texture, the noise is contrasty and visible enough to be kept and upscaled.</i>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/24.png" alt="texture with noise removed" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/24.png" alt="texture with noise removed" class="center">
   <i class="center"><b>Picture 22:</b> The shulker box is an example of a texture where the noise is barely visible, and therefore should be removed.</i>
-  <p class="red-text center" style="text-align: center;"><b>Special rules and/or exceptions can apply to specific textures if the Art Director Council approves it.</b></p>
 </ol>
 
+::: danger NOTE
+<b>Special rules and/or exceptions can apply to specific textures if the Art Director Council approves it.</b>
+:::
+
 **Tips**
 
 <ol>
   <li id="mob-faces"><b>Mob faces</b> can be particularly hard to interpret in only double the resolution. If all attempts at upscaling the face end up looking bad, it is acceptable to use a “mixel-face” – just keeping the vanilla mob face, without any edits, on an upscaled background.</li>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/25.png" alt="acceptable mob face" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/25.png" alt="acceptable mob face" class="center">
   <i class="center"><b>Picture 23:</b> An acceptable mob face.</i>
   <br>
   <li id="dithering-tip"><b>Dithering</b> should not be overdone, unless you’re re-drawing a particularly noisy texture (e.g. sand). Also while dithering, try to avoid lone pixels, as in the ones that do not border other ones of the same colour.</li>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/26.png" alt="overdone dithering" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/26.png" alt="overdone dithering" class="center">
   <i class="center"><b>Picture 24:</b> A close-up of a colour transition with lone pixels, which should be avoided.</i>
   <br>
   <li id="stairing-pixels"><b>Try to minimise the occurrence of stairing pixels</b>, an example of which is shown below.</li>
   <br>
-  <img src="/images/textures/f32-texturing-guidelines/27.png" alt="stairing pixels" class="center" loading="lazy">
+  <img src="/images/textures/f32-texturing-guidelines/27.png" alt="stairing pixels" class="center">
   <i class="center"><b>Picture 25:</b> Left: Example of a colour transition featuring stairing pixels. Right: The same transition, with the stairing removed.</i>
 </ol>
 
@@ -200,28 +203,28 @@ There exists a correlation between the roughness and shininess of a material and
 
 **Smooth metal** should only use anti-aliasing as a colour blending method, or no blending at all. The colour palette should be limited and contrasty. In some cases mild linear dithering is acceptable if it’s required to keep the texture from looking like plastic. Additionally, in item textures, faces of an object which are in the shade should have a lighter outline (as well as the item outline itself) to simulate light reflection.
 
-<img src="/images/textures/f32-texturing-guidelines/28.png" alt="smooth metal textures" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/28.png" alt="smooth metal textures" class="center">
 <i class="center"><b>Picture 26:</b> Examples of various smooth metal textures.</i>
 
 <br id="rough-metal">
 
 **Rough metals** such as raw ore blocks, netherite, anvils and even iron golems should follow the same lighting logic as regular metals while being dithered. Regular dithering should be used as the preferred method.
 
-<img src="/images/textures/f32-texturing-guidelines/29.png" alt="rough metal textures" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/29.png" alt="rough metal textures" class="center">
 <i class="center"><b>Picture 27:</b> Examples of rough metal textures.</i>
 
 <br id="gems">
 
 **Diamonds and other gemstones** in Minecraft’s context should be shaded like reflective rocks more than anything – they usually don’t let much light pass through, unlike their real-life counterparts. Only anti-aliasing should be used here. For faces in the shade in item textures, the same shading logic as on smooth metal textures applies.
 
-<img src="/images/textures/f32-texturing-guidelines/30.png" alt="gemstone textures" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/30.png" alt="gemstone textures" class="center">
 <i class="center"><b>Picture 28:</b> Examples of gemstone textures.</i>
 
 <br id="contiguous-stones">
 
 **Contiguous stones** that are not broken up into smaller rocks are very rough, so they should use dithering as much as possible. For textures with a linear pattern (stone, dripstone), it is recommended to use a mixture of linear and regular dithering to emphasise the material even more. Anti-aliasing can be used here, but only when the material is smoother than usual, like with dripstone.
 
-<img src="/images/textures/f32-texturing-guidelines/31.png" alt="raw stone textures" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/31.png" alt="raw stone textures" class="center">
 <i class="center"><b>Picture 29:</b> Examples of contiguous raw stone textures.</i>
 
 <br id="polished-stones">
@@ -229,42 +232,42 @@ There exists a correlation between the roughness and shininess of a material and
 **Polished stones** should use dithering (linear when applicable) a bit, but not nearly as much as raw stones. Instead, anti-aliasing should be used in heavier amounts to express the smoothness of the material.
 Smooth stone is a special case however, as it directly reuses regular stone’s texture pattern (which you should do as well, as per rule 10).
 
-<img src="/images/textures/f32-texturing-guidelines/32.png" alt="polished stone textures" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/32.png" alt="polished stone textures" class="center">
 <i class="center"><b>Picture 30:</b> Examples of polished stone textures.</i>
 
 <br id="rocky-materials">
 
 **Rocky materials** such as cobblestone and netherrack should be dithered as much as raw stones, but unless the rocks are arranged in a clear linear pattern (like in the deepslate texture), linear dithering should never be used.
 
-<img src="/images/textures/f32-texturing-guidelines/33.png" alt="rocky material textures" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/33.png" alt="rocky material textures" class="center">
 <i class="center"><b>Picture 31:</b> Examples of rocky material textures.</i>
 
 <br id="wood">
 
 **Wood** should use a lot of linear dithering and very minimal amounts of regular dithering. To smooth colour transitions, anti-aliasing can be used if it looks good.
 
-<img src="/images/textures/f32-texturing-guidelines/34.png" alt="wood textures" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/34.png" alt="wood textures" class="center">
 <i class="center"><b>Picture 32:</b> Examples of wood textures.</i>
 
 <br id="flowers">
 
 **Most flowers, foliage, and other plant matter** can use dithering (linear or regular) depending on the general roughness/smoothness of the surface. While flower petals can employ this shading method, genuine leaves should never use dithering.
 
-<img src="/images/textures/f32-texturing-guidelines/35.png" alt="plant textures" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/35.png" alt="plant textures" class="center">
 <i class="center"><b>Picture 33:</b> Examples of plant textures.</i>
 
 <br id="corals">
 
 **Corals** should mainly use anti-aliasing, but regular dithering is also acceptable.
 
-<img src="/images/textures/f32-texturing-guidelines/36.png" alt="coral textures" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/36.png" alt="coral textures" class="center">
 <i class="center"><b>Picture 34:</b> Examples of coral textures.</i>
 
 <br id="sands">
 
 **Sand and other powdery materials** should be heavily dithered: there should be no large contiguous area of a single colour. Even checkerboard dithering can be used in this case, in small amounts. Anti-aliasing is encouraged to a smaller degree. This also applies to gravel, where the individual rocks that make up the material are clearly visible.
 
-<img src="/images/textures/f32-texturing-guidelines/37.png" alt="powdery textures" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/37.png" alt="powdery textures" class="center">
 <i class="center"><b>Picture 35:</b> Examples of powdery textures.</i>
 
 <br id="bee-nests">
@@ -279,7 +282,7 @@ Smooth stone is a special case however, as it directly reuses regular stone’s
 
 **Glazed terracotta** should only use minimal amounts of anti-aliasing when required, otherwise no colour blending should be present.
 
-<img src="/images/textures/f32-texturing-guidelines/38.png" alt="glazed terracotta textures" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/38.png" alt="glazed terracotta textures" class="center">
 <i class="center"><b>Picture 36:</b> Examples of glazed terracotta textures.</i>
 
 <br id="glass">
@@ -290,7 +293,7 @@ Smooth stone is a special case however, as it directly reuses regular stone’s
 
 **Bones** (including skeletons) should ideally mainly use anti-aliasing, with a bit of occasional linear dithering sprinkled in, near colour transitions. This applies to tusks as well.
 
-<img src="/images/textures/f32-texturing-guidelines/39.png" alt="bone textures" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/39.png" alt="bone textures" class="center">
 <i class="center"><b>Picture 37:</b> Examples of bone textures.</i>
 
 <br id="cloth-paper">
@@ -301,7 +304,7 @@ Smooth stone is a special case however, as it directly reuses regular stone’s
 
 **Skin (in mob textures) and leather** should mainly use anti-aliasing. Not using many colour blending methods can lead to heavy colour banding and looking plasticky, so this is a reminder to try and eliminate that if possible. Depending on the roughness of a specific skin type, linear and regular dithering can also be used to communicate the feel of the material.
 
-<img src="/images/textures/f32-texturing-guidelines/40.png" alt="skin textures" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/40.png" alt="skin textures" class="center">
 <i class="center"><b>Picture 38:</b> Examples of skin textures.</i>
 
 <br id="creepers">
@@ -312,14 +315,14 @@ Smooth stone is a special case however, as it directly reuses regular stone’s
 
 **Fur and hair** should employ linear dithering, but in such a way that it creates visible strands of hair. Some regular dithering and anti-aliasing can also come in handy. This applies to wool on sheep as well.
 
-<img src="/images/textures/f32-texturing-guidelines/41.png" alt="fur/hair textures" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/41.png" alt="fur/hair textures" class="center">
 <i class="center"><b>Picture 39:</b> Examples of fur/hair textures.</i>
 
 <br id="fish">
 
 **Fish entities** should have clearly visible scales present where appropriate (don’t just draw a checkerboard!). Basically all colour blending methods can be used here.
 
-<img src="/images/textures/f32-texturing-guidelines/42.png" alt="fish texture" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/42.png" alt="fish texture" class="center">
 <i class="center"><b>Picture 40:</b> Example of a fish texture.</i>
 
 <br>
@@ -330,14 +333,14 @@ Smooth stone is a special case however, as it directly reuses regular stone’s
 
 **Cylindrical type objects** such as iron bars, individual dynamite sticks that make up TNT and metal railings should have visible shades along both sides and a highlight on the side near the centre like so:
 
-<img src="/images/textures/f32-texturing-guidelines/43.png" alt="cylindrical type objects" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/43.png" alt="cylindrical type objects" class="center">
 <i class="center"><b>Picture 41:</b> An example showing how to shade cylindrical type objects</i>
 
 ## Part 4: Fixing JAPPA’s Mistakes and Things He’s Forgotten
 
 Faithful extends its field of expertise to correcting JAPPA’s mistakes. One such example would be the oak sign, which until 1.17 used this texture:
 
-<img src="/images/textures/f32-texturing-guidelines/44.png" alt="forgotten texture" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/44.png" alt="forgotten texture" class="center">
 <i class="center"><b>Picture 42:</b> Pre-1.17 vanilla oak sign texture</i>
 
 <br>
@@ -350,7 +353,7 @@ Let’s take the sign texture mentioned above as an example. It is clear that it
 
 On the contrary, a texture that should NOT be “Jappafied” is blaze powder, for instance. The number of colours and the shading style make it clear that it was not made by JAPPA, meaning that it can be classed as programmer art. One might think of trying to re-interpret the texture using the art style present in other item textures by JAPPA, but one major problem arises – there is no obvious way to do it correctly. What colour palette should be used? How contrastive should the colours be? Should the shape be preserved? Would the same shading methods be kept? Nobody knows for sure, and these assumptions are not for Faithful artists to make. As such, this texture, and all the other textures that fall into this category, are to be left as-is, and should be upscaled like any other texture according to the rules mentioned above.
 
-<img src="/images/textures/f32-texturing-guidelines/45.png" alt="texture should not be jappafied" class="center" loading="lazy">
+<img src="/images/textures/f32-texturing-guidelines/45.png" alt="texture should not be jappafied" class="center">
 <i class="center"><b>Picture 43:</b> Blaze powder, an example of a texture that should not be “Jappafied”.</i>
 
 ## Conclusion
diff --git a/pages/textures/f64-texturing-guidelines.md b/pages/textures/f64-texturing-guidelines.md
index 189663c..45fb300 100644
--- a/pages/textures/f64-texturing-guidelines.md
+++ b/pages/textures/f64-texturing-guidelines.md
@@ -22,12 +22,12 @@ To put it simply, a 64x64 canvas is **big**. With this added space comes both ad
 
 While 32x isn't a small resolution, some blocks and items can benefit from the additional space 64x offers to make the texture look closer to its real-life equivalent. For instance, the 64x fishing rod moves up the string like a real fishing rod would, which would not be possible in Faithful 32x.
 
-<img src="/images/textures/f64-texturing-guidelines/fishing_rod.png" alt="fishing rod example" class="center" loading="lazy">
+<img src="/images/textures/f64-texturing-guidelines/fishing_rod.png" alt="fishing rod example" class="center">
 <i class="center">Adding additional detail where vanilla could not.</i>
 
 This point is more about simply working with the resolution rather than against it, so remember not to go overboard with added details. The same goes for adding colours — try bringing in colours from other parts of the texture or dither harsh colour transitions instead of adding colours.
 
-<img src="/images/textures/f64-texturing-guidelines/fermented_spider_eye.png" alt="excessive dithering example" class="center" loading="lazy">
+<img src="/images/textures/f64-texturing-guidelines/fermented_spider_eye.png" alt="excessive dithering example" class="center">
 <i class="center">Unnecessary detailing.</i>
 
 As a rule of thumb, if the detail you're adding would be possible in 32x without significantly compromising its look, the addition is probably too excessive.
@@ -36,12 +36,12 @@ As a rule of thumb, if the detail you're adding would be possible in 32x without
 
 While the Faithful 32x guidelines emphasizes using one pixel wide highlights and shadows for textures, this can have problems in 64x with both visibility and rendering. Glass can turn completely invisible on small screens with a one pixel wide outline in 64x, so using a two pixel wide shaded outline is better in these circumstances.
 
-<img src="/images/textures/f64-texturing-guidelines/glass.png" alt="glass example" class="center" loading="lazy">
+<img src="/images/textures/f64-texturing-guidelines/glass.png" alt="glass example" class="center">
 <i class="center">One pixel wide versus two pixel wide gaps. Note how the thinner outlines become nearly invisible in-game.</i>
 
 Exceptions can also apply to blocks with defined gaps, such as stone bricks. Thin gaps can make the texture look flat or unrealistically proportioned at times, but highlights don't have this issue. Therefore, using smaller highlights and bigger gaps ends up looking the best in this scenario, despite the 32x reference texture having the same width for both.
 
-<img src="/images/textures/f64-texturing-guidelines/stone_bricks.png" alt="brick example" class="center" loading="lazy">
+<img src="/images/textures/f64-texturing-guidelines/stone_bricks.png" alt="brick example" class="center">
 <i class="center">An example of mismatching gap and highlight sizes looking better than being fully consistent.</i>
 
 Above all, get feedback from others about using a one pixel versus two pixel wide outline, since it can vary from texture to texture.
@@ -50,12 +50,12 @@ Above all, get feedback from others about using a one pixel versus two pixel wid
 
 The Faithful 32x guidelines go into depth about not upscaling mob faces, but in 64x there's a lot more space to experiment. Many eye shapes that don't work well in 32x can become viable in higher resolutions since there's more space to add realistic detail.
 
-<img src="/images/textures/f64-texturing-guidelines/squid_eyes.png" alt="good eyes example" class="center" loading="lazy">
+<img src="/images/textures/f64-texturing-guidelines/squid_eyes.png" alt="good eyes example" class="center">
 <i class="center">Upscaling the squid's eyes works well in 64x since the eyes can be properly rounded.</i>
 
 The same rule about keeping a "mixel face" if no options look particularly good still applies, but try different options and see if any look good first.
 
-<img src="/images/textures/f64-texturing-guidelines/villager_eyes.png" alt="bad eyes example" class="center" loading="lazy">
+<img src="/images/textures/f64-texturing-guidelines/villager_eyes.png" alt="bad eyes example" class="center">
 <i class="center">While a cross-eyed model could be considered a limitation, removing that can have... undesirable effects.</i>
 
 ## Materials
@@ -68,7 +68,7 @@ Dithering in Faithful 64x works differently to dithering in Faithful 32x. Conven
 
 To get around this, Faithful 64x heavily relies on a form of linear dithering often colloquially called "wispy" dithering. Instead of using single pixels to smooth out colour transitions, small clusters of pixels are used instead. These clusters usually face in the same direction, giving a slight linear look to the texture.
 
-<img src="/images/textures/f64-texturing-guidelines/linear_dithering.png" alt="wispy dithering example" class="center" loading="lazy">
+<img src="/images/textures/f64-texturing-guidelines/linear_dithering.png" alt="wispy dithering example" class="center">
 <i class="center">Checkerboard-heavy dithering in 32x should be converted into clusters and lines in 64x, with minimum single-pixel displacement.</i>
 
 Do note that other types of dithering can still be used, and there are occasions with particularly rough textures where conventional dithering can be used as well.
@@ -79,22 +79,22 @@ This is a much more general reference than the Faithful 32x guidelines, since th
 
 **Metal and polished gems** should use no dithering of any type.
 
-<img src="/images/textures/f64-texturing-guidelines/polished.png" alt="polished texture examples" class="center" loading="lazy">
+<img src="/images/textures/f64-texturing-guidelines/polished.png" alt="polished texture examples" class="center">
 <i class="center">Examples of polished textures.</i>
 
 **Smooth-ish textures** should not use any lone pixels with dithering, but can have additional linear detail to fill empty spaces.
 
-<img src="/images/textures/f64-texturing-guidelines/smooth.png" alt="smoothish texture examples" class="center" loading="lazy">
+<img src="/images/textures/f64-texturing-guidelines/smooth.png" alt="smoothish texture examples" class="center">
 <i class="center">Examples of somewhat smooth textures.</i>
 
 **Hair and fur** should use a combination of wispy and conventional dithering, to portray a messy and chaotic surface accurately.
 
-<img src="/images/textures/f64-texturing-guidelines/fur.png" alt="fur and hair texture examples" class="center" loading="lazy">
+<img src="/images/textures/f64-texturing-guidelines/fur.png" alt="fur and hair texture examples" class="center">
 <i class="center">Examples of hair and fur.</i>
 
 **Stone, planks, and other rough textures** should use both linear and wispy dithering, but not much conventional dithering.
 
-<img src="/images/textures/f64-texturing-guidelines/rough.png" alt="rough texture examples" class="center" loading="lazy">
+<img src="/images/textures/f64-texturing-guidelines/rough.png" alt="rough texture examples" class="center">
 <i class="center">Examples of rough, natural textures.</i>
 
 For materials not explicitly stated here, follow their 32x equivalents where possible. In particularly difficult cases, you can also ask the original author what their intent was, something not possible in 32x.