TMI
A CLI tool that analyzes web pages to discover image weight and optimization opportunities.
What is TMI?
TMI (Too Many Images) is a command-line tool that analyzes web pages to discover their total image weight and identify optimization opportunities. It helps developers understand how images impact page performance by comparing image weight against Google's BigQuery quantiles. The tool provides actionable insights to reduce image bloat and improve loading times.
Web developers, performance engineers, and site owners who want to optimize image loading performance and reduce page weight.
Developers choose TMI because it provides a simple, focused way to measure image weight specifically, integrates with Google's performance data for benchmarking, and offers clear, actionable recommendations for optimization.
Overview
TMI (Too Many Images) - discover your image weight on the web
Use Cases
Best For
- Auditing image weight on production websites
- Identifying specific images that need compression or format optimization
- Benchmarking image performance against industry quantiles
- Integrating image weight checks into development workflows
- Quick performance assessments during site development
- Educating teams about image optimization impact
Not Ideal For
- Developers needing real-time performance monitoring or automated alerts
- Projects focused on non-web platforms like mobile or desktop applications
- Teams requiring local file or offline analysis without internet dependency
Pros & Cons
Pros
Provides dedicated insights into image weight, breaking down contributions by individual images as shown in the verbose mode screenshot for actionable optimization.
Compares image weight against Google's BigQuery quantiles, offering context relative to other sites, which is highlighted as a key feature for performance gauging.
Leverages Google PageSpeed Insights under the hood, ensuring reliable and standardized performance data, as noted in the README's integration details.
Supports analyzing pages with both mobile and desktop strategies, allowing tailored assessments for different user scenarios per the usage options.
Cons
The README admits that support for localhost and local files is planned but not yet available, forcing reliance on workarounds like ngrok for development testing.
Relies on Google APIs such as PageSpeed Insights and BigQuery, which may require API keys for extended use, introduce rate limits, and depend on external service availability.
Focuses solely on analysis and identification of heavy images without built-in tools for automated compression, format conversion, or integration with build pipelines.
Frequently Asked Questions
Related Projects
LazysizesHigh performance and SEO friendly lazy loader for images (responsive and normal), iframes and more, that detects any visibility changes triggered through user interaction, CSS or JavaScript without configuration.
CriticalExtract & Inline Critical-path CSS in HTML pages
uCSSFind unused and duplicate CSS
HTTPinvokeA no-dependencies HTTP client library for browsers and Node.js with a promise-based or Node.js-style callback-based API to progress events, text and binary file upload and download, partial response body, request and response headers, status code.
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.