{"id":45,"date":"2010-04-12T21:34:10","date_gmt":"2010-04-12T20:34:10","guid":{"rendered":"http:\/\/www.forestsoftware.co.uk\/blog\/?p=45"},"modified":"2024-05-03T20:38:11","modified_gmt":"2024-05-03T19:38:11","slug":"webpage-speed-how-to-squeeze-some-extra-speed-from-your-page","status":"publish","type":"post","link":"https:\/\/www.forestsoftware.co.uk\/blog\/2010\/04\/webpage-speed-how-to-squeeze-some-extra-speed-from-your-page\/","title":{"rendered":"Webpage speed \u2013 how to squeeze some extra speed from your page"},"content":{"rendered":"Reading Time: <\/span> 2<\/span> minutes : <\/span><\/span>

The recent Google announcement that they were officially adding a new signal to their search ranking algorithms to take account of site speed (Google blog<\/a>) prompted me to write these few tips about getting your page to load as quickly as possible.<\/p>\n

There are many things you can do to speed up a page, these range from the purely technical that you may or may not be able to implement through to much more simple options.<\/p>\n

Images<\/strong><\/p>\n

File size and resolution – Do you have images on your page?\u00a0 I once looked at a site for a prospective client that had a photo of a boat on the home page, the image looked nice but when I looked at the image properties the file was 4 Mb in size – the client’s designer had taken a digital photograph, placed in on the page and resized it.\u00a0 By taking the photo into a graphics editor, changing the resolution to 72dpi (dots per inch)\u00a0 (most monitors display at 72 or 96dpi while printers work at 300dpi) and resizing the image in the editor we reduced the file size down to a much more reasonable 120Kb.\u00a0 This means that the image took only 3% of the time that the original image took to download.<\/p>\n

HTML code<\/strong><\/p>\n

Whitespace – If you write your own code have a look at the number of blank lines and amount of whitespace in the code – I often work on pages that have multiple spaces between words (normally as a result of someone that has copy and pasted from a word document).\u00a0 Removing the extra whitespace can reduce the amount to time taken to send the code from your server to the browser.\u00a0 This is often only 1 or 2Kb of data but every little bit helps.<\/p>\n

Extra code – If you are copying and pasting from some word processors or programs like MS Publisher (yes some people design their web pages in publisher and send them to us to build) there is often lots of extra code embedded in the page.\u00a0 Removing this can take some time and effort but can produce a good saving in file size.<\/p>\n

Extra code (unwanted html) – older pages and pages that have been put together in a graphics html editor can often have unwanted spans, divs, font changes etc.\u00a0 These often are opened and immediately closed and if they are not needed for page layouts (some layouts use empty divs) they they can be removed to once again save space.<\/p>\n

Styles – If you are using styles on your pages try to put the common ones into a style sheet and only embed those styles that will be used once and only on that page.<\/p>\n

Styles CSS files – The same thing applies to CSS files as to webpages where whitespace is concerned – I have worked on style sheets where the creator has used 20 or 30 blank lines between sections, this resulted is a style sheet that was both unreadable and extremely large.<\/p>\n

All of these are simple ways to improve the speed of your page and, as a by product, reduce the band width that your site uses when sending the pages to visitors.<\/p>\n

More technical ways of speeding up your web pages<\/a> will be in another article – but at least the tips above will give you a good start.<\/p>\n","protected":false},"excerpt":{"rendered":"

Reading Time: <\/span> 2<\/span> minutes : <\/span><\/span>The recent Google announcement that they were officially adding a new signal to their search ranking algorithms to take account of site speed (Google blog) prompted me to write these few tips about getting your page to load as quickly as possible. There are many things you can do to speed up a page, these […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[22],"class_list":["post-45","post","type-post","status-publish","format-standard","hentry","category-seo","tag-website-development"],"_links":{"self":[{"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/posts\/45","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=45"}],"version-history":[{"count":0,"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/posts\/45\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=45"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=45"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=45"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}