Performance is not quoted. Google's performance score is a timing taken on a simulated slow phone, and it moves between runs of an unchanged page — in one test run for this practice, by 32 points between two runs seven minutes apart. A single performance figure says more about the moment of the test than about the site.
A reading is a date, not a promise. Gaure Mdee's site scored 100 for best practices on 24 September and 96 the next day, with nothing on the site changed. Google's test had begun downloading a 35 MB film clip meant for the page's second scene, and the download was cut off when the test ended — which the audit counts as an error. The clip now loads only once a visitor starts to scroll or tap, which also spares anyone on mobile data a film they may never reach. Re-read after the change: 100.
Some of what a site sends is added by its host. The hosting platform inserts a small bot-detection script into three of these sites as they are served. Their security policies refuse to run it, which leaves one line in the browser console. It does not affect the scores above and is disclosed here rather than hidden.
A header grade is not a security audit. The largest real risks to a website are rarely in its headers: a takeover of the hosting or domain account, email sent in the owner's name, a contact form flooded until real enquiries are buried. Those are covered in the security practice, and they are where an engagement starts.
Code is marked, not locked. Each site's scripts ship minified and obfuscated, as a mark of ownership and a deterrent to casual copying. Anything a browser runs can be read by the person running it; this is not protection, and it is not sold as protection.