sparks.do

----------------------------------------------
Coding Towards Accessibility ◆ 24 ways

journo-geekery:

Another goodies from the 24Ways geeky advent calendar.

Prebrowsing | High Performance Web Sites

journo-geekery:

Steve Souders:

You might ask, “isn’t [pre-fetching performance gains] what the cache is for?” Yes! In many cases when you visit a website the browser avoids making costly HTTP requests and just reads the necessary resources from disk cache. But there are many situations when the cache offers no help:

  • first visit – The cache only comes into play on subsequent visits to a site. The first time you visit a site it hasn’t had time to cache any resources.
  • cleared – The cache gets cleared more than you think. In addition to occasional clearing by the user, the cache can also be cleared by anti-virus software and browser bugs. (19% of Chrome users have their cache cleared at least once a week due to a bug.)
  • purged – Since the cache is shared by every website the user visits, it’s possible for one website’s resources to get purged from the cache to make room for another’s.
  • expired69% of resources don’t have any caching headers or are cacheable for less than one day. If the user revisits these pages and the browser determines the resource is expired, an HTTP request is needed to check for updates. Even if the response indicates the cached resource is still valid, these network delays still make pages load more slowly, especially on mobile.
  • revved – Even if the website’s resources are in the cache from a previous visit, the website might have changed and uses different resources.

Something more is needed.

Long term php guy (I maintained APC for years, slowly given up now), so I've wor... — Hacker News

dhotson:

A former PHP APC maintainer comments on HN about writing high performance PHP using async techniques.

I’ve been struggling with a few of these issues lately. It’s difficult to write PHP in this way when almost none of the libraries or extensions are designed with it in mind.

journo-geekery:

Breaking the 1000ms Time to Glass Mobile Barrier ∙ An A List Apart

Ilya Grigorik discusses in detail how to construct a mobile website that loads as quickly as possible. A site that not only renders in 1 second, but one that is also visible in 1 second. 

mrgan:

Are you undecided in the great Flat vs. Skeuououmourphic design debate of 2012? Are you unsure of how flat is flat enough (but not too flat)? Wondering what it means to let a button be a button? Use this handy chart to pick the button that looks like a button to you!

mrgan:

Are you undecided in the great Flat vs. Skeuououmourphic design debate of 2012? Are you unsure of how flat is flat enough (but not too flat)? Wondering what it means to let a button be a button? Use this handy chart to pick the button that looks like a button to you!

weandthecolor:

Branding and Web Design
This is a nice case study by creative agency Tractorbeam for Exigo, a company that provides the premier platform-as-a-service (PAAS) solution for the direct selling industry.
More about the branding project on WE AND THE COLORWATC//Facebook//Twitter//Google+//Pinterest

weandthecolor:

Branding and Web Design

This is a nice case study by creative agency Tractorbeam for Exigo, a company that provides the premier platform-as-a-service (PAAS) solution for the direct selling industry.

More about the branding project on WE AND THE COLOR
WATC//Facebook//Twitter//Google+//Pinterest

(via matarua)

kelly norton: On Layout & Web Performance

journo-geekery:

Via tech colleagues at The NYT, in their weekly link roundup.  Andre Behrens noted this one:

This short and sweet piece explains how you can trigger bad paint performance just by reading the values of certain DOM properties. Basically: any dynamic layout value will, upon being accessed (whether or not it’s modified), trigger a total paint. In my apps, I’ve taken to doing total size calculations in one place, all at once, updated only on window resizes. It’s unpleasant, but it’s worth the performance bump.

The post includes a list of common JS properties that trigger “layout thrashing”, like offsetHeight, scrollTo, scrollHeight, offsetTop, offsetParent and more.  And Ms. Norton follows up the post with an examination of one particular content-oriented JS property, .innerText, that also thrashes layout.  She recommends .textContent, which is a great tip.

Excellent series of posts.

moderation:

Not soon enough…

moderation:

Not soon enough…

Dontcom: Compass and Wordpress

darren131:

Over the past few months I’ve been doing an awful lot of Wordpress theme development. I’ve also being doing a lot of Sass/Compass development. In this short post I’m going to show you my config.rb set up and my style.scss set up.

Chris Coyier has a pretty good article on this very thing. My…

maxistentialist:

Goodnight everyone.

Selling international yet or do I have to send you pineapple lumps?

maxistentialist:

Goodnight everyone.

Selling international yet or do I have to send you pineapple lumps?