Guias Acionáveis
How to perform a complete website triage in 30 minutes
A practical checklist to quickly audit your site's technical health, visibility, and performance.
Executive brief
Key takeaways
- Prioritize high-conversion routes.
- Use field data (CrUX) rather than lab tests.
- Extract a prioritized backlog to investigate later.
Deciding what to investigate first when a site shows anomalies can paralyze a team. A 30-minute triage does not solve the root cause but isolates the observed evidence into a clear plan.
What is triage and what is its method?
Triage identifies critical symptoms. The method samples high-value pages (homepage, checkout) using Google Search Console, DevTools, and field data (CrUX).
1. Technical verification (10 min)
Focus on server response and initial loading.
- HTTP Codes:
5xxresponses indicate service failure.404on critical routes drops conversion. - Error Console: Observe CORS failures or blocked scripts that break interactions in Chrome DevTools.
Limitation: Console errors do not always interrupt the journey for all users. Identify only critical ones.
2. Visibility (10 min)
Verify crawling for profitable URLs.
- Sitemap and Coverage: In GSC, look for spikes in excluded pages.
- Rendering and indexing: Validate
canonicalandrobotstags.
3. Performance (10 min)
Evaluate UX bottlenecks at the 75th percentile.
- Core Web Vitals: Look for INP (Interaction) and LCP (Rendering) anomalies with field data.
- Blocking resources: Assess the size of scripts during main loading.
Recommended action
Compile the observations into an effort vs. impact matrix. Re-verify field metrics via Remountly on subsequent deploys to ensure the plan stabilized the environment.
Direct answers
Frequently asked questions
Can I fix a website in 30 minutes?
No. Triage raises hypotheses and organizes the investigation for engineering teams.
One useful idea at a time
