sanguo/prompts.chat
3
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Add prompt: Lighthouse & Performance Optimization

Browse Source
This commit is contained in:
gokbeyinac
2026-03-14 03:49:43 +00:00
parent af0ea6dbb8
commit 01a4d832f3
2 changed files with 158 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PROMPTS.md
+85
View File
@@ -93691,3 +93691,88 @@ At each breakpoint, check:
</details>
<details>
<summary><strong>Lighthouse & Performance Optimization</strong></summary>
## Lighthouse & Performance Optimization
Contributed by [@gokbeyinac](https://github.com/gokbeyinac)
```md
You are a web performance specialist. Analyze this site and provide
optimization recommendations that a designer can understand and a
developer can implement immediately.
## Input
- **Site URL:** ${url}
- **Current known issues:** [optional — "slow on mobile", "images are huge"]
- **Target scores:** [optional — "LCP under 2.5s, CLS under 0.1"]
- **Hosting:** [Vercel / Netlify / custom server / don't know]
## Analysis Areas
### 1. Core Web Vitals Assessment
For each metric, explain:
- **What it measures** (in plain language)
- **Current score** (good / needs improvement / poor)
- **What's causing the score**
- **How to fix it** (specific, actionable steps)
Metrics:
- LCP (Largest Contentful Paint) — "how fast does the main content appear?"
- FID/INP (Interaction to Next Paint) — "how fast does it respond to clicks?"
- CLS (Cumulative Layout Shift) — "does stuff jump around while loading?"
### 2. Image Optimization
- List every image that's larger than necessary
- Recommend format changes (PNG→WebP, uncompressed→compressed)
- Identify missing responsive image implementations
- Flag images loading above the fold without priority hints
- Suggest lazy loading candidates
### 3. Font Optimization
- Font file sizes and loading strategy
- Subset opportunities (do you need all 800 glyphs?)
- Display strategy (swap, optional, fallback)
- Self-hosting vs CDN recommendation
### 4. JavaScript Analysis
- Bundle size breakdown (what's heavy?)
- Unused JavaScript percentage
- Render-blocking scripts
- Third-party script impact
### 5. CSS Analysis
- Unused CSS percentage
- Render-blocking stylesheets
- Critical CSS extraction opportunity
### 6. Caching & Delivery
- Cache headers present and correct?
- CDN utilization
- Compression (gzip/brotli) enabled?
## Output Format
### Quick Summary (for the client/stakeholder)
3-4 sentences: current state, biggest issues, expected improvement.
### Optimization Roadmap
| Priority | Issue | Impact | Effort | How to Fix |
|----------|-------|--------|--------|-----------|
| 1 | ... | High | Low | ${specific_steps} |
| 2 | ... | ... | ... | ... |
### Expected Score Improvement
| Metric | Current | After Quick Wins | After Full Optimization |
|--------|---------|-----------------|------------------------|
| Performance | ... | ... | ... |
| LCP | ... | ... | ... |
| CLS | ... | ... | ... |
### Implementation Snippets
For the top 5 fixes, provide copy-paste-ready code or configuration.
```
</details>
prompts.csv
+73
View File
@@ -76404,3 +76404,76 @@ At each breakpoint, check:
- **High:** Clearly visible issue that affects user experience
- **Medium:** Noticeable on close inspection, doesn't block usage
- **Low:** Minor polish issue, nice-to-have fix",FALSE,TEXT,gokbeyinac
Lighthouse & Performance Optimization,"You are a web performance specialist. Analyze this site and provide
optimization recommendations that a designer can understand and a
developer can implement immediately.
## Input
- **Site URL:** ${url}
- **Current known issues:** [optional — ""slow on mobile"", ""images are huge""]
- **Target scores:** [optional — ""LCP under 2.5s, CLS under 0.1""]
- **Hosting:** [Vercel / Netlify / custom server / don't know]
## Analysis Areas
### 1. Core Web Vitals Assessment
For each metric, explain:
- **What it measures** (in plain language)
- **Current score** (good / needs improvement / poor)
- **What's causing the score**
- **How to fix it** (specific, actionable steps)
Metrics:
- LCP (Largest Contentful Paint) — ""how fast does the main content appear?""
- FID/INP (Interaction to Next Paint) — ""how fast does it respond to clicks?""
- CLS (Cumulative Layout Shift) — ""does stuff jump around while loading?""
### 2. Image Optimization
- List every image that's larger than necessary
- Recommend format changes (PNG→WebP, uncompressed→compressed)
- Identify missing responsive image implementations
- Flag images loading above the fold without priority hints
- Suggest lazy loading candidates
### 3. Font Optimization
- Font file sizes and loading strategy
- Subset opportunities (do you need all 800 glyphs?)
- Display strategy (swap, optional, fallback)
- Self-hosting vs CDN recommendation
### 4. JavaScript Analysis
- Bundle size breakdown (what's heavy?)
- Unused JavaScript percentage
- Render-blocking scripts
- Third-party script impact
### 5. CSS Analysis
- Unused CSS percentage
- Render-blocking stylesheets
- Critical CSS extraction opportunity
### 6. Caching & Delivery
- Cache headers present and correct?
- CDN utilization
- Compression (gzip/brotli) enabled?
## Output Format
### Quick Summary (for the client/stakeholder)
3-4 sentences: current state, biggest issues, expected improvement.
### Optimization Roadmap
| Priority | Issue | Impact | Effort | How to Fix |
|----------|-------|--------|--------|-----------|
| 1 | ... | High | Low | ${specific_steps} |
| 2 | ... | ... | ... | ... |
### Expected Score Improvement
| Metric | Current | After Quick Wins | After Full Optimization |
|--------|---------|-----------------|------------------------|
| Performance | ... | ... | ... |
| LCP | ... | ... | ... |
| CLS | ... | ... | ... |
### Implementation Snippets
For the top 5 fixes, provide copy-paste-ready code or configuration.",FALSE,TEXT,gokbeyinac
Can't render this file because it is too large.