CDNs (Content Delivery Networks) are great to speed up website performances, but they are a mess when you are testing your website on your development machine.
Another problem may arise if you want to change your CDN to another one. Do yoy have to replace all URLs in all your pages?
In this article I'll show you a clever and definitive solution to avoid hardcoding the CDN URLs in your HTML markup.

Read all the article...

Posting links on social media (Facebook, Twitter, etc..) its a daily practice, usually blog articles, new products or a description of your professional services.
The problem is that often these links look graphically disappointing, so they catch very few visitors.

I promise you that after reading this article the appearance of your links will no longer be left to chance, you will have full control over the images and descriptive texts.

Read all the article...

There is a well-known bug on Internet Explorer 10 for WIndows Phone 8 that avoids responsive web sites to display correctly. The cause is that Internet Explorer 10 doesn't differentiate device width from viewport width, and thus doesn't properly apply the media queries in your favorite responsive CSS framework.
You can find many fixes on the client side, but if you're using ASP.NET, you have the chance to fix it server side with only few lines of code.

Read all the article...

Lazy loading applied to a web page is an excellent technique when all contents aren't immediately visible and you want to speed up page rendering.
A perfect candidate for this method are image galleries with many items, only the first image is visible when the page loads, other images will be visible only if the user decides to browse them.
This technique sounds great, but has a big SEO problem: search engine crawlers does not execute scripts, they only analyze HTML markup, so all the code that renders images dynamically is totally ignored along with images and captions.

Here're four solutions and, as often happens, the best is the last one.

Read all the article...

In this article we will see how to precisely control the cache of the client (the browser of your PC, for example) in order to avoid the transmission of data from the server when the client already owns them. The ASP.NET server already has systems for data caching, for example to avoid repeating the same database query; would not it be nice not to avoid sending these data to avoid bandwidth consumption?

The technique is called conditional GET and uses the 304 HTTP status code and is particularly useful when data are dynamically generated on the server side and change during the time.

Read all the article...