@thedaviddias
Staff Front-End Engineer | Front-End Architecture, Design Systems & Accessibility | Creator of the Front-End Checklist (74K+ ⭐) and serving 100K+ devs
467 skills6 repositories 75.2K
Audit and write page titles for search results and browser tabs. Check that each page has one descriptive title, an appropriate length, a unique wording across the site, and its main keyword near the beginning.
Audit structured data for businesses serving a physical location or geographic area. Check or add LocalBusiness JSON-LD, a machine-readable format for business details, verify addresses against visible page content, and validate the markup with Google's Rich Results Test.
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.
Audit web pages for excessive keyword repetition in body text, titles, metadata, and image descriptions. Report frequent terms and their density, identify hidden keyword text, and help rewrite repetitive passages into natural language focused on readers.
Review image alt text, the descriptions read by screen readers, for unnecessary phrases and duplication of nearby text. Identify specific images to fix and make their descriptions concise while preserving information about what the images mean.
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 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.
Review CSS layouts for unwanted horizontal scrolling on narrow screens and at high browser zoom. Identify fixed widths, overflowing media, and unbroken text, then apply layout fixes that keep content readable within the viewport.
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.
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.
Find optional features that slow the first page load and defer their code until a user interacts. Use dynamic imports, which load code on demand, and add immediate loading feedback while preserving the initial page experience.
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.
Review interface copy for assumptions about disability, gender, or culture. Suggest neutral wording, clearer instructions, and constructive error messages that guide people through problems without blaming them or relying on culturally specific expressions.
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.
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.
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.
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.
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.
Audit article update dates across the visible page, HTTP response headers, and structured data that describes the article to search engines. Align these signals with substantive content changes and review how the CMS or build process updates them.
Audit conflicting search indexing settings across robots.txt, noindex directives, and canonical tags that identify preferred URLs. Identify why pages may be included or excluded unexpectedly, and review changes that align the settings with the intended outcome.
Check that HTTP requests redirect to HTTPS with a permanent 301 response while preserving the page path and query parameters. Review server or CDN settings, verify response headers, and explain how HSTS helps returning visitors avoid HTTP requests.
Review public forms for automated abuse protection. Check CAPTCHA, a mechanism for detecting bots, along with hidden trap fields and request limits, then help integrate a CAPTCHA service and validate its tokens on the server.
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.
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.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)