A bookmarklet and Chrome extension that overlays a performance heatmap on web pages using the Resource Timing API.
PerfMap is a front-end performance heatmap tool that overlays a visual timeline on web pages to show when images and resources finished loading. It uses the browser's Resource Timing API to collect data and color-codes elements based on their load completion time, helping developers identify rendering bottlenecks and understand the user's visual experience during page load.
Front-end developers, web performance engineers, and UX designers who need to quickly diagnose and visualize page load performance issues directly in the browser.
PerfMap provides an intuitive, visual alternative to complex waterfall charts by overlaying performance data directly on the page, making it easy to correlate load times with actual page content without switching to external tools.
Front-end performance heatmap bookmarklet.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Overlays a heatmap directly on the page, color-coding elements by load finish time, making it intuitive to spot delays without interpreting complex waterfall charts.
Available as a simple bookmarklet for any browser and a Chrome extension, requiring no installation beyond adding the bookmark, as highlighted in the README.
Detects and visualizes CSS background images, which are often overlooked in performance tools, specifically mentioned as a feature added in 2014.
Includes a legend with page-level timings like DOMContentLoaded, and updates on hover to show when specific images loaded, enhancing context.
Requires Resource Timing API support, which in Firefox needs manual enabling via about:config, limiting out-of-the-box usability across browsers.
Last update was in 2014, with unresolved 'To Do' items like handling fixed position elements and iframe images, indicating lack of recent development.
Focuses only on images and background images, missing other critical resources like scripts or stylesheets, which restricts comprehensive performance analysis.
Must be triggered after page load, making it unsuitable for automated testing or scenarios requiring hands-off monitoring.