Warning

 

Close
Confirm Action

Are you sure you wish to do this?

Cancel Confirm
AR15.COM
8/24/2007 7:19:04 AM EDT
HI All,  I revamped my website, and need feedback.  

Please visit my new website:  www.LMIInc.com

and let me know your experiences with the loading, and browsing of the site, and it's pages.

If you could, also please let me know what browser you are using, if possible.

Thanks for the help..

[email protected]
8/27/2007 2:08:45 PM EDT
[#1]
bump, been repaired,,
8/27/2007 2:42:20 PM EDT
[#2]
Looks good except for one thing I really hate.

It's got that code in it that doesn't let me use the previous page arrow button unless I click it really fast several times.

I hate websites that do that.
8/27/2007 2:53:58 PM EDT
[#3]

Quoted:
Looks good except for one thing I really hate.

It's got that code in it that doesn't let me use the previous page arrow button unless I click it really fast several times.

I hate websites that do that.


It doesn't do that for me, using Firefox.
8/27/2007 2:54:42 PM EDT
[#4]
It loads slowly, even though I'm behind a caching server.  That tells me that the designer is trying to be very clever and show the whole world how clever s/he is with bizarre coding.

There is no need for anything other than straight, static HTML for your site.  As simple as it is (and that isn't a dig... simple is good), it should load nearly instantly.
8/27/2007 11:50:01 PM EDT
[#5]

Quoted:

Quoted:
Looks good except for one thing I really hate.

It's got that code in it that doesn't let me use the previous page arrow button unless I click it really fast several times.

I hate websites that do that.


It doesn't do that for me, using Firefox.


Must be a java/ie thing that Firefox is saving you from.
8/27/2007 11:59:24 PM EDT
[#6]

Quoted:
There is no need for anything other than straight, static HTML for your site.  As simple as it is (and that isn't a dig... simple is good), it should load nearly instantly.


+10000

What's with all the <div>s? Old school html!
8/28/2007 12:44:15 AM EDT
[#7]
Doesn't work for me.
9/1/2007 4:30:50 PM EDT
[#8]
bump
9/6/2007 11:58:31 AM EDT
[#9]
BUMP,  the bugs have been worked out, still hoping for more helpful input,,
9/6/2007 12:07:29 PM EDT
[#10]
Hmm... The main text block goes away in Opera 7.54.  I see "LMI is dedicated to providing something" and then it just disappears.  Also, the main logo and navigation bar disappears.
9/6/2007 12:07:42 PM EDT
[#11]
The links for http://bladerigger.com, and http://newyorkpacking.com don't work. The first one is dead, the second takes you somewhere that is not about NYC gun laws. While you are at it, have them make the links that do work open in a new tab. Also, maybe add some pics of the facility/ranges? You may want to think about adding your address in the contact information.
9/6/2007 12:27:41 PM EDT
[#12]
It looks good (Firefox on Ubuntu Linux).

The background images are really slowing the site down. Each one (I see two at a quick glance) is like 74k, and it makes the site less "snappy". A static page like that should load up MUCH faster. Knock those image sizes down. Way down. If you're not married to the idea of a gradient, you could lose the images entirely.

Also for code readability, you might want to consider using a linked stylesheet. Reference the class from the stylesheet there, instead of cluttering up the code. It'll make facelifts to the site 10 times easier, too. Kudos to you for using CSS to place images, instead of tables. I like that, and it makes using a templating engine easier to implement someday, should you decide to use a server side scripting language like PHP. Tables are for tabular data, not positioning. The world has changed a little bit since 1996 and I'm glad you noticed.
9/6/2007 1:31:50 PM EDT
[#13]
Cutting up large images and loading the parts separately will make it fell faster also.

What kind of bandwidth does your server have?
9/6/2007 1:34:24 PM EDT
[#14]

Quoted:

Quoted:
There is no need for anything other than straight, static HTML for your site.  As simple as it is (and that isn't a dig... simple is good), it should load nearly instantly.


+10000

What's with all the <div>s? Old school html!


It *is* static HTML, and he's adhering to a standard that's been adopted for several years now.

EDIT: It's not strict adherence, but it's close enough.
9/6/2007 1:39:25 PM EDT
[#15]
Run it through these two and post an update, my firefox plugins were complaining about bits being invalid.

validator.w3.org/ -- HTML validator.  7 Errors.

jigsaw.w3.org/css-validator/ -- CSS validator.  If you decide to start using it (CSS); which you probably will, as you remove invalid HTML and find the only valid way to achieve the given effect is with CSS.

9/6/2007 1:40:58 PM EDT
[#16]


Browser:  Camino 1.5
9/6/2007 1:44:27 PM EDT
[#17]

Quoted:
Run it through these two and post an update, my firefox plugins were complaining about bits being invalid.

validator.w3.org/ -- HTML validator.  7 Errors.

jigsaw.w3.org/css-validator/ -- CSS validator.  If you decide to start using it (CSS); which you probably will, as you remove invalid HTML and find the only valid way to achieve the given effect is with CSS.



Which page? His home page checks out.
9/6/2007 1:47:20 PM EDT
[#18]
And he is using CSS, he just isn't doing all of it with a linked stylesheet. He can run it through the CSS validator just fine (and he should).
9/6/2007 1:51:45 PM EDT
[#19]
Visually looks good.

Problem:

The website is made up of all graphic files and no real text.

The search engines won't be able to crawl the pages because of this.

It's actually a huge issue.  The alt tags alone, will not solve this issue.

Your using iWeb 1.1, you should be able to change the graphic text to real text.

Just a suggestion, if you want the search engines to pick up your website.
9/6/2007 1:52:26 PM EDT
[#20]

Quoted:

Quoted:
Run it through these two and post an update, my firefox plugins were complaining about bits being invalid.

validator.w3.org/ -- HTML validator.  7 Errors.

jigsaw.w3.org/css-validator/ -- CSS validator.  If you decide to start using it (CSS); which you probably will, as you remove invalid HTML and find the only valid way to achieve the given effect is with CSS.



Which page? His home page checks out.


The default start page.. here's the link:

validator.w3.org/check?uri=http%3A%2F%2Fwww.LMIInc.com&charset=%28detect+automatically%29&doctype=Inline&group=0

And the results:


This page is not Valid XHTML 1.0 Transitional!
Result: Failed validation, 7 Errors

9/6/2007 1:54:14 PM EDT
[#21]

Quoted:
Visually looks good.

Problem:

The website is made up of all graphic files and no real text.

The search engines won't be able to crawl the pages because of this.

It's actually a huge issue.  The alt tags alone, will not solve this issue.

Your using iWeb 1.1, you should be able to change the graphic text to real text.

Just a suggestion, if you want the search engines to pick up your website.


Holy shit, I didn't even notice that. The main page text is a graphic (and a 90kb one at that!). No wonder it's loading so slow.
9/6/2007 1:54:17 PM EDT
[#22]

Quoted:
And he is using CSS, he just isn't doing all of it with a linked stylesheet. He can run it through the CSS validator just fine (and he should).


Ahhh the validator doesn't do the "javascript refresh break the back button" dance.  It's that page that's breaking it, not the page that it sends you to; LMIinc_Marksmanship.html.
9/6/2007 1:55:23 PM EDT
[#23]
It has some issues in Mac OS X Safari (Apples web browser)
9/6/2007 1:55:52 PM EDT
[#24]
Regarding the validator.. the page the initial one refreshes you to, www.lmiinc.com/LMIinc_Marksmanship.html gets:

20 errors and 2 warnings on the CSS validator.

No errors or warnings on the HTML validator -- since as already discovered, there basically is none.  
9/6/2007 1:58:14 PM EDT
[#25]

Quoted:
The default start page.. here's the link:

validator.w3.org/check?uri=http%3A%2F%2Fwww.LMIInc.com&charset=%28detect+automatically%29&doctype=Inline&group=0

And the results:


This page is not Valid XHTML 1.0 Transitional!
Result: Failed validation, 7 Errors



Oh, that's weird. I checked http://www.lmiinc.com/LMIinc_Marksmanship.html and it validated.

validator.w3.org/check?uri=http%3A%2F%2Fwww.lmiinc.com%2FLMIinc_Marksmanship.html
9/6/2007 2:00:27 PM EDT
[#26]

Quoted:

Quoted:
And he is using CSS, he just isn't doing all of it with a linked stylesheet. He can run it through the CSS validator just fine (and he should).


Ahhh the validator doesn't do the "javascript refresh break the back button" dance.  It's that page that's breaking it, not the page that it sends you to; LMIinc_Marksmanship.html.


Aha! He ought to just name the home page index.html (or whatever the default is for his server's DocRoot). I don't see the point in doing the redirect.
9/6/2007 2:03:34 PM EDT
[#27]

Quoted:

Quoted:

Quoted:
And he is using CSS, he just isn't doing all of it with a linked stylesheet. He can run it through the CSS validator just fine (and he should).


Ahhh the validator doesn't do the "javascript refresh break the back button" dance.  It's that page that's breaking it, not the page that it sends you to; LMIinc_Marksmanship.html.


Aha! He ought to just name the home page index.html (or whatever the default is for his server's DocRoot). I don't see the point in doing the redirect.


Not much use troubleshooting this one, it's created with iweb 1.1 an Apple program.  Unless this is a redo and the new developer is using another program now.
9/6/2007 2:04:15 PM EDT
[#28]

Quoted:

Quoted:

Quoted:
And he is using CSS, he just isn't doing all of it with a linked stylesheet. He can run it through the CSS validator just fine (and he should).


Ahhh the validator doesn't do the "javascript refresh break the back button" dance.  It's that page that's breaking it, not the page that it sends you to; LMIinc_Marksmanship.html.


Aha! He ought to just name the home page index.html (or whatever the default is for his server's DocRoot). I don't see the point in doing the redirect.


Well if he's reading this, I'm more than willing to fix that, and redo every one of these pages as text rather than with the big images, over the course of a couple of days, if he's interested.

You still here, Ron?
9/6/2007 2:08:51 PM EDT
[#29]

Quoted:

Quoted:

Quoted:

Quoted:
And he is using CSS, he just isn't doing all of it with a linked stylesheet. He can run it through the CSS validator just fine (and he should).


Ahhh the validator doesn't do the "javascript refresh break the back button" dance.  It's that page that's breaking it, not the page that it sends you to; LMIinc_Marksmanship.html.


Aha! He ought to just name the home page index.html (or whatever the default is for his server's DocRoot). I don't see the point in doing the redirect.


Well if he's reading this, I'm more than willing to fix that, and redo every one of these pages as text rather than with the big images, over the course of a couple of days, if he's interested.

You still here, Ron?


You can fix it for sure, but if the developer is going to still update the site with Apple iweb, then your fix will be overwritten every time they re-upload any minor site changes.
9/6/2007 2:09:56 PM EDT
[#30]

Quoted:

Quoted:

Quoted:

Quoted:
And he is using CSS, he just isn't doing all of it with a linked stylesheet. He can run it through the CSS validator just fine (and he should).


Ahhh the validator doesn't do the "javascript refresh break the back button" dance.  It's that page that's breaking it, not the page that it sends you to; LMIinc_Marksmanship.html.


Aha! He ought to just name the home page index.html (or whatever the default is for his server's DocRoot). I don't see the point in doing the redirect.


Not much use troubleshooting this one, it's created with iweb 1.1 an Apple program.  Unless this is a redo and the new developer is using another program now.


Oh, no shit? No wonder he's not commenting on the HTML.

I missed the generator meta tag. Well, to it's credit - it writes cleaner code than Frontpage (and most other WYSIWYG editors I've seen). I've never used it, but does it let the user edit the HTML?
9/6/2007 2:13:10 PM EDT
[#31]

Quoted:

Quoted:

Quoted:

Quoted:

Quoted:
And he is using CSS, he just isn't doing all of it with a linked stylesheet. He can run it through the CSS validator just fine (and he should).


Ahhh the validator doesn't do the "javascript refresh break the back button" dance.  It's that page that's breaking it, not the page that it sends you to; LMIinc_Marksmanship.html.


Aha! He ought to just name the home page index.html (or whatever the default is for his server's DocRoot). I don't see the point in doing the redirect.


Not much use troubleshooting this one, it's created with iweb 1.1 an Apple program.  Unless this is a redo and the new developer is using another program now.


Oh, no shit? No wonder he's not commenting on the HTML.

I missed the generator meta tag. Well, to it's credit - it writes cleaner code than Frontpage (and most other WYSIWYG editors I've seen). I've never used it, but does it let the user edit the HTML?


No, you can not edit the HTML in iweb.  You could edit the htlm in dreamweaver or another program after you publish your pages, but then if you make any changes in iweb, iweb will delete the edits you made to the html and reformat the html it's own way.  iWeb is very easy to use, but very limited in what it can do, especially the old version 1.1 that he is using for this.
9/6/2007 2:17:01 PM EDT
[#32]

Quoted:
You can fix it for sure, but if the developer is going to still update the site with Apple iweb, then your fix will be overwritten every time they re-upload any minor site changes.


Well then he fires this "developer" while he's at it.  Doesn't need the guy anyway, quite obviously.  
9/6/2007 2:21:03 PM EDT
[#33]
This is going downhill fast....
9/6/2007 2:22:22 PM EDT
[#34]

Quoted:
This is going downhill fast....


9/6/2007 2:32:55 PM EDT
[#35]
WYSIWYG editors, new "developers", overwriting this, undoing that, loads of eye-candy, FF on Linux doesn't align up right, list goes on.

For all we know this server is running a modem connection to the net.

All spells techno trouble.

Shrug.