6 Types Of Web Bugs Found During QA Testing

banner image

There are many ways with which developers can boost their work, and work towards gaining optimization. Amongst this assortment of ways, one is finding bugs and eliminate them, well that is quite evident isn’t it? And the time it takes up is troublesome.

Traditionally it is discussed during monotonous real-time meetings which consume so much time that could be used productively. Am I right or am I right? The continuous affair of processing, managing, organizing, documenting, and finding bugs can be tedious.

It would be highly effective if we had a way of finding bugs, which is speedy. While developing a website, bugs can ruin the whole project. Additionally, it also determines your reputation as a website developer. Well, now you know why your website should be bug-free but how? Let’s see!

What Are The 6 Types of Web Bugs Found During QA Testing?

Types of web bugs found during QA testing;

  1. The Adaptability of Browser: A website may often have problems with browser adaptability. A QA team tests these websites overseveralf browsers. For the testing of the website, an appropriate browser is chosen which mainly depends on user preferences. According to such tests, developers say that the most troublesome browsers to work with are the old versions of Safari and Internet Explorer.
  2. Authentication: Unacceptable, invalid characters if entered can cause authentication and validation problems. It can also occur if maximum length surpasses, as a result, bugs crop up. They are not very serious but can be avoided and can ruin your software.
  3. Managing of Date: Date control can often invite bugs. There are times when a website needs age restrictions, and for that reason, people need to put up their date of birth. This is where the problem occurs since developers test with the cut-off date generally. Developers need to go just above and behind the cut-off date to avoid such issues.
  4. Website Crash: Often a website crashes with a click of a random button. This is extremely problematic. These are common but are as much difficult to remove by developers. In this case, developers need to run software testing.
  5. Resolution: Developers have to keep in mind which is the most used to browse and test the website or web app in that way. There are times when a website or web app has problems with page layouts and resolution while usage.
  6. User Friendliness: Developers need to design a website that is communicative and user-friendly. If not so it makes way for a lot of problems. Contents of your the the page should be easily accessible. Information too should be crisp and clear. Providing a help and contents section would be amazing.

Web Bugs Found img 2

Which Kind Of Bugs Are Most Harmful?

Bugs can be detrimental to website development or any kind of web work. They can take a toll on web security and hence should be avoided at any cost.

Recently studies have found out 3 most dangerous bugs that are harming web development worldwide. Let’s have a look at these bad guys.

  • Heartbleed: It affected 17% of servers worldwide in 2014 and still affects a large population. It is claimed as a catastrophic bug. It is an OpenSSL bug.
  • Shellshock: Although a patch created this bug is quite harmful and continues to affect millions of vulnerable websites and software. It is even bigger a bug than Heartbleed.
  • Shellshock: Although a patch created this bug is quite harmful and continues to affect millions of vulnerable websites and software. It is even bigger a bug than Heartbleed.

Web Bugs Found img 3

How Do You Eliminate Website Bugs?

Here is how you eliminate website blogs;

  • Checking Contents: One should start by checking the contents which include correction of grammatical errors and elimination of inconsistent data. Thus content should be error-free and consistent.
  • Testing: testing your website on the most used browsers is a wise thing to do. The site must function equally with different types of browsers. Gather up as many browsers as you can and run a test on them. One can run tests on Chrome, Safari, Firefox, and Internet Explorer.
  • Device Testing: Your website should work freely and efficiently on all of the high-demand devices out there such as popular Android devices, iPhone, and others. The experience should be consistent irrespective of the device used.
  • Validating and Authenticating: Validate all the links that should take you to the page it means to. Validate colors, fonts, and styles of texts. It should be consistent. Further check, validate, and authenticate the security of the website. Sensitive details should be highly protected such as an online payment site.
  • Efficiency: Forms in your website should work properly. Users should be able to fill out the forms easily. The stored data should be accurate and should be according to the specifications. Additionally, confirmation emails should reach on time to every user after they fill out the forms. Efficiency should be worked upon with utmost care.

Bugs can pretty easily spoil every hard work and hence it is crucial to eliminate them as fast as possible. Now that you know how to find bugs and how to get in their way, you are all set to try your hands on web development tasks and it will be pretty amazing after you know how to demolish bugs and their creepy ways. Go ahead!

Quality Is Your Responsibility! Here’s Why Your Website Needs A Quality Assurance Plan

Quality Is Your Responsibility 01

Creating a website exactly like the vision you had for it is not an easy task. It must also hold up to the expectation of your customers. Anything to the contrary and you might end up losing the trust of your customers, and thus losing precious leads and revenue. Here’s where a Quality Assurance plan can help you maintain the standards of your website.

As the name itself suggests, Quality Assurance is a way of making sure that you are able to maintain the quality of the product or service that you are offering to your customers. It focuses on improving the quality of your product by making it more efficient and effective as per the defined quality standards. Quality Assurance is popularly known as QA Testing.

Having a QA Test plan for your website is an imperative step for your business and your establishment. A major part of website testing is done to provide for its quality, creating a better experience for your customers. QA testing can often be the difference between a successful and a failed website.

Think Zero Defects!

Think Zero Defects

Having a Quality Assurance Plan can help you work towards building a website with zero defects! But What is a Quality Assurance Plan? A Quality Assurance Plan is a document created by the project team and if followed will ensure the finished product meets all the criteria making it a product of the best possible quality standards. The product should not only meet your customer’s expectations and requirements but also meet your objectives and targets.

An ideal QA Plan comprises the following components:

  • A website testing strategy
  • The objectives of the testing
  • The resources available(manpower, software and hardware tools)
  • Schedule for the tests
  • The estimation for the list
  • The things that need to be delivered before, after and during the whole website testing process.

Once a test plan is set, the QA team who are directly involved in the website testing process creates a QA plan.

How Can I Break It?

This might seem like an absurd question. Why would anyone try to break their service? Any developer asks the question “How can I make It?”, but a QA Plan will find out “How can I Break It?”. A QA Plan will aim to bring out the defects in your website and give you an opportunity to correct them and make sure that you maintain the quality standards.

Here’s why you must create a QA Plan:

  • It helps determine the amount and type of work required to validate the quality of the tested application
  • People who are not a part of the QA team(management team, the developers and even the customers) understand the website testing process and approach for the website with the help of a test plan.
  • The test plan sets all the rules and procedures that need to be followed by the team during the testing process. Just like a guide book or a rule book.
  • Some important aspects like test strategy, test scope and the estimates are contained in the document. They can be reviewed and reused by the management team for future projects. Thus, the test plan helps build stable processes and accumulate know-how.

These website testing plans are made by the QA testers team. There are a lot of different processes for testing a website.

What You Need To Do As a QA Tester?

What You Need To Do As a QA Tester 01

As a QA tester, what will you do on a website? They must completely test and challenge everything that has been developed.Here are the most common responsibilities that a QA tester is required to take up:

1. Running Tests

The main role of a QA tester is to run various tests on software products to ensure the program satisfies all specifications and requirements. They run debugging programs to fix any issues or bugs in a program. Once these problems are solved, they run additional tests before the products are issued for sale to customers.

2. Record Defects And Issue Reports

QA testers record all defect details, create reports stating the type of defects found and the measures taken to resolve these issues. A website tester must have a system for recording and documenting all testing results performed. Maintaining these reports help QA testers to recognise similar problems in the future and provide a quick resolution.

3. Performing Root Cause Analysis

QA testers are responsible for ensuring that the end-users are happy. Therefore, they must determine the problem at its source. The when, where and why of each production defect should be looked into by the testers. Finding a primary cause or a series of interrelated problems may be involved.

4. Assist software Developers

Testers also apply their knowledge early in the software development process. They work closely and together with the developers to recognise the chances of any operational issues, assess risks and resolve those and other issues before the software is complete.

5. Training

Testers will offer to teach their juniors or other team members about all the processes and technologies involved in the websites and applications. They can also explain proper areas in which these assurances should be applied.

The Road to Breaking it Down

The Road to Breaking it Down

As mentioned before the aim of QA Testers is to “Break It”. So the next question is, “How to Break it?”. Now that we’ve learnt all the basic concepts of QA Testing, here’s what you need to do to create a test plan.

1. Product Analysis

A basic starting point is to get to know what the product is and get acquainted with the project documentation. Why the product was created, who’s meant to use it, how will it look, on what environment it would run? When testing the compatibility on different platforms- devices, web browsers, OS’s etc, the latter is important.

2. Developing the strategy

The test manager develops a really important document- the test strategy. It defines the whole process for testing a website.

List of the many things that need to be done here:

  • Which of the tested components of the website will be ‘in scope’ and which ones ‘out of scope’ needs to be decided. Everything that will be tested will be in the ‘in scope’ while the left out will be ‘out of scope’. A precise testing scope has two benefits:
    1. A precise knowledge of what tests will be performed
    2. All the members of the team will know exactly what to test and what not to test.

    For determining the scope of a testing project, the customer requirements are to be considered, the project budget, the project specification and most importantly the skills and talent of the test team.

  • As we know, there are a lot of tests out there and it is impossible to apply them all especially when we have a constraint on the money and time. The appropriate type of tests is to be selected based on the type of project. Select ones that are relevant to the project.
  • For seeing all potential risks like tight schedule, incorrect estimates, members lacking required skills and then suggesting a proper action to handle those problems
  • Plan the flow of the whole process and who will perform the tests and the time by which they will be done
  • Testing should begin only when the specifications are ready, all the resources are available and the testing environment has been set
3. Load testing of your website

To make the interface more user friendly, it is crucial to test the load-bearing capacity of your website. This will help gather data from testing with different inputs and will also give an insight into the faults of the website.

Load testing tools suitable for varied needs and perspective are available. To drive high-value customers, planning load testing is essential.

Certain parametric to consider while load testing:

  1. Throughput: It is the amount of bandwidth used by a website while performing the load-bearing test. It says the volume of data sent and received from different servers.
  2. Error Rate: The frequency of errors occurring in the website while processing requests and the phase during which they occur.
  3. Response time: It is the time a website takes to respond during peak or average times.
4. Define the test objectives

The goal usually is to find as many software defects as possible and fix them so that the tested website is free from all the bugs before it’s release. However, creating a 100% bug-free product is next to impossible. So you need to find and fix all the bugs considered critical to the proper functioning of the product and then launch post-release updates and bug fixes.

Two steps that need to be done:

  • A collective list of all the features of the website that will require to be tested
  • Define the overall goal of the tests based on the list
5. Define the test criteria

Test criteria are the guidelines on which the testing procedure of the product can be based. There are 2 criteria types:

  1. Suspension criteria- When this criterion is met, the testing is suspended until the development team can resolve any issues that would cause the criteria to be met. Website testing can continue after this. Suspension criteria mean suspending the complete or part of the testing activities.
  2. Exit criteria- This criterion is used to determine whether a given test activity has been completed or not. Exit criterion should be a part of the test plan and should be decided while planning.
    Some examples of exit criteria:
    • Verify if all tests that were planned have been run that is all the test cases have been executed
    • Verify if all the high priority areas have been completely tested and all the critical bugs and issues have been resolved
    • Verify if the coverage of the requirements and functionalities for the website has been given
    • Verify if the software development activities are completed within the timelines
    • Verify if all the software development activities are completed within the projected cost
    • Reaching the targeted percentage of passed test cases
6. Planning the resources

The plan is a summary of all the different types of resources(human resources, equipment, materials etc) required for the testing process.

  • Human Resources: Make a list of all the team members who are going to participate in the testing process and also the roles they will play in the process.
  • Other system resources: List of all the non-human resources needed for testing the project.
7. Planning test environments

A test environment consists of all the different components needed to perform the needed task for your website.

Different types of environments:

  1. Test environment – A testing environment is a setup of software and hardware for testing teams to execute test cases without worrying about breaking any functionality which could impact the user experience. Once the work is done, they can be handed off to the testing team for further tests.
  2. Staging environment – This is the part where all the bug fixes and latest features will be tested before being deployed to the production. It is strongly recommended that a staging test are performed before deployment so that the testing team can find any issues that could occur in production.
  3. Production environment – This is the part which the end-users see.
8. Testing schedules and time estimations
  • Test estimations: This is the time needed to complete the whole process of testing. It’s best to divide the whole process into small tasks and provide an estimate. Then they can be added to see how much time is required to finish everything.
  • Project schedule: A proper schedule helps you get a clear image of how the work on the website is progressing. Few important things needed to prepare a good schedule for the website testing:
    1. The deadline for the project completion should come first as it will define the time-frame in which the schedule must fit.
    2. Arranging working days and employee availability also helps in the proper arrangement of the testing activities within the schedule.
    3. Estimating the time required to complete all the tasks related to the website in advance.
    4. Knowing potential risks allows for the allocation of extra time to deal with those.
9. Testing Deliverables

These include all the documents, tools and reports that are produced and maintained in support of the tests. Depending on the phases of the project, there are different deliverables:

  1. Deliverables provided before the testing begins like the test plan, test specifications and test case.
  2. Deliverables provided during the testing process like test scripts, test data, error logs etc.
  3. Deliverables provided after the conclusion of the test like test results, defect reports, release notes.

A Website QA Checklist You Need to Tick Off Before Your Website Goes Live

Often in a hurry, we overlook small errors before making the website live and then later receive negative feedback from users. This website testing checklist below will help avoid any mistakes while launching a site.

  1. The first thing you need to check is the functionality of your website. Create a layout in your mind that breaks down how your website should look and how it should work. If you don’t know where to start, here’s the basics that you need to check: Dropdowns, buttons, checkboxes, input fields and forms.
  2. Now move on to checking your site’s process flow. Check whether the experience the user will have is what you had in mind for them.
  3. You also need to make sure that all the links in your website are functional and take the user exactly where you want them.
  4. Take time and secure your website from spam links. No one will want to visit the site if they are irritated repeatedly by spam links.
  5. Check browser compatibility. Users can access your site from any browser, device or operating system. Test your website with every browser other than the targeted few.
  6. You must also check the cookies on your website for proper functionality and their impact on your site’s security. Make sure that they are not active after their expiry period, they are encrypted before being saved on a user’s device.
  7. Check the site loading speed. Maintaining a site loading speed is one of the top priorities of the website testing checklist nowadays. It has become a Google ranking factor.
  8. Double-check the site’s security with SSL certificate. Having an SSL certificate is the top priority as protecting the site from hackers is your responsibility.
  9. Have a backup solution for a disaster. A lot of hard work and effort goes into creating a website. So, you should have a backup solution installed in case of any sort of disaster.
  10. HTML and CSS validation. Minor HTML/CSS error doesn’t harm a site’s result but it is recommended to verify that the code is proper and clean.
  11. Lastly, find out the small errors in the website(like any type of typo errors). This is an important part of a website testing checklist. Take some time out to proofread the content as many times as possible to ensure error-free content.

Now go and Create Your Own QA Test Plan!

Now go and Create Your Own QA Test Plan 01

As you must have realised by now, the purpose of a QA Website Test Plan is to improve, analyse, measure and controls the entirety of your website and make sure that the output created is the best one possible. The test plan we’ve provided covers important processes for testing a website and contains all the information you will needed for testing a website. Now you can create your own QA Test Plan and create a website that holds up to the vision you have!

How to get an unresponsive client to respond with ready-to-use follow-up email template

main image 1

Has any client ever become unresponsive out of the blue to you? Every freelancer has to go through that at some point in their career, and trust me; it can be a nightmare! Especially after they pay a deposit to get a project started and then disappear!

You are riddled with thoughts like-

  • Is it something I did that led to this?
  • I wish I knew what was up!
  • Does the client no longer want to work with me?
  • What about the deposit they made?

Left in a confused state of mind, you weigh your options, wondering what would be the best approach in your situation. There are quite a few things that you can do to get your client to respond, cope with the unresponsiveness mentally, and take precautions in case similar situations appear before you in the future.

This blog is your guide to dealing with unresponsive clients.

P.S. Read till the end of the blog to get your hands on ready to use follow up email to clients that are unresponsive or indecisive

So, they became unresponsive after paying a deposit!

There can be many reasons for your client to become unresponsive after deposit, some coincidental and others that require your attention. Here are some of the reasons why your client might become unresponsive after they commissioned or paid for in advance.

1. Email Clutter

Artboard 2 100

Email clutter is a real thing. When you manage multiple projects or oversee operations, you’re usually a part of every email thread. And it is difficult to catch up with the vast amounts of emails that land in your inbox.

According to Hubspot, it takes around a minute to recover from reading a single email; now imagine hundreds of emails that need to be read and responded to. Your client simply might not have the resources or time to spare.

2. Busy Clients

More often than not, the contact person between you and the client company is at a managerial position and has a tight schedule. In short, they are busy people. I can understand how they can miss an email or two, text, or a follow-up. As a designer, there is not much you can do to clear up their schedule to respond to you.

If the project you are collaborating on is of high priority, they will get back to you, but if they don’t, there is no need to worry as they are probably caught up in a crisis or another project.

3. They are suffering decision paralysis.

Artboard 4 100 1

Your client could also probably be stuck in making a project related decision. Decision paralysis happens to the best of us. You can reach out to them in such situations and ask them what you can do to help them decide, be it by providing some information or educating them. Your client will appreciate your help.

This way, you and your client are on the same page, and you are a part of what is happening rather than being worried about the delay.

4. No news or new update

Artboard 5 100

In these situations, your client is probably waiting for an update from their superiors and has nothing new to report to move the project ahead. This is out of your control; all you can do is remind them of the set deadlines and the importance of meeting them.

Do this for your sanity!

An unresponsive client not only causes project delays and stress but can also be mentally draining if you chase them. Here are a few things you can do to cope mentally with unresponsive clients:

a. Do not jump to conclusions.

I know it can be very frustrating to see your client become unresponsive, especially when you have some time-sensitive deadlines to meet. We tend to imagine the worst that could come out of the situation. Here is the best thing you can do for the sake of your sanity and mental health- Do not overthink and jump to any conclusions. Anything can be causing the delay, and it might not be something to do with you.

b. Keep Calm

We often panic in challenging situations and make snap decisions like- calling the client multiple times or sending emails every few hours. Your client might not appreciate it.

Trust me; you want to avoid that and try to keep yourself calm. You can do that by working on a different project, doing something you like, or even working on a passion project. This will keep you occupied and calm.

c. Try to find the root of the problem.

You can try to find what is causing the unresponsiveness, is it the email clutter, is the client on holiday, waiting for an update from supervisors, etc. This way, you know where the hold-up is, and you can find a fast-track solution to it.

E.g., If your client is not replying to your emails, you can ring them up at an appropriate time to remind them of the deadlines.

d. Remember, it is not always you.

Most of us think that something we did lead to the client becoming unresponsive. But, understand this, your clients have other things to look after, and your project might not be a priority at the point. You can be patient and wait for the client to get back to you in this situation.

5. Move on

Artboard 3 100

When you cannot help in a situation, you should move on to things like working with other clients, looking for prospects, upgrading your skills, etc. This way, you do not waste time waiting around for a client and focus your mind on something productive.

This will get them talking!

a. Send a calendar invite.

This works more often than not. Send something as simple as ‘I am sending an invite for Thursday, February 25 at 4 pm, but let me know if another time works better.’ This works only when the matter at hand needs a discussion; if the task can be completed just by sending in an email, a calendar invite is not helpful.

b. Try reaching them through various platforms.

If you think your client has a clutter of emails leading to your email getting lost, you can try reaching them over any other preferred platform that you have previously communicated on. E.g., Whatsapp, Slack, direct messaging, calls, etc. There is a 90% chance of this working and them getting back to you in a day or two.

c. Be direct and upfront.

If the client has been unresponsive for quite some time and has missed a lot of deadlines leading you to fall behind schedule, you can be direct with them and ask them if they would like to:

  • Pause the project
  • Clear any doubts that they have
  • Take a different approach
  • Would appreciate any help in taking the project forward
  • Terminate the project

By being direct and upfront, you can either find a solution to the problem or stop working with the client altogether. Either way, you move somewhere with the project.

Precaution is better than cure.

1. When setting deadlines, emphasise important ones.

Be upfront and firm about essential deadlines that dictate the execution of the project. Let your client know the consequences that the project faces because of missing the deadline. This way, your client can get as serious as you are about it.

2. Get a proper communication structure in place.

Structure every communication that goes from your end so that your client gets exactly what you mean and understands its urgency. Send each email, text or get on a call with some intention and ensure that you get a step in the right direction from this.

3. Schedule a follow-up before ending the current meeting

It is always a good practice to schedule up the next meeting before ending the current. This way, you do not have to chase your clients for their time, and you ensure that you are on schedule.

4. Get acquainted with your client’s schedule.

Knowing about your client’s working hours can help you communicate better. E.g., If your client had mentioned that their lunchtime is 1 PM, do not text, call, or schedule a meeting during that time.

Knowing your client’s schedule simply helps you to plan better.

5. Analyse your communication

If you are someone who finds themselves ghosted by your clients a lot, evaluate your communication. Ask yourself if there is something that is making them unresponsive to you. If yes, fix it.

6. Set up an email workflow in place

Set up a generic email workflow that you can later customise in case any clients become unresponsive. These emails are supposed to help you find out why your client is unresponsive. Again, set a clear communication tone to these emails and make them sound as urgent or as laid back as necessary.

Ready to use follow up email template

As promised, here is a ready-to-use workflow of follow up email for an unresponsive client that you can directly use or take as a reference to create your own.

a. Email follow-up after three days of the client becoming unresponsive.
Subject: Following up about < specification here >

Hello < First Name>,

I hope you are well.

I sent you an email about < Specification here > a few days ago, I did not hear back from you. I hope you had the time to review it. I would like to know your thoughts about the same.

Please get back to me at your earliest convenience.


< Your Name>
b. Email follow-up after a week of the client becoming unresponsive.
Subject: Important: Update needed to move the project ahead

Hello < First Name>,

I believe you might have missed a couple of emails about our project < specification here if necessary>. We are behind on our deadlines. I request you to kindly go through to move ahead with the project.

Let me know if you need any help with the same.


< Name here>
c. Email follow-up 10-days after the client becoming unresponsive.
Subject: Scheduled meeting on the < date here >, < time here>

Hello < First Name>,

Since I haven’t heard back from you for the past two weeks, I have taken the liberty to schedule a call on the < date here >, < time here>, but let me know if another time works better for you.

Please find attached the link for the same.


< Your Name>
d. Email follow-up after the day of the meeting.
Subject: Should we temporarily pause the project?

Hello < First Name>,

You did not make it to the meeting that was scheduled for yesterday.

We are behind on our project by days now and have missed a few critical deadlines. I would like to know the reason behind the lack of communication. And I want to offer you any help that I can provide to move ahead with the project.

If you would like to pause the project temporarily, please let me know, we can revisit it at a more convenient time.


< Your Name>
e. Email follow-up 25- 30 days after the client becomes unresponsive.
Subject: Let’s stop the project

Hello < First Name>,

I have been trying to get in touch with you over calls, emails, messages, and a scheduled meeting for the past month.

Since you have been unavailable, we will not be moving ahead with the project.

We can resume the project provided you have a valid reason for your unresponsiveness and unavailability. You know where to reach me.


< Your Name>

To sum it up

If your client is unresponsive after many texts, emails, calls, there is nothing that you can do to get them to respond. It is best to move on and be better prepared for any similar situations in the future.

Be wise about the people you work with; if your client is consistently unavailable, you can always choose to never work with them again. Work with people who are professional and passionate. By collaborating with them, you can create something amazing together.

How do you deal with unresponsive clients? Any tips appreciated. Comment them down below.

6 Website Design Feedback Questions You Must Start Asking Your Clients

main banner

The feedback stage is very important for digital agencies and freelancers. It’s another opportunity for you to prove your expertise and maintain the client’s trust in your abilities.

But most agencies and designers don’t properly structure this crucial part of their workflow.

Where do you start? What kind of feedback should you ask for?

Our digital agency has been guilty of this in the past. We would simply send the design to the client and ask them what they thought about it. The replies from the clients would read:

“It lacks pizzazz.”

After looking the word up in the dictionary, we learnt our lesson – to get specific feedback we need to ask questions that forced the client to be specific.

But you also need to be strategic about it.

To get feedback from clients which will help you fulfill their expectations, you need to be able to get the most relevant information from your clients.

In this article, I’m going to show you how we do this at our agency, by framing the questions properly, anchoring them in goals, and keeping the feedback free of vague feelings.
ask about website

Ask About Website’s Ability to Engage, Not First Impressions

Most web designers worth their salt know that a website must clearly communicate its value to a user in 10 seconds or so.


So that the user remains engaged with the website and doesn’t bounce back to the search engine results page or wherever they came from.

But the agencies are guilty of not seeing the forest for the trees. During the feedback, they ask the clients about their first impressions, about doing a blink test, and how they feel after spending 5 seconds on the website. This results in vague replies from the clients:

“It’s good but I think it lacks animations like on our competitor’s website.”

“We liked it but our VP of Comm. thinks that the primary color isn’t going to work out.”

“The website is as per our requirements. But shouldn’t we use the parallax effect somewhere to attract attention and make it catchy?”

Such comments completely miss the point:

Having animations like the competitors, attractive color schemes, and parallax effects isn’t the goal!

The goal is to keep the users engaged with the website. The website should be good enough to keep the users browsing it. It doesn’t need to do more than that, let alone be the best-looking website in the niche.

Don’t ask:

What was your first thought when you saw the design?

Do ask:

Once you were on the website, did you want to keep browsing it? Why/Why not?

keep focus on target

Keep the Focus on Target Audience

So should you completely discard how the client’s feel about the website design?

Well, you won’t really be able to escape it. If the client’s feel strongly about something, they’ll make sure to point it out to you even if you aren’t explicitly asking for feedback on it.

But asking clients to bring their feelings into the feedback process can lead to comments like:

I don’t feel this style of design at all
This shade of red in the hero section is marvellous in my opinion
I feel that the website can look more futuristic but my cofounder feels that you’ve nailed the brief
On the surface, this kind of feedback actually looks good. You believe that you’re getting reliable information to work with.

But this kind of feedback, based on the client’s feelings, is neither accurate nor useful.

Firstly, feelings are completely subjective and circumstantial. They depend on the current mood, immediate environment, and existing knowledge.

Secondly, the website should work for the users. It has been designed with the end users in mind. It should attract, engage, and persuade them. The end users should be able to form an emotional connection with the website. That’s the most important bit.

So even before your clients can get into how they feel about the website design, ask them if the website design will work well for their users.

Don’t ask:

  • How do you feel about the website’s design?
  • What does the design make you feel?

Do ask:

Will the website design resonate with your users?

websit design goal

Anchor Your Questions in Website Design Goals

Before you even start the website design project, you should be clear about the goals of the website.

What is the design supposed to do?

Goals are the primary constraints that shape our creativity. Unbound creativity is useless to the client as well as to the designer.

In my experience, design clients always have two goals in mind: one for what the website is supposed to do for the business and one for what the website is supposed to do for the stakeholders.

Here are some examples of business and stakeholder goals.

Business goals

The website should:

  • Get product sales
  • Get contact form submissions
  • Show information about the business’s new initiative

Stakeholder goals

The website should:

  • Show how our business is more eco-friendly than the competition
  • Showcase our brand’s legacy
  • Highlight the culture of inclusivity at our startup
  • Both the goals are equally important. Satisfying these goals is necessary AND sufficient to complete the project to a good client’s satisfaction.

Stop asking for feedback on vague things that won’t move the needle for these goals and start framing all feedback in the context of these goals.

Don’t ask:

  • Did you like the design of the website?
  • Did you like the colors of the website?
  • Does the header menu look good?

Do ask:

  • Is the design fulfilling the goals we had agreed upon?
  • For example: Does the website design draw focus on your company’s inclusive culture?

Use the Feedback Questions to Build Client’s Perspective

Creativity and cleverness have their place when we want to persuade the user to stay on the website. But that has already been taken care of.

We also know that the website will fulfill the client’s goals.

Now, the website design should present the website’s messaging in a manner that is clear and precise. This will put the user one step closer to taking the actions that we want them to take.

Most clients don’t know this and assume that the design should try to be clever or creative throughout. They’re stuck on wanting the website to be attractive instead of valuable.

You can prevent them from going down this road by asking the right questions here.

Do ask:

  • Is everything on the website clear and self-explanatory? Did you need help understanding something?
  • Is the messaging and main content clear to you?
  • Do the images on the website adequately support the messaging and main content?

do not make client work

Don’t Make the Client Do Your Work

Many designers think of the feedback process as getting the design proofed by the client.

They complete what they believe their “tasks” are and send the design to the clients assuming that if they missed out on something the client will point it out. And if the client doesn’t point out something, then they didn’t miss anything.

Making the clients do YOUR work during feedback has serious consequences.

Firstly, clients finding out something that you missed is quite bad. Not only does this make you look like an amateur, it is also the fastest way to lose client’s trust in your expertise and knowledge.

Secondly, it’s an invitation for bad clients to start micromanaging your work. From then on, you can be sure that they’ll start telling you how to do things.

Always remember that the client hired you because you have the design expertise. They came to you with a problem and now it’s your job to solve it.

As such, they don’t know what’s the best approach, what to put on the website, and what not to put.

You should understand what the design needs to accomplish the client’s goals, limit the design to those elements, and make those elements clear so that the user can take the desired action.

Don’t ask:

  • Is there anything missing from the design?
  • Are there elements you don’t want to see in the design?

Do ask:

  • Did anything about the design prevent you from completing an action?
  • Was it easy to use the navigation to access any information that you might want to access?

smaller screen

Ask Relevant Questions for Smaller Screens

In the last 12 months, mobile usage has maintained an edge over desktop usage by 5%.

Mobile website design is a tad more important than desktop.

So when you take feedback, make sure that you include some mobile-specific questions as well.

You can do this for all the questions from the previous sections:

  • Once you were on the mobile website, did you want to keep browsing it? Why/Why not?
  • Will the mobile website design resonate with your users? And so on.

But you also need to include some questions for interactions that are unique to the mobile.

Ask the clients to compare mobile design to desktop design as well.

Do ask:

  • Is the text legible on mobile?
  • Are you able to use all the buttons and interactive elements on mobile with ease?
  • Did you have trouble understanding something on mobile that was easy to understand on desktop?
  • Is the mobile layout forcing some information out that improved your experience on the desktop website?

list of questions

Steal this List of Feedback Questions

Always remember that your clients are super busy. When you ask them to give feedback, they’ll delay it because they don’t have time and they don’t know where to start.

Also, when they do finally sit down to give feedback, they’ll be looking for ALL the things that they believe are off or wrong. Changing the footer colors will help no one, it’ll just delay the project.

Such delays, caused by client’s lack of time and them focusing on the wrong things, will harm your productivity and hamper your agency’s growth.

But by giving them a list of website design feedback questions, you’re making their job easier. The list of questions doubles as a checklist they can quickly run through. They realize that 6-10 questions will take them half an hour at most and they can schedule that task for the next day.

They also don’t need to think about what they have to give feedback on, eliminating the mental gymnastics. And since you must’ve already taken care of the things that you ask about, the client will be reassured that you’ve thought of everything that’s important.

This will revitalize their trust in you and prevent them from focusing on things like footer color or header menu font size.

So steal this list and make the feedback process a stress-free time for everyone.

Do you have suggestions for what we should include in the list of questions? Let me know in the comments below.