We've developed the first version of our website and going to lunch it and introduce it to a crowd. How do we know which part of our work has weakness and how we should correct it?
You can of course use analytics that will give you statistics, but will not answer "Why?". Gathering Customer Feedback is crucial and You have to be preprared for low response rates. For better understanding of Customers' interactions with Your site You can use tracking/heatmap solutions (i.e. Crazy Egg or Hotjar). But most important is to define goals and identify steps that lead to them - what do You expect Customer will do or act like? What needs to be done to acheive it? Then start monitor those steps, gather feedback, mae changes and see if this works looking at stats.
Simple. Provide a survey and ask site visitors to inform you of their ux through a short list of strategic exit questions. Need assistance formulating your survey questions, please feel free to book a call with me!
This is why you need goals for your website. Otherwise you don't know if it is working or not.
The goals should be about the website itself, not traffic to it. In other words, it can't be volume of visits etc., as that determines the success of your traffic generation efforts, not the website.
What are the actions people can take on your website? What do you want people to do? Most importantly: what is in it for them? What does a person get back for spending time on your website?
Track activities (the more visitor-centric the better) such as clicks on buttons, paper/info downloads, newsletter subscriptions, etc. The more you have to offer the client, the better tracking you will get.
You can see where people are dropping off from in Google Analytics. You can look at the overall conversion rate and see if it's effective. I don't recommend spending much before doing some best-practices oriented conversion rate optimization. I can help with that.
Aside from getting visitor feedback, usability testing can help catch a great many issues. When it comes to website usage, many visitors/customers might be able to tell you that something isn't right, but they may not be able to pinpoint what that "something" is. Usability analysts know what to look for and know how to spot pitfalls.
If I had to rephrase your question, you are trying to understand what part of the website were people able to understand, which parts were they not. Sure, analytics, heatmaps etc will help you a lot with it but nothing is better than actually talking to some people. This could be over chat where you could ask people if they understood what the service was about but is best done over call - I don't know your business to tell you how to get people on call but nothing beats the density and richness of information and surrounding context you can get when you get users on a call.