Site performance
Give your fonts a small, deliberate budget
A font family can bring several files and several layout decisions. Keep only the styles the site actually uses.
Open guide ↗Independent WordPress guides
Site performance
Understand what loads, what waits and what to measure.
Site performance
Count what an embedded widget brings with it
A small visible widget can bring a large set of requests. Evaluate the feature and its dependencies together.
Open guide ↗
Site performance
A video preview can wait for a real click
A preview should make the next action obvious and preserve the information around the video.
Open guide ↗
Site performance
Count plugin work, not just installed plugins
The number in the plugin list does not describe the work done on a particular page.
Open guide ↗
Site performance
Do not turn database cleanup into guesswork
A row that looks old is not necessarily disposable. Begin with ownership, a recoverable copy and a specific reason to clean.
Open guide ↗
Site performance
Understand editor background requests before disabling them
Periodic editor requests can support real features. Identify the traffic before trying to suppress it.
Open guide ↗
Site performance
When scheduled work depends on site traffic
A scheduled time and an actual execution time are not always the same. Establish what triggers the work before changing its schedule.
Open guide ↗
Site performance
Compare themes with the same content
A nearly empty demo cannot tell you how a theme will handle your actual publication. Give both candidates the same job.
Open guide ↗