visitor evaluation response - willmaster · 5. page navigation on page navigation is for the most...

Visitor Evaluation Response for sipalaysuites.com Tony Simpson © 2009 webpageaddons.com – the-search-engine-optimizer.com

Visitor Evaluation Response

for Sipalaysuites.com Through a detailed analysis of the 10 responses people and 10 responses search engines have to your web site it is possible to improve visitor retention and search engine friendliness. This can lead to more visitors through better indexing and ranking by the search engines and improvements in visitor experience that lead to more sales. People and search engines visit your web pages and web site looking for entirely different things. For your web site to be successful it needs to cater effectively to both types of visitor. Firstly, the analysis focus is on how your web site looks and responds to people, in terms of web optimisation, layout and function, including:

Visual Appearance Visitor Impression Marketing Message Sales Experience Page Navigation Site Navigation Page Download Speed Image Optimization W3C Standards Compliance Accessibility

Secondly we focus on the main landing (home) page and how it responds to a search engine. We determine whether you are presenting a search engine friendly web site with a correct balance between web page optimization and web site optimisation, including:

Use of Keywords Web Page Optimization Web Page Coding for Search Engines Web Site Indexing for Search Engines Meta Tag Compatibility Page Title and Description Compatibility Internal Linking Structure & Tags Link Validation Page Theme Site Theme


1. Visual Appearance The site makes good use of complimentary colors with soft brown and sepia tones and good contrast that makes the text on the page easy to read. The layout of each page is consistent with generally clear navigation and a professional looking design.


2. Visitor Impression The site gives an impression that the hotel rooms are large, with large comfortable looking beds and basic amenities. Some rooms do however look a little bare, particularly in the standard range, although one accepts that this is the cheapest rate room.

Standard Room Junior Room It was not possible to determine the physical location of the hotel within the city since there was no map provided. There were also no views from the hotel windows which would indicate what the hotel overlooks or what overlooks the hotel. It also took quite some time to find any views of the outside of the hotel which were hidden away under a “read more” link on the home page which linked to the page stay-in-sipalay-hotel.htm. The executive rooms promote a “nice view of the beach” but no hotel beach views were found.


3. Marketing Message The hotel is marketing itself as providing “value for your money while enjoying the charming ambiance of a beachside escape”

Is this the hotel beach ? Is this the hotel beach ? The hotel in marketing itself as a “beachside escape” but does not provide any recognizable views of the hotel’s beach front. There is a photo gallery, but none of the photos are clearly labelled to show what or where the view actually is. On the page “sipalay-white-sand-beach-resort.htm” a great deal is written to market this as a beach resort but there are no photo views on this page to support the marketing message. A picture is worth a thousand words. Prices for a room at the hotel range from 2,600.00 pesos to 1,500.00 pesos. Since the hotel is trying to attract local and foreign tourists it would be advisable to have prices in at least one other major currency ( $ ) and also have a currency converter on the site. We suggest displaying prices as 2,600 not 2,600.00 to reduce the number of zeros which may create the impression the rooms are more expensive than they actually are. The site does not offer any Unique Selling Proposition (USP) that would differentiate what it offers from that of any of its competitors. Offering value for money or a beachside escape is not a unique proposition. The site also does not have a Value Proposition (VP) that states in 10 words or less clearly and succinctly why someone should stay at the hotel. What specific value does the hotel offer that is quantifiable that would encourage someone to make a booking.


4. Sales Experience Links to the reservations page are clear from every page of the site. Booking requests are made by completing an online form and submitting that to the hotel who then contact the potential visitor by email or phone. While the site has no “real-time” online booking facility that enables a visitor to book and make payments online a useful addition would be an availability calendar. An availability calendar would enable potential clients to at least check room availability prior to making an enquiry. The reservations page states that “we can guarantee a total satisfaction in your whole stay” but we could find nothing regarding a formal guarantee or even a statement of the hotel’s policies. We would suggest adding a page about the hotel’s policies and terms and conditions. In addition if a total satisfaction guarantee is being implied then we would suggest a formal written guarantee policy is also added. Now let us look at hotel occupancy. If we assume the hotel is open 48 weeks of the year, or 336 days, with 16 rooms, that is 5,376 room nights per year, or 487 room nights per month available for full occupancy. If we assume the hotel needs to have a room occupancy rate of 33% for the hotel to break even financially, or give an adequate return on your investment, then that means of 487 room nights, about 160 room nights on average, always need to be occupied. If we also assume the average stay is 4 nights, then 160 room nights per month requires an average 40 guest bookings per month. If we assume 10 of these room bookings come from direct telephone enquiries the remaining 30 would need to come from the web site.

So the question is How many visitors does sipalaysuites.com need

to generate 30 guest bookings per month ? The percentage of visitors to a web page that result in a sale (reservation) is known as the page conversion. How well a web page and a web site can convert visitors into buyers involves many factors involving among others, page design and marketing. Let us assume your “sales” page converts 1 in 100 visitors into a reservation. That’s a conversion rate of 1%, or for every hotel reservation your most important “sales” page needs to get 100 visitors. A 1% conversion rate would be quite good. Therefore to achieve 30 guest bookings per month the hotel requires 30 x 100 visitors to the sales page per month, or 3000 visitors per month. Note this is 3,000 visitors to the site’s sales page, not 3,000 visitors to the web site. To determine how many visitors to the web site would be required to get 3,000 of these visitors to the site’s main sales page we need to look at two other factors, site visitor retention and site design. Not all site visitors that come to a web site are interested in what the site has to offer. In fact for the majority of web sites 75% of visitors to a site leave the site in less than 30 seconds.


The way visitors are directed to move from page to page within the site will determine how many visitors end up on the site’s “sales” page. This is determined by careful site design. If we assume the site is designed such that 40% of visitors to the site end up on the sales page, then the total number of “interested” visitors required to the site is 7,500. If we now account for the 75% of visitors “not interested,” the site now needs 30,000 visitors per month. Working this result backwards of the 30,000 visitors per month to the site, 75% or 22,500 are not retained (not interested in what the site offers) which leaves 7,500 visitors who go further into the site. Of these 7,500 visitors, only 40% or 3,000 ever get to the “sales” page.

So, assuming a 33% hotel occupancy rate and the indicated web site performance, sipalaysuites.com would need 30,000 visitors per month to the site to achieve

30 guest reservations per month Later in this report it was stated that if sipalysuites.com were designed to achieve a 1st page ranking on Google for all 27 phrases we researched, then the estimated visitor traffic to the site could be around 8,000 visitors per month from Google. Since Google accounts for 60% of search traffic that means total search engine visitors to the site from other search engines accounts for 40%. Therefore, the maximum likely traffic to the site is 13,300 visitors per month, 8,000 from Google and 5,320 from other search engines. Based on the figures in this report there would not be enough traffic (visitors) available to sipalaysuites.com to support the level of reservations required.

There is simply not enough search engine users looking for phrases to do with hotels and related topics in sipalay, at least not yet

Of course with actual figures for hotel occupancy required to provide an acceptable return on investment (ROI) and using actual site performance data, a more accurate and realistic assessment of the required visitors to the site could be made.

So, with less than the required visitors available to sipalaysuites.com How can the required number of guest reservations be achieved ?

With an absolute maximum of 13,300 visitors available, the site would need to be more

efficient at converting those visitors into bookings. This means instead of a 1% conversion rate, the sales page for the site would need to have a conversion rate of at least 2.25%. The conversion rate of any sales page is determined through careful design and testing. The process involves creating different page designs and testing which design converts the best through a series of tests known as split-testing and Taguchi accelerated testing.


5. Page Navigation On page navigation is for the most part clear on each page and consistent from page to page. Each page has top and bottom of page navigation links with images to the left of the page and main body content to the right on each page. Page text is in a single column format read from top to bottom. Each page has a navigation scheme that would be familiar to most web users. There are some pages, for example, philippines/negros-occidental/sipalay-city/sipalay-dive-spot.htm that make use of blue text which turns dark purple when the page is visited. These links are very difficult to read given the dark brown background color of the page. 6. Site Navigation Navigation around the site to key pages like Accommodation, Services, Reservation and Contact is clearly defined at the top and bottom of each page. Links to other pages are also provided at the bottom of each page. Of the 20 pages on the site on average only 12 of those pages can be reached consistently from each page. Overall navigation around the site is clear and consistent although it should be said that we still found some things difficult to find, for example exterior views of the hotel. 7. Page Download Speed Most site pages comprise about 12KB of html code with 170KB of image and flash video. This would give the first page a download time of around 36 seconds on a dial-up connection and about 3 seconds on a medium speed broadband Internet connection. A major contributor on most pages to the download time is a flash header that accounts for around 81% of the total download. Subsequent pages will load faster since the visitor’s browser will use its cache for the flash file and other images rather than having to download them again for each page. Provide this site considers most of its visitors to have a broad-band connection these download times would be acceptable.


8. Image Optimization Many of the thumbnail images that can be clicked to be viewed at full size could be better optimized to reduce the file size by an average 50% with no loss of visual quality. For example:

Original Site Image 48KB

Optimized Image 24KB 9. W3C Compliance See Appendix 1


10. Accessibility See also Appendix 1

11. Use of Keywords The absolutely critical part of designing a web site for today’s world is discovering keyword phrases. These are the phrases that searchers will type into the search box on a search engine, in particular Google, since it dominates on average, 60% of Internet searches, worldwide. Designing a web site optimized for certain keyword phrases will determine how well that site’s web pages will rank with the likes of Google. Correct optimization will play an important part in determining if a site like sipalaysuites.com will appear on the 1st page of Google for particular search terms. The purpose of keyword research is not only to determine what phrases searchers are using on a search engine, but to discover how often they search using those phrases. For example take the search term “sipalay beach resorts.” This according to Google, is a search phrase used on average 16 times per month on Google worldwide. The phrase “sipalay hotels” is searched for on average 210 times per month. Therefore, in designing a web page it makes sense to optimize that page to rank well on Google for the search phrase “sipalay hotels” not “sipalay beach resorts.” The former gets 13 times as many searches (traffic) so it makes sense to rank well for “sipalay hotels” and not “sipalay beach resorts.” Take another example “philippine hotel” searched for on Google an average 590 times per month and “philippines hotel” searched on Google 3,600 times per month. Note the only difference between these phrases is an “s” in “philippines”, but that “s” gives the one phrase 6 times as many searches per month. So a high ranking on Google for “philippines hotel” is better than ranking well for “philippine hotel” in terms of the likely visitors coming to the site.

There is also no point in ranking highly for a search phrase that no one uses on Google or any other search engine


For example on sipalaysuites.com there is a page called “visit sipalay city.” If we assume this page were designed and optimized to rank well on Google for the search phrase “visit sipalay city” that would be good if lots of people were searching on Google using that phrase. No one according to Google uses that phrase (yet), so currently there is nothing to be gained in ranking highly for it on Google, it will bring zero visitors to the site.

One final factor to take into account in keyword research is how many competing web sites there are trying to rank highly for the same phrases as your site. The more competing web pages, the more difficult it becomes to rank well for that phrase. For example, take the search phrase “beach vacations.” This gets 135,000 searches on Google per month. However, it also has 450,000 other site’s pages competing to rank well for the same phrase. Ranking well on Google for “beach vacations” would be virtually impossible for a new site like sipalysuites.com, even if it wanted to rank well for this phrase. There are over 200 factors that Google uses to determine how a web page and site will rank for any particular search phrase. It is not known what keyword research was done by the existing webmaster before designing the sipalaysuites.com website. However, based on over 5 years of experience in designing websites for search engines it is clear that some pages on sipalaysuites.com are optimized to rank well for phrases that will bring very few visitors to the site. Having completed some preliminary keyword research for sipalysuites.com we have compiled a list of 27 keyword phrases that are used on Google and get a combined total of just under 32,000 searches per month. If sipalysuites.com were designed to achieve a 1st page ranking on Google for all 27 phrases, the estimated visitor traffic to the site could be around 8,000 visitors per month from Google. While possible, this level of traffic (visitors) is not likely for a new website and could well take up to 2 years of effort, or more, to achieve naturally from free search engine traffic. Visitors to a web site are its life blood especially for a commercial web site. There are basically only three ways to increase visitors (traffic) to a web site.

1. Free natural traffic from the major search engines, Google, Yahoo, MSN Live. 2. Paid for traffic from Pay Per Click (PPC) or other paid sources. 3. Unpaid links from other web sites to your site.

Increasing free traffic from the search engines can take a long time and a lot of work. Paying for traffic is by far the quickest method to bring visitors to a site. That is, if you have the funds and it’s cost effective in terms of the sales made being enough to cover the cost of the traffic. Paying for traffic through Google Adwords (PPC) is frequently not cost effective for many web sites and many web site owners spend a lot of money on PPC without ever realizing that fact. There is a Pay Per Click Optimization tool at: http://www.the-search-engine-optimizer.com/ppc-optimization-tool.htm

http://www.the-search-engine-optimizer.com/ppc-optimization-tool.htm


By inputting various figures to this tool it will determine for you how much you can afford to pay for each click (visitor) to your site. This tool will tell you that there are circumstances when paying for visitors through PPC is going to cost more money than you are ever going to make in sales and is therefore not cost effective. The 3rd method for getting visitors through unpaid links from other sites, while valuable in many respects, it can be difficult and time consuming to achieve. Like free traffic from the search engines it is a process that can take a long time and can not be rushed. Finally on the subject of visitors, web site owners very often become obsessed with getting more and more traffic to their web site in the belief that the more visitors they get, the more sales they will make. Very often this is not true. Take for example sipalaysuites.com. While I don’t know exactly how many visitors the site or any page on the site currently gets (your webmaster does) it will not be many. I know that much from the research I have done and the fact the site is new. 12. Web Page Optimization There is evidence that an attempt has been made in the design of the site to optimize it for the search engines. This can be seen in the use of keyword terms in the link text and in page names. However based on our keyword research the correct keywords have NOT been chosen. Each page also correctly makes use of a separate navigation scheme for search engines. This takes the form of links at the bottom of each page which duplicate the flash navigation links at the top of the page that would not be navigable by a search engine. Effort has also been made to feature keywords and phrases in the main text content of the page. To the search engines sipalaysuites.com is a website comprising 20 web pages. Five of these web pages are duplicated or contain the same content as 5 other pages and one page sipalay-accomodations.htm does not exist and produces a 404 page not found. This is because the page name is misspelled and should be sipalay-accommodations.htm. The site therefore has only 14 unique web pages. Having duplicate web pages on the same web site should be avoided since it is a practice not liked by the search engines. We can offer no explanation as to why there are 5 duplicate pages on the site and it is our recommendation these 5 duplicate pages be removed. Sipalysuites.com contains more than 15 spelling mistakes and a large number of grammatical errors and incorrect phrasing that could be amusing to an English reader.


13. Web Page Coding for Search Engines The site’s pages also contain a large number of commonly repeated browser coding errors, but these would be easily corrected (see Appendix 1).


14. Web Site Indexing for Search Engines The domain sipalaysuites.com was registered on March 18, 2008 for just 1 year, so it expires on March 18, 2009. The major search engines like Google, generally do not rank websites highly for competitive search terms when the domain name is registered for only 1 year. The standard registration period is at least 2 years. Google regards such 1 year registered sites as “throw away” sites, here today, gone tomorrow. It therefore treats them with lower importance than longer registered domains. To be considered a “long term” site of more importance by Google, we suggest the next registration be at least 4 years or more. There was no robots.txt file, sitemap.xml or urllist.txt file found associated with this site and it is recommended that all three files should be available for the search engines. Of the 14 unique pages on the site, 13 pages are indexed (catalogued by) Google.com and 6 pages are indexed by Yahoo.com. Unless a page is indexed (known) to the search engines it can not appear in a search engine’s results listing when someone is looking for that subject on the Internet. It is therefore very important to a web site to have as many pages as possible indexed by a search engine. The most important search engine is Google and secondly Yahoo. Sipalaysuites.com is well known to Google, but will probably do better with Yahoo given more time (Yahoo tends to be much slower at indexing new sites).

15. Meta Tag Compatibility


16. Page Title and Description Compatibility


17. Internal Linking Structure & Tags


18. Link Validation Broken links, ordered by link: http://www.sipalaysuites.com/sipalay-accomodations.htm error code: 404 (not found), linked from page(s): http://www.sipalaysuites.com/sipalay-hotel-contact.php http://www.sipalaysuites.com/sipalay-city-hotel-reservation.php Correct internal URLs, by MIME type: text/html 20 URLs 224134 Bytes (218 KB) 12.35% text/css 1 URLs 1171 Bytes (1 KB) 0.62% application/x-shockwave-flash 1 URLs 151640 Bytes (148 KB) 0.62% image/gif 19 URLs 239676 Bytes (234 KB) 11.73% image/jpeg 121 URLs 3874080 Bytes (3783 KB) 74.69% Total 162 URLs 4490701 Bytes (4385 KB) 100.00% All pages, by result type: ok 162 URLs 92.57% skip external 12 URLs 6.86% not found 1 URLs 0.57% Total 175 URLs 100.00% List of valid URLs you can submit to a search engine: www.sipalaysuites.com/ www.sipalaysuites.com/sipalay-photo-gallery.htm www.sipalaysuites.com/stay-in-sipalay-hotel.htm www.sipalaysuites.com/sipalay-hotel-services.htm www.sipalaysuites.com/how-to-get-to-sipalay-suite.htm www.sipalaysuites.com/philippines/negros-occidental/sipalay-city/sipalay-visit.htm www.sipalaysuites.com/philippines/negros-occidental/sipalay-city/sipalay-vacation.htm www.sipalaysuites.com/philippines/negros-occidental/sipalay-city/sipalay-dive-spot.htm www.sipalaysuites.com/philippines/negros-occidental/sipalay-city/sipalay-hotel-accommodation.htm www.sipalaysuites.com/philippines/negros-occidental/sipalay-city/sipalay-white-sand-beach-resort.htm www.sipalaysuites.com/index.htm www.sipalaysuites.com/sipalay-accommodations.htm www.sipalaysuites.com/sipalay-city-hotel-reservation.php www.sipalaysuites.com/sipalay-hotel-contact.php www.sipalaysuites.com/sipalay-visit.htm www.sipalaysuites.com/sipalay-vacation.htm www.sipalaysuites.com/sipalay-dive-spot.htm www.sipalaysuites.com/sipalay-hotel-accommodation.htm www.sipalaysuites.com/sipalay-white-sand-beach-resort.htm www.sipalaysuites.com/sipalay-video-gallery.htm

http://www.sipalaysuites.com/sipalay-accomodations.htm

http://www.sipalaysuites.com/sipalay-hotel-contact.php

http://www.sipalaysuites.com/sipalay-city-hotel-reservation.php

http://www.sipalaysuites.com/

http://www.sipalaysuites.com/sipalay-photo-gallery.htm

http://www.sipalaysuites.com/stay-in-sipalay-hotel.htm

http://www.sipalaysuites.com/sipalay-hotel-services.htm

http://www.sipalaysuites.com/how-to-get-to-sipalay-suite.htm

http://www.sipalaysuites.com/philippines/negros-occidental/sipalay-city/sipalay-visit.htm

http://www.sipalaysuites.com/philippines/negros-occidental/sipalay-city/sipalay-vacation.htm

http://www.sipalaysuites.com/philippines/negros-occidental/sipalay-city/sipalay-dive-spot.htm

http://www.sipalaysuites.com/philippines/negros-occidental/sipalay-city/sipalay-hotel-

http://www.sipalaysuites.com/philippines/negros-occidental/sipalay-city/sipalay-white-sand-

http://www.sipalaysuites.com/index.htm

http://www.sipalaysuites.com/sipalay-accommodations.htm

http://www.sipalaysuites.com/sipalay-city-hotel-reservation.php

http://www.sipalaysuites.com/sipalay-hotel-contact.php

http://www.sipalaysuites.com/sipalay-visit.htm

http://www.sipalaysuites.com/sipalay-vacation.htm

http://www.sipalaysuites.com/sipalay-dive-spot.htm

http://www.sipalaysuites.com/sipalay-hotel-accommodation.htm

http://www.sipalaysuites.com/sipalay-white-sand-beach-resort.htm

http://www.sipalaysuites.com/sipalay-video-gallery.htm


19. Page Theme (index.htm): The page theme is determined from the overall prominence of terms on the page and in the coding of the page and for the index.htm page this is: sipalay city suites 034 0350 2006 473 It should also be noted that the site will be seen by the search engines as having two home pages, one at http://www.sipalaysuites.com and one at http://www.sipalaysuites.com/index.htm since links on other pages point to this latter page. The site should not have links pointing to http://www.sipalaysuites.com/index.htm 20. Site Theme Starting Page = http://www.sipalaysuites.com Total Pages Found = 20 Total Links = 390 Total Internal Links = 379 Total External Links = 11 Site Wide Reputation = city sipalay accommodation beach dive gallery hotel Site Wide Topic = city sipalay hotel diving beach resort Average Reputation/Topic Match = 3 out of 5 Most important pages seen by a search engine

http://www.sipalaysuites.com



http://www.sipalaysuites.com


Summary We have outlined a number of areas in which corrections and improvements to sipalysuites.com could be made. Based on various assumptions for hotel occupancy and site design it was shown the site could require up to 30,000 visitors to obtain 30 guest reservations per month. It was also shown that 30,000 visitors to the site from free search engine traffic would be highly unlikely given the limited number of searchers looking for topics related to this hotels business. To achieve the required bookings it was outlined why the site design would need to be improved to convert more of the limited available visitors into hotel reservations.


Find more information at: How well is your site optimized for people ? http://www.webpageaddons.com/optimization-tutorial-quiz.php Increasing Traffic & Sales: http://www.webpageaddons.com/increasing-traffic-sales-quiz.php Does your Landing Page Qualify for Optimization: http://www.webpageaddons.com/landing-page-optimization.php How well is your site search engine optimized ? http://www.webpageaddons.com/optimized-search-engine-quiz.php Guaranteed website optimization services: http://www.webpageaddons.com/website-optimization-services.php Competitor Analysis (On-Page and Off-Page Optimization): http://www.the-search-engine-optimizer.com/competitor-analysis.htm Keyword Discovery at: http://www.the-search-engine-optimizer.com/keyword-discovery.htm Choosing Keywords at: http://www.the-search-engine-optimizer.com/choosing-keywords-pt1.htm Keyword Research Tools to Help You at: http://www.the-search-engine-optimizer.com/keyword-research-tools-pt1.htm

http://www.webpageaddons.com/optimization-tutorial-quiz.php

http://www.webpageaddons.com/increasing-traffic-sales-quiz.php

http://www.webpageaddons.com/landing-page-optimization.php

http://www.webpageaddons.com/optimized-search-engine-quiz.php

http://www.webpageaddons.com/website-optimization-services.php

http://www.the-search-engine-optimizer.com/competitor-analysis.htm

http://www.the-search-engine-optimizer.com/keyword-discovery.htm

http://www.the-search-engine-optimizer.com/choosing-keywords-pt1.htm

http://www.the-search-engine-optimizer.com/keyword-research-tools-pt1.htm


Appendix 1: Validation Report

index.htm Line: char Type Message Description

2:2 Message (Web Content Accessibility Guidelines 1.0 (Priority 3)) [ACCESSIBILITY]

The natural primary language of a document should be identified [P3, 4.3]. Consider using the "lang" and/or (for XHTML) "xml:lang" attributes with the "html" tag to specify the language. For example, lang="en" for English or lang="fr" for French. Note that the language may also be specified by the web server through HTTP headers in which case checkpoint 4.3 would be satisfied without the "lang" or "xml:lang" attributes.

<html><head>

5:2 Message (Search Engine)

Tip - A good title is very important for search engine listings. Use many keywords and search terms in the title but make it readable. Don't just stuff keywords in the title. The title should also be something that a user will want to click on when it's listed on a search engine. A good title is also important when a visitor bookmarks a page. Example: <title>Download CSE HTML Validator - Powerful HTML and Link Checking Software for Windows</title>. We recommend that the "title" tag be the first tag inside the "head" section.

<title>Sipalay Suites - Sipalay City Hotel</title>


[107] The web page description contains 238 characters. We recommend a maximum of 200 characters (about 25 words). Consider reducing the description's length.

<meta name="description" content="Sipalay Suites Hotel. The best hotel in Sipalay City, Negros Occidental. A great place where you can stay in Sipalay City while having a vacation with you family and friends and enjoying the beautiful tourist spots and white sand beaches.">


[8] Found 1 repeated keyword/phrase ("festivals" (2x)). Many search engines consider repeated keywords and phrases "spamming" and may punish spamming by reducing a web page's rank or by not listing it at all. Consider removing any repeated keywords or phrases.

<meta name="keywords" content="Sipalay, Sipalay City, hotels, hotel, dive spots, diving center, resorts, resort, white sand, beach, beaches, reservation, accommodation, vacation, Negros Occidental, Negros Oriental, Philippines, visit, tourist, stay, pension house, festivals, festivals, tour, inn, party, jet ski, destination, treking, hiking, camping, island hopping, caving, diving school, coral reefs, affordable, tourism, snorkeling, restaurant, bars">

9:2 Warning (Search Engine)

A "title" tag has already been used. Search engines can easily detect multiple title tags and have been known to ban sites which use such spamming methods. Be sure to only use one appropriate title per document. We recommend that the "title" tag be the first tag inside the "head" section and that it contains many keywords and search terms but is also readable.

<title>Sipalay Suites, Sipalay City, Philippines</title>

9:2 Error HTML and XHTML documents may have only one title. The "title" element has been used 2 times.

<title>Sipalay Suites, Sipalay City, Philippines</title>


10:2 Message (Section 508 Accessibility Standards) [ACCESSIBILITY]

Documents must be organized so they are readable without requiring an associated style sheet [Section 1194.22 (d)]. This means that when a document is rendered without its associated style sheet(s) that it is still possible to read it. This message is displayed only once.

<link href="index_files/sipalaysuitescss.css" rel="stylesheet" type="text/css">


Documents should be organized so they can be read without style sheets [P1, 6.1]. This means that when a document is rendered without its associated style sheet(s) that it is still possible to read it. This message is displayed only once.

<link href="index_files/sipalaysuitescss.css" rel="stylesheet" type="text/css">

13:8 Error This table doesn't appear to have the same number of cells in each of its 16 rows. Number of cells in each row, starting with the first row: 1, 1, 1, 1, 1, 1, 0, 1, 1, 1, 0, 1, 1, 1, 1, 1. Note that for the purposes of this message, a table cell with a "colspan" or "rowspan" value greater than 1 is considered to be multiple cells.

<table align="center" border="0" cellpadding="0" cellspacing="0" width="750">


Row and column headers should be identified for data tables [P1, 5.1]. This table contains no "th" elements. If it is a data table, then "th" elements should be used to specify and identify row and/or column header cells. Use "td" elements to identify data cells. If this is a layout table, then use the word "layout" in the table's "summary" attribute and this message will not be displayed.



Row and column headers shall be identified for data tables [Section 1194.22 (g)]. This table contains no "th" elements. If it is a data table, then "th" elements must be used to specify and identify row and/or column header cells. Use "td" elements to identify data cells. If this is a layout table, then use the word "layout" in the table's "summary" attribute and this message will not be displayed.



Consider using a "summary" attribute with this "table" tag to provide a summary of the entire table's purpose and structure for user agents rendering to non-visual media such as speech and braille. Note that this attribute may not be widely supported and that the summary text is not displayed on the screen. [P3, 5.5]



Avoid using tables for layout unless the table makes sense when linearized (if it doesn't make sense, then provide an alternative equivalent, which may be a linearized version) [P2, 5.3]. Also, if a table is used for layout, do not use any structural markup for the purpose of visual formatting [P2, 5.4]. CSS is recommended for visual formatting. A linearized table is one that makes sense when its cells are read in row order. This message is displayed only once.


13:8 Message (Accessibility Tips) [ACCESSIBILITY]

If appropriate, consider using a "caption" element to describe or identify the nature or purpose of this table. Use this element immediately after the "table" start tag. Note that the contents of this element does appear as onscreen text and should not be the same as the contents of the "summary" attribute. Example captions: "Hamburgers consumed by each student", "Who spends the most on advertising?". If this is a layout table, then use the word "layout" in the table's "summary" attribute and this message will not be displayed.



13:8 Message (General Compatibility)

[5] The "table" element is an official HTML 4.01 and XHTML element but may not be supported by older or nongraphical browsers. Furthermore, nongraphical browsers that do support tables may not support them the way that you expect. However, most browsers used today should support this element.


13:14 Message (Deprecated)

[9] The "align" and "bgcolor" attributes for the "table" element are deprecated in HTML 4.01 and XHTML in favor of using style sheets. Instead of align="center", consider using the following CSS to center the table: "margin-left: auto; margin-right: auto". This is the correct CSS way but it may not work with some (mostly older) browsers.



When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology [Section 1194.22 (l)]. Ensure that all the programmatic objects and elements on this page conform to this requirement (for example, consider using the "noscript" element to provide functional HTML/text for "script" elements). This requirement helps ensure that user agents that don't support these objects or that have them turned off will still be able to provide the user with usable content. This message is displayed only once.

<td><object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,29,0" width="750" height="298">


If appropriate for this object, consider using the "accesskey" attribute to provide keyboard access to objects. Even though this attribute is not an official HTML or XHTML attribute for the "object" element, it is supported by browsers such as Internet Explorer 4.0+ and Netscape 6.2+. This message is displayed only once.



Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported (for example, consider using the "noscript" element to provide functional HTML/text for "script" elements). If this is not possible, provide equivalent information on an alternative accessible page [P1, 6.3]. This message is displayed only once.



When designing web pages, consider that scripts and programmatic objects pose potential accessibility problems for users: 1) some user agents, like the Lynx text-only browser, do not support scripts, 2) scripts can cause problems with screen readers, 3) some users disable scripts even though their user agent supports them, and 4) scripts are sometimes disabled in schools, libraries, and public access places.


27:8 Error The "embed" tag must have an end tag (</embed>) but the end tag was not found.

<embed src="index_files/sipalay.swf" quality="high" pluginspage="http://www.macromedia.com/go/getflashplayer" type="application/x-shockwave-flash" width="750" height="298">

http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6




http://www.macromedia.com/go/getflashplayer



[5] The "embed" element is not an official HTML or XHTML element. Some browsers may not support this element. Consider using the "object" element instead.

<embed src="index_files/sipalay.swf" quality="high" pluginspage="http://www.macromedia.com/go/getflashplayer" type="application/x-shockwave-flash" width="750" height="298">

28:6 Error The end tag for "embed" (opened in line 27) should appear before the end tag for "object" (nesting error).

</object></td>

31:22 Error (Section 508 Accessibility Standards) [ACCESSIBILITY]

The "img" element requires the "alt" attribute to specify a text equivalent. The text equivalent should be a short phrase that succinctly identifies the image and makes its function clear (like "next page" instead of "green arrow"). However, use alt="" when appropriate, such as when images are intended to format a page (such as spacer images). If appropriate, consider also using the "longdesc" attribute to specify the URI to an extended description of the image. [Section 1194.22 (a)]

<td height="10"><img src="index_files/spacer.gif" width="1" height="1"></td>

31:22 Error (Web Content Accessibility Guidelines 1.0 (Priority 1)) [ACCESSIBILITY]

The "img" element requires the "alt" attribute to specify a text equivalent. The text equivalent should be a short phrase that succinctly identifies the image and makes its function clear (like "next page" instead of "green arrow"). However, use alt="" when appropriate, such as when images are intended to format a page (such as spacer images). If appropriate, consider also using the "longdesc" attribute to specify the URI to an extended description of the image. [P1, 1.1]


31:22 Warning [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "img" element. The "alt" attribute is critical for accessibility. It lets authors specify equivalent text to serve as content when the image cannot be seen or displayed. Use alt="" when alternate text is not appropriate, such as when images are intended to format a page (such as spacer images).



[9] The "height" and "width" attributes for the "td" and "th" elements are deprecated in HTML 4.01 and XHTML in favor of using style sheets.



[8] Alt text is often used by search engines. Use this to your advantage (but do it appropriately). Furthermore, alt text is critical for accessibility. For these reasons and others, it is highly recommended that appropriate alt text be specified using the "alt" attribute. This message is displayed only once.




<td><table border="0" cellpadding="0" cellspacing="0" width="750">

34:10 Message (Web Content

Row and column headers should be identified for data tables [P1, 5.1]. This table contains no "th" elements. If it is a data table, then "th" elements should be used to specify and identify row

http://www.macromedia.com/go/getflashplayer


Accessibility Guidelines 1.0 (Priority 1)) [ACCESSIBILITY]

and/or column header cells. Use "td" elements to identify data cells. If this is a layout table, then use the word "layout" in the table's "summary" attribute and this message will not be displayed.










<td align="left" valign="top" width="280"><table border="0" cellpadding="0" cellspacing="0" width="280">










38:18 Error (Web Content Accessibility Guidelines 1.0

The "img" element requires the "alt" attribute to specify a text equivalent. The text equivalent should be a short phrase that succinctly identifies the image and makes its function clear (like "next page" instead of "green arrow"). However, use alt="" when appropriate, such as when images are intended to format a page (such as spacer images). If appropriate, consider also


(Priority 1)) [ACCESSIBILITY]

using the "longdesc" attribute to specify the URI to an extended description of the image. [P1, 1.1]

<td><img src="index_files/every-rooms.gif" width="280" height="30"></td>
















<td><table align="center" border="0" cellpadding="0" cellspacing="0" width="270">







<td><a href="http://www.sipalaysuites.com/sipalay-photo-gallery.htm"><img src="index_files/photo_gallery.jpg" border="0" width="280" height="40"></a></td>








<td width="7"><img src="index_files/spacer.gif" width="1" height="1"></td>






70:40 Message (Web Content Accessibility Guidelines 1.0






(Priority 1)) [ACCESSIBILITY]

<td align="left" valign="top"><table border="0" cellpadding="0" cellspacing="0" width="463">












<td><div align="center"><img src="index_files/curly-bar.gif" width="104" height="38"></div></td>







[9] The "align" attribute is deprecated in HTML 4.01 and XHTML in favor of using style sheets. Instead of align="center", consider using the CSS "text-align: center" instead.

<td><div align="center"><img src="index_files/curly-bar.gif" width="104"


height="38"></div></td>















<table border="0" cellpadding="0" cellspacing="0" width="225">







89:28 Message (Web Content

Consider using a "summary" attribute with this "table" tag to provide a summary of the entire table's purpose and structure for user agents rendering to non-visual media such as speech and


Accessibility Guidelines 1.0 (Priority 3)) [ACCESSIBILITY]

braille. Note that this attribute may not be widely supported and that the summary text is not displayed on the screen. [P3, 5.5]




<td><img src="index_files/featured-services.gif" width="210" height="23"></td>














109:114

Error (Section 508 Accessibility Standards) [ACCESSIBILITY]

The "img" element requires the "alt" attribute to specify a text equivalent. The text equivalent should be a short phrase that succinctly identifies the image and makes its function clear (like "next page" instead of "green arrow"). However, use alt="" when appropriate, such as when images are intended to format a page (such as spacer images). If appropriate, consider also using the "longdesc" attribute to specify the URI to an extended description of the image.


[Section 1194.22 (a)]

<td class="link1"><a href="http://www.sipalaysuites.com/sipalay-hotel-services.htm"><img src="index_files/more-services.gif" border="0" width="168" height="40"></a></td>

109:114

Error (Web Content Accessibility Guidelines 1.0 (Priority 1)) [ACCESSIBILITY]



109:114

Warning [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "img" element. The "alt" attribute is critical for accessibility. It lets authors specify equivalent text to serve as content when the image cannot be seen or displayed. Use alt="" when alternate text is not appropriate, such as when images are intended to format a page (such as spacer images).




</tbody></table></td><td width="8"><img src="index_files/spacer.gif" width="8" height="8"></td>









112:48 Message (Accessibility

If appropriate, consider using a "caption" element to describe or identify the nature or purpose of this table. Use this element immediately after the "table" start tag. Note that the contents of this





Tips) [ACCESSIBILITY]

element does appear as onscreen text and should not be the same as the contents of the "summary" attribute. Example captions: "Hamburgers consumed by each student", "Who spends the most on advertising?". If this is a layout table, then use the word "layout" in the table's "summary" attribute and this message will not be displayed.










<td><img src="index_files/our_location.gif" width="224" height="23"></td>









117:37 Error (Section 508 Accessibility Standards) [ACCESSIBILIT

The "img" element requires the "alt" attribute to specify a text equivalent. The text equivalent should be a short phrase that succinctly identifies the image and makes its function clear (like "next page" instead of "green arrow"). However, use alt="" when appropriate, such as when images are intended to format a page (such as spacer images). If appropriate, consider also


Y] using the "longdesc" attribute to specify the URI to an extended description of the image. [Section 1194.22 (a)]






<td><a href="http://www.sipalaysuites.com/how-to-get-to-sipalay-suite.htm"><img src="index_files/how-to-get-here.gif" border="0" width="167" height="40"></a></td>






141:4 Error The "tr" element must directly contain at least one of the following elements: "td", "th".

<tr>











145:10 Message

(Section 508 Accessibility Standards) [ACCESSIBILITY]







[5] The "background" attribute for the "td" and "th" elements is not an official HTML or XHTML attribute and is only supported by Internet Explorer 3.0+ and Netscape 4.0+. Other browsers may not support this attribute. For instance, Netscape 3.0 does not support this attribute.

<td background="index_files/curly.gif" height="35"> </td>



<td><div align="center"><img src="index_files/copyright.gif" usemap="#Map" border="0" width="372" height="31"></div></td>






163:4 Error The "tr" element must directly contain at least one of the following elements: "td", "th".

<tr>

185:4 Error (Web Content Accessibility Guidelines 1.0 (Priority 1))

The "area" element requires the "alt" attribute to specify a text equivalent to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is important for visually impaired users and user agents that cannot display images and image maps. [P1, 1.1]


[ACCESSIBILITY] <area shape="rect" coords="1,1,42,15" href="http://www.sipalaysuites.com/index.htm">

185:4 Error (Section

508 Accessibility Standards) [ACCESSIBILITY]

The "area" element requires the "alt" attribute to specify a text equivalent to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is important for visually impaired users and user agents that cannot display images and image maps. [Section 1194.22 (a)]

<area shape="rect" coords="1,1,42,15" href="http://www.sipalaysuites.com/index.htm">

185:4 Warning [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps.

<area shape="rect" coords="1,1,42,15" href="http://www.sipalaysuites.com/index.htm">



<area shape="rect" coords="53,-1,159,14" href="http://www.sipalaysuites.com/sipalay-accommodations.htm">






186:30 Error The value for the "coords" attribute contains an invalid length value "-1". Length values should be non-negative integer lengths or percentages. For rectangles, the value for the "coords" attribute should be in the following format: "left-x,top-y,right-x,bottom-y".




<area shape="rect" coords="170,-1,226,13" href="http://www.sipalaysuites.com/sipalay-hotel-services.htm">

187:4 Error (Section 508 Accessibility Standards)

The "area" element requires the "alt" attribute to specify a text equivalent to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is important for visually impaired users and user agents that cannot display images and image




http://www.sipalaysuites.com/sipalay-




http://www.sipalaysuites.com/sipalay-hotel-


[ACCESSIBILITY]

maps. [Section 1194.22 (a)]




187:30 Error The value for the "coords" attribute contains an invalid length value "-1". Length values should be non-negative integer lengths or percentages. For rectangles, the value for the "coords" attribute should be in the following format: "left-x,top-y,right-x,bottom-y".




<area shape="rect" coords="230,1,312,16" href="http://www.sipalaysuites.com/sipalay-city-hotel-reservation.php">








<area shape="rect" coords="319,1,372,15" href="http://www.sipalaysuites.com/sipalay-hotel-contact.php">







http://www.sipalaysuites.com/sipalay-city-






189:4 Warning [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This

attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps.


Comment (Accessibility Tips) [ACCESSIBILITY]

This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options.

Comment (Search Engine)

If you're concerned about top search engine rankings, visit http://www.htmlvalidator.com/seo.html

Comment You can ignore the nesting errors by turning off the option to check HTML tag nesting. However, it is recommended that you leave this feature enabled. This option is in CSE HTML Validator's Validator Engine Options.

Comment Possibly misspelled words (35, 12 unique): Aircondition (1x), Bldv (1x), Boracay (1x), Brgy (1x), Concepcion (1x), Juana (1x), Mercedez (1x), Montilla (1x), prestine (1x), treking (1x), Negros (4x), Sipalay (21x). Complete list.

Comment HTML 4.01 Transitional document detected. Comment

(Search Engine) [113] Random Search Engine Tip #7 - Each page on a site should have its own unique title. Every title should contain appropriate keywords and search terms that are relevent to the page.

Comment This document contains tables nested to 5 levels. Too many nested tables may cause significant performance problems and may reduce the ability of browsers to render your document properly. This message appears if you have nested tables more than 3 levels deep. Note that Netscape in particular (v4.x and below) may render nested tables much slower than other browsers such as Internet Explorer.

Comment (Web Content Accessibility Guidelines 1.0 (Priority 3)) [ACCESSIBILITY]

Be sure to provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. This is often done using the "accesskey" attribute. [P3, 9.5]

Comment (Web Content Accessibility Guidelines 1.0 (Priority 3)) [ACCESSIBILITY]

The "a" element was used 13 times but not one "a" tag contained an "accesskey" attribute. Be sure to provide keyboard shortcuts for any important links [P3, 9.5].

Comment An ICRA RDF label was not found in the "head" section of this document. Browsers that are enabled with this rating system may not display documents that have not been labelled. It is recommended that every page include an ICRA label. For more information, please visit http://www.icra.org/.

Comment 9986 bytes; [email protected], [email protected], 2.0s@50, 1.6s@64, 0.8s@128, 0.3s@384, 0.2s@512, 0.1s@768, [email protected], 0.0s@10Mbps.

Comment 0.09s, 54 errors, 24 warnings, 54 messages, 14 validator comments, 191 lines, 190 tags (148 closed), 0 document comments, 15 entities, 449 programs run.


http://www.htmlvalidator.com/seo.html

http://www.icra.org/.

mailto:[email protected],

mailto:[email protected],

mailto:0.0s@10Mbps.