Think the speed of your website doesn’t matter? That's something you would have to reconsider.
A web page speed study analysis has shown that a 1-second delay in page load time yields:
11% fewer page views for a given website
Customer satisfaction decreases by about 16%
A business will lose 7% in conversions and that can account for millions of dollars in lost revenue depending on your traffic and items sold.
Amazon also found this to be true after it reported increased revenue of 1% for every 100 milliseconds improvement to their site speed.
Walmart also realized a 2% increase in conversions for every 1 second of improvement.
According to Yahoo, 80% of a Web page’s load time is spent downloading the different pieces-parts of the page: images, stylesheets, scripts, Flash, etc. An HTTP request is made for each one of these elements, so the more on-page components, the longer it takes for the page to render.
Quite often, the easiest and quickest way to improve your site speed is to make the design simple.
Streamline the number of elements on your page.
Whenever possible, use CSS instead of images. Images are heavier and take more time to load.
Reduce your number of CSS style sheets by combining them into one. That way you load your CSS sheet just once and reduce the HTTP requests.
When it comes to your website, leaner is always better.
Start by reducing the number of components on each page, plugins, excess and uncessary CSS, removing white space and compressing your HTML. This reduces the number of HTTP requests required to render a page and should make your pages load significantly faster.
A good server response time is something under 200ms (milliseconds).
Google recommends using Pagespeed to findout about page load problems and how to speed up your site.
Use the Serpana pagespeed Tool to examine issues that are slowing your website.
Large pages are often 100kb and more. This happens often if you are looking at creating high quality content. Large content pages are bulky and slow to download. To speed up thse pages, you can employ a technique called compression.
Compression reduces the bandwidth of your pages, thereby reducing HTTP response. Using Gzip Compression helps to zip or compress your web pages. Many web browsers today can decompress and serve compressed web pages. Use the Pagespeed Tool on Serpana to check of your site is using Gzip.
Most web servers can compress files in Gzip format before sending them for download, either by calling a third-party module or using built-in routines. In some cases, this can reduce download times by about 70%.
Since 90% of today’s Internet traffic travels through browsers that support Gzip like Firefox, Internet Explorer, Google Chrome, it’s a great option for speeding up your site.
Servers that offer Compression Modules
Apache: Use mod_deflate
Nginx: Use HttpGzipModule
IIS: Configure HTTP Compression
You can enable Gzip by simply adding the following code into your .htaccess file:
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/xml
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/rss+xml
# Or, compress certain file types by extension:
When you visit a website, the elements on the page you visit are stored on your hard drive in a cache, or temporary storage, so the next time you visit the site, your browser can load the page without having to send another HTTP request to the server.
Here’s how Tenni Theurer, formerly of Yahoo, explains it…
For all cacheable resources (JS and CSS files, image files, media files, PDFs, etc.), set Expires to a minimum of one week, and preferably up to one year in the future. Don’t set it to more than one year in the future because that violates the RFC guidelines.
WYSIWYG resources make it easy to build a Web page, but they sometimes create messy code—and that can slow your website considerably.
Since every unnecessary piece of code adds to the size of your page, it’s important that you eliminate page comments, extra spaces, line breaks, and indentation and unnecessary code in your code. Making your page lean enable them to load much faster.
It also helps to minify your code. Here’s Google’s recommendation:
To minify HTML, you can use the Serpana HTML minifier to generate an optimized version of your HTML code. Enter your HTML code and click on Minify HTMl. Your minified code should appear below.
To minify CSS, you can you the CSS Minifier here on Serpana.
Link to your stylesheets, don’t use @importSimilarly to the point above, @import uses up more resource than directly linking to your stylesheets despite achieving the exact same result. Another reason why not to use @import is that some of the older browsers do not support it, so it’s best to avoid it where possible Optimize images With images, you need to focus on three things: size, format and the src attribute. Image size Oversized images take longer to load, so it’s important that you keep your images as small as possible. Use image editing tools to: Crop your images to the correct size. For instance, if your page is 570px wide, resize the image to that width. Don’t just upload a 2000px-wide image and set the width parameter (width=”570”). This slows your page load time and creates a bad user experience. Reduce color depth to the lowest acceptable level. Remove image comments. Image format JPEG is your best option. PNG is also good, though older browsers may not fully support it. GIFs should only be used for small or simple graphics (less than 10×10 pixels, or a color palette of 3 or fewer colors) and for animated images. Do not use BMPs or TIFFs. Optimize CSS Delivery CSS holds the style requirements for your page. Generally, your website accesses this information in one of two ways: in an external file, which loads before your page renders, and inline, which is inserted in the HTML document itself. The external CSS is loaded in the head of your HTML with code that looks something like this: Prioritize above-the-fold content Having just recommended that you use only one CSS stylesheet and no inline CSS, there is one caveat you need to consider. You can improve user experience by having your above-the-fold (top of the page) load faster—even if the rest of the page takes a few seconds to load. Reduce redirects Redirects create additional HTTP requests and increase load time. So you want to keep them to a minimum. If you’ve created a responsive website, more than likely, you have redirects in place to take mobile users from your main website to the responsive version. Serpana offers cost-effective and reliable uptime and performance monitoring for your websites. We use more than 70 global polling locations to test and verify our customers’ sites 24/7, all year long. With Serpana you can monitor your website’s uptime, performance, and interactions for a better end-user-experience. Your customers will thank you. Nobody Likes a Slow Website – We built this Website Speed Test to help you analyze the load speed of your websites and learn how to make them faster. It lets you identify what about a web page is fast, slow, too big, what best practices you’re not following, and so on. We have tried to make it useful both to experts and novices alike. In short, we wanted it to be a easy-to-use tool to help webmasters and web developers everywhere optimize the performance of their websites. Feature Overview Use a CDN (Content Delivery Network) Hosting your media files on a content delivery network is one of the best ways to speed up your site, and can often saves up to 60% bandwidth and halve the number of requests your website makes. CDNs work by hosting your files across a large network of servers around the World. When a user visits your site from Thailand, they are downloading files from the server that is closest to them. Because the bandwidth is spread across so many different servers, it reduces the load on any single server and also protects your sites from DDoS attacks and traffic spikes. Enable Keep-Alive HTTP Keep Alive refers to the message that’s sent between the client machine and the web server asking for permission to download a file. Enabling Keep Alive allows the client machine to download multiple files without repeatedly asking permission, which helps to save bandwidth. To enable Keep Alive, simply copy and paste the code below into your .htaccess file.
Copyrights © 2020 Voticle. All Rights Reserved.