#12876 closed enhancement (fixed)
Remove unused images / compress other images
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | 3.0 | Priority: | low |
| Severity: | normal | Version: | |
| Component: | Optimization | Keywords: | |
| Focuses: | Cc: |
Description
In wp-admin/images/ exists some images which we didn't need (anymore).
If we clean up the code, we should clean up the images too.
Unused images
- wp-admin/images/
- ico-add.png
- ico-close.png
- ico-edit.png
- ico-viewpage.png
- loading.gif (think we have wpspin_*.gif for it)
- loading-publish.gif (think we have wpspin_*.gif for it)
I think there are more unused images, so use this ticket to clean up the images.
Compress images
Some images are already compressed, but not all. I use PunnyPNG for compressing and didn't have any problems with it. Some examples:
- wp-admin/images/fav.png | orig: 214 bytes after: 96 bytes
- wp-admin/images/imgedit-icons.png | orig: 9,607 bytes after: 7,105 bytes
Totaly we can save 16.3 KB which are 11% (only wp-admin/images/).
Maybe a committer can do this or I can upload a zip with all compressed images.
Change History (7)
Note: See
TracTickets for help on using
tickets.
The issue with removing loading.gif and loading-publish.gif is that a plugin may be using them. (Indeed, if a plugin developer goes looking for an ajax loading animated gif in wp-admin/images, they're probably more likely to notice loading*.gif than they are wpspin_*.gif.)
No real harm in keeping those, as they add very little weight to the package, and add nothing to page load -- unless a plugin is using them, of course.
On the other hand, the other ones are from Woo, [13267]. Those can go.
Compressing -- definitely something we should do. I don't really like PunyPNG because it's a site, versus a script like pngcrush.