Day 13: Performance and Optimization Checks

Dec. 11, 2024, 9:20 p.m.

It’s Not Perfect, But Neither Am I: A Day in the Life of Optimizing Blogggel

Good morning, afternoon, or whatever time it is that you’ve decided to give me your precious eyeballs. It’s Sazzzel here again, reporting from the front lines of the Blogggel development battlefield. Today, I tackled performance optimization, which is a posh way of saying, “I spent hours trying to make my code slightly less embarrassing.”

Let me paint the picture for you: I woke up, brewed a cup of tea (I am British—we do this like breathing), and opened up Blogggel. It loaded, which was an excellent start. Then I noticed something. My buttons—which were supposed to be sleek and inviting—looked like a toddler’s art project on a slow internet connection. It was time to roll up my sleeves and start optimizing.

Step 1: Slimming Down the CSS

First stop, CSS. My style sheet looked as if it had eaten one too many biscuits. It was bloated with unnecessary rules, including an unused .fabulous-glow class that I vaguely remember testing in Week 1 (it did not make anything fabulous). I spent the morning tidying it up, removing classes that were about as useful as a chocolate teapot, and trimming down redundancies. It’s now leaner, meaner, and… still functional (thank goodness).

Step 2: Image Compression, or "Why Are These Pictures So Chunky?"

Next, I tackled the images. Apparently, I had been uploading images in their full, glorious 4000x4000 resolution. Who doesn’t want a close-up of a blog post thumbnail that could double as a mural, right? Well, my users, for one. After compressing and resizing them to sensible dimensions, I shaved a good few seconds off the load time. Blogggel is now practically sprinting compared to before. (Though let’s be honest, it’s still more of a brisk jog.)

Step 3: Script Shenanigans

Then came the scripts. Oh, the scripts. Some of them were like that one uncle at a family wedding who just won’t stop talking: taking up space, contributing little. I reviewed every external library, checked my own scripts, and, with a heavy heart, decided to let go of a redundant dependency I had been clinging to for no reason other than sentimentality. Farewell, FancyFont.js. You were never actually used, but you were there for me in spirit.

Step 4: Accessibility Tweaks (Because I’m a Nice Person)

I couldn’t call it a proper optimization day without addressing accessibility. Screen readers now have actual descriptive alt text for all images, and I’ve made sure the navigation is friendly to keyboard users. I also resisted the urge to label every button “Click Me, Mate.” Small victories.

Lessons Learned (Other Than Don’t Be Lazy with Assets)

Optimizing is a bit like decluttering your house. You don’t realize how much rubbish you’ve accumulated until you start looking for it. But once you’ve done the work, everything feels lighter, cleaner, and… well, less likely to fall apart under pressure. Today was a reminder that even simple things can have a big impact, much like a good cup of tea and a sarcastic quip.

What’s Next?

Tomorrow, I’ll be prepping for the big launch. Blogggel is nearly ready to face the world (or at least my classmates). If all goes well, it will dazzle with its functionality and minimalist charm. If it doesn’t… well, I’ll just blame it on the weather. That’s the British way.

So, here’s to another productive day of development. Remember, folks: code like nobody’s watching, but optimize like you’re about to get audited.

Cheers,
Sazzzel



No comments yet. Be the first to comment!