Comments on: Performance Research, Part 5: iPhone Cacheability - Making it Stick

By: Performance web » Archive du blog » Limitations du cache WebKit

Performance web » Archive du blog » Limitations du cache WebKit — Tue, 06 May 2008 09:41:50 +0000

[…] a de sérieuses limitations sur le cache. Yahoo! avait déjà débusqué les limites de l’iphone : les fichiers ne doivent pas dépasser 25 ko une fois décompressés et le total doit être […]

By: User First Web » iPhone Caching

User First Web » iPhone Caching — Thu, 20 Mar 2008 04:50:25 +0000

[…] case you missed, test show that Safari on the iPhone will only cache objects that are under 25k. Something to keep in mind as you build your iPhone web apps. This entry was written by […]

By: Gene Vayngrib

Gene Vayngrib — Mon, 17 Mar 2008 20:08:56 +0000

Dave, can you elaborate on “replacing images with inline canvases”?
Thanks.

By: SitePoint Blogs » News Wire: Safari Speeds Up AND Gets Web Fonts!

SitePoint Blogs » News Wire: Safari Speeds Up AND Gets Web Fonts! — Tue, 12 Feb 2008 06:26:35 +0000

[…] Performance Research, Part 5: iPhone Cacheability - Making it Stick The YUI blog investigates how to optimize web performance for the iPhone. The iPhone’s cache clears at each power cycle, and it will not cache files 25KB or larger. These facts call for special considerations when optimizing for performance. (tags: yahoo! apple iphone mobile […]

By: Dave Richards

Dave Richards — Thu, 07 Feb 2008 23:21:33 +0000

Since I got my iPhone, I’ve spent a lot of time on wrapping existing websites I use A LOT for my iPhone.

I got a MASSIVE boost in performance by replacing images with inline canvases instead, especially for animations.

By: Wayne Shea

Wayne Shea — Thu, 07 Feb 2008 18:51:46 +0000

Hi Niall,

Regarding your question “Why is there then a maximum cache ceiling range extending 25 KB above the sum of these objects (475-500 KB)?”, note that it is possible for the maximum limit to be anywhere in the 475K to (500K - 1) range for 19 components of size 25KB to be cacheable.

By: Optimizing Web Page Performance For iPhone / iTouch | David Bisset: Web Designer, Coder, Wordpress Guru

Thu, 07 Feb 2008 15:21:34 +0000

[…] focuses on the full capabilities of the iPhone’s Safari browser including browser cache and transfer spee… It’s an interesting read, for example: The iPhone has an amazing UI, but it is limited by […]

By: EJ

EJ — Thu, 07 Feb 2008 02:36:24 +0000

This is great stuff.

It would also be awesome if you also performed this analysis for something like the Blackberry browser. For some sites, it’s able to take the full version and quickly generate a version of the site optimized for the phone; however, for sites on Y! network, the results are generally pretty horrendous.

The answer may be to create WAP version for the phone, but there might be ways of generating HTML that renders well and offers users a richer experience. Knowing it’s constraints would be great.

By: Put Together Quickly » More Optimization for your site

Put Together Quickly » More Optimization for your site — Wed, 06 Feb 2008 23:31:14 +0000

[…] Sill looking for a way to improve your site’s performance after trying other methods? Well Tenni Theurer, a Product Optimization Manager at Yahoo has five great articles that covers reducing the number of HTTP requests, explains web browser caching, the effect of HTTP cookies (co-written by Patty Chi), parallel downloads (co-written by Steve Souders) and details on caching for the iPhone and iPod Touch. […]

By: Niall Kennedy

Niall Kennedy — Wed, 06 Feb 2008 21:08:57 +0000

You mention up to 19 external objects of 25 KB or smaller may be placed into the Safari for iPhone cache. Why is there then a maximum cache ceiling range extending 25 KB above the sum of these objects (475-500 KB)?