Own website · Development notes

Making my portfolio easier to find, browse and contact

A practical improvement to my own website: make the project gallery lighter to browse, make my work clearer to search systems, and check that a contact message reaches my inbox.

Request a website review

The problem was bigger than the page's appearance

My portfolio already introduced my work and displayed website screenshots. The remaining questions were functional: was the site publishing clear search information, were large images being used sensibly, and could a visitor send a message through the custom domain?

That made this a small project about the whole path from discovery to inquiry, rather than a visual redesign.

A contact form checked through to the inbox

The form sends validated inquiries to my Gmail address through a server-side endpoint. The visitor's address is used for replies, while the delivery account and recipient stay in server configuration.

The work addressed the allowed origin for the public www domain, Gmail app-password formatting, and useful failure feedback. A successful message is reported only after the mail server accepts the recipient.

The important final check happened in the live site: a test inquiry was submitted in Chrome and the corresponding email was observed in my Gmail inbox on October 20, 2026.

Clear identity and crawlable information

I added a consistent canonical address, page and social sharing metadata, structured information connecting my name to the site, a sitemap and crawler guidance. The details reflect the work and experience visible on the page.

Live checks confirmed the published discovery files and the redirect from the duplicate index.html address. Search Console reported the homepage indexed and the sitemap successfully processed. Those checks establish discoverability; they are not a claim about a future ranking or AI recommendation.

Keep the full screenshot for the moment it is wanted

The gallery uses responsive WebP previews instead of downloading every original PNG as a thumbnail. The full-resolution WebP is loaded when someone opens a project. This keeps the image-focused presentation while avoiding a full screenshot download for a visitor who only wants to scan the gallery.

The image pipeline preserves the original files outside the public output. Checks confirmed all 24 generated gallery assets were available on the live site. No new page-speed score or business result is claimed here.

What this project shows

A small website still has several connected jobs: communicate the work, load the right assets, expose accurate information to search systems, and deliver the inquiry. Checking the final destination is what makes a working form different from a button that only looks finished.

Questions before getting started

Was this a client project?

No. This is my own portfolio. It is included as a direct example of the implementation and verification behind a small business website.

Did the work improve search rankings or conversion?

No ranking or conversion improvement is claimed. The verified outcomes were the published search information, live asset availability, Search Console indexing status and receipt of a contact-form test email.

Related reading

Does your website's inquiry path need attention?

Tell me what visitors should be able to do and where the current experience stops short.

Discuss your website