
--------------------------------------------------

CSE HTML Validator Standard v17.05 (Registered)
Checking "F:\Homepages\iajo\iajo05\2021\n2021100.htm" (4499 characters).
File date is Montag, 20. Oktober 2025 at 13:09:01.
File checked on Donnerstag, 20. November 2025 at 11:17:32.

     Number of lines checked: 192 in 0.00 seconds
 Number of lines in document: 192 (100.0% of lines checked)
     Number of lines ignored: 0
Number of character entities: 11
        Number of start tags: 130
          Number of end tags: 89 (68.5% of start tags with end tags)
Number of <% ... %> sections: 0
     Number of HTML comments: 0

Number of validator comments: 15
          Number of messages: 22
            Number of errors: 1 (first in line 170)
          Number of warnings: 10

--------------------------------------------------

[CSE] Warning number 1:
Possibly misspelled words (19, 19 unique): Angelozzi (1x),
Carulli (1x), Emanuele (1x), Ginevra (1x), IAJO (1x),
IAJOLOGO (1x), Informations (1x), jazzorgan (1x), Jolina
(1x), Luca (1x), Manufunk (1x), Marcone (1x), Mongia (1x),
Mr.F (1x), Pett (1x), PlayCab (1x), Poisoing (1x), Pol (1x),
Spotify (1x). Complete list. 167 total words checked (0 in
comments).

[CSE] Message number 1:
This document's title is 72 characters long. Consider adding
a <meta name="apple-mobile-web-app-title" content="(13
character short title)"> tag to the head section. This
shorter title will be used when an iOS user adds the page to
their Home Screen, otherwise the page title will be used and
will be chopped off after the 13th character. The title is:
"International Archives For The Jazz Organ (IAJO) - New
Releases n2021100".

   1: <!DOCTYPE HTML>
-------|||||||||||||

[CSE] Message number 2 in line 1:2:
An HTML5 DOCTYPE was found. HTML5 (sometimes called just
HTML) is in a constant state of flux. While many parts of
HTML5 are considered stable and safe to use, there are parts
that are not stable or that may not be well supported by
browsers. When using HTML5, be sure to understand the
potential problems when using parts and features that may
not be stable (and thus may change in the future) or that
may not be widely supported. Visit
https://www.htmlvalidator.com/help.php?m=3&h=safetouse for
information about what is safe to use.

   2: <html lang="en">
   3: <head>
   4:   <link rel="canonical" href="https://www.iajo.org/iajo05/2021/n2021100.htm">

   5: <title>International Archives For The Jazz Organ (IAJO) - New Releases n2021100</title>
-------------||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

[CSE] Warning number 2 in line 5:8:
This document's title is 72 characters and may be too long.
A good title is important to your search engine rankings and
listings. Optimal page title length is 5-15 words and no
more than 60 characters (Google typically displays the first
50-60 characters but it's a good idea to keep titles under
55 characters so they display properly most of the time).
The title should contain relevant and descriptive phrases
and/or relevant keywords and search terms while also
remaining human-readable. If possible, use important
keywords at the very beginning of the title. The title is:
"International Archives For The Jazz Organ (IAJO) - New
Releases n2021100".

   5: <title>International Archives For The Jazz Organ (IAJO) - New Releases n2021100</title>
-------|||||

[CSE] Message number 3 in line 5:2:
Tip - A good title is important for search engine listings.
Try to use keywords and search terms in the title but keep
it readable and not too long. Don't just stuff keywords in
the title. The first words in the title are more likely to
result in higher rankings than subsequent words, so use
important keywords at the very beginning when reasonable.
The title should also be something that a user will want to
click on when it's listed on a search results page. 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 one of the first tags inside the
"head" section (but after any meta charset or viewport
tags).

   5: <title>International Archives For The Jazz Organ (IAJO) - New Releases n2021100</title>
-------------||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

[CSE] Message number 4 in line 5:8:
This document's title contains 11 words. It may be
inadequate for search engine purposes. A good title is
important to your search engine rankings and listings.
Optimal page title length is 5-15 words and no more than 60
characters (Google typically displays the first 50-60
characters but it's a good idea to keep titles under 55
characters so they display properly most of the time). The
title should contain relevant and descriptive phrases and/or
relevant keywords and search terms while also remaining
human-readable. If possible, use important keywords at the
very beginning of the title.

   6: <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
   7: <meta name="Robots" content="follow">
   8: <meta name="Author" content="Jürgen Wolf">

   9: <meta name="Publisher" content="International Archives For The Jazz Organ">
------------------|||||||||

[CSE] Warning number 3 in line 9:13:
The name "Publisher" specified by the "name" attribute is
not a recognized metadata name. Visit
https://www.w3.org/TR/html51/document-metadata.html#standard
-metadata-names and
https://wiki.whatwg.org/wiki/MetaExtensions for more
information.

  10: <meta name="Copyright" content="Jürgen Wolf Köln/Germany">
------------------|||||||||

[CSE] Warning number 4 in line 10:13:
Remove this meta tag and use one or more of these metadata
names instead: "dcterms.dateCopyrighted" for the date of the
copyright (like <meta name="dcterms.dateCopyrighted"
content="2014">), "dcterms.rights" for information about the
rights held in and over the resource (like <meta
name="dcterms.rights" content="statement or information
about copyright">), and/or "dcterms.rightsHolder" to specify
the person or organization owning or managing the rights
(like <meta name="dcterms.rightsHolder" content="ABCXYZ
Corp">). Furthermore, "Copyright" is not a
standards-compliant metadata name. Visit
https://www.w3.org/TR/html51/document-metadata.html#standard
-metadata-names and
https://wiki.whatwg.org/wiki/MetaExtensions for more
information.

  11: <meta name="Keywords" content="organ, Hammond organ, jazz, jazzorgan, organ players, archives, downbeat poll, jazz organ scene, jazz links, jazz on the church organ, jazz organ, gig dates, galleries">
------------------||||||||

[CSE] Warning number 5 in line 11:13:
The keywords meta tag is generally not recommended nowadays
because it is seldom (if ever) used and might even be
considered an indicator of spam. Consider removing this
keywords meta tag.

  12: <meta name="Description" content="Informations on jazz organ, organ players, their records, new releases, the jazz organ scene worldwide, articles about the jazz organ, jazz links, gig dates, jazz organ galleries">
----------------------------------------||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

[CSE] Message number 5 in line 12:35:
This description meta tag contains 8 commas. Some search
engines may think this indicates a keyword list, consider it
spam, and penalize your listing. We recommend using no more
than three commas in the description meta tag.

  13: <meta name="Page-topic" content="Jazz, Organ">
------------------||||||||||

[CSE] Warning number 6 in line 13:13:
The name "Page-topic" specified by the "name" attribute is
not a standard metadata name and is generally useless. This
was probably a proprietary meta tag that was once supported
by a search engine. It is recommended that this tag be
removed. Visit
https://www.w3.org/TR/html51/document-metadata.html#standard
-metadata-names and
https://wiki.whatwg.org/wiki/MetaExtensions for more
information.

  14: <meta name="Audience" content="Jazz fans">
  15: <link rel=stylesheet type="text/css" href="../../iajo1.css">
  16: <link rel=stylesheet type="text/css" href="../../iajo2.css">

  17: <link rel="icon" type="image/png" sizes="48x48" href="../../iajoicon.png">
----------------------------------------|||||

[CSE] Message number 6 in line 17:35:
[123] The HTML5 "sizes" attribute for "link" was used. Some
browsers may not support this attribute. This message is
displayed only once.

  18: </head>
  19: 
  20: <body>
  21: 
  22: <div id="head">
  23: 

  24: <a href="../../iajofram.htm"><img src="../../iajologg.gif" id="headlogo" alt="IAJOLOGO"></a>
------------------------------------|||

[CSE] Message number 7 in line 24:31:
Image searches can be a significant source of visitors and
traffic. Therefore, try to use keywords when naming images,
and separate keywords with hyphens (not underscores). This
message is displayed only once.

  24: <a href="../../iajofram.htm"><img src="../../iajologg.gif" id="headlogo" alt="IAJOLOGO"></a>
------------------------------------|||

[CSE] Message number 8 in line 24:31:
It is recommended that the "height" and "width" attributes
be used with the "img" element so browsers can leave the
correct amount of space for them while downloading the image
(which can take more time on mobile networks and devices).
This will also prevent issues and annoyances due to reflow
when the image becomes available or if image downloading is
disabled. This message is displayed up to 5 times.

  24: <a href="../../iajofram.htm"><img src="../../iajologg.gif" id="headlogo" alt="IAJOLOGO"></a>
------------------------------------|||

[CSE] Message number 9 in line 24:31:
[7] Ensure that the "img" element is rarely, if ever, used
as a layout tool. Always use CSS for layout and positioning.
For example, do not use "img" elements to display
transparent images which rarely convey meaning and rarely
add anything useful to the document. This message is
displayed only once.

  24: <a href="../../iajofram.htm"><img src="../../iajologg.gif" id="headlogo" alt="IAJOLOGO"></a>
---------------------------------------------||||||||||||||||||

[CSE] Message number 10 in line 24:40:
[117] Both "height" and "width" attributes should be used
with the "img" element. Recommend height="200" and
width="200" for this image. Using these attributes generally
result in faster and smoother (less jumpy) rendering. Using
them is also considered to be good style.

  24: <a href="../../iajofram.htm"><img src="../../iajologg.gif" id="headlogo" alt="IAJOLOGO"></a>
---------------------------------------------||||||||||||||||||

[CSE] Message number 11 in line 24:40:
GIF images are well supported in today's browsers but so are
PNG images, which are, in many cases, superior to GIF
because PNG images can support more colors, better
transparency, and better compression (smaller file sizes).
However, PNG does not support animation and may suffer from
CSS color matching issues (visit
https://www.htmlvalidator.com/CSEForum/viewtopic.php?f=3&t=1
583). Consider using PNG images instead of GIF images if
animation is not required. JPG is usually best for
photographs. This message is displayed only once. There may
be other GIF images specified in this document.

  25: 
  26: <div id="headtext">New Releases 2021</div>
  27: <div id="head_line"></div>
  28: </div>
  29: <p>

  30: &nbsp;<br>
-------------||

[CSE] Message number 12 in line 30:8:
Ensure that the "br" element is used only for line breaks
that are actually part of the content, as in poems or
addresses. For presentational formatting, CSS should be
used. This message is displayed only once.

  31: &nbsp;<br>
  32: </p>
  33: 
  34: <div class="center1">
  35: <table style="width:600px">

  36: <tr>
-------||

[CSE] Message number 13 in line 36:2:
[132] Assuming an omitted "tbody" start tag before this
start tag. For better structure, it is recommended to
explicitly start all "tbody" elements with an explicit start
tag. The omitted "tbody" start tag should probably be placed
right before this start tag. This message is displayed up to
3 times.

  37: 
  38: <td class="pictblock_left">

  39: <img src="n2021100.jpg" alt="cover picture" class="pict_animation" width=150 height=150>
-------------------------------------------------------------------------------|||

[CSE] Warning number 7 in line 39:74:
[117] The value for the "width" attribute is "150" but the
actual image width is "450". The user agent/browser may
resize the image but this may not be wanted. Usually the
actual image width is used.

  39: <img src="n2021100.jpg" alt="cover picture" class="pict_animation" width=150 height=150>
------------------------------------------------------------------------------------------|||

[CSE] Warning number 8 in line 39:85:
[117] The value for the "height" attribute is "150" but the
actual image height is "450". The user agent/browser may
resize the image but this may not be wanted. Usually the
actual image height is used.

  40: <p style="color:orange">To enlarge the image, touch it!</p>
----------------|||||

[CSE] Message number 14 in line 40:11:
When a foreground color is defined, consider also defining a
background color (by using the "background" or
"background-color" property). This helps to avoid conflict
with user-defined style sheets and to improve accessibility.
This message is displayed up to 5 times.

  41: </td>
  42: <td class="textblock_right">
  43: <div class="artists_name">Frank Hammond:<br>Turtle Walk</div>
  44: <table class="table2_general">

  45: <tr>
-------||

[CSE] Message number 15 in line 45:2:
[132] Assuming an omitted "tbody" start tag before this
start tag. For better structure, it is recommended to
explicitly start all "tbody" elements with an explicit start
tag. The omitted "tbody" start tag should probably be placed
right before this start tag. This message is displayed up to
3 times.

  46: <td class="table2_left">Label</td>
  47: <td class="table2_right">PlayCab</td>
  48: </tr>
  49: <tr>
  50: <td class="table2_left">recorded</td>
  51: <td class="table2_right">
  52: 
  53: </td>
  54: </tr>
  55: <tr>
  56: <td class="table2_left">online distribution</td>
  57: <td class="table2_right">
  58: 
  59: </td>
  60: </tr>
  61: </table>
  62: 
  63: <p>&nbsp;</p>
  64: 
  65: <div class="center1">

  66: <table>
-------|||||

[CSE] Message number 16 in line 66:2:
With "table" elements, consider using the "width" CSS
property to specify the table width (by assigning a class
with the "class" attribute (preferred) or by using the
"style" attribute). Specifying the width is considered to be
good style and may cause the table and page to render
faster. Do not use the "width" attribute because it is not
valid for this document type. This message is displayed up
to 3 times.

  67: <tr>
-------||

[CSE] Message number 17 in line 67:2:
[132] Assuming an omitted "tbody" start tag before this
start tag. For better structure, it is recommended to
explicitly start all "tbody" elements with an explicit start
tag. The omitted "tbody" start tag should probably be placed
right before this start tag. This message is displayed up to
3 times.

  68: <td class="artists_block">
  69: Credits
  70: </td>
  71: </tr>
  72: </table>
  73: </div>
  74: 
  75: <table class="table2_general">
  76: <tr>
  77: <td class="table2_left"><a href="../../iajo04/italy/angelo.htm">Franco Angelozzi</a></td>
  78: <td class="table2_right">organ</td>
  79: </tr>
  80: <tr>
  81: <td class="table2_left">Luca Mongia</td>
  82: <td class="table2_right">guitar</td>
  83: </tr>
  84: <tr>
  85: <td class="table2_left">Emanuele Carulli</td>
  86: <td class="table2_right">bass</td>
  87: </tr>
  88: <tr>
  89: <td class="table2_left">Andrea Marcone</td>
  90: <td class="table2_right">drums</td>
  91: </tr>
  92: </table>
  93: <p>&nbsp;</p>
  94: 
  95: <div class="center1">

  96: <table>
-------|||||

[CSE] Message number 18 in line 96:2:
With "table" elements, consider using the "width" CSS
property to specify the table width (by assigning a class
with the "class" attribute (preferred) or by using the
"style" attribute). Specifying the width is considered to be
good style and may cause the table and page to render
faster. Do not use the "width" attribute because it is not
valid for this document type. This message is displayed up
to 3 times.

  97: <tr>
  98: <td class="artists_block">
  99: Track List
 100: </td>
 101: </tr>
 102: </table>
 103: </div>
 104: <table class="table2_general">
 105: <tr>
 106: <td class="table2_review">
 107: 01: Manufunk<br>
 108: 02: Ginevra<br>
 109: 03: Sweetest Touch<br>
 110: 04: Shes My Reason<br>
 111: 05: Turtle Walk<br>
 112: 06: Pol-Pett<br>
 113: 07: My Poisoing<br>
 114: 08: Back To Myself<br>
 115: 09: The Thief<br>
 116: 10: Jolina<br>
 117: 11: Remember When<br>
 118: 12: Tribal Mr.F<br>
 119: </td>
 120: </tr>
 121: </table>
 122: <p>&nbsp;</p>
 123: 
 124: <div class="center1">

 125: <table>
-------|||||

[CSE] Message number 19 in line 125:2:
With "table" elements, consider using the "width" CSS
property to specify the table width (by assigning a class
with the "class" attribute (preferred) or by using the
"style" attribute). Specifying the width is considered to be
good style and may cause the table and page to render
faster. Do not use the "width" attribute because it is not
valid for this document type. This message is displayed up
to 3 times.

 126: <tr>
 127: <td class="artists_block">
 128: Review
 129: </td>
 130: </tr>
 131: </table>
 132: </div>
 133: <table class="table2_general">
 134: <tr>
 135: <td class="table2_review">
 136: n/a
 137: </td>
 138: </tr>
 139: <tr>
 140: <td class="table2_stars">
 141: 
 142: </td>
 143: </tr>
 144: </table>
 145: </td>
 146: 
 147: </tr>
 148: </table>
 149: </div>
 150: 
 151: <p>&nbsp;</p>
 152: 
 153: <div class="center1">
 154: <div class="artists_block" style="width:590px">
 155: Sound Samples
 156: </div>
 157: </div>
 158: 
 159: <div class="center1">
 160: <table class="artist_samples_general">
 161: <tr>
 162: <td class="artists_samples_left">
 163: <img src="../../mp3/mp3logo2.gif" width=50 height=50 alt="MP3">
 164: </td>
 165: <td class="artists_samples_right">
 166: n/a
 167: </td>
 168: <td class="artists_samples_left">

 169: <a href="https://open.spotify.com/album/38oLHPVz3nsAWo1IQDCmkK" target="_blank" rel="noopener"><img src="../spotify.gif" width=50 height=50 alt="Spotify"></a></td>
-------------------------------------------------------------------------------------------------------------------------------------||

[CSE] Warning number 9 in line 169:128:
[117] The value for the "width" attribute is "50" but the
actual image width is "225". The user agent/browser may
resize the image but this may not be wanted. Usually the
actual image width is used.

 169: <a href="https://open.spotify.com/album/38oLHPVz3nsAWo1IQDCmkK" target="_blank" rel="noopener"><img src="../spotify.gif" width=50 height=50 alt="Spotify"></a></td>
-----------------------------------------------------------------------------------------------------------------------------------------------||

[CSE] Warning number 10 in line 169:138:
[117] The value for the "height" attribute is "50" but the
actual image height is "225". The user agent/browser may
resize the image but this may not be wanted. Usually the
actual image height is used.

 169: <a href="https://open.spotify.com/album/38oLHPVz3nsAWo1IQDCmkK" target="_blank" rel="noopener"><img src="../spotify.gif" width=50 height=50 alt="Spotify"></a></td>
------------------------------------------------------------------------------||||||

[CSE] Message number 20 in line 169:73:
Pop-up windows and changing the current window may cause
user confusion. Also, some less-capable mobile devices
cannot support more than one window, and trying to open more
than one window will have unpredictable results. Keep this
in mind, especially when targeting less-capable mobile
devices. This message is displayed only once.

 170: </td>
-------|||

[CSE] Error number 1 in line 170:2:
The end tag for "td" was found, but all "td" start tags
already have end tags (or there is a nesting error). The
next expected end tag is </tr>, which was started in line
161, column 2.

 171: <td class="artists_samples_right">
 172: complete album:<br>Frank Hammond - Turtle Walk
 173: </td>
 174: </tr>
 175: </table>
 176: </div>
 177: 
 178: <p>
 179: &nbsp;<br>
 180: &nbsp;<br>
 181: </p>
 182: <p style="text-align:center;">
 183: <a href="newr2021.htm" class="backbutton">Back</a>
 184: <br>&nbsp;<br>

 185: <b><i>If you don't see the left hand menu,<br>please go back to the homepage.</i></b><br>
-------|

[CSE] Message number 21 in line 185:2:
Ensure that the "b" element is used appropriately and as a
last resort when no other element is more appropriate. In
particular, headings should use the "h1" to "h6" elements,
stress emphasis should use the "em" element, importance
should be denoted with the "strong" element, and text marked
or highlighted should use the "mark" element. This message
is displayed only once.

 185: <b><i>If you don't see the left hand menu,<br>please go back to the homepage.</i></b><br>
----------|

[CSE] Message number 22 in line 185:5:
The "em" element (for emphasized text) or the "cite" element
(for citations) or the "dfn" element (for the defining
instance of a term) may be more appropriate than the "i"
element. The "i" element is often used when the "em" element
would be more appropriate. Use the "i" element for text in
an alternate voice or mood. If only italic text is desired,
then use CSS. This message is displayed only once.

 186: <a href="../../iajo0.htm" class="backbutton">Back to the homepage</a>
 187: &nbsp;<br>
 188: &nbsp;<br>
 189: </p>
 190: 
 191: </body>
 192: </html>

[CSE] Comment number 1:
[73] Section 508 accessibility checking is off.

[CSE] Comment number 2:
[73] WCAG 1.0 accessibility checking is off.

[CSE] Comment number 3:
[73] WCAG 2.0 accessibility checking is off.

[CSE] Comment number 4:
Accessibility checking is off. 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
mobile phones and PDAs. An accessible web site makes good
business sense (and possibly good legal sense as well) and
may even improve search engine rankings. You can enable or
disable accessibility checking in the Validator Engine
Options.

[CSE] Comment number 5:
If you want to improve your website's search engine
rankings, visit https://www.htmlvalidator.com/seo.html

[CSE] Comment number 6:
Keyword density: Organ (13x - 7.8%), Jazz (11x - 6.6%), Back
(4x - 2.4%), Hammond (3x - 1.8%), New (3x - 1.8%), Releases
(3x - 1.8%), Turtle (3x - 1.8%), Walk (3x - 1.8%), Archives
(2x - 1.2%), dates (2x - 1.2%), Frank (2x - 1.2%), galleries
(2x - 1.2%), gig (2x - 1.2%), homepage (2x - 1.2%), links
(2x - 1.2%), n (2x - 1.2%), players (2x - 1.2%), scene (2x -
1.2%), touch (2x - 1.2%), 01 (1x - 0.6%). Remember: Don't
write SEO optimized content. Write for people, which is what
search engines want. List limited to first 20 unique words.
27 words excluded.

[CSE] Comment number 7:
HTML5 document detected.

[CSE] Comment number 8:
Editing Tip: This document was specified as utf-8 encoded.
Editing documents with the wrong encoding may cause document
corruption. Ensure that any editor used to edit a document
properly supports the document's encoding and properly loads
it with the correct encoding. CSE HTML Validator's editor
supports UTF-8 and other common encodings.

[CSE] Comment number 9:
Use CSS class names that describe the nature of the content
instead of names that describe the presentation of the
content. For example, don't use class="red" or class="bold",
instead use something like class="important".

[CSE] Comment number 10:
[133] Mobility Tip #4 - Always use valid, well structured,
logical, terse, meaningful, and efficient markup, with
proper headings and sub-headings. Check the markup for
errors and for possible improvements (like with CSE HTML
Validator).

[CSE] Comment number 11:
Number of "a" links: 5, of which 0 (0.0%) have
rel="nofollow". Use rel="nofollow" to tell search engines
not to follow the link and tell Google not to transfer
PageRank or anchor text across the link. Use rel="nofollow"
for untrusted content, paid links, and crawl prioritization.
Visit https://support.google.com/webmasters/answer/96569 for
more information.

[CSE] Comment number 12:
No "h1" or "h2" heading element was found. Using these
heading elments (especially "h1" and preferably with your
best keywords) to describe sub-topics of a page may improve
search engine rankings. If "h1" text is too large then you
can reduce its size with CSS.

[CSE] Comment number 13:
[113] Random Search Engine Tip #14 - MAINTAIN CONTENT
QUALITY. Provide fresh, unique, original, and relevant
content from time to time to keep your site content from
"decaying". Avoid "thin content"; most content should be at
least 600-700 words.

[CSE] Comment number 14:
This document contains tables nested to 2 levels. Too many
nested tables may cause significant performance problems and
may reduce the ability of some mobile browsers to render and
display the document properly. This message appears when
there are nested tables more than 1 level deep.

[CSE] Comment number 15:
0.00s, 1 error, 10 warnings, 22 messages, 15 validator
comments, 192 lines, 130 elements (with 89 end tags), 0
document comments, 11 character references, 167 words spell
checked (0 in comments).

--------------------------------------------------

<html> (2)
| <head> (3)
| | <link /> (4)
| | <title> (5) </title> (5)
| | <meta /> (6)
| | <meta /> (7)
| | <meta /> (8)
| | <meta /> (9)
| | <meta /> (10)
| | <meta /> (11)
| | <meta /> (12)
| | <meta /> (13)
| | <meta /> (14)
| | <link /> (15)
| | <link /> (16)
| | <link /> (17)
| </head> (18)
| <body> (20)
| | <div> (22)
| | | <a> (24)
| | | | <img /> (24)
| | | </a> (24)
| | | <div> (26) </div> (26)
| | | <div> (27) </div> (27)
| | </div> (28)
| | <p> (29)
| | | <br /> (30)
| | | <br /> (31)
| | </p> (32)
| | <div> (34)
| | | <table> (35)
| | | | <tbody> (i)
| | | | | <tr> (36)
| | | | | | <td> (38)
| | | | | | | <img /> (39)
| | | | | | | <p> (40) </p> (40)
| | | | | | </td> (41)
| | | | | | <td> (42)
| | | | | | | <div> (43)
| | | | | | | | <br /> (43)
| | | | | | | </div> (43)
| | | | | | | <table> (44)
| | | | | | | | <tbody> (i)
| | | | | | | | | <tr> (45)
| | | | | | | | | | <td> (46) </td> (46)
| | | | | | | | | | <td> (47) </td> (47)
| | | | | | | | | </tr> (48)
| | | | | | | | | <tr> (49)
| | | | | | | | | | <td> (50) </td> (50)
| | | | | | | | | | <td> (51) </td> (53)
| | | | | | | | | </tr> (54)
| | | | | | | | | <tr> (55)
| | | | | | | | | | <td> (56) </td> (56)
| | | | | | | | | | <td> (57) </td> (59)
| | | | | | | | | </tr> (60)
| | | | | | | | </tbody> (i)
| | | | | | | </table> (61)
| | | | | | | <p> (63) </p> (63)
| | | | | | | <div> (65)
| | | | | | | | <table> (66)
| | | | | | | | | <tbody> (i)
| | | | | | | | | | <tr> (67)
| | | | | | | | | | | <td> (68) </td> (70)
| | | | | | | | | | </tr> (71)
| | | | | | | | | </tbody> (i)
| | | | | | | | </table> (72)
| | | | | | | </div> (73)
| | | | | | | <table> (75)
| | | | | | | | <tbody> (i)
| | | | | | | | | <tr> (76)
| | | | | | | | | | <td> (77)
| | | | | | | | | | | <a> (77) </a> (77)
| | | | | | | | | | </td> (77)
| | | | | | | | | | <td> (78) </td> (78)
| | | | | | | | | </tr> (79)
| | | | | | | | | <tr> (80)
| | | | | | | | | | <td> (81) </td> (81)
| | | | | | | | | | <td> (82) </td> (82)
| | | | | | | | | </tr> (83)
| | | | | | | | | <tr> (84)
| | | | | | | | | | <td> (85) </td> (85)
| | | | | | | | | | <td> (86) </td> (86)
| | | | | | | | | </tr> (87)
| | | | | | | | | <tr> (88)
| | | | | | | | | | <td> (89) </td> (89)
| | | | | | | | | | <td> (90) </td> (90)
| | | | | | | | | </tr> (91)
| | | | | | | | </tbody> (i)
| | | | | | | </table> (92)
| | | | | | | <p> (93) </p> (93)
| | | | | | | <div> (95)
| | | | | | | | <table> (96)
| | | | | | | | | <tbody> (i)
| | | | | | | | | | <tr> (97)
| | | | | | | | | | | <td> (98) </td> (100)
| | | | | | | | | | </tr> (101)
| | | | | | | | | </tbody> (i)
| | | | | | | | </table> (102)
| | | | | | | </div> (103)
| | | | | | | <table> (104)
| | | | | | | | <tbody> (i)
| | | | | | | | | <tr> (105)
| | | | | | | | | | <td> (106)
| | | | | | | | | | | <br /> (107)
| | | | | | | | | | | <br /> (108)
| | | | | | | | | | | <br /> (109)
| | | | | | | | | | | <br /> (110)
| | | | | | | | | | | <br /> (111)
| | | | | | | | | | | <br /> (112)
| | | | | | | | | | | <br /> (113)
| | | | | | | | | | | <br /> (114)
| | | | | | | | | | | <br /> (115)
| | | | | | | | | | | <br /> (116)
| | | | | | | | | | | <br /> (117)
| | | | | | | | | | | <br /> (118)
| | | | | | | | | | </td> (119)
| | | | | | | | | </tr> (120)
| | | | | | | | </tbody> (i)
| | | | | | | </table> (121)
| | | | | | | <p> (122) </p> (122)
| | | | | | | <div> (124)
| | | | | | | | <table> (125)
| | | | | | | | | <tbody> (i)
| | | | | | | | | | <tr> (126)
| | | | | | | | | | | <td> (127) </td> (129)
| | | | | | | | | | </tr> (130)
| | | | | | | | | </tbody> (i)
| | | | | | | | </table> (131)
| | | | | | | </div> (132)
| | | | | | | <table> (133)
| | | | | | | | <tbody> (i)
| | | | | | | | | <tr> (134)
| | | | | | | | | | <td> (135) </td> (137)
| | | | | | | | | </tr> (138)
| | | | | | | | | <tr> (139)
| | | | | | | | | | <td> (140) </td> (142)
| | | | | | | | | </tr> (143)
| | | | | | | | </tbody> (i)
| | | | | | | </table> (144)
| | | | | | </td> (145)
| | | | | </tr> (147)
| | | | </tbody> (i)
| | | </table> (148)
| | </div> (149)
| | <p> (151) </p> (151)
| | <div> (153)
| | | <div> (154) </div> (156)
| | </div> (157)
| | <div> (159)
| | | <table> (160)
| | | | <tbody> (i)
| | | | | <tr> (161)
| | | | | | <td> (162)
| | | | | | | <img /> (163)
| | | | | | </td> (164)
| | | | | | <td> (165) </td> (167)
| | | | | | <td> (168)
| | | | | | | <a> (169)
| | | | | | | | <img /> (169)
| | | | | | | </a> (169)
| | | | | | </td> (169)
| | | | | | <td> (171)
| | | | | | | <br /> (172)
| | | | | | </td> (173)
| | | | | </tr> (174)
| | | | </tbody> (i)
| | | </table> (175)
| | </div> (176)
| | <p> (178)
| | | <br /> (179)
| | | <br /> (180)
| | </p> (181)
| | <p> (182)
| | | <a> (183) </a> (183)
| | | <br /> (184)
| | | <br /> (184)
| | | <b> (185)
| | | | <i> (185)
| | | | | <br /> (185)
| | | | </i> (185)
| | | </b> (185)
| | | <br /> (185)
| | | <a> (186) </a> (186)
| | | <br /> (187)
| | | <br /> (188)
| | </p> (189)
| </body> (191)
</html> (192)
