Technical SEO and performance[ ]
Technical SEO and performance
Finding out why something is slow or doesn't show up on Google and fixing it in the code, not with a plugin on top.
01
The problem
A slow page loses people before they read anything, and if search engines don't understand its structure, nobody arrives either. The cause is almost always in the code: unoptimised images, too much JavaScript or a structure that doesn't make sense.
02
How I work on it
I work on it in the code. This very site is the example: the blog, the structured data for Google, the two language versions and how each section loads are all done that way.
- -Measure firstBefore changing anything, I measure with Lighthouse and Core Web Vitals to find where the real problem is.
- -Fix the causeImages, JavaScript loading, fonts or rendering: whatever is slowing it down, not whatever's easiest to touch.
- -A structure that makes senseSemantic HTML, structured data and metadata so search engines know what each thing is.
- -Check the resultMeasure again to see whether the change worked.
03
How I'd do it
Review
Measure performance, review the structure and see what's being penalised.
- ›Lighthouse
- ›Core Web Vitals
- ›Structure and metadata
Fix
Prioritise what has the most impact and fix it in the code.
- ›Loading and images
- ›Structured data
- ›Sitemap and canonicals
Measure again
Compare before and after to confirm the improvement.
- ›Before and after
- ›What's still pending
04
What it'd include
- ✓Performance report
- ✓Loading improvements applied
- ✓Structured data
- ✓Reviewed sitemap and metadata
- ✓Before and after comparison