![]() If you had say a million requests, which is not unheard of if you consider that this overhead is added to every page, then you are looking at around 0.6GB of bandwidth and that's before you add up extra bandwidth usage from the images and Android/Chrome/Windows XML/JSON configuration files. ![]() 650 Bytes for every page can add up to a fair amount of bandwidth, especially if you have a large number of requests coming into your site. You can support all of it, none of it or anything in between. However, you should be using GZip compression for transferring your HTML pages over the internet (I'll be covering GZip compression in a subsequent post) so when compressed we are talking around 650 Bytes if you include everything or around 465 Bytes if you remove support for Apple splash screens.Īt the end of the day it's a trade off and I'll leave making that decision up to you. Those 24 lines take up around 2.8KB, if you decide to support everything or around 1.4KB if you skip support for Apple splash screens which takes about half the space due to its extremely verbose meta tags. All we are really trying to do is set an icon for our site! Performance and Size Trade-Off Take a moment to let the insanity of this situation settle in. That is 30 files and almost as many lines of code if you decide to have your files in a nice separate folder. Now don't be too scared, there are only 24 lines that you need, the rest is all comments describing what each line is for, which I'll go through it in the rest of this post. Now you can add all these files to the root directory of your site and have a really messy project or you can add the files to a /content/icons folder in your project and add the following link and meta tags to the head section of your HTML pages: The list of all files required to support favicon's and splash screen images on all devices. So without further ado, here is a list of files that you need to add to support all the different devices that can access your site: This blog post tries to be as comprehensive as possible in explaining the absolute madness that is the internet favicon and its related 'bits' for want of a better word. It provides the minimum amount of code required on top of the default MVC template provided by Microsoft. Its a professional ASP.NET MVC template for building secure, fast, robust and adaptable web applications or sites. Some of them go even further and even allow you to specify splash screens for when your page is loading or an RSS feed URL for the latest updates from your site.Ī brain dump of all my knowledge regarding favicon's and many other ASP.NET MVC features can be found in the ASP.NET Core Boilerplate project on GitHub. Most of them will require some kind of icon or image to display for your website. These days there is a ridiculous range of devices that can access your website from phone and desktop browsers to phone apps, operating systems and search engine bots. Building RSS/Atom Feeds for ASP.NET MVC.Dynamically Generating Robots.txt Using ASP.NET MVC.Content Security Policy (CSP) for ASP.NET MVC. ![]()
0 Comments
Leave a Reply. |