Comments on: 101 on HTTPS Web Site Performance Impact

By: registry cleaner reviews

registry cleaner reviews — Sun, 02 May 2010 05:54:17 +0000

This is my first time i visit have visited here. I found many interesting stuffs in your article. Well-done!

By: Création site internet bretagne

Création site internet bretagne — Sun, 25 Apr 2010 01:24:19 +0000

Création site internet bretagne…

Merci pour cet article intéressant. Bien à vous…….

By: How to analyze and speed up content rich web sites likes www.utah.travel in minutes Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog)

Tue, 16 Mar 2010 02:03:46 +0000

[...] For completeness: We also see DNS Time and Connect Time. DNS Time is the time it takes to lookup a domain name. If you embed resources from many different domains this might become a problem. This is often seen on sites that host multiple external ads or include scripts from different external locations. Connect Time is the time it takes to establish a physical connection to the server. This depends on the number of domains involved as well as whether you use HTTP or HTTPS. The HTTPS Handshake is accounted to the Connect Time. For more information on HTTP/HTTPS overhead check out my blog about 101 on HTTPS Performance Impact [...]

By: dynaTrace AJAX Edition 1.6 available for public download Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog)

Tue, 09 Mar 2010 15:06:20 +0000

[...] Network Resource Issues: 101 on HTTPs Web Site Performance Impact [...]

By: telecharger sonnerie gratuite

telecharger sonnerie gratuite — Mon, 01 Mar 2010 06:50:46 +0000

You know, i was really impress by your article. It is what i need. Thanks so much for what you have shared.

By: Week 2 – The many faces of end-user experience monitoring Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog)

Mon, 18 Jan 2010 10:17:49 +0000

[...] The network times should be split up into wait time (the delay until a browser connection available), DNS lookup time, transfer time and server time. This is especially useful in diagnosing network related problems. Further we want to see HTTP Headesr to find improper caching configuration or problems like HTTPS related connection problems. [...]

By: Web site performance team

Web site performance team — Mon, 11 Jan 2010 11:23:14 +0000

In fact mixed content one one page isn’t a good idea either. To be more exact, it’s really bad when your visitors/users are not technicians as browser alerts make them feel unprotected. My suggestion is to embed graphics into HTML or use CSS sprites on HTTPS pages. Also it makes sense to cut out graphic design from secure pages.

By: Clay Lenhart

Clay Lenhart — Wed, 11 Nov 2009 04:07:14 +0000

You can combine all your images into one image file and use CSS sprites to display them.

http://css-tricks.com/css-sprites/

By: Tamas

Tamas — Tue, 10 Nov 2009 07:52:07 +0000

@Thrull:
You know it, I know it, but by default eg. tomcat does not set the session cookie as secure, thus they are shared.

I agree with you; it is better not annoy the user with useless warnings.

By: thrull

thrull — Mon, 09 Nov 2009 11:30:13 +0000

@Tamas: Cookies with attribute “Secure” will not be shared beetween http/https connections so this is not an argument. Anyway – using http content on https is not an option (security warnings = tons of user complains).