Layout Review Checklist

Beginner

Perform a comprehensive layout quality review -- checking performance, accessibility, print readiness, security, and user experience against a 40-point checklist.

What you'll learn

  • How to systematically review layouts for performance, security, and UX
  • Specific checks that catch the most common layout production bugs
  • How to prioritize and document review findings
  • How to incorporate layout review into a development workflow

A layout review before releasing features to users catches problems that are expensive to fix later: slow load times, accessibility issues, broken print output, fields that expose data to wrong users, and interactions that confuse or frustrate users. This structured 40-point checklist covers every dimension of layout quality from performance to production readiness.

1/4
1

Performance review checks

Run these checks before releasing any layout to production. Performance issues are invisible to developers on local machines but immediately noticeable to users on WAN connections.

TEXT
// Layout Performance Checklist:
// [ ] Layout load time tested on WAN (not just local): target < 2 seconds
// [ ] No unstored calculation fields with aggregate/SQL functions in visible display
// [ ] All portals: row limits set to visible count + scrolling enabled
// [ ] No portal sorts on unindexed fields
// [ ] Relationship match fields indexed (both sides)
// [ ] Hide Object When formulas: no aggregates, no ExecuteSQL
// [ ] No more than 3 relationship hops in portal field references
// [ ] Layout tested with maximum expected found set size (not just 5 records)

Sign in to track your progress and pick up where you left off.

Sign in to FM Dojo