Ways to improve website performance
Once the document (website's main page) has been downloaded, we
analyze it. It allows us to give webmasters some recommendations on how
to optimize page load speed. We analyze the internal and external
factors.
Enable GZIP Compression
This is a good practice to give the user content in compressed form.
We've detected 224.59 Kb of content that could be compressed.
By compressing content you can achieve the size of ~ 56.15 Kb
(saving 168.44 Kb). This would accelerate the page loading speed and would positively
impact the bandwidth savings in State Of Washington.
http://access.wa.gov/. File size 29.32 Kb and you can save up to 21.99 Kb
http://access.wa.gov/foresee/foresee-trigger.js. File size 61.71 Kb and you can save up to 46.28 Kb
http://access.wa.gov/js/jquery-1.4.2.min.js. File size 88.86 Kb and you can save up to 66.65 Kb
http://access.wa.gov/WebResource.axd?d=oih9VltfGv27JcBUFGIr7F5Z6QpVO2B.... File size 20.79 Kb and you can save up to 15.6 Kb
http://access.wa.gov/foresee/foresee-surveydef.js. File size 2.58 Kb and you can save up to 1.93 Kb
http://access.wa.gov/foresee/foresee-dhtml-popup.js. File size 21.32 Kb and you can save up to 15.99 Kb
Keep Components under 25K
Users often visit web site using a mobile phone. Even the most modern and advanced gadgets
have some limitations. For example an iPhone browser do not cache page components bigger
than 25K. So you should strive to ensure that scripts, CSS-styles, etc.
are less than 25K.
http://access.wa.gov/ Content-Encoding: text/html; charset=utf-8. File size 29.32 Kb.
http://access.wa.gov/foresee/foresee-trigger.js Content-Encoding: application/x-javascript. File size 61.71 Kb.
http://access.wa.gov/js/jquery-1.4.2.min.js Content-Encoding: application/x-javascript. File size 88.86 Kb.
http://access.wa.gov/images/banner.jpg Content-Encoding: image/jpeg. File size 38.09 Kb.
http://access.wa.gov/common/home/images/rotation/spokane_manitopark.jpg Content-Encoding: image/jpeg. File size 32.38 Kb.
http://access.wa.gov/common/home/images/rotation/holidaytree3.jpg Content-Encoding: image/jpeg. File size 35.23 Kb.
Alternate text for the images.
As you may already know, search engine that indexes your pages, do not
have eyes. And all content you are trying to display on your site is
just HTML & CSS code, images, Flash, etc for the robots. It is It's
extremely important to describe each of the objects more datailed using
ALT, TITLE and other tags.
Our robot has determined that the wa.gov page has
1
images, which has no tag ALT. Tag ALT is a text field, that specifies an
alternate text for an image. But not only. Search engines consider this
tag as a supplemental result for assessing the content of your page
entirely. Do not ignore it!
For example your page has this code:
| 173. |
|
<img src="common/home/images/rotation/snow_apple.jpg"> |
We recommend you use rich img code in that place:
| 173. |
|
<img src="common/home/images/rotation/snow_apple.jpg" alt="online tools"> |
P.S. We used keyword for this image that seemed to us most important for your page.
But you can go ahead and give to each of 1 images an ALT text. This problem requires
responsible approach. No need to put the same text at alt tag of the all images.
Imagine that the pictures do not show and try to make sure that users understand what
is shown on the picture based on the alt tag
Specify image dimensions
The browser needs to know the actual dimensions of image (width and height) to quickly render webpage.
We have detected that the 27 images has no width and height.
If you do not specify the width and/or height, then in order to
correctly display the image browser needs to download it and only then
put on the screen. Otherwise, there is a chance browser will display
elements under the picture inappropriately as well as the possible
presence of "jumping" effect of the page content (until the page load
is finished).
We provide below example of how to define the image images/aw_footer_logo.gif dimensions:
| 518. |
|
<img src="images/aw_footer_logo.gif" id="ctl00_Img3" title="Access Washington" alt="Access Washington" width="IMAGE_WIDTH_HERE" height="IMAGE_HEIGHT_HERE"> |
Using H1 tag
Avoid frequent use of the
<Н1> tag. Our robot has found 13
<Н1> tags in the document's body. We recommend you use one
<Н1>
tag per page only.
Content Semantics
We suggest you along with important and well-known tags like Title &
H1 use also H2, H3, H4, H5, STRONG tags. Each page can (and should)
highlight not only the main topic, but also complement the semantic
core of the page and the whole site with the secondary keywords. For
example, if the main topic of the page is dedicated servers, there is
a probability that page has a blog about managed dedicated servers.
If so try to highlight the title of the block by using tag <H2>, and
an information that you provide this service in the United Kingdom
highlight with
H3 tag and so on. Thus try to highlight every important
fragment of the information on your page with tags like STRONG, H2,
H3, etc.
We did not find H2 tags, H3 tags, H4 tags, H5 tags, STRONG tags on the page Use the TITLE for A tag
As we have already mentioned, search engine bots can not see the site
like a people do it. They more focused on the descriptions of certain
page elements. That's why we strongly recommend use TITLE operator in
the "A" tag. This operator not only describes the page referenced by
the page more detailed, but also takes part in the page describing.
For example, you have the link on your website:
| 129. |
|
<a href="mobile/index.aspx" id="ctl00_A1" class="hide">Mobile Version</a> |
We suggest you to remake it in this way:
| 129. |
|
<a href="mobile/index.aspx" id="ctl00_A1" class="hide" title="media center">Mobile Version</a> |
Of course, you can (and should) use more proper phrase instead of the "media center" that describes the link
mobile/index.aspx.
Number of links on the page
Try to avoid a large number of links on the page. Our robot
have found 129 links on this page. Google recommends
to keep the number of links fewer than 100.
More information about this topic you can find in
Google
Webmaster Guidelines
and in the post
"How many links per page?"
by Matt Cutts (head of Google’s Webspam team)