@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
Review the HTML delivered to browsers for a correct UTF-8 character encoding declaration. Find missing or misplaced charset tags in templates and rendered pages, then position the declaration early to help prevent garbled multilingual text.
Find broken or fragile image references in markup, styles, and components. Correct paths, restore missing assets, and add fallback images, then verify how the page behaves when image requests fail.
Audit breadcrumb structured data, a machine-readable description of a page’s navigation path. Check that BreadcrumbList matches the visible trail and site hierarchy, then guide JSON-LD changes using the rendered HTML and HTTP response.
Review rotating slideshows for accessibility and guide fixes to pause controls, keyboard navigation, and screen reader announcements. Check the rendered HTML and ensure the carousel respects users who request reduced motion in their device settings.
Investigate chains of dependent resource requests that delay a page’s first display. Use performance measurements to identify bottlenecks, then reduce waiting by embedding essential CSS or preloading important assets discovered late in the chain.
Find console output left in production JavaScript and help remove it, disable it by environment, or replace it with a logging service. Reviews cover source code and browser execution paths, including how to verify the changes.
Audit publication and update dates on articles and blog posts. Add visible dates and structured metadata, information search engines can read, and check that modification dates reflect meaningful content changes rather than routine deployments.
Find and fix internal links that lead to missing pages or server errors. Check rendered pages and HTTP responses, then identify URLs to update or remove and explain how broken links affect search engine crawling.
Audit browser caching to reduce repeated downloads when people revisit a site. Check cache headers for static files and HTML pages, then suggest suitable storage durations and validation settings based on measured loading problems.
Review JavaScript variable declarations, report every use of var with line numbers, and replace declarations with const or let according to reassignment. Explain variable scope and initialization behavior, and check affected browser execution paths.
Review and create print styles for web pages so printed content stays readable. Adjust typography and page breaks, hide navigation and ads, and display external link URLs in the printed output.
Review images needed when a page first opens, checking file size, display dimensions, and loading priority. Identify changes to preload settings and lazy loading that help the main visual content appear sooner.
Review component styles to find where CSS containment, which isolates rendering work, can limit layout recalculation and repainting. Identify suitable components and off-screen list items, then check their appearance across screen sizes and interaction states.
Review conflicting CSS rules and organize styles with cascade layers, explicit groups that control override order. Define layers for resets, base styles, components, and utilities to make large stylesheets easier to reason about and maintain.
Audit CSS file sizes and loading behavior to find stylesheets that delay page rendering. Confirm the problem with performance measurements, then reduce unnecessary CSS through minification, unused-style removal, or splitting files by page.
Review help links, chat controls, phone numbers, and FAQ entry points across related pages. Compare their relative positions and order under matching layout conditions, then identify changes that make support easier to find throughout a task.
Audit slow page loads by measuring how static files, such as images and scripts, are delivered. Check CDN usage, a network of distributed servers, and identify caching or delivery settings that need improvement.
Review and fix breadcrumb HTML so readers, including people using screen readers, can understand site hierarchy and their current location. Check navigation labels, ordered lists, current-page attributes, and consistency with structured data.
Review large JavaScript bundles to find code that can load later. Suggest dynamic imports, which load modules when needed, and page-level splitting, with loading states for heavy libraries and features outside the initial view.
Review CSS custom properties, often called CSS variables, used in animations and transitions. Add @property registrations with value types, initial values, and inheritance settings to support smooth changes and validate assigned values.
Measure CLS, a score for unexpected movement of page content, and identify what causes it. Review image dimensions, reserved advertising space, fonts, and animations to recommend changes that reduce reading interruptions and accidental clicks.
Review CSS loading that delays a page’s first visible content. Help inline essential styles and defer other stylesheets, using preload and media conditions, while checking rendered layouts at different screen widths and interaction states.
Review communication between different websites for security issues. Inspect code and browser behavior to identify overly broad CORS permissions, unchecked message senders, missing request protections, and unsafe redirects, then propose fixes and browser checks.
Review how a page loads CSS, the rules that control its appearance. Inline the styles needed for the first visible content and load the rest asynchronously, while checking layouts across screen sizes and interaction states.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)