Skip to content

browser-analysis.md

Latest commit

 

History

History
48 lines (31 loc) · 3.35 KB

browser-analysis.md

File metadata and controls

48 lines (31 loc) · 3.35 KB
Raw

Browser Compatibility Analysis Report

Project: Website Analysis Date: 16/10/2025 Analyst: Reedham

Testing Scope

Category Details
Websites NeverSSL, GitHub, YouTube
Viewports Desktop (1920x1080), Tablet (768x1024), Mobile (390x844)
  1. There is only a single visible difference that is the URL, HTTP website has http:// URL and HTTPS has https:// URL otherwise there is no visible difference between the request headers in HTTP and HTTPS website from the user end but a key difference between them is that in HTTP website the request header is easily visible to anyone means apart from the user and the developer server it is visible to anyone snooping on the network whereas on the other side in HTTPS website the data of the request header is encrypted and passed and can be decrypted by the server only, anyone who attacks the server cannot easily get the data.

In both HTTP and HTTPS websites we can see the actual data as a user but from the view of anyone random who is snooping into the network will see the actual data only in the case of HTTP website and in the case of HTTPS website he will only see encrypted data.

HTTPS is more secure than HTTP because:

  1. Encryption: HTTPS uses Transfer Layer Protocol also known as SSL which encrypts all the communication so even if someone sneeks into the network they will only see some jumbled text, only browser and the server have the keys to decrypt it whereas on the other side HTTP website does not have any encryption and if someone sneeks into the network then he can see everything as plain text meaning he can even see your passwords and every bit of data.

  2. Authentication: HTTPS websites have SSL/TLS certificate which is checked by the browser if it the same website which it claims to be, before we provide any data to that website keeping the data safe and secure whereas there is no such system in HTTP websites so any random person can create a fake copy of the website and you will open that website without even knowing whether it is fake or legimate and you will leak your important data.

  3. Integrity: HTTPS creates a secure Hash or digital fingerprint of your data so during the transit from your end to the server's end if even a single bit of data is changed then the fingerprints won't match and then the browser will warn us about the malicious activity whereas in HTTP there is no such system so a hacker can easily alter your data, passwords, everything and you won't even get to know about it.

  1. Total Number of Requests generated: NeverSSL: 3-4 GitHub: Around 150 YouTube: 250-300 The number of requests for GitHub and YouTube vary significantly if some activity is done on these websites.

Resources loaded: NeverSSL: A single JS file GitHub: TS,JS,CSS,BootStrap YouTube: JS,AppShell,ServiceWorker,etc.

YouTube made the most requests because it has the more data than other two that needs to be requested from the server before loading it on the website.

  1. Total load time: NeverSSL: less than 1 sec GitHub: 2-4 secs YouTube: 5-6 secs

Request of the type document takes the highest time to load because it is the first request that the browser makes as the document contains all the instructions to other assets like CSS,JS,etc.