Skip to content
TrustedSkillsbeta
Back to all skills

Wordpress Performance Best Practices

Checked
bartekmis·vlatest·backend·MIT

Helps with performance optimization, best practices as part of agent workflows workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add bartekmis/wordpress-performance-best-practices --skill wordpress-performance-best-practices -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

bartekmis

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned bartekmis/wordpress-performance-best-practises at 577a08fb1c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
577a08fb1c
Manifest
SKILL.md
Scanned
41 files, 8,124 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides best practices for improving the performance of WordPress websites. It includes recommendations on optimizing images, leveraging caching mechanisms, minimizing HTTP requests, and using efficient plugins and themes.

When to use it

  • You're experiencing slow load times on your WordPress site.
  • You want to improve SEO rankings by enhancing page speed.
  • You’re preparing a WordPress site for high traffic or e-commerce purposes.
  • You need guidance on optimizing resources without compromising functionality.

Key capabilities

  • Optimizing images and media files
  • Implementing caching strategies (browser, server, CDN)
  • Minimizing HTTP requests through code optimization
  • Recommending lightweight plugins and themes
  • Enabling Gzip compression and proper content delivery

Example prompts

  • "How can I optimize my WordPress site for faster loading?"
  • "What are the best caching plugins for WordPress?"
  • "I need tips to reduce the number of HTTP requests on my site."

Tips & gotchas

  • Always test changes in a staging environment before applying them live.
  • Some performance improvements may require server-level access or configuration, so ensure you have the necessary permissions.