| name | drupaltools-site-audit |
| description | Generate comprehensive Drupal site audit reports before RFPs or project proposals. Use this skill when inspecting a Drupal site, preparing a technical report, or evaluating an existing Drupal project for fixes or changes. |
Drupal Site Audit Report
Generate a comprehensive audit report for Drupal sites before providing proposals or starting work.
When to Use
Use this skill when:
- "Audit this Drupal site"
- "Prepare a report before starting"
- "Inspect Drupal project structure"
- "Generate a technical report for RFP"
Before the Report
Gather this information before starting:
Required
Important
Common Reports
Performance
- PageSpeed Insights
- GTmetrix
- Yellow Lab Tools
SEO & UX
- SEO checklist
- Mobile responsiveness
- Heatmaps (Hotjar)
Security
- Drupal Security Scanner (hackertarget.com)
- Security Headers
- Sucuri SiteCheck
Drupal Specific Audit
Content Structure
Functionality
Users & Permissions
Theming
Modules
Technical
Audit Commands
Run these commands to gather site information:
drush pm-list --type=module --status=enabled
drush ups
drush cex
drush status
drush entity-type-list node
drush eval "print_r(node_type_get_types());"
drush role-list
php -i | grep memory_limit
Useful Audit Modules
| Module | Purpose |
|---|
audit_export | Export audit data |
field_report | Field analysis |
security_review | Security checklist |
unused_modules | Find unused modules |
mglaman/drupal-check | Check module health |
Report Structure
1. Executive Summary
Brief overview of site health and recommendations.
2. Technical Findings
Detailed analysis by category:
- Content structure
- Modules and updates
- Performance
- Security
- Best practices violations
3. Recommendations
Prioritized list of fixes with:
- Issue description
- Impact level (High/Medium/Low)
- Estimated effort (hours)
- Recommended approach
4. Deliverables
- PDF report with screenshots
- Itemized pricing
- Timeline estimate
Best Practices
- Do not give estimates before completing the audit
- Get credentials or demo access before starting
- Use agile methodology - fix one thing at a time, get paid by hour
- Treat the report as a doctor's diagnosis
- Avoid criticizing previous developers - focus on the site
- Consider refusing poorly structured projects
Resources