Her er en intern mail for at give her en ide om hvad vi roder med:
I had gone over the optimization again, together with Wilmer and Jerome.
Just to recap what had been done this week:
We had combined the ad images in the footer to one image only with image hotspots for the links.
Some buttons are converted to CSS3. We removed the background image and utilized rounded corners and background fills to render the button. In IE9, there are no rounded corners, but there is gradient fills.
Headers at the right side (widgets) have also been converted to CSS.
What we’re checking now is the number of requests in the server. Using Firebug in Firefox, out of 96 requests, there are 53 that we cannot cache. These are the ad components, handlers (.ashx), and web/script resources.
That’s about 50% of the objects in the page.
We cannot remove the ads (36 requests), we don’t have control of the web/script resources (9 request), but we may be able to do something the handlers (8 requests), The ashx are used mostly to retrieve the avatars. We can convert them to direct links, but that means any change in the avatar may not change at once in the browser. I also don’t know if there are other reasons why they are requested this way either. Maybe they can be dynamically resized?
I just have to note that any change that we can do may not have significant impact at all due to the number (~50%) of non-cacheable objects that we have.
However I had ran the page through Page Speed, and the critical changes listed are:
- Enable compression (IIS is already set to compress though)
- Leverage browser caching (there are some images that we can still cache)
- Minimize redirects (these are the image handlers. We don’t know yet why they redirect)
- Minify HTML (we had done what we can here before)
- Serve resources from a consistent URL (EAS links. We don’t control this)
The non-critical items:
- Optimize images (we had done this, we’ll see what we can do about the current detected ones)
- Avoid bad request (these are calls to Sponsorlinks. We still have to check if we can remove or fix them)
- Defer parsing of Javascript (May affect layout, and some if not most are used by the ads).
- Serve scaled images (these are the image handlers
What we can currently do right now is optimize the browser caching and the images, and fix the bad requests.
Secondary thing is the image handlers, if that’s possible at all. But that would handle ‘minimize redirects’, ‘serve scaled images’, and also browser caching.
Det er bare for at vise at vi er i fuld gang, men vi skal huske på at vi ikke har hele sourcekoden til Amino, da det er en indkøbt platform og det giver os udfordringer.
De bedste hilsner
Martin