Hi — I’m Eslam Hamed. I build things for the web as a Senior Software Engineer (.NET) and AI Product Engineer, and I do it from Cairo, Egypt.

A few weeks ago, I opened Google Search Console for my portfolio. I expected a small pat on the back. Instead, I got that quiet, uncomfortable feeling that hits when the dashboard is politely saying: “Yeah… this could be better.” 😅

And I know myself — when something is “kind of fine,” it’s dangerously easy to spend a full day tweaking random things and calling it progress. So I tried a different approach.

I treated AI like a teammate I could sanity-check ideas with. I fed it the report, asked for a simple plan, and then promised myself I’d work through it from easiest to hardest. No wandering. No ego. Just steps.

The first fix was about people, not rankings

Search Console pointed out something I genuinely didn’t notice. My site was stopping mobile users from zooming.

It’s one of those things that doesn’t bother you until you remember: not everyone views your site the same way you do. For someone trying to read comfortably, blocking zoom is basically saying, “Good luck.”

So I removed the no-zoom behavior and let the site behave normally. It took minutes. It also felt like the kind of fix that makes you proud for the right reasons.

Then I saw the performance report… and yeah, it needed work

The site looked decent, but it didn’t feel great. Stuff loaded out of order. Some sections shifted while I was reading. It had that “almost smooth” vibe — which is basically the worst kind.

I asked the AI one simple thing:

Give me a clean checklist from easy to hard. Start with the quick wins.

That’s when things clicked. Not because AI did the work (it didn’t), but because it saved me from that endless loop of “maybe I should optimize this… or this… or this…”

What I improved (the real-world version)

• I stopped the page from jumping around: I gave images clear sizing rules so the layout stays stable while things load. Once you notice layout shift, you can’t unsee it.
• I pushed the heavy stuff later: Blog images, icons, and logos now load when you scroll. The first view feels lighter, and the page feels like it’s moving with you instead of against you.
• I made fonts behave like adults: Text shows up quickly and doesn’t suddenly jump when the font file finally arrives.
• I added proper caching: Returning visitors don’t have to download the same assets every time. It’s one of those invisible upgrades… until you feel how much faster everything is.

After these changes, the site went from “a bit heavy and jumpy” to “clean and calm.” And honestly — that’s the feeling I want when someone lands on my portfolio.

SEO wasn’t about tricks — it was about being understood

Speed matters, but I also want the right people to actually find me. Especially for searches like: Eslam Hamed, software engineer Cairo, .NET backend developer, and AI engineer portfolio.

So I focused on the basics — the unglamorous stuff that makes search engines trust a site:

• Clear titles and descriptions: so search results don’t look like placeholders.
• A sitemap and robots file: basically a friendly map and some polite instructions.
• A “this is who I am” identity block: so it’s obvious the site is about Eslam Hamed and my work.
• Verified ownership: so Google and Bing treat changes like they matter.

The biggest upgrade: my blog became real pages

This one was a turning point. My blog used to behave like a single page that swaps content. It looked fine, but it wasn’t doing my writing any favors in search.

So I changed it to something simpler (and more honest): a real blog page, and a real page for each post.

Now every article has its own home — and a better chance to show up when someone searches for things related to .NET, backend, or AI.

I kept the one-page vibe… but made it easier to discover

I like the smooth, animated one-page portfolio experience. I didn’t want to kill that.

So I kept the same experience for humans, but added direct, crawlable links for search engines (like About / Resume / Contact).

Best of both worlds: it still feels modern, and it’s easier to index.

What I learned (the part I’ll actually remember)

• AI doesn’t replace developers. It replaces the wasted time between decisions.
• If you ask for “easy to hard,” you ship faster and make fewer mistakes.
• A great portfolio isn’t only design. It’s also clarity, speed, and trust.

Final thought: AI won’t stop developer magicians from doing magic. It just helps us do more magic… faster. 🪄⚡

Keywords: Eslam Hamed, portfolio website, Senior Software Engineer, .NET developer, backend engineer, AI Product Engineer, Cairo, Egypt, Google Search Console, portfolio SEO, personal website.