Site entry page loading slow

I am testing PageBlaster (free version). After running for almost a day I noticed that the home page (first time enter the site domain) loads slower while the rest of the pages load faster, compared to the pre-pageblaster performance.

To make it more clear:

I installed pageblaster (free) on two sites, one with DSLocalizator installed, one without. The one without DSLocalizator installed works fine (including the www.site1.com page). The one with DSLocalizator  www.site2.com loads very slow (much slower than before). But if you click the home tab link (something like http://www.site2.com/Home/tabid/73/language/en-US/default.aspx ) instead of typing in the site url www.site2.com , it loads fast just as all the other pages.

Any clue why this is happening?  Most of my search engine indexed pages link to the www.site2.com and I really hope this default page could perform better...

 Ok I just realized that it's not only the entry page, actually any pages as long as there is no language parameters load slower compared to those with language parameters. For example, http://www.site2.com/Category1/tabid/173/language/en-US/default.aspx would load faster than http://www.site2.com/Category1/tabid/173/default.aspx.

So this is more like a DSLocalizator related issue. Wonder if Apollo users experience the same.

I would need to see a trace file for the site with the slowness to understand what may be happening.

You can enable tracing in the Snapsis.pageBlaster.config file by setting trace level="Debug" and then restart the application.

Another thing to be aware of is that if you just refresh a page more than once it may clear the cache because the browser will send the same signal as when you hold CTRL and refresh.

Another thing you can do is monitor the response headers with something like this page:

http://web-sniffer.net/

If you enter your Url you should see a header that looks like this on the first test:

X-Snapsis-PageBlaster:

v:2.3.0;c:-;x:+;r:+

The c:- means that the page was not cached, which is normal the first time you run the test. On the next test it should have c:m which means it came from memory.

It may also have c:d which means it was not in memory but was in the disk cache and added back to memory.

Thanks for the fast response.

I tried to enable "debug" but after I restarted the application the site got crashed. :-( So I changed it back the site started working again.

Then I used http://web-sniffer.net , I tested for 3 times and the results are the same:

X-Snapsis-PageBlaster: v:2.2.4;c:-;x:-;r:-

I also made some changes for the home page and the www.site2.com (without language parameter) reflected the changes right away (even though loaded slow) but http://www.site2.com/Home/tabid/73/language/en-US/default.aspx (with language parameter) did not reflect the changes until I gave it a force refresh.

So it looks like pages without language parameters ( actually I am only concerned the default loading page that uses domain name) do not get cached with DSLocalizator when using PageBlaster.

I think I have seen something like this before. The localizer puts a language variable on the querystring but no tabid for the home page so the rule for excluding any paths that do not have tabid kicks in.

Try changing the line in the config file that looks like this:

<pathpattern="\?(?!tabid)"excludeFrom="All"/>

To this:

<pathpattern="\?(?!tabid|language)"excludeFrom="All"/>

Great it works like a charm...

Thanks you.