Error: Stray start tag script.

David B. STALKER wrote:

It would be helpful if Mayayana were to post a link to the URL of his
friend's website - simply so that others could actually SEE the mess
which is his coding!

...but YOU wouldn't understand any of it.

I've learned much by studying the coding instructions posted he-

www. tekrider. net

You haven't learned anything about HTML from there. There is nothing on my
site that relates to this thread. Knock off your damn stalking.

--
-bts

On 06/01/2019 22:14, Beauregard T. Shagnasty wrote:
David B. Private Investigator, wrote:

It would be helpful if Mayayana were to post a link to the URL of his
friend's website - simply so that others could actually SEE the mess
which is his coding!

..but YOU wouldn't understand any of it.

Perhaps so - but other folk might!

I'd still like to take a look anyway.

I've learned much by studying the coding instructions posted he-

www. tekrider. net

You haven't learned anything about HTML from there. There is nothing on my
site that relates to this thread. Knock off your damn stalking.

The other day Mayayana wrote:-

Maybe because it's outside the body tag? But I'm
not sure if they consider that an error. It looks
like *your webhost injected* and it could just
be removed. The rest of your code is very simple
and clean. (Though I don't know why you need
open graph markup.)
[....]
It looks like you're hosting on GoDaddy. You might
want to consider getting a more professional host
*that doesn't inject crap into your pages*.

Message-ID:

http://al.howardknight.net/msgid.cgi?ID=154681544400

=

Thinking back to that 'code' I found on YOUR website, BTS, might it have
been GoDaddy (that's YOUR host!) which injected the 'code' which I found
onto your website page?

I don't understand why YOU aren't curious about what happened.

=

Please don't shoot me - I'm just the messenger! ;-)

--
David B.

David B. STALKER wrote:

On 06/01/2019 22:14, Beauregard T. Shagnasty wrote:
David B. STALKER wrote:
It would be helpful if Mayayana were to post a link to the URL of his
friend's website - simply so that others could actually SEE the mess
which is his coding!

..but YOU wouldn't understand any of it.

Perhaps so - but other folk might

I'd still like to take a look anyway.

At what? You don't understand coding AT ALL.

I've learned much by studying the coding instructions posted he-

www. tekrider. net

You haven't learned anything about HTML from there. There is nothing on
my site that relates to this thread. Knock off your damn stalking.

The other day Mayayana wrote:-

It looks like you're hosting on GoDaddy. You might
want to consider getting a more professional host *that doesn't inject
crap into your pages*.

Thinking back to that 'code' I found on YOUR website, BTS, might it have
been GoDaddy (that's YOUR host!)

GoDaddy *IS NOT* my web host. You know nothing about web sites other than
what your browser displays to you. Think back to ibuoy.co.uk - your
miserable failed attempt at writing your own site.

which injected the 'code' which I found onto your website page?

GoDaddy injects nothing, and does not have the capability to do so.

I don't understand why YOU aren't curious about what happened.

I'm not curious because I KNOW you are a stalker.

Please don't shoot me - I'm just the messenger! ;-)

No, you are a *STALKER*.

Read up on this:
https://validator.w3.org/nu/?doc=htt...g%2F2018%2F12%
2F08%2Fvxer-a-profile%2F

If you think validation is so important, why don't you fix all YOUR errors
before you attempt to tell others to fix theirs.

--
-bts

On Sat, 5 Jan 2019 22:34:52 -0500, "Mayayana"
wrote:

"Joy Beeson" wrote

| On the other hand, why do you care about W3C?
|
| Because getting rid of errors that don't matter makes it much easier
| to find errors that do matter.

That doesn't make sense. If they don't matter then
they don't affect anything.

They clutter things up when you are looking for the other errors.

[snip]

Sincerely,

Gene Wirchenko

On 07/01/2019 00:02, Beauregard T. Shagnasty wrote:
David B. Investigator extraordinaire, wrote:

On 06/01/2019 22:14, Beauregard T. Shagnasty wrote:
David B. STALKER wrote:
It would be helpful if Mayayana were to post a link to the URL of his
friend's website - simply so that others could actually SEE the mess
which is his coding!

..but YOU wouldn't understand any of it.

Perhaps so - but other folk might

I'd still like to take a look anyway.

At what? You don't understand coding AT ALL.

Mahayana's web page! I've learned a great deal! :-)

I've learned much by studying the coding instructions posted he-

www. tekrider. net

You haven't learned anything about HTML from there. There is nothing on
my site that relates to this thread. Knock off your damn stalking.

The other day Mayayana wrote:-

It looks like you're hosting on GoDaddy. You might
want to consider getting a more professional host *that doesn't inject
crap into your pages*.

Thinking back to that 'code' I found on YOUR website, BTS, might it have
been GoDaddy (that's YOUR host!)

GoDaddy *IS NOT* my web host. You know nothing about web sites other than
what your browser displays to you. Think back to ibuoy.co.uk - your
miserable failed attempt at writing your own site.

Huh? Then WHOIS your web host????????????

Domain Name: TEKRIDER.NET
Registry Domain ID: 1447011823_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2018-04-04T15:49:07Z
Creation Date: 2008-04-10T14:01:36Z
Registry Expiry Date: 2020-04-10T14:01:36Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone: 480-624-2505
Domain Status: clientDeleteProhibited
https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited
https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited
https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited
https://icann.org/epp#clientUpdateProhibited
Name Server: NS1.GENWEBSERVER.COM
Name Server: NS2.GENWEBSERVER.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form:
https://www.icann.org/wicf/
Last update of whois database: 2019-01-07T10:58:41Z


which injected the 'code' which I found onto your website page?

GoDaddy injects nothing, and does not have the capability to do so.

I don't understand why YOU aren't curious about what happened.

I'm not curious because I KNOW you are a stalker.

Please don't shoot me - I'm just the messenger! ;-)

No, you are a *STALKER*.

Read up on this:
https://validator.w3.org/nu/?doc=htt...g%2F2018%2F12%
2F08%2Fvxer-a-profile%2F

I will.

If you think validation is so important, why don't you fix all YOUR errors
before you attempt to tell others to fix theirs.

I'm not telling anyone anything! Have you been drinking?
--
David B.

On 07/01/2019 00:02, Beauregard T. Shagnasty suggested:

Read up on this:
https://validator.w3.org/nu/?doc=htt...g%2F2018%2F12%
2F08%2Fvxer-a-profile%2F

I actually went here as that link is borken!

https://validator.w3.org/nu/?doc=htt...-profile%2F%3E

=

I did! My URL seems to work just fine! :-)

https://vxer.home.blog/2018/12/08/vxer-a-profile/

Even though THIS address does NOT! :-(

https://vxer.home.blog/2018/12/08/vxer-a-profile/

IO Error: HTTP resource not retrievable. The HTTP status from the remote
server was: 404.

https://vxer.home.blog/2018/12/08/vxer-a-profile/%3E

There's more to this than needed to steer a narrowboat!

--
David B.

David B. STALKER wrote:

On 07/01/2019 00:02, Beauregard T. Shagnasty wrote:
David B. STALKER wrote:
Thinking back to that 'code' I found on YOUR website, BTS, might it
have been GoDaddy (that's YOUR host!)

GoDaddy *IS NOT* my web host. You know nothing about web sites other
than what your browser displays to you. Think back to ibuoy.co.uk -
your miserable failed attempt at writing your own site.

Huh? Then WHOIS your web host????????????

GoDaddy is my domain name registrar, NOT my web host. There's no point
trying to explain it to you because even all these years of you stalking
people's web sites, you wouldn't understand it.

I'm not telling anyone anything! Have you been drinking?

No, that's your practice.

--
-bts

David B. STALKER wrote:

On 07/01/2019 00:02, Beauregard T. Shagnasty suggested:

Read up on this:
https://validator.w3.org/nu/?doc=htt...e.blog%2F2018%
2F12%
2F08%2Fvxer-a-profile%2F

I actually went here as that link is borken!

Mo, it is not. It's simply wrapped and you weren't smart enough to figure
that out.

I did! My URL seems to work just fine! :-)

What about the nearly fifty errors on your page?

--
-bts

"Gene Wirchenko" wrote

| That doesn't make sense. If they don't matter then
| they don't affect anything.
|
| They clutter things up when you are looking for the other errors.
|

Clutter? Look at any major, commercial website.
Some pages are over 5 MB, with mostly unnecessary
javascript pulled in from external sources. Most also
use automated software that inserts extreme nesting,
numerous empty DIVs, and often far more CSS than
webpage content. Those pages often break in older
browsers or with script disabled. What good is it if
W3C says they have no mistakes?

Do you write code from scratch? If not you probably
have a lot of clutter. Dreamweaver? jquery? Clutter.

Last week I was looking for some kind of code to
format JSON. I found lots of webpages that would do
it. Most were using jquery, a gigantic javascript
wrapper for people who don't know how to write
script. After a lot of research I finally discovered
that I only needed one simple line of javascript in
a webpage to fornat JSON. It's built into the javascript
"engine" in browsers. That's ridiculous clutter, using
jquery to format JSON, but those webpages might
pass the W3C test.

My examples in the post above were meant to
illustrate that many things the W3C consider errors
have reasons. Changing them can sometimes break
a page. It's not always a case of overlooked errors.
For example, I don't use a DOCTYPE tag. W3C
considers that an error. But it's deliberate. It signals
quirks mode. If I use an HTML5 DOCTYPE tag then
every version of IE will render the page differently.
That means I'd need custom code for each version.
That's why so many webpages have spaghetti code
that reads like: !-- If IE7..... If IE8..... If IE9... etc

They're trying to be compliant and end up having to
write custom code to accommodate different browsers.

Joy provided a link to her own webpage. It's very
simple. I looks fine. No one even needs W3C to look for
errors because it's all very simple and clear. (Also,
Mozilla browsers show what they consider to be errors
in red in the source code view.)

Joy's page has several very real errors. /PP
An extra CENTER closing tag. An extra H4 closing tag.
And it has no CSS at all. Does that matter? I think
her page looks fine. And unlike most newspaper sites,
with 20px, triple-spaced text, her text displays at
my default preference because there's no CSS. So
I see a very civilized 13px verdana. Her page will
probably also look fine in any browser.
If it were me I'd fix those errors. They're easy to
find and easy to fix. And they're actual structural
errors. But the page does still work, because HTML
was designed that way. A browser is supposed to
do the best it can and not choke on errors.

I got curious and tested Wired's homepage and WashPo's
lead article. Wired had 274 errors. It's somewhat readable
for me. My error list would be blandness and everything
is too big. (The heading "MOST RECENT" is 7/16" high on
my screen! And what's with the all caps?) I also consider
serif text an error on computer screens. But that's just
my error list. At least the page is readable.
But I don't see why these sites don't check the userAgent
and only give giant text to phones. Why are they giving
phone webpages to desktops and laptops? Do they think so
littl of their own journalism that they expect it to be
read only by bored and self-conscious commuters, trying
to look busy on the bus to work?

On WashPo, W3C found 82 errors and then gave up
with an "unrecoverable error". That page looks very
good to me, except for the problem of giant text,
which forces me to view it with No Style if I want
to read very much.

(Though I should note that I'm blocking script,
so I don't see "errors" like intrusive popups, ads for
hemmorhoid cream, demands for subscriptions that
block the page, Facebook spyware iframes, videos
I didn't ask for, or the horror of modern webpages:
pointless slideshows that won't stop moving.

I even have CSS customized in Firefox and Pale
Moon to block obnoxious CSS like :before, :after, and
CSS animation. So such "error filled" webpages
still look readable and civilized to me.)

Many sites also do another thing I'd call an error:
They load CSS and images from another domain
unnecessarily. I often block external domains for
privacy and security reasons. The Web was designed
to maintain privacy between domains. That's why
cookies can only be read by the origin domain. That's
why 3rd-party cookies are actually a spyware cheat.
But loading ads from the likes of Doubleclick, and
trackers from the likes of scorecardresearch, has
become so common that webpages are now designed
to be composites of data and programming code from
multiple domains. No chance of the privacy that was
considered common sense when the Internet was
designed. Does the W3C complain about that?
Not that I know of. They're busy complaining about
people jaywalking on a country road, 18 miles from
civilization.

On 07/01/2019 13:29, Beauregard T. Shagnasty wrote:
David B. wrote:

On 07/01/2019 00:02, Beauregard T. Shagnasty suggested:

Read up on this:
https://validator.w3.org/nu/?doc=htt...e.blog%2F2018%
2F12%
2F08%2Fvxer-a-profile%2F

I actually went here as that link is broken!

https://validator.w3.org/nu/?doc=htt...-profile%2F%3E

No, it is not. It's simply wrapped and you weren't smart enough to figure
that out.

A man of your experience should be able to provide an UN-wrapped link.
If *I* can do it, so can you!

https://validator.w3.org/nu/?doc=htt...-profile%2F%3E

I did! My URL seems to work just fine! :-)

What about the nearly fifty errors on your page?

Huh? I see this:-

"Document checking not completed. The result cannot be determined due to
a non-document-error."

I'll provide an image if you advise which facility you will trust (and
view).

--
David B.

David B. wrote:

The other day Mayayana wrote:-

Â* Maybe because it's outside the body tag? But I'm
not sure if they consider that an error. It looks
like *your webhost injected* and it could just
be removed. The rest of your code is very simple
and clean. (Though I don't know why you need
open graph markup.)
[....]
Â* It looks like you're hosting on GoDaddy. You might
want to consider getting a more professional host
*that doesn't inject crap into your pages*.

Message-ID:

http://al.howardknight.net/msgid.cgi?ID=154681544400

=

Thinking back to that 'code' I found on YOUR website, BTS, might it have
been GoDaddy (that's YOUR host!) which injected the 'code' which I found
onto your website page?

I don't understand why YOU aren't curious about what happened.

=

Please don't shoot me - I'm just the messenger! ;-)

In that instance it was hosting script injection, but in yours with
techrider.net I'd bet the "injection" was the result of the *client*.
You most likely have some browser "security" plugin or Internet
"security" software running...

BTW: Domain Registrar != Hosting Company although *some* hosting
companies offer domain registration services.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

David B. STALKER wrote:

On 07/01/2019 13:29, Beauregard T. Shagnasty wrote:
What about the nearly fifty errors on your page?

Huh? I see this:-

"Document checking not completed. The result cannot be determined due to
a non-document-error."

I'll provide an image if you advise which facility you will trust (and
view).

You do not need to provide an image. The reason is simple. You inserted
the link in the validator and included the trailing "" but not the
starting one. The page has *47* errors. In addition, the page has 2 CSS
errors and *380* warnings.
http://jigsaw.w3.org/css-validator/

Man up and fix it.

--
-bts

On 07/01/2019 16:48, Jonathan N. Little wrote:
David B. wrote:

The other day Mayayana wrote:-

Â* Maybe because it's outside the body tag? But I'm
not sure if they consider that an error. It looks
like *your webhost injected* and it could just
be removed. The rest of your code is very simple
and clean. (Though I don't know why you need
open graph markup.)
[....]
Â* It looks like you're hosting on GoDaddy. You might
want to consider getting a more professional host
*that doesn't inject crap into your pages*.

Message-ID:

http://al.howardknight.net/msgid.cgi?ID=154681544400

=

Thinking back to that 'code' I found on YOUR website, BTS, might it have
been GoDaddy (that's YOUR host!) which injected the 'code' which I found
onto your website page?

I don't understand why YOU aren't curious about what happened.

=

Please don't shoot me - I'm just the messenger! ;-)

In that instance it was hosting script injection, but in yours with
techrider.net I'd bet the "injection" was the result of the *client*.
You most likely have some browser "security" plugin or Internet
"security" software running...

Anything is possible - but I wasn't aware of something being amiss with
my Apple iMac

BTW: Domain Registrar != Hosting Company although *some* hosting
companies offer domain registration services.

You are correct in sensing my confusion with this! I'd simply like to
understand. Can *YOU* fathom out who the 'web host' is?

This is what Virus Total tells me:-

www.tekrider.net domain information
Categories
Forcepoint ThreatSeeker uncategorized
Passive DNS Replication
Date resolved IP address
2018-12-09 192.251.238.3
Whois Lookup
Domain Name: TEKRIDER.NET
Registry Domain ID: 1447011823_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2018-04-04T15:49:07Z
Creation Date: 2008-04-10T14:01:36Z
Registry Expiry Date: 2020-04-10T14:01:36Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone: 480-624-2505
Domain Status: clientDeleteProhibited
https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited
https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited
https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited
https://icann.org/epp#clientUpdateProhibited
Name Server: NS1.GENWEBSERVER.COM
Name Server: NS2.GENWEBSERVER.COM
DNSSEC: unsigned
Updated Date: 2018-04-04T15:49:06Z
Registrar Registration Expiration Date: 2020-04-10T14:01:36Z
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited
http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited
http://www.icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited
http://www.icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited
http://www.icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Country: US
Registrant Email:
Registry Admin ID: Not Available From Registry
Admin Organization: Domains By Proxy, LLC
Admin City: Scottsdale
Admin State/Province: Arizona
Admin Postal Code: 85260
Admin Country: US
Admin Email:
Registry Tech ID: Not Available From Registry
Tech Organization: Domains By Proxy, LLC
Tech City: Scottsdale
Tech State/Province: Arizona
Tech Postal Code: 85260
Tech Country: US
Tech Email:

*Sibling Domains*

mail.tekrider.net
cd59.tekrider.net
webdisk.tekrider.net
www.cd59.tekrider.net


--
David B.

On 07/01/2019 17:46, Beauregard T. Shagnasty wrote:
David B. STALKER wrote:

On 07/01/2019 13:29, Beauregard T. Shagnasty wrote:
What about the nearly fifty errors on your page?

Huh? I see this:-

"Document checking not completed. The result cannot be determined due to
a non-document-error."

I'll provide an image if you advise which facility you will trust (and
view).

You do not need to provide an image. The reason is simple. You inserted
the link in the validator and included the trailing "" but not the
starting one. The page has *47* errors. In addition, the page has 2 CSS
errors and *380* warnings.
http://jigsaw.w3.org/css-validator/

You are right. Just *HOW* know this seems rather magical. Are you
looking over my shoulder, BTS?

https://validator.w3.org/nu/?doc=htt...vxer-a-profile

Man up and fix it.

Sorry, it's not my field of expertise!

Shall I report matters to WordPress? After all, it is all THEIR work!
I'm just a user - or am I the product?

--
David B.

On 07/01/2019 17:50, Tim Streater wrote:
In article , Beauregard T. Shagnasty
wrote:

David B. STALKER wrote:

On 07/01/2019 13:29, Beauregard T. Shagnasty wrote:
What about the nearly fifty errors on your page?

Huh?Â* I see this:-

"Document checking not completed. The result cannot be determined due to
a non-document-error."

I'll provide an image if you advise which facility you will trust (and
view).

You do not need to provide an image. The reason is simple. You
inserted the link in the validator and included the trailing "" but
not the starting one. The page has *47* errors. In addition, the page
has 2 CSS errors and *380* warnings.
http://jigsaw.w3.org/css-validator/

Man up and fix it.

This sort of ******** appears to be typical of Our David.

Tim

What SHOULD I do about these errors? Just your opinion I realise.

=

Nu Html Checker
This tool is an ongoing experiment in better HTML checking, and its
behavior remains subject to change

Showing results for https://vxer.home.blog/2018/12/08/vxer-a-profile

Checker Input
Show sourceoutlineimage report

Check by


Use the Message Filtering button below to hide/show particular messages,
and to see total counts of errors and warnings.
Message Filtering
Warning: The type attribute is unnecessary for JavaScript resources.
From line 10, column 3; to line 10, column 229
low' /↩ script
src='https://r-login.wordpress.com/remote-login.php?action=js&host=vxer.home.blog&id …&back=https%3A%2F%2Fvxer.home.blog%2F2018%2 F12%2F08%2Fvxer-a-profile%2F'
type="text/javascript"/scri
Warning: The type attribute is unnecessary for JavaScript resources.
From line 11, column 3; to line 11, column 33
script↩ script type="text/javascript"↩ /*
Warning: The type attribute is unnecessary for JavaScript resources.
From line 28, column 2; to line 28, column 32
eed/" /↩ script type="text/javascript"↩ /*
Warning: The type attribute is unnecessary for JavaScript resources.
From line 43, column 4; to line 43, column 34
cript↩ script type="text/javascript"↩ wi
Warning: The type attribute for the style element is not needed and
should be omitted.
From line 47, column 3; to line 47, column 25
script↩ style type="text/css"↩img.w
Warning: The type attribute is unnecessary for JavaScript resources.
From line 64, column 1; to line 64, column 239
='all' /↩script type='text/javascript'
src='https://s0.wp.com/_static/??-eJyFztEKwjAMBdAfsquTiXsRv6XWOFKXtDb…bIxv4ChnDITq Eh5A/2kRVYF0vxjCOYIpDdUG+16BpXXIqiBCIVraTfLyFPCPNfFkCT8 zeTQfC5tJ7o2Hb9Yde3+24bXjRNW9I='/scri
Warning: The type attribute for the style element is not needed and
should be omitted.
From line 99, column 921; to line 99, column 972
on.ico" /style type="text/css" id="syntaxhighlighteranchor"/styl
Warning: The banner role is unnecessary for element header.
From line 112, column 3; to line 112, column 58
ction"↩ header id="masthead" class="site-header" role="banner"↩ d
Warning: The navigation role is unnecessary for element nav.
From line 131, column 5; to line 131, column 72
div↩↩ nav id="site-navigation" class="main-navigation"
role="navigation"↩ d
Warning: The main role is unnecessary for element main.
From line 142, column 3; to line 142, column 48
-area"↩ main id="main" class="site-main" role="main"↩↩ ↩
Warning: The navigation role is unnecessary for element nav.
From line 191, column 2; to line 191, column 59
--↩↩ ↩ nav class="navigation post-navigation" role="navigation"↩ h2
Warning: Article lacks heading. Consider using h2-h6 elements to add
identifying headings to all articles.
From line 205, column 4; to line 205, column 52
ment"↩ article id="div-comment-1" class="comment-body"↩
Error: An img element must have an alt attribute, except under certain
conditions. For details, consult guidance on providing text alternatives
for images.
From line 243, column 46; to line 243, column 114
4MQN.png"img src="https://i.imgur.com/ffG4MQN.png"
style="max-width:100%;" //a/
Warning: Article lacks heading. Consider using h2-h6 elements to add
identifying headings to all articles.
From line 227, column 4; to line 227, column 52
ment"↩ article id="div-comment-2" class="comment-body"↩
Error: An img element must have an alt attribute, except under certain
conditions. For details, consult guidance on providing text alternatives
for images.
From line 269, column 46; to line 269, column 114
ZZ2d.png"img src="https://i.imgur.com/H0HZZ2d.png"
style="max-width:100%;" //a/
Warning: Article lacks heading. Consider using h2-h6 elements to add
identifying headings to all articles.
From line 250, column 4; to line 250, column 52
ment"↩ article id="div-comment-3" class="comment-body"↩
Error: An img element must have an alt attribute, except under certain
conditions. For details, consult guidance on providing text alternatives
for images.
From line 292, column 46; to line 292, column 114
uWMi.jpg"img src="https://i.imgur.com/jC3uWMi.jpg"
style="max-width:100%;" //a/
Warning: Article lacks heading. Consider using h2-h6 elements to add
identifying headings to all articles.
From line 276, column 4; to line 276, column 52
ment"↩ article id="div-comment-5" class="comment-body"↩
Error: The frameborder attribute on the iframe element is obsolete. Use
CSS instead.
From line 321, column 26; to line 321, column 198
ed-vimeo"iframe
src="https://player.vimeo.com/video/305979105?app_id=122963" width="176"
height="144" frameborder="0" title="raidintro" allow="autoplay;
fullscreen" allowfullscreen/ifra
Warning: Article lacks heading. Consider using h2-h6 elements to add
identifying headings to all articles.
From line 305, column 4; to line 305, column 52
ment"↩ article id="div-comment-6" class="comment-body"↩
Warning: Article lacks heading. Consider using h2-h6 elements to add
identifying headings to all articles.
From line 328, column 4; to line 328, column 53
ment"↩ article id="div-comment-10" class="comment-body"↩
Warning: Article lacks heading. Consider using h2-h6 elements to add
identifying headings to all articles.
From line 362, column 4; to line 362, column 52
ment"↩ article id="div-comment-7" class="comment-body"↩
Warning: Article lacks heading. Consider using h2-h6 elements to add
identifying headings to all articles.
From line 385, column 4; to line 385, column 53
ment"↩ article id="div-comment-12" class="comment-body"↩
Warning: Article lacks heading. Consider using h2-h6 elements to add
identifying headings to all articles.
From line 407, column 4; to line 407, column 53
ment"↩ article id="div-comment-13" class="comment-body"↩
Warning: Article lacks heading. Consider using h2-h6 elements to add
identifying headings to all articles.
From line 433, column 4; to line 433, column 53
ment"↩ article id="div-comment-18" class="comment-body"↩
Warning: Article lacks heading. Consider using h2-h6 elements to add
identifying headings to all articles.
From line 455, column 4; to line 455, column 53
ment"↩ article id="div-comment-21" class="comment-body"↩
Warning: Article lacks heading. Consider using h2-h6 elements to add
identifying headings to all articles.
From line 482, column 4; to line 482, column 53
ment"↩ article id="div-comment-22" class="comment-body"↩
Warning: Article lacks heading. Consider using h2-h6 elements to add
identifying headings to all articles.
From line 504, column 4; to line 504, column 53
ment"↩ article id="div-comment-23" class="comment-body"↩
Warning: Article lacks heading. Consider using h2-h6 elements to add
identifying headings to all articles.
From line 558, column 4; to line 558, column 53
ment"↩ article id="div-comment-24" class="comment-body"↩
Warning: The type attribute is unnecessary for JavaScript resources.
From line 793, column 1; to line 793, column 31
↩↩/div↩↩script type="text/javascript"↩var h
Warning: The contentinfo role is unnecessary for element footer.
From line 839, column 3; to line 839, column 63
nt --↩↩ footer id="colophon" class="site-footer" role="contentinfo"↩

Warning: The type attribute is unnecessary for JavaScript resources.
From line 849, column 219; to line 849, column 300
/a/divscript type='text/javascript'
src='//0.gravatar.com/js/gprofiles.js?ver=201902y'/scri
Warning: The type attribute is unnecessary for JavaScript resources.
From line 850, column 1; to line 850, column 31
/script↩script type='text/javascript'↩/* !
Warning: The type attribute is unnecessary for JavaScript resources.
From line 855, column 1; to line 855, column 122
/script↩script type='text/javascript'
src='https://s1.wp.com/wp-content/mu-plugins/gravatar-hovercards/wpgroho.js?m=1380573781h'/scri
Warning: The type attribute is unnecessary for JavaScript resources.
From line 887, column 1; to line 887, column 31
↩ /div↩script type='text/javascript'↩/* !
Warning: The type attribute is unnecessary for JavaScript resources.
From line 892, column 1; to line 892, column 175
/script↩script type='text/javascript'
src='https://s2.wp.com/_static/??/wp-content/js/jquery/jquery.autoresize.js,/wp-content/mu-plugins/highlander-comments/script.js?m=1521806916j'/scri
Warning: The type attribute is unnecessary for JavaScript resources.
From line 916, column 2; to line 916, column 32
/div↩↩ script type="text/javascript"↩ win
Warning: The type attribute is unnecessary for JavaScript resources.
From line 938, column 1; to line 938, column 31
endif]--↩script type='text/javascript'↩/* !
Warning: The type attribute is unnecessary for JavaScript resources.
From line 943, column 1; to line 943, column 31
/script↩script type='text/javascript'↩/* !
Warning: The type attribute is unnecessary for JavaScript resources.
From line 948, column 1; to line 948, column 31
/script↩script type='text/javascript'↩/* !
Warning: The type attribute is unnecessary for JavaScript resources.
From line 953, column 1; to line 953, column 31
/script↩script type='text/javascript'↩/* !
Warning: The type attribute is unnecessary for JavaScript resources.
From line 958, column 1; to line 958, column 479
/script↩script type='text/javascript'
src='https://s2.wp.com/_static/??-eJydUttOwzAM/SFSj7EJXhCfgrLUbd3mhp2…zjfbloPvyYap517UI1hyxoocc US13qCCzVN5A4TOqpWsH7tJYm8NI6YpCkGquJQTrN5NujLaQ39/q43Ww3q/Xq+aX/ApnZaTs='/scri
Warning: The type attribute is unnecessary for JavaScript resources.
From line 959, column 1; to line 959, column 31
/script↩script type='text/javascript'↩var w
Warning: The type attribute is unnecessary for JavaScript resources.
From line 988, column 1; to line 988, column 31
/script↩script type="text/javascript"↩// !
Error: The scrolling attribute on the iframe element is obsolete. Use
CSS instead.
From line 1005, column 12; to line 1005, column 167
/script iframe
src='https://widgets.wp.com/likes/master.html?ver=20180319#ver=20180319'
scrolling='no' id='likes-master' name='likes-master'
style='display:none;'/ifra
Warning: The type attribute is unnecessary for JavaScript resources.
From line 1007, column 1; to line 1007, column 72
ul/div↩script src="//stats.wp.com/w.js?56" type="text/javascript"
async defer/scri
Warning: The type attribute is unnecessary for JavaScript resources.
From line 1008, column 1; to line 1008, column 31
/script↩script type="text/javascript"↩_tkq
Document checking completed.

Used the HTML parser. Externally specified character encoding was UTF-8.
Total execution time 385 milliseconds.

About this checker • Report an issue • Version: 18.12.26

--
David B.