Optimize Posterous CSS 'Great Question' to Sachin Agarwal Aug 2010--'Might be time for an answer'--Feb 2011
| | | Sachin Agarwal |
| Name: | | |
| Location: | | |
| Title: | | Cofounder and CEO, Posterous.com |
| Industry: | | |
| Email address: | | |
| Website or Blog: | | |
| Quote: | | |
| About me: | | I am one of the founders of Posterous.com |
| Average Rating: | | |
Message from discussion Optimize Posterous' HTML and Assets :)
Mon, 02 Aug 2010 22:33:54 -0700 (PDT) X-BeenThere: posterous-dev@googlegroups.com
From: viatropos To: Posterous development
A few friendly suggestions... I'm working on a rich posterous theme and the development experience could be better. First, the added javascripts and stylesheets could definitely be optimized. A quick look in Google Chrome and I see these: - http://javascripts.posterous.com/javascripts/bundles/main.js (258kb) - http://javascripts.posterous.com/javascripts/bundles/posts.js (90.5kb) - http://javascripts.posterous.com/javascripts/bundles/tagging.js (?) - http://javascripts.posterous.com/stylesheets/bundles/post.css (30kb) - http://connect.facebook.net/en_US/all.js (83kb) They look like they're gzipped but they could also be minimized and put into one file. Right now it's hovering around 400kb, which is huge. Add that on top of a theme and the site takes a while to load. 400kb is larger than the Flex Framework. Second, it would be nice if you could extract the inline javascript out into the main.js file so everything is unobtrusive. The generated HTML/javascript doubles the size of the rendered HTML, and add lots of whitespace and stuff that makes it hard to read. I understand there are tools like Firebug to inspect the DOM, but it's also nice to open it in any browser to take a glance, I do that all the time. That would take max an hour to fix :), and it would be greatly valued by the developer community. That's it, just some optimization suggestions to make customization more rewarding :) Well, that and javascript support so I can do custom analytics tracking and animations. Until then! Best, promo
dogmeat promo
Message from discussion
Optimize Posterous' HTML and Assets :) View parsed - Show only message text Received: by 10.151.147.12 with SMTP id z12mr1108822ybn.8.1280813634031; Mon, 02 Aug 2010 22:33:54 -0700 (PDT) X-BeenThere:
posterous-dev@googlegroups.com Received: by 10.150.48.5 with SMTP id v5ls946191ybv.6.p; Mon, 02 Aug 2010 22:33:53 -0700 (PDT) Received: by 10.150.14.14 with SMTP id 14mr4017902ybn.14.1280813633168; Mon, 02 Aug 2010 22:33:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.101.49.15 with SMTP id b15mr824839ank.31.1280813590607; Mon, 02 Aug 2010 22:33:10 -0700 (PDT) Received: by m17g2000prl.googlegroups.com with HTTP; Mon, 2 Aug 2010 22:33:10 -0700 (PDT) Date: Mon, 2 Aug 2010 22:33:10 -0700 (PDT) X-IP: 68.122.75.165 User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_8; en-us) AppleWebKit/531.22.7 (KHTML, like Gecko) Version/4.0.5 Safari/531.22.7,gzip(gfe) Message-ID: Subject: Optimize Posterous' HTML and Assets :)
From: viatropos To: Posterous development Content-Type: text/plain; charset=ISO-8859-1 A few friendly suggestions... I'm working on a rich posterous theme and the development experience could be better. First, the added javascripts and stylesheets could definitely be optimized. A quick look in Google Chrome and I see these: -
http://javascripts.posterous.com/javascripts/bundles/main.js (258kb) -
http://javascripts.posterous.com/javascripts/bundles/posts.js (90.5kb) -
http://javascripts.posterous.com/javascripts/bundles/tagging.js (?) -
http://javascripts.posterous.com/stylesheets/bundles/post.css (30kb) -
http://connect.facebook.net/en_US/all.js (83kb) They look like they're gzipped but they could also be minimized and put into one file. Right now it's hovering around 400kb, which is huge. Add that on top of a theme and the site takes a while to load. 400kb is larger than the Flex Framework. Second, it would be nice if you could extract the inline javascript out into the main.js file so everything is unobtrusive. The generated HTML/javascript doubles the size of the rendered HTML, and add lots of whitespace and stuff that makes it hard to read. I understand there are tools like Firebug to inspect the DOM, but it's also nice to open it in any browser to take a glance, I do that all the time. That would take max an hour to fix :), and it would be greatly valued by the developer community. That's it, just some optimization suggestions to make customization more rewarding :) Well, that and javascript support so I can do custom analytics tracking and animations. Until then! Best,
