Technical SEO · Live own-site implementation

From crawl friction to a cleaner, faster search foundation.

A screenshot-backed case study showing how I diagnosed, implemented and retested technical SEO improvements across performance, crawlability, indexation and measurement.

View verified results ↓Discuss your website ↗

47 → 90Verified Lighthouse performance

5.6s → 1.3sBest verified LCP run

27.5s → 1.7sSpeed Index, selected runs

1 → 0Internal 4xx errors

2 → 0Internal 3xx URLs

01 · Business brief

A portfolio site needed technical trust, not just attractive pages.

The goal was to make service and proof pages easy to discover, fast enough to use and accurately measured. The work started with the audience, conversion path and key URLs—then moved into technical evidence.

Business

Independent Meta Ads Marketer & SEO Specialist.

Audience

Founders and marketing teams evaluating capability and proof.

Goal

Clean crawl paths, indexable pages, faster rendering and reliable tracking.

Key surfaces

Home, services, portfolio, case studies and blog.

All screenshots are sourced from my own SEO publications and practical implementation records.

02 · Verified scorecard

Before and after, with the source and limitation attached.

Lab results vary by device, extensions and run conditions. Category scores, individual metrics and crawl checks are therefore kept separate.

Measure	Before	Verified after	Outcome	Tool
Lighthouse Performance	47	90	+43 points	Chrome Lighthouse
Largest Contentful Paint	5.6s	1.3s	−76.8%	Selected lab runs
Speed Index	27.5s	1.7s	−93.8%	Selected lab runs
Internal client errors	1	0	Fixed	Screaming Frog
Internal redirects	2	0	Fixed	Screaming Frog
Final HTML state	Mixed crawl	8/8: 200 & indexable	Clean retest	Screaming Frog

Latest reported run: Performance 93 and Accessibility 100 after continued cleanup. The preserved score screenshot is the preceding 90 / 96 / 100 / 100 run, so 93 / 100 is labelled as reported—not presented as screenshot proof.

All screenshots are sourced from my own SEO publications and practical implementation records.

03 · Performance engineering

Diagnose the rendering path, fix the main bottleneck, rerun.

Lighthouse, PageSpeed insights and source review isolated LCP priority, render-blocking CSS, JavaScript cost, main-thread work and contrast issues.

01 · BASELINE

Expose the bottleneck

Performance 47; LCP 5.7s and TBT 5,810ms in the earliest preserved run.

02 · IMPLEMENT

Prioritize the hero

Preloaded the LCP image, added high fetch priority and reviewed CSS/JS delivery.

03 · RETEST

Verify several signals

Best selected metrics reached LCP 1.3s and Speed Index 1.7s; preserved score reached 90.

Lighthouse baseline showing Performance 47, Accessibility 96, Best Practices 96 and SEO 100 — Before
**Performance score: 47**The report also warns that Chrome extensions affected this run.

Lighthouse metrics with FCP 1.8 seconds, LCP 5.7 seconds, TBT 5810 milliseconds, CLS 0 and Speed Index 3.5 seconds — Before
**Metric-level baseline**FCP 1.8s · LCP 5.7s · TBT 5,810ms · CLS 0 · SI 3.5s.

HTML source showing preload for anjuman-anwar.jpg with fetchpriority high — Fix
**Source-level LCP prioritization**The above-the-fold image was preloaded and given `fetchpriority="high"`.

Performance run showing FCP 0.8 seconds, LCP 5.6 seconds, TBT 1560 milliseconds, CLS 0 and Speed Index 27.5 seconds — Before
**Selected slow rendering run**LCP 5.6s and Speed Index 27.5s exposed severe delay.

Improved run showing FCP 0.9 seconds, LCP 1.3 seconds, TBT 1460 milliseconds, CLS 0 and Speed Index 1.7 seconds — After
**Best verified metric run**FCP 0.9s · LCP 1.3s · TBT 1,460ms · CLS 0 · SI 1.7s.

LCP breakdown showing time to first byte 70 milliseconds and element render delay 410 milliseconds — Retest
**LCP subpart review**TTFB 70ms and render delay 410ms isolated the remaining delay.

Lighthouse showing Performance 90, Accessibility 96, Best Practices 100 and SEO 100 — After
**Preserved scorecard**Performance 90 · Accessibility 96 · Best Practices 100 · SEO 100.

All screenshots are sourced from my own SEO publications and practical implementation records.

04 · Crawlability & architecture

Follow every redirect back to its internal source.

Screaming Frog separated internal/external URLs, response codes and Inlinks “From → To” sources. Outdated hrefs were edited, legacy redirects retained where needed, then the site was recrawled.

Screaming Frog baseline with 78 URLs, 68 success responses, 8 redirects and 1 client error — Before
**Broken asset found**78 URLs · 68 success · 8 redirects · 1 client error.

Screaming Frog showing eight redirects and inlinks to case-studies/index.html — Before
**Redirect inventory**The Inlinks panel exposed which pages still used redirecting destinations.

HTML source with navigation link to case-studies/index.html — Fix
**Locate the exact href**Navigation and content references were inspected at source level.

Updated HTML source where case-studies/index.html returns zero matches — Fix
**Replace with clean destination**The old `index.html` path returns 0/0 after direct-link cleanup.

Screaming Frog showing two internal 301 redirects — Before retest
**Two internal 301 URLs remained**The Inlinks panel made each source-to-destination relationship actionable.

Screaming Frog showing zero internal redirects, redirect chains, loops and client errors — After
**Clean internal response path**Internal 3xx 0 · chains 0 · loops 0 · internal 4xx 0.

Screaming Frog final HTML list with eight URLs all 200 OK and indexable — Final QA
**8/8 HTML URLs: 200 OK and indexable**Crawl depth 0–1; unique inlinks 3–8; internal redirect chains/loops 0.

All screenshots are sourced from my own SEO publications and practical implementation records.

05 · Indexation & canonicalization

Move from crawlable to confidently indexable.

Google Search Console verified Google’s view; source review and Screaming Frog validated the implemented metadata and final internal state.

Google Search Console showing URL is on Google, indexed and served over HTTPS — Verified
**URL is on Google**Page indexed and served over HTTPS.

GSC showing crawl allowed yes, fetch successful, indexing allowed yes, user canonical none and Google canonical inspected URL — Early snapshot
**Canonical gap visible**User-declared canonical None; Google selected the inspected URL.

HTML source showing title, description, robots, canonical and Open Graph metadata — Fix
**Self-canonical and metadata implemented**Final tested filters reported 0 canonical issues and 8/8 self-referencing canonicals.

GSC sitemap report showing sitemap.xml submitted with Success status — After
**Sitemap submitted successfully**`sitemap.xml` returned Success.

GSC performance with 4 clicks, 6 impressions, 66.7 percent CTR and position 1 — Directional
**Early search signal**4 clicks · 6 impressions · 66.7% CTR · position 1. Very small sample.

All screenshots are sourced from my own SEO publications and practical implementation records.

06 · Media QA

Image hygiene measured at URL and source level.

The tested crawl showed 0 missing alt text, 0 missing alt attributes and 0 images above 100 kB, while exposing 25 of 37 images without intrinsic size attributes.

Screaming Frog image overview showing 25 missing size attributes among 37 images and zero missing alt text — Before
**25 images lacked width/height attributes**Explicit dimensions were added to SEO portfolio evidence images.

Status: Partially Fixed / Needs Monitoring. The record does not preserve a full-site zero-issue recrawl for this filter, so completion is not overstated.

All screenshots are sourced from my own SEO publications and practical implementation records.

07 · Measurement QA

Lead tracking validated after source changes.

GTM and GA4 are supporting measurement QA—not substitutes for crawl or performance tools. They confirm that lead interactions stayed observable.

Google Tag Manager preview showing failed generate lead event — Before
**Failure reproduced**The broken trigger was visible before publication.

Google Tag Manager preview showing generate lead firing — After
**`generate_lead` fired**Trigger logic was corrected and retested.

Google Analytics 4 Realtime report showing lead event — Verified
**GA4 received the event**End-to-end confirmation connected the interaction to the analytics property.

All screenshots are sourced from my own SEO publications and practical implementation records.

08 · Workflow

A repeatable audit-to-retest sequence.

DISCOVER

Business, audience, CTA and key URLs

Mapped the service discovery and lead-enquiry journey.

BASELINE

GSC, Lighthouse, PageSpeed and Screaming Frog

Captured index state, metrics, response codes, inlinks and media issues.

FIX

HTML, links, metadata and asset priority

Edited source files and normalized technical signals.

DEPLOY

Hostinger file update

Corrected files were uploaded live. Completion is user-confirmed; no separate Hostinger UI screenshot was preserved.

RETEST

Fresh crawl and lab reruns

Confirmed final HTML health, indexability, performance movement and measurement flow.

All screenshots are sourced from my own SEO publications and practical implementation records.

09 · Findings register

Issue, evidence, owner and retest in one view.

“Fixed” means the stated retest passed; unresolved proof is labelled Partially Fixed or Needs Monitoring.

ID	Issue / scope	Evidence	Impact	Recommendation	Priority	Effort	Owner	Retest	Status
TSEO-01	Broken hero image URL	1 internal 404	Rendering + crawl quality	Correct asset path	High	Low	SEO / Dev	Internal 4xx = 0	Fixed
TSEO-02	Internal links to redirecting paths	2 internal 301 URLs	Extra hop	Link to clean paths	High	Low	SEO	Internal 3xx = 0	Fixed
TSEO-03	Canonical absent in early GSC snapshot	User canonical: None	Signal ambiguity	Add self-canonical	High	Low	SEO / Dev	Source + SF	Fixed
TSEO-04	Slow LCP	5.6s / SI 27.5s	User experience	Preload LCP asset; review CSS/JS	High	Medium	SEO / Dev	LCP 1.3s	Fixed
TSEO-05	Main-thread cost	TBT 1,560 → 1,460ms selected runs	Responsiveness	Continue script reduction	Medium	Medium	Dev	Mobile lab + field data	Monitor
TSEO-06	Missing image size attributes	25/37 images	Potential layout shift	Add width/height	Medium	Low	Dev	Fresh image crawl	Partially fixed
TSEO-07	Sitemap / index validation	GSC Success; URL on Google	Discovery confidence	Maintain and monitor	Medium	Low	SEO	GSC monitoring	Fixed
TSEO-08	Lead event failed	GTM fail → fire; GA4	Conversion evidence	Correct trigger	High	Low	Analytics	GTM + GA4	Fixed

All screenshots are sourced from my own SEO publications and practical implementation records.

10 · Outcome

Technical SEO delivered as implementation, not a checklist.

Each claim is tied to a screenshot, URL, metric or crawl filter; fixes are assigned, deployed and retested.

Results boundary: this case study documents technical quality improvements and early search evidence. Rankings, traffic and leads depend on competition, content, authority, demand and time; no ranking or revenue guarantee is implied.

All screenshots are sourced from my own SEO publications and practical implementation records.

Need the same clarity on your site?

Turn technical findings into a prioritized, testable action plan.

I can audit key pages, document the evidence, communicate fixes and retest the result.

Book a technical SEO review ↗