Review slow page loads and choose resource hints, browser instructions that start loading or connecting earlier. Use measurements to identify bottlenecks, then recommend preload, preconnect, prefetch, or dns-prefetch for important assets and likely next-page resources.
- Reviewing slow loading of prominent images and fonts
- Preparing connections to external services
- Prefetching resources for likely next-page visits
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review and implement loading feedback for operations such as fetching content or submitting actions. Use skeleton placeholders, spinners, and accessible status updates to communicate progress, while checking for layout shifts and measuring actual performance bottlenecks.
- Adding loading feedback during data fetching
- Showing progress while an action is running
- Checking screen reader announcements for loading states
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Audit slow page loads by measuring LCP, the time until the largest visible content appears. Identify bottlenecks in images, server responses, and rendering, then recommend changes supported by measurements.
- Find why a page's main content appears slowly
- Review hero image loading
- Prioritize fixes using Lighthouse measurements
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review whether interactive web elements work with keyboard navigation. Check Tab order, hidden elements, and focus traps where users cannot move away, then identify specific fixes and ways to verify behavior with browser accessibility tools or assistive technology.
- Check whether all controls are reachable with Tab
- Align keyboard focus order with the visual reading order
- Remove hidden content from the Tab sequence
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review links so their destinations are clear even without surrounding text. Identify vague wording, improve names announced by screen readers, and check keyboard behavior and download details such as file type and size.
- Replace vague link text with clear destination names
- Review links for screen reader users
- Check download links for file type and size
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review website navigation markup so screen reader users can identify and jump between navigation areas. Check nav elements, descriptive labels, and skip links, then pinpoint issues in the HTML delivered to the browser.
- Reviewing accessibility of main and footer navigation
- Adding distinct labels to multiple navigation areas
- Checking navigation markup from shared components
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Audit page loading and defer offscreen images, videos, iframes, and heavy components until needed. Use measurements and page context to identify suitable changes while keeping images needed for the initial view loaded with priority.
- Investigate slow initial page loads
- Defer images below the initial viewport
- Delay offscreen videos, iframes, and heavy components
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review large tables, feeds, and lists for rendering overhead. Introduce virtualization, which renders only visible items and a small buffer, while preserving keyboard access, selection, and expected scrolling behavior.
- Investigate sluggish admin tables
- Review long search result lists
- Reduce rendering overhead in feeds
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Find TypeScript values that bypass type checking through any, including inferred types and assertions. Suggest unknown, generics that preserve type relationships, or Zod validation for external data, with the checks needed where each value is used.
- Addressing ESLint warnings about explicit any
- Reviewing type safety around external API data
- Checking functions that pass any to their callers
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Inspect compressed JavaScript bundles, the files that package application code, to find excessive size and loading costs. Recommend splitting code, removing unused portions, and reviewing dependencies based on measured effects on page responsiveness.
- Finding JavaScript files over 200KB after compression
- Investigating delays before a page becomes interactive
- Reducing bundle size through code splitting
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review page landmarks, the named regions screen reader users navigate between. The skill checks semantic HTML elements, a single main content region, and labels for repeated region types, then identifies markup changes and ways to verify them.
- Reviewing page structure for screen reader navigation
- Replacing generic containers with semantic HTML elements
- Checking labels for multiple navigation regions
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review TypeScript settings and indexed access to arrays and objects to find values that may be undefined. Enable compiler checks and update unsafe code so potential failures become visible before the code runs.
- Audit TypeScript safety settings
- Review array access in data processing
- Investigate unexpected undefined errors
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Audit JavaScript page redirects, confirm their impact on loading time with performance measurements, and identify where server-side 301 or 302 redirects can replace them. Get specific findings and an explanation of loading and search indexing concerns.
- Investigating slow loads caused by page redirects
- Reviewing redirects that use window.location
- Planning server-side 301 or 302 redirects
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review JavaScript JSON parsing for malformed input and unexpected data structures. Add error handling and validate parsed data before use, helping prevent failures when reading API responses, browser storage, or user-provided content.
- Reviewing JSON parsing in API response handling
- Handling malformed data from localStorage
- Validating data structures before accessing properties
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Find and fix JavaScript memory leaks that accumulate as people use a web app. Review event listeners, timers, retained page elements, and outdated asynchronous tasks, then explain how to verify cleanup in the browser.
- Investigating rising memory use during long sessions
- Reviewing cleanup when components are removed
- Canceling outdated requests after view changes
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review HTML list structure so screen readers can identify lists and announce item counts. Find list items without valid containers, check custom accessibility roles, and guide fixes to markup used for navigation or styling.
- Review list markup split across components
- Fix navigation lists with invalid nesting
- Check parent roles for custom lists
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review JavaScript loops and replace suitable ones with standard array and object methods. Make transformations, filtering, and aggregation easier to understand, with practical explanations and browser checks to confirm that changes preserve the intended behavior.
- Refactoring manual loops into array methods
- Clarifying data transformation, filtering, and aggregation
- Reviewing object transformations and deep copying
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review CSS spacing, borders, and positioning for conversion to logical properties, which follow writing direction. Check rendered layouts across screen sizes and interaction states to support right-to-left languages and vertical text.
- Adapting layouts for Arabic or Hebrew
- Replacing fixed left and right spacing in CSS
- Reviewing layouts for vertical writing
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review JavaScript libraries for outdated versions, known security flaws, and unnecessary size. Use performance measurements to identify costly dependencies, then recommend secure updates or lighter alternatives with specific files and requests to investigate.
- Checking dependencies for known security flaws
- Investigating libraries behind slow page loads
- Considering lighter library alternatives
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Audit website images and guide conversion to WebP and AVIF, formats that reduce image transfer size. Identify affected files, add fallback images, and review dimensions and loading behavior alongside the impact on initially visible content.
- Finding JPEG and PNG images to convert
- Adding WebP and AVIF sources with fallback images
- Reviewing CSS background image formats
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review modal dialogs for keyboard and screen reader accessibility. The skill checks dialog roles, title labels, focus movement within the modal, Escape dismissal, and focus returning to the opening control, then identifies issues and ways to verify fixes.
- Reviewing keyboard operation in modal dialogs
- Checking focus movement when opening and closing modals
- Reviewing dialog titles and screen reader labels
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Audit CSS class names for inconsistency and ambiguity, then organize them using BEM, a convention that names components, their elements, and variations. Check the rendered interface across screen sizes and interaction states when reviewing changes.
- Auditing inconsistent CSS class names
- Renaming component classes using BEM
- Separating utility classes and JavaScript hooks
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Check whether images visible when a page first opens are unnecessarily lazy loaded, meaning their loading is deferred. Verify rendering delays with performance measurements, then guide changes to loading attributes and request priority.
- Review loading settings for hero images
- Investigate image loading delays affecting LCP
- Adjust loading attributes for images in the initial viewport
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Audit JavaScript delivered to modern browsers for unnecessary older code and compatibility patches. Confirm performance costs with measurements, then review build targets and browser-specific delivery to reduce avoidable download size and processing work.
- Investigating slow page loads
- Checking unnecessary JavaScript compatibility code
- Reviewing build targets for modern browsers
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026