Issue 1022 in modpagespeed: Option to avoid inline images on favicons (pagespeed_no_transform for <link>)

4 views
Skip to first unread message

modpag...@googlecode.com

unread,
Nov 19, 2014, 3:27:31 PM11/19/14
to mod-pagesp...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium

New issue 1022 by ttim...@gmail.com: Option to avoid inline images on
favicons (pagespeed_no_transform for <link>)
https://code.google.com/p/modpagespeed/issues/detail?id=1022

Using pagespeed version: 1.8.31.5-4307

We have a number of <link> tags on our site that look like this:
<link rel="apple-touch-icon" sizes="57x57" href=".." />
<link rel="apple-touch-icon" sizes="114x114" href=".." />
...
<link rel="icon" type="image/png" href="/favicon-32x32.png" sizes="32x32"/>
<meta name="msapplication-TileColor" content=".."/>
etc.

These are for favicons on a variety of browsers and platforms. Because
they're small, pagespeed automatically inlines all of them, even though
most browsers will only ever use (and download) one of them. Thus the
processing time is wasted, and the HTML is actually inflated unnecessarily.

It would be fantastic if the "rel" attribute could be natively 'understood'
by pagespeed and recognised favicon <link>s treated differently from other
images, or, failing that, to allow the use of "pagespeed_no_transform" on
<link> tags. I've tried adding it, but I guess it only works on <img> tags
at the moment.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

modpag...@googlecode.com

unread,
Apr 8, 2015, 2:06:25 PM4/8/15
to mod-pagesp...@googlegroups.com

Comment #1 on issue 1022 by jcro...@google.com: Option to avoid inline
images on favicons (pagespeed_no_transform for <link>)
https://code.google.com/p/modpagespeed/issues/detail?id=1022

this issue has been migrated to github:
https://github.com/pagespeed/mod_pagespeed/issues/1022
Reply all
Reply to author
Forward
0 new messages