And in other news, water is wet. In design “choice” kills, if you try to say everything you end up saying nothing. I am not a big fan of clutter or anything that gets in the way of a user achieving their goals, like social media icons on websites. Therefore, it is really no surprise when I read Removing Social Sharing Buttons Increases Conversions. Yes, You Heard That Right! I am a big fan of “Goal-Driven Design” and if your goal is to drive traffic away from your website, add the social media icons and other distractions.
Every object on a web page is competing for the user’s attention and it is a user-centered designers job to lead the users to their goal, and every design element should have it is time, place and weight. If your primary objective is to drive traffic to your social media presence, sure the links should be prominent. However, if your goal is for the user to interact with your website, then wait. Wait until after the user has completed their goal then invite them to like your social media page. If your website does not have a goal, well then check out my last post on defining your website objectives.
Strategic communication is the best communication, so it’s important to define the strategy in the discovery stage of the project. Our strategy will determine the tactics we use for a developing a successful website. It’s hard to determine the strategy without knowing first what the primary objective of the project is. I have broken the discovery phase of user centered into 7 categories; each category may have questions, test or exercises.
- Audience Discovery
- Accessibility Discovery
- Brand Discovery
- Goal Discovery
- SEO Discovery
- Speed Discovery
- Usability Discovery
Over the years I’ve acquired quite an arsenal of questions for gathering information. Below are 5 questions that I use in the Goal Discovery category.
- What exactly is purpose of this website? (please define a clear, concise objective)
- What is your vision for the website?
How will you determine whether the vision is a success?
- What are your goals for this website and each section of the website?
Are the goals really the goals? Can you define alternative goals? Last year Home Depot sold millions of ¼” drill bits. “Nary a soul” (as my grandmother used to say) wanted ¼”drill bit, they all wanted 1/4” holes. What is the end result, users need?
- Can you rank the applicable purposes of your site below, with 1 being the most important?
[ ] Information
[ ] Branding
[ ] Lead generation/qualifying prospects
[ ] Sales revenue
[ ] Ad revenue
[ ] Internal needs
[ ] Transformation
- What are the 3 main things you want people to do you your web site?
Some of the questions will lead to more questions, and hopefully, they will help define the overall strategy.
In my quest to build the fastest website possible, I stay busier than a Colorado Taco Bell employee working the late shift. I have several methods of testing website speed; one of the automated tests I like to use is Google PageSpeed Insights.
In following their recommended techniques, websites will get a lower grade for using an external style sheet (if the style sheet is small). Therefore, I started testing inline styles as opposed to an external style sheet. I realize there are many different variables in determining the speed and my test are not the most scientific, but if you look at “exhibit A”, the page with the inline styles is over 100 milliseconds slower than “exhibit B” which is using an external style sheet. However, by using an external style sheet, the site loads faster in the real world, so I believe I am going to stay with the external file on my website for now.
I am using Typekit for my web fonts and that also brings down the score, but I am thinking it is still faster than using images, not to mention the time it takes to develop and optimize the images. I believe speed is king and it will always be a factor on the web. With the percentage of mobile web surfers climbing it will be even more of a factor. In the end, using automated tools for testing is good, but using common sense and real world test will always be a better solution.
When optimizing a website for usability content should be easy to read. Writing web or email copy should be easy to scan and written on a 6th to 8th-grade level. You might want to knock that down a couple of grades if you are writing for the average redneck. Regardless of your audience, it is important to test the readability of your copy. I try to score a 60 or above on the Flesch–Kincaid readability tests there’s a great online tool or you can use Microsoft Word to test this.
To check the readability of your copy in Microsoft Word
- Make sure “Show readability statistics” is checked under “File > Options > Proofing”
- Open Microsoft Word and paste your text in the new document
- Click “Review > Spelling and Grammar”
For this post, I scored 69.3 on the test, and it looks like I am writing on about a 7th-grade level. I am guessing my audience is not the average redneck; I’m guessing they are classy and sophisticated or at least like me — an above average redneck:)
When it comes to designing fast websites, I guess I’m a dinosaur. I remember the distinct sound of my 56k modem firing up and the challenges of trying to develop a website that would look good and load fast on slow connection. To me, a big part of user-centered design is fast loading pages and a snappy interface whether you are designing for 56k or 3g.
Like any pure blooded redneck- I believe faster is always better and It looks like having a fast website pays off where it counts, a recent internal study by Wal-Mart found that:
- A 100 millisecond delay resulted in a 1% DROP in revenue
- A 500 millisecond delay resulted in a 20% DROP in traffic
I’ve wrote about website speed being king before and it’s nice to see real results. I can’t begin to imagine what a 1% drop in revenue might look like for the Wal-Mart website? I’m guessing a redneck like me could probably buy a pretty fast truck with 1% of the profits from an hour or two. 🙂
I started using SASS a few months ago and feel like I have just scratched the surface of this new approach to CSS. I was hesitant to start using SASS, at first I thought it ran on the server and was like a type of middleware, and I would have to learn another scripting language. However it’s not middleware, and I didn’t have to learn anything new to start using SASS. I’m using a nifty tool called compass.app it’s easy to use and here are 3 reasons I will continue to use SASS.
Helps keep my development files organized.
I’m a speed freak; I like fast websites and will try to squeeze every last byte out of a file. By using SASS, I can keep comments in the production file, and it compresses the final CSS automatically. I used to use PHP to strip out the end-of-line breaks and comments and maintain 2 files, not anymore.
Variables and Mixins
Defining variables and mixins saves me time. No more find-and-replace, which isn’t too bad until you start working with multiple files.
Having the ability to use @import and break the CSS into multiple files allows several developers to work on different areas of the site without running into one another. I’m using the @import to pull in my reset, and form stylesheets and to test my CSS 2.1 files before I use the CSS 3.