Read Next

Native or Web?

I moderated a panel this week at the Mobile Health Expo on the pros & cons of native vs. HTML mobile development.

The panel speaker was Bill French, and he did a great job outlining the advantages and disadvantages of each approach. You can also find a related blog I posted of the recent Silicon Valley Mobile Monday event on the same topic.

Anyone trying to understand the challenges in mobile development should understand the mobile pyramid, and read PointAbout's whitepapers on the topic - especially the one on 14 mistakes not to make.

The video of Bill's presentation is below. You can also download his slides in Keynote and PowerPoint formats.

Thorough List of Factors That Help Speed Up Your Website

On Zach Browne

Here are the best ways for speeding up your WordPress.

80% of the end-user response time is spent on the front-end. Most of this time is tied up in downloading all the components in the page: images, stylesheets, scripts, Flash, etc. Reducing the number of components in turn reduces the number of HTTP requests required to render the page. This is the key to faster pages.

One way to reduce the number of components in the page is to simplify the page's design. But is there a way to build pages with richer content while also achieving fast response times? Here are some techniques for reducing the number of HTTP requests, while still supporting rich page designs. Combined files are a way to reduce the number of HTTP requests by combining all scripts into a single script, and similarly combining all CSS into a single stylesheet. Combining files is more challenging when the scripts and stylesheets vary from page to page, but making this part of your release process improves response times.

CSS Sprites are the preferred method for reducing the number of image requests. Combine your background images into a single image and use the CSS background-image and background-position properties to display the desired image segment.

Image maps combine multiple images into a single image. The overall size is about the same, but reducing the number of HTTP requests speeds up the page. Image maps only work if the images are contiguous in the page, such as a navigation bar. Defining the coordinates of image maps can be tedious and error prone. Using image maps for navigation is not accessible too, so it's not recommended.

Rendering New Theme...