How to write a bug report for a website?

Question

Software testing

Hello.
I would like to clarify with specialists who are already involved in testing or "who is in the subject." Actually the question is in the topic, I will concretize it a little with my comments. Dropped the following as a test:

Make a bag report for the site: xxx. Pay attention to: what defects were found and the correctness of their registration. Send the result in text format (word, docs).

Junior QA vacancy, I have not come across testing before, but everyone starts somewhere. After googling and reading habr, I threw in an approximate bug report template. I decided to ask for help, for several reasons:

1. I liked the conditions. Quite an interesting area in IT with the opportunity to further grow in the direction that you like more (I mean soft / hard skill)
   
2. The bug report template that I compiled is most likely not ideal. I took from articles where people have already described working with full-fledged bug tracking systems (in my case, there is none and the task was given apparently to check a common understanding). In addition, I did not see a specific bash report for a web application.
   

Actually an exemplary bug report template:

• header
  
• Description:
  
  • Playback steps
    
  • Result
    
  • Waiting for the result
    
  
  
• Environment (in my case, browsers (+ version) in which I checked)
  
• Severity (s1...s5)
  
• Priority (p1...p3), I don't know. Many say that it is filled either by a team lead or a manager. For the tester, the field is optional, right?
  
• Author
  

Do I need to add or remove something (Referring to site testing)? Tell me the procedure, what is checked first of all, whether it is necessary to use any third-party services, check the site itself for functionality, usability or something else.
I would really appreciate some tips :)

Answer 1

you yourself described normas as a whole
, usually the sales funnel is checked (well, targeted actions) - it’s useless if the user doesn’t register, doesn’t log in, doesn’t add to the cart, doesn’t search
then SEO, if there is a dependence on it (it doesn’t always happen)
then aesthetics
priority - yes, team lead, product, project, owner ))

Answer 2

The pattern is generally good. I would add a screenshot / video of the error, the date the error was registered. Errors can be in the code, check the code through the browser console, there may be hints (I had it at 1 interview). Also check the correctness of the mobile layout, transitions between pages, etc.