This project is read-only.

Change Set [10244e5873fd ] PageLoad Speed

Feb 22, 2012 at 6:31 AM

Hello All,

I have the latest change set 10244e5873fd on my test website below:

When running a Page Speed test I get the following:

Page Speed Score of 70 (out of 100)

  • Medium priority. These suggestions may represent smaller wins or much more work to implement. You should address this item next:
    Enable compression
  • Low priority. These suggestions represent the smallest wins. You should only be concerned with these items after you've handled the higher-priority ones:
    Inline Small JavaScript, Minify HTML

Rtur said for the

This puppy scores 100/100 on page speed with properly configured IIS.

Rtur how did you configured the IIS to get 100/100 ?

When I tried to enable the compression in the web.config file I get an Internal Server 500 error.

Would like to know how you "Properly Configured IIS" to get the 100/100 ?

Also great job on the latest change set!  Very noticeable and increase Page Speed from the previous change sets.

Just would like to get it to 100/100 like you did for


Brian Davis

Feb 22, 2012 at 3:23 PM

Local IIS 7.5, all defaults, used with page speed add-in for FireBug.

Feb 22, 2012 at 5:35 PM
rtur wrote:

Local IIS 7.5, all defaults, used with page speed add-in for FireBug.

I'm not familiar with FireBug, but isn't that skewing the results? Shouldn't the test be ran on a "stock" browser?

Feb 22, 2012 at 8:34 PM

Take a look at this video - that's pretty much same I did with BE, on both pagespeed and yslow. Problem with online test is that you might run into restrictions with your provider, for example mine won't let me turn on "keep alive" and it costs plenty of points. Others can run into different issues, depending on what IIS they use and how it configured.

Feb 22, 2012 at 9:37 PM

Well I guess my question, and partially kbdavis07's as well, is what's the best configuration for IIS? I know it's dependent on the server and if it's shared hosting or not, but I'm scoring an 86/100 on the release while kbdavis07 is scoring 70/100 on the latest change set that you scored 100/100. Is there a "baseline optimization" that should be done to IIS 7.5 if users have access to it and can tweak it?

Feb 22, 2012 at 10:50 PM

The main issue now is how to enable Gzip on shared hosting servers with only application level settings in the web.config file.

I been experimenting with different settings and so far no luck on that end.

But, I found out if you use the CDN

It increases the Page Speed greatly.

Its now at:

Page Speed Score of 95 (out of 100)

My other website:

Using BE gets the following:

Page Speed Score of 93 (out of 100)

So with the newest change set it adds +2 points 

Also I notice a big different in results from the online speed test


The FireBug Plugin

for FireFox results

In those results the gets (91/100)

                 gets (87/100)


So the issue now with BE is the server side settings and not BE itself.

Would be nice to figure out an universal web.config settings that would work on the most restrictive web servers (Shared Hosting) that

would enable Gzip.

This way when users upload BE to their servers there is no need for them to mess around with it to get the best PageSpeed and load performance.

Just Upload and Go :)

But, until we can find that solution users can

1. Use

2. Configure their own servers to use Gzip

If anyone has any questions about using please let me know.

If anyone figures out how to enable Gzip using only the web.config settings please let us know here :)

Thanks for all of the BE Developers on their great work on BE so far!!!!

BE has came along way from BE release to the current change set.


Brian Davis

Feb 22, 2012 at 10:54 PM

Here's whats left on what needs to be compressed:


Compressing the following resources with gzip could reduce their transfer size by 39.7KiB (73% reduction).

Feb 22, 2012 at 10:59 PM

I was only getting 72/100, but then I added the following to the web.config, and that raised the score by about 10:

      <clientCache cacheControlMode="UseMaxAge" cacheControlMaxAge="365.00:00:00" />
      <remove fileExtension=".mp4" />
      <remove fileExtension=".gif" />
      <remove fileExtension=".htm" />
      <remove fileExtension=".html" />
      <remove fileExtension=".jpeg" />
      <remove fileExtension=".jpg" />
      <remove fileExtension=".js" />
      <remove fileExtension=".png" />
      <remove fileExtension=".txt" />
      <mimeMap fileExtension=".mp4" mimeType="video/mp4" />
      <mimeMap fileExtension=".gif" mimeType="image/gif" />
      <mimeMap fileExtension=".htm" mimeType="text/html" />
      <mimeMap fileExtension=".html" mimeType="text/html" />
      <mimeMap fileExtension=".jpeg" mimeType="image/jpeg" />
      <mimeMap fileExtension=".jpg" mimeType="image/jpeg" />
      <mimeMap fileExtension=".js" mimeType="application/x-javascript" />
      <mimeMap fileExtension=".png" mimeType="image/png" />
      <mimeMap fileExtension=".txt" mimeType="text/plain" />

Since you guys already had a score in the 80s (or 90s), I'm guessing that these settings were already enabled on your web servers.

I was unable to use gzip properly using my shared hosting plan (I'm starting to think its not even installed).  However, I got around that issue by passing scripts via tha js.axd handler that comes with blog engine.  So, for example, I changed the following:

<script language="javascript" type="text/javascript" src="/myuploads/autocomplete.js"></script>


<script language="javascript" type="text/javascript" src="/js.axd?path=%2fmyuploads%2fautocomplete.js&minify="></script>

and that compressed my script and raised the score a little bit.

Also, I've noticed that the web method of getting the score doesn't always change (it appears to use a cache or some sorts), while the scores in the google and firebug dev tools update as soon as I make the changes on my site.

Feb 25, 2012 at 9:30 AM
Edited Feb 25, 2012 at 9:53 AM

Hi Brian, 

Thanks for the tip on cloudfare, I'm still using BE 2, ran Google Page Speed and got score of 90, signed up to cloudfare and it's now on 100%.

Quite happy with this as I'm stuck with .NET 3.5 hosting for a while and can't use BE 2.5 (or versions thereafter with the new change set).



Just ran it again and got 96 (homepage), I'm guessing that some fluctuation in results is normal.

Post view not so good (75), but it looks like the performance hit is down to the images, no doubt some careful housekeeping can improve it.