Optimize images for SEO and website loading speed

Why Do I need to optimize Images on my Website?

Then Simple and most basic reason is for improving website SEO and load the website faster. The faster the websites is loaded the more SEO traffic you can expect.

How to reduce the load times of pages by loading appropriately sized images.

Diminish file sizes based on where images will be displayed.

Resize image files themselves instead of via CSS.

Save files in appropriate format depending on usage.

Cost benefit ratio: high value

Access needed

90% of most websites are graphics dependent and therefore there are a lot of image files. Leaving these images uncompressed and in the wrong format can drastically slow down your web page load times. So it’s  important to optimize your images.

Optimizing images for the web

The images create using programs like Photoshop and Illustrator look amazing but often the file sizes are very large.

This is because the images are made in a format which makes them easier to manipulate in different ways.

With file sizes upwards of a couple of megabytes per image, if you put these files on your website it would be very slow to load.

Optimizing your images for the web means saving or compiling your images in a web friendly format depending on what the image contains.

Images hold data other than just the pixels we see on the screen.

This data can add unnecessary size to the image which leads to longer load times as the user waits for the image to download.

In terms of cost versus benefit optimizing your images should be near the top of your page speed optimizations if you don’t have them optimized already.

How it work?

Optimizing images for the website can reduce your total page load size upto 80%.

There are two forms of compression that we need to understand, Lossy and Lossless.

Images in a lossy format will look slightly different than the original image when uncompressed.

Keep in mind that this is only visible at a very close look. Lossy compression is good for website, because images use small amount of memory, but can be sufficiently like the original image.

Images in lossless format retain all the information needed to produce the original image.

For this reason these images carry a lot more data and in return are a much large file size.

Can you imagine take a poster size image and using it as a thumbnail? The little 20px by 20px image would take as long to load as the original poster, when we could just be loading a 20px

We can also optimize images for the website by saving them as the appropriate dimensions.

Resizing the image on the webpage itself using CSS is helpful but the issue is the web browser will still download the entire original file, then resize it and display it.

Optimize Your Images

Full optimization of images can be quite an art to perfect as there are such a wide variety of images you might be dealing with. Here are the most common ways to optimize your images for the web.

Reduce the white space around images – some developers use whitespace for padding which is a big no no.

Crop your images to remove any whitespace around the image and use CSS to provide padding.

Use proper file formats –

If you have icons, bullets or any graphics that don’t have too many colours use a format such as GIF and save the file with lower amounts of colours.

If you have more detailed graphics then use JPG file format to save your images and reduce the quality.

Save your images in the proper dimensions.

If you are having to use HTML or CSS to resize your images, stop right there. Save the image in the desired size to reduce the file size.

To resize your images you will have to use some form of program.

For basic compression you can use a simple editing program such as GIMP.

For more advanced optimization you will have to save specific files in Photoshop, Illustrator or Fireworks.

Tools PageSpeed use to test this recommendation –

WooCommerce Server Requirements


The first step insetting up your WooCommerce-powered online store is to install WordPress and the WooCommerce plugin itself. But before doing so, you should check that your hosting environment meets our minimum requirements. These are:

  • PHP 5.6 or greater
  • MySQL 5.6 or greater
  • WooCommerce 2.5 requires WordPress 4.1+
  • WooCommerce 2.6 requires WordPress 4.4+
  • WP Memory limit of 64 MB or greater (128 MB or higher is preferred)


You should also check WordPress minimum requirements.

Optional Items
  • Some other optional things that may be required include:
  • CURL or fsockopen support for PayPal IPN
  • Some of our extensions require SOAP support
  • An SSL certificate if you wish to install direct payment gateways
  • Multibyte String support if you’re running a non-english store
  • If you want WordPress pretty-permalinks, there are some additonal requirements listed here
  • You can check if your server has the items listed above after installing WooCommerce from the System Status page.

You can check if your server has the items listed above after installing WooCommerce from the System Status page.

Moving Hosts

Need a new host? Check out our hosting here or dedicated WordPress web hosts listed here.

Domain Name 60 Day Lock

Domain lock
Domain lock

To prevent domain name theft, ICANN requires that domain names be prevented for transfer for 60 days in certain situations:

  • Domain name is within 60 days of initial registration
  • Domain name is within 60 days of a previous transfer

In addition, certain registrars may have procedures to prevent transfer for 60 days as well. For example, the registrar GoDaddy places a 60 day lock on any domain name when the whois information is modified. However, as discussed on Domain Name Wire by Bobdobbs (and verified by DomainSherpa), “The 60 day lock can be overridden by a supervisor if you really NEED your domain transferred.”

However, a domain can be sold and transferred during the 60-day registrar lock. Although the domain cannot typically be transferred to an account outside of your registrar, it can be “pushed” to another account within the same registrar. To do so, the buyer must have an account at the current registrar. The seller then uses the buyer’s registrar account login name and/or account number during the transfer.

What is DomainKeys


What is DomainKeys – DomainKeys is an email authentication technology developed by Yahoo, and is primarily used as an additional anti-spam and anti-phishing method.

How DomainKeys works

  • Sending emails


The domain owner generates a public / private key pair to use for signing all outgoing messages (multiple key pairs are allowed). The public key is published in DNS, and the private key is made available to their DomainKey-enabled outbound email servers.

When each email is sent by an account within the domain, the DomainKey-enabled email server automatically uses the stored private key to generate a digital signature of the message. This signature is embedded as a header in the sent email, and the email is sent on to the target recipient’s mail server.

  • Receiving emails


The DomainKeys-enabled receiving email server extracts the signature and claimed From: domain from the email headers and fetches the public key from DNS for the claimed From: domain.

The public key from DNS is then used by the receiving mail server to verify that the signature was generated by the matching private key. This proves that the email was indeed sent by, and with the permission of, the claimed sending From: domain and that its headers and content weren’t altered during the transfer.

The receiving email server applies the local policies based on the results of the signature test. If the domain is verified and no other antispam tests catch it, the email can be delivered to the user’s inbox. If the signature fails to verify, or there isn’t one, the email can be dropped, flagged or quarantined.


How to use a Microsoft Access database on Windows Plesk Hosting

Uploading your database

Login to your the Plesk Control Panel and open the File Manager.

Open the private folder and select Add New Folder.

Click the Browse button and location the database file (*.mdb) file from your local computer.

Press the OK button to upload it.


Setting up a database connection

Click on Home to return to the Home page and select ODBC Settings under Services.

Click on the “Add new ODBC DSN” button

Enter the name of the new connection for the database uploaded in the previous steps (You must only use letters and numbers – no spaces). You can also add an optional description.

From the drop down, select “Microsoft Access Driver (*.mdb)” and click OK.

Enter the Database File Path, this will be in a format similar to: E:\inetpub\vhosts\<example.com*gt;\private\<uploaded_database.mdb> (See the section Finding the Database Path below) where example.com is your domain name and uploaded_database.mdb is the name of the database uploaded to the site. Normally the domain name will not include the www part.

The rest of the fields are optional and are normally not needed.

Click on the “Test” button and if the connection has been created correctly you will be shown the message “Connection Successful”.

If you do not see “Connection Successful” please check you have specifed the correct path (without the www). If you need to enter a password to open the database enter the appropriate username and password details.


Finding the Database Path

Save the attachment shown below “showpath.asp” and upload this to the ‘httpdocs’ folder for your website.

Browse to this page in your web browser http://www.example.com/showpath.asp (replacing www.example.com)

This should show you a path similar to C:\inetpub\vhosts\<example.com*gt;\httpdocs\showpath.asp

To create the path to your database remove the portion “httpdocs\showpath.asp” from the end and add “private\<uploaded_database.mdb>.

Once this is working, please remove the file showpath.asp from your website as it is no longer needed

CentOS 5 End of Life- Bye Bye


CentOS 5 – 6 months until End of Life

This notice was originally posted when CentOS 5 had one year of supported life left. It now has 6 months. You are encouraged to put your migration plans into action now if you haven’t already done so. CentOS 6 goes EOL in 2020, CentOS 7 in 2024.

As per the announcement upstream, http://rhn.redhat.com/errata/RHSA-2016-0561.html you should know that CentOS 5 now has one year of support life left. People using CentOS 5 are encouraged to start their migration process to a supported version.

It should be noted that, unlike RHEL, there is no extended support option for CentOS. Once RHEL 5 goes EOL upstream on March 31st 2017, there will be no further updates for CentOS 5 at all. Those using CentOS 5 and requiring more than 1 year of life are encouraged to investigate the RH extended support program although that will require a migration to RHEL 5 as it does not apply to CentOS 5.

How to know your Server meets PayPal SSL Requirements


PayPal is upgrading the SSL certificates it uses to secure its sites and API endpoints. SSL certificates will need to be signed using the SHA-256 algorithm and VeriSign’s 2048-bit G5 Root Certificate.

PayPal’s service will discontinue the use of SSL connections that rely on the VeriSign G2 Root Certificate.

You can easily determine whether your server supports this new standard by logging into your server via SSH and running a single command:

openssl s_client -connect api-3t.sandbox.paypal.com:443 -showcerts | egrep -wi “G5|return”

If your server complies with the requirements, you will see a result similar to the following:

i:/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=(c) 2006 VeriSign, Inc. – For authorized use only/CN=VeriSign Class 3 Public Primary Certification Authority – G5
Verify return code: 0 (ok)

In that output, you will want to note the presence of two specific items:

  • A Certification Authority containing “G5”. Note that you may see several CA lines in your output; as long as G5 is included, your server is compliant.
  • A Verify return code of “0 (ok)”.

If both are present, your server is compliant and no further action needs to be taken.

If neither is present, then your server will need to have the G5 certificate bundle installed.

NOTE: CentOS 5 (and earlier) is not capable of supporting the new standard. If your server runs CentOS 5 (or earlier), it will need to be upgraded.

Google Webmaster Tools: An Overview


Google Webmaster Tools (GWT) is the primary mechanism for Google to communicate with webmasters. Google Webmaster Tools helps you to identify issues with your site and can even let you know if it has been infected with malware (not something you ever want to see, but if you haven’t spotted it yourself, or had one of your users tweet at you to let you know, it’s invaluable).

And the best part? It’s absolutely free. If you don’t have a GWT account, then you need to go get one now.

This guide to Google Webmaster Tools will walk you through the various features of this tool, and give you insight into what actionable data can be found within. (For more in-depth help, go toGoogle’s Webmaster Help.)

Highlights of Magento Edition 2.1.0


Magento edition 2.0.1 includes several exciting and new features:

Braintree Hosted Fields securely collect all sensitive payment information in checkout so merchants can qualify for the simplest set of PCI compliance requirements. Merchants retain complete control over their checkout style and layout because Braintree gathers credit card data using small, transparent iframes that replace individual payment fields. Braintree settlement reports are now also conveniently available within the Magento Admin.

PayPal enhancements include PayPal in-context checkout and saved credit cards. In-context checkout helps to increase conversion rates 69 bps by allowing shoppers to pay with PayPal without leaving the merchant’s site. PayPal saved credit cards boost repeat purchases by allowing merchants to securely store credit card information with PayPal so customers do not need to re-enter it in checkout or when reordering items from the Admin interface.

Improved management interfaces make it faster and easier to search for information in the Admin, set up global search synonyms, and create new product, category, and CMS content.

Security Enhancements

The release includes enhancements to improve the security of your Magento application. There are no confirmed attacks related to these issues to date, certain vulnerabilities can potentially be exploited to access customer information or take over administrator sessions. Its recommend that to upgrade Magento software to the latest version as soon as possible.

System Requirements

Our technology stack is built on PHP and MySQL. Magento 2.1.0 supports:


Incase you are looking for Magento hosting try our : Specialized Magento Web hosting packages