Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

need-for-speed

Estrelas477

Forks79

Atualizado5 de maio de 2026 às 15:17

Run a frontend performance audit on a WordPress site and get actionable optimization recommendations.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

Automattic

Automattic/studio

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	need-for-speed
description	Run a frontend performance audit on a WordPress site and get actionable optimization recommendations.
user-invokable	true

Performance Audit

Run a performance audit on a WordPress site to measure Core Web Vitals and page composition, then provide actionable recommendations.

How to Run

Determine which site to audit. If the user hasn't specified, ask them or use the site from the current context.
Ensure the site is running (use site_start if needed).
Call need_for_speed with the site name and path (defaults to /).
Analyze the results using the interpretation guide below.
Present a clear summary with specific, actionable recommendations.

Interpreting Results

Core Web Vitals Thresholds

Metric	Good	Needs Improvement	Poor
TTFB	< 800 ms	800–1800 ms	> 1800 ms
FCP	< 1800 ms	1800–3000 ms	> 3000 ms
LCP	< 2500 ms	2500–4000 ms	> 4000 ms
CLS	< 0.1	0.1–0.25	> 0.25

Page Composition Benchmarks

DOM elements: Concern if > 1500
Total page weight: Concern if > 3 MB
Total requests: Concern if > 80
Scripts: Concern if > 20 scripts or > 500 KB total
Stylesheets: Concern if > 10 stylesheets or > 200 KB total

Common WordPress Recommendations

Based on the metrics, suggest specific actions:

High TTFB: Enable page caching (e.g., wp_cli: plugin install wp-super-cache --activate), check for slow database queries, consider object caching.
High LCP / FCP: Check for render-blocking CSS/JS, add lazy loading for below-the-fold images, defer non-critical scripts.
Large JS payload: Identify heavy plugins from the scripts URL list, suggest deactivating unused plugins, check for jQuery dependency chains.
Large CSS payload: Look for unused theme stylesheets, check for multiple Google Fonts loads.
Many HTTP requests: Suggest reducing plugin count, enabling asset concatenation.
High CLS: Check for images without explicit width/height dimensions, ads or dynamic content injection, web fonts causing layout shifts.
Large DOM: Check theme template complexity, excessive nesting in block content, too many wrapper elements.

Important Notes

These are synthetic measurements on a local dev server. TTFB will be artificially low compared to production. Focus on relative comparisons (before/after changes) rather than absolute values.
CLS is measured during page load only, not during user interaction.
INP (Interaction to Next Paint) is not measured — it requires real user interaction patterns.
Page weight may undercount if some resources report 0 transfer size (e.g., service worker cached resources).

Mais deste repositório

mesmo repositório

liberate

Automattic/studio

Import and rebuild a website from a closed platform (Wix, Squarespace, Webflow, Shopify, GoDaddy, Hostinger, HubSpot, Weebly) into a Studio WordPress site. Extracts pages/posts/products + media, then reconstructs the design as editable blocks + WooCommerce OR as a high-fidelity replica theme. Invoke when the user wants to migrate, import, liberate, or rebuild a site from one of these platforms.

2026-07-06477

plugin-recommendations

Automattic/studio

Choose recommended plugins and plugin-provided blocks for features core WordPress blocks do not cover - ecommerce (WooCommerce), forms and newsletters (Jetpack), online courses and quizzes (Sensei LMS), polls, surveys and ratings (Crowdsignal), spam protection (Akismet) - while keeping generated content editable and avoiding raw HTML fallbacks. Any request to sell products or build a shop, store, or storefront requires WooCommerce with products.

2026-07-03477

site-spec

Automattic/studio

Gather the site name and layout preference before building a WordPress site. Run this before creating any new site.

2026-07-03477

studio-cli

Automattic/studio

Use the Studio CLI to manage local WordPress sites, authentication, and preview sites. Invoke this skill when you need to run Studio CLI commands, manage sites, or troubleshoot site issues.

2026-07-03477

block-content

Automattic/studio

Write editable WordPress block markup for local Studio sites, including core/html limits, block-theme layout rules, full-width sections, validation, and skeleton-first page/CSS recipes.

2026-07-02477

hosting-plans-helper

Automattic/studio

Answer WordPress.com plan, pricing, upgrade, and feature-tier questions (plan names, what each tier unlocks — plugins, themes, custom code, SSH, hosting — and current prices) from authoritative live data. Load before answering ANY plan, pricing, or feature-gating question; never answer these from memory.

2026-07-01477

Performance Audit

Run a performance audit on a WordPress site to measure Core Web Vitals and page composition, then provide actionable recommendations.

How to Run

Determine which site to audit. If the user hasn't specified, ask them or use the site from the current context.

Ensure the site is running (use site_start if needed).

Call need_for_speed with the site name and path (defaults to /).

Analyze the results using the interpretation guide below.

Present a clear summary with specific, actionable recommendations.

Interpreting Results

Core Web Vitals Thresholds

Metric

Good

Needs Improvement

Poor

TTFB

< 800 ms

800–1800 ms

> 1800 ms

FCP

< 1800 ms

1800–3000 ms

> 3000 ms

LCP

< 2500 ms

2500–4000 ms

> 4000 ms

CLS

< 0.1

0.1–0.25

> 0.25

Page Composition Benchmarks

DOM elements: Concern if > 1500

Total page weight: Concern if > 3 MB

Total requests: Concern if > 80

Scripts: Concern if > 20 scripts or > 500 KB total

Stylesheets: Concern if > 10 stylesheets or > 200 KB total

Common WordPress Recommendations

Based on the metrics, suggest specific actions:

High TTFB: Enable page caching (e.g., wp_cli: plugin install wp-super-cache --activate), check for slow database queries, consider object caching.

High LCP / FCP: Check for render-blocking CSS/JS, add lazy loading for below-the-fold images, defer non-critical scripts.

Large JS payload: Identify heavy plugins from the scripts URL list, suggest deactivating unused plugins, check for jQuery dependency chains.

Large CSS payload: Look for unused theme stylesheets, check for multiple Google Fonts loads.

Many HTTP requests: Suggest reducing plugin count, enabling asset concatenation.

High CLS: Check for images without explicit width/height dimensions, ads or dynamic content injection, web fonts causing layout shifts.

Large DOM: Check theme template complexity, excessive nesting in block content, too many wrapper elements.

Important Notes

These are synthetic measurements on a local dev server. TTFB will be artificially low compared to production. Focus on relative comparisons (before/after changes) rather than absolute values.

CLS is measured during page load only, not during user interaction.

INP (Interaction to Next Paint) is not measured — it requires real user interaction patterns.

Page weight may undercount if some resources report 0 transfer size (e.g., service worker cached resources).