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
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
Find links that use identical text but lead to different URLs. Review the rendered page and suggest distinct labels or consistent destinations so readers, including people using screen readers, can understand where each link goes.
- Find identical link text with different destinations
- Improve labels in screen reader link lists
- Review links in shared components
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review website image delivery and configure an image CDN, a service that optimizes and distributes images. Check file formats, dimensions, loading behavior, and initial screen impact, with guidance on verifying changes in DevTools.
- Checking whether website images use a CDN
- Configuring automatic image resizing and format conversion
- Reviewing image loading and initial screen impact
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Audit a page’s HTTP requests to find unnecessary network activity behind slow loading. Confirm bottlenecks with performance measurements, then suggest changes such as combining files, grouping icons, or embedding resources needed for the initial display.
- Investigating slow initial page loads
- Finding unnecessary requests for images, CSS, and JavaScript
- Planning file consolidation and icon sprites
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review iframe and frame titles so screen reader users can identify embedded content before entering it. Find missing or empty title attributes, add meaningful descriptions, and verify the changes with browser accessibility tools or assistive technology.
- Checking titles on embedded advertisements and social media widgets
- Reviewing missing or empty iframe title attributes
- Verifying frame identification with a screen reader
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Find JavaScript code that changes existing objects or arrays, then replace those updates with modified copies. Review shared state and browser behavior to make data changes easier to trace and check fixes in context.
- Finding direct changes to shared objects
- Replacing push and splice with copy-based updates
- Reviewing state updates in client components
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review form validation so users, including people using screen readers, can understand and correct errors. Check field descriptions, required states, and grouped choices in rendered HTML, while accounting for React forms that handle submission in the browser.
- Make form errors understandable to screen reader users
- Check how required fields and grouped choices are marked
- Review validation in React forms
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review HTML to find important fonts, images, and scripts discovered late during loading. Suggest resource hints, instructions that start fetching or connecting earlier, and check the final markup delivered to the browser.
- Reviewing preload hints for important fonts and images
- Checking early connections to third-party domains
- Auditing resource hints in rendered HTML
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review long pages and dashboards to defer heavy components until they approach the visible screen area. Identify unnecessary initial JavaScript, introduce visibility-based loading, and preserve layout space so scrolling content is ready when needed.
- Defer charts located far down a dashboard
- Review loading behavior on long landing pages
- Load embeds and related products as they approach the screen
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review website images and reduce file sizes while limiting visible quality changes. Check compression, formats, display dimensions, loading behavior, and delivery settings, then recommend suitable tools or build automation and verification in browser DevTools.
- Find oversized images on web pages
- Choose compression methods for photos and graphics
- Automate image compression during builds
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review pop-ups, modals, and banners that obscure page content. Identify mobile usability and search visibility concerns, then improve dismissal controls and keyboard focus, the element currently receiving keyboard input.
- Review promotional pop-ups on mobile
- Check keyboard dismissal of modals
- Verify focus movement when dialogs open and close
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Set up ESLint, a tool that checks JavaScript for errors and coding rule violations. Configure shared rules, connect checks to editors and automated workflows, and review flagged code alongside its behavior in the browser.
- Setting up ESLint for a JavaScript project
- Applying consistent coding rules across a team
- Adding code checks to editors and CI/CD
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review website images for file format, size, dimensions, and loading behavior. Produce improved HTML with image variants for different screen sizes, suitable compression, and deferred loading where appropriate, while addressing loading speed and layout shifts.
- Auditing image sizes and formats on slow-loading pages
- Serving suitable image sizes for mobile and desktop screens
- Preventing layout shifts while images load
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review JavaScript that changes a parent element’s appearance based on its children. Find opportunities to replace class toggling with CSS :has() rules, and explain how those rules express conditions involving child elements.
- Replacing JavaScript class toggling with CSS
- Styling form containers based on input state
- Changing parent styles when child content exists
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review image input buttons for missing or empty alternative text. Suggest alt attributes that describe actions such as searching or submitting, and explain how to verify that screen readers communicate each button’s purpose.
- Checking alternative text on image input buttons
- Improving labels for search and submit buttons
- Reviewing shared image button components
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Measure how quickly a webpage updates after user interactions using INP, a responsiveness metric. Identify confirmed bottlenecks and improve event handlers, split long tasks, or move heavy computation to web workers.
- Investigating slow responses to clicks and other interactions
- Reviewing event handlers and long tasks using measurements
- Considering web workers for heavy computation
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Audit website image file sizes against guidelines for photos, graphics, hero images, and thumbnails. Report oversized assets with target sizes, distinguish compression issues from dimension mismatches, and guide format conversion and delivery of smaller variants to mobile devices.
- Listing oversized images and target file sizes
- Reviewing uploaded images managed by a CMS
- Reducing hero image and thumbnail file sizes
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review and fix HTML form fields so their input types match the data being entered. Check autocomplete settings and the final browser markup to support suitable mobile keyboards, built-in validation, and browser autofill.
- Reviewing input types in an existing form
- Improving mobile keyboards for email and phone fields
- Adding autocomplete settings for browser autofill
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Check whether production JavaScript files are minified, meaning unnecessary characters are removed to reduce size. Review build settings and unused code removal, suggest configuration changes, and describe how to verify the resulting files in the browser.
- Check production JavaScript minification
- Review build settings for smaller files
- Remove unused code from bundles
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review rendered HTML and replace generic div elements with elements that describe their purpose, such as main, nav, and article. Clarify page structure to support screen-reader navigation, search-engine understanding, and code maintenance.
- Reviewing page structure built mostly with div elements
- Checking HTML output from templates and shared components
- Improving page structure for screen-reader navigation
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review web page headings for skipped levels, unclear labels, and incorrect structure. Organize HTML headings around the content so people using screen readers can understand page sections and navigate between them.
- Audit heading levels on a web page
- Improve navigation for screen reader users
- Review headings in design-system patterns
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Audit an HTTPS website for HTTP links in pages, resources, and application code. Group findings by link type, update internal URLs, and check whether external destinations support HTTPS before changing them.
- Checking links during an HTTPS migration
- Finding hardcoded HTTP URLs
- Reviewing image and script URLs
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026
Review web page headings for skipped levels and unclear hierarchy. Identify specific elements to adjust, explain how heading structure supports screen reader navigation, and describe how to verify the revised page with accessibility tools.
- Checking heading levels across a web page
- Reviewing heading structure in shared components
- Improving navigation through screen reader heading lists
thedaviddias/Front-End-Checklist☆ 74.6KUpdated Oct 6, 2026