Website speed has become an important advantage in our increasingly wired world. The speed of your site can effect a number of important factors including conversion rates, bounce rates, loyalty, and as of 2010 search rankings. This article sheds some light on how website speed can effect Google rankings.
The size of the average web page of the top 1000 websites passed 1600K for the first time in July (see Figure 1). At the same time the number of objects in the average web page increased to 112 objects in July 2014.
WordPress is a very popular CMS used for websites. Offering an intuitive interface to manage and update websites WordPress is justifiably popular. However, WordPress sites can be slow, which can harm conversions and search engine rankings. This article explores the most frequent performance issues with WordPress sites and offers some solutions.
Mass web hosting is a popular way to host web sites. Lower costs, easy site creation, and convenience lure site owners to host with the likes of HostGator, GoDaddy.com, and Yahoo.com. The problem with mass hosting is just that, a massive amounts of sites on overloaded servers. With sometimes hundreds of sites on a single web server, your site can suffer slowdowns when another site on the same server gets hammered. Often the best approach in this situation is to move to a new host with more lightly loaded servers. This article shows the effects of such a move for a client on a mass web host.
Google is now factoring in mobile friendly web designs and mobile site speed into their search engine rankings. With the growth of mobile devices surfing the Web (some sites we’ve tested have more than 40% of their traffic from mobile devices) Google wants its search engine users to experience the full richness of the Web by rewarding sites with fast mobile-friendly designs.
There are a number of automated ways to speed up your website. Web developers can deploy both software and hardware solutions to speed up their website automatically. By embedding best practices into code, vendors can speed up websites without the need to involve developer resources. This article evaluates Radware’s Fastview web acceleration hardware. Some other solutions are listed below.
The first Velocity Web Performance and Operations conference held in New York City ran from October 14-16, 2013. In its sixth year, Velocity is a conference devoted to testing and speeding up websites. Co-founded by Steve Souders, of YSlow and Page Speed fame and now with Google, attending Velocity is a great way to stay up to date on the latest performance trends, include mobile performance. This article gives some highlights from the conference.
The Affordable Care Act began enrollment on October 1, 2013 for health care coverage beginning on January 1, 2014. Health care consumers are directed to log-on to the healthcare.gov website (see Figure 1), call, or show up in person. Over 2 million people have accessed the site in the first two days, many experiencing errors or delays (which the media is characterizing as “glitches” and “growing pains”). Let’s take a closer look at the healthcare.gov website to see how its performance can be improved.
Start render optimization takes place before the first content appears to the user, and is critical for good HCI feedback. A fast start render time gives the user visual feedback
that the web server is responsive. Ideally you want a start render time (and useful content
display) of under 1-2 seconds (see Website Optimization Secrets for details). The start render (the time it takes for the first visible changes to appear) is composed of Time to First Byte (TTFB) connect time, server response time, processing objects in the HEAD of your document, and initial page parsing and rendering. Optimizng your start render time is a matter of optimizng each of these delay components.
When a user requests a page, it can take from 200 to 500ms for the backend server to create the HTML. During that time the browser is idle, waiting for data to arrive. Developers can speed up start render times and the display of useful content by flushing the buffer. Flushing HTML sends a partial HTML response to the browser, which modern browsers can display. Flushing allows the browser to start fetching components and rendering the response while the backend can continue creating the rest of the HTML page.