Read the article
Start with the layout. One page, one column, a plain font in a readable size, and margins that leave white space. Fancy templates with icons, bars showing skill levels and two columns often confuse the software some companies use to read resumes, and they confuse human readers too. Save it as a PDF unless asked for another format, and name the file with your name.
Put your contact details at the top: name, phone, email and, if it is up to date, a LinkedIn link or a code repository. Use an email address that looks professional. A full postal address is not needed; your city is enough.
For a fresher, education and projects come next, usually in that order, or projects first if they are your strongest part. For education, list your degree, college, year and marks or CGPA, in the same format throughout. If you have a strong result from school, one line is enough.
Projects deserve the most careful writing. For each, give a name and two lines. The first says what it is and who it is for: 'A stock-alert app for small shops that warns the owner before an item runs out.' The second says what you did and with what: 'I designed the database and wrote the alert logic in Python with a SQLite database.' Avoid long lists of technologies and claims such as 'improved efficiency by 40%' unless you measured it. Everything on the page can be asked about.
Skills: list the ones you could be asked questions about on the day. A list of fifteen tools you have touched once invites a test you will not enjoy. A short, honest list of five is stronger.
Certificates, internships, competitions and volunteering come after, each in a line. Include them if they show something relevant: a course you finished, a hackathon you took part in, a role in a college club where you organised something. Say what you did, not just the title.
What to cut: the objective statement ('seeking a challenging position') that says nothing; a photograph, unless a company specifically asks for it; a long list of hobbies; your father's name and other personal details that are not needed; and anything you could not talk about for two minutes.
Check for small mistakes: spelling, tense, inconsistent dates and a different font in one line. These are easy for a recruiter to notice and suggest carelessness.
Finally, ask someone who has hired freshers, or a senior who was recently placed, to read it and tell you what they noticed first. Fix that, and then keep one version for each kind of role, rather than sending the same page everywhere.