Performance optimization Practical
Who pays for the milliseconds a tag adds?
A tracking script does not stop at downloading. While it is parsed and executed the main thread is busy, and a busy page ignores fingers. That cost is…
Technote
WordPress know-how, from real work Technotes worth picking
5 articles· Performance optimization · Marketers
Performance optimization Practical
This is how a landing page gets heavy
Nobody decides to make a landing page heavy. It accumulates: one addition per campaign, and nothing ever removed when the campaign ends.
Performance optimization Practical
When field and lab data disagree, which do you believe?
Lab data is one reproducible run under controlled conditions; field data is the distribution of what real customers experienced. When they disagree, they are answering different questions.
Performance optimization Intro
The Lighthouse score is a summary; the work is in the items
The score is several metrics weighted into one number. What you can act on is the list underneath it — and that list, not the number, is what…
Performance optimization Intro
The three routes from speed to revenue
"A second of delay costs this much conversion" is a number from somebody else's site. Once you know the three routes from speed to money, you can measure…
Cited
Technotes worth reading next
Topics outside WordPress are collected on Dongji Communication Tech Insights, run by the same team. The summaries below are quoted from the originals; the titles link to them.
-
Working with AI
Writing a CLAUDE.md — teaching an AI coding assistant your project
AI coding tools such as Claude Code, Cursor and Copilot do better work the more precisely they know your project. Here is a structure and a set of principles that hold up.
-
Working with AI
Prompting an AI for UI design — drafting with Claude and GPT
Asking an AI to "make a nice button" gets you a disappointing button. Structured prompts that carry constraints, references and a defined role get you the design you meant.
-
Themes & plugins
SCSS from the ground up — variables through module structure
The core syntax of SCSS (Sass) and what it solves that plain CSS cannot: variables, nesting, mixins, @use and module structure — organised around patterns you can use immediately.
-
Themes & plugins
Design tokens and theme colour systems — brand identity in SCSS variables
How to turn a colour palette from a pile of hex codes into a system that means something — semantic token structure and SCSS variable patterns, from a real project.
-
Performance optimization
Designing a responsive typography system — the science of readability
Hard-coded pixel font sizes are over. Type scales, fluid sizing with clamp(), Korean webfont optimisation and line-height ratios — building typography that reads well on any screen.
-
Development workflow
From Figma to SCSS — a designer-developer handoff guide
Minimising what gets lost between a Figma file and the code: extracting tokens, naming components, keeping the spacing system in sync — the whole workflow, step by step.