This is what I see at that URL:
This is almost impossible for Netlify to troubleshoot. Part of the issue here is that we are trying to compare apples with “secret apples only you can see” (and I’m joking here to be clear). I’m trying to explain why we are having difficulty troubleshooting. We cannot see your local deployment so we cannot do any comparison. We cannot compare the published site to a local version on your computer which we have no access to.
Again, Netlify doesn’t modify the files which are published unless asset optimization is enabled. However, it is not enabled so we wouldn’t modify any files:
We only serve the built content as is without changes. Even with optimization, the changes should be to whitespaces in the code. There should be no visible difference to a displayed page with asset optimization enabled (and again, it isn’t enabled anyway).
So the next step will be to see if there are difference in your locally build files and the ones hosted on Netlify. You can download the exact files uploaded for any successful deployment using the “download deploy” button shown in the following screenshot:
Then you can compare the deploy versions of your files with the local versions to see if there is a difference between the two (using
diff for example). If you do find differences, we can research why the local build of the site doesn’t match the build on Netlify. Please let us know if you do find differences in the two builds.
If there are no differences, this could be something as simple as the default zoom preference being set differently for the local URL then it is for the published one. This would be a setting in the browser itself and completely unrelated to Netlify.
To summarize, we can suggest ways to troubleshoot this but (without the same access that you have to the locally deployed version) all we can do is give guidance about how to troubleshoot. This, again, is because we lack the required information to be able to troubleshoot ourselves.