How to reduce JavaScript HTTP requests from AjaxControlToolkit components?

I’m having trouble with the ASP.NET Ajax Control Toolkit. It’s easy to use, but it’s not scaling well on my page. I’ve got two date input fields, each with a TextBox and CalendarExtender. This setup is causing 11 separate JavaScript calls to ScriptResource.axd.

Is there a way to make this more efficient? The current setup seems excessive. Are there any alternatives to the Ajax Control Toolkit that offer similar features but with better performance and customization options? I’m looking for something that’s more scalable and straightforward, but I don’t want to build everything from scratch.

Has anyone else run into this issue? What solutions have you found that work well with .NET? Any advice would be appreciated!

I’ve encountered similar issues with the Ajax Control Toolkit. One effective approach is to use the ScriptManager’s CompositeScript feature to combine multiple script resources into a single HTTP request, which significantly reduces overhead. Another option worth exploring is switching to a more lightweight library such as Vanilla JavaScript or a minimalist datepicker plugin, as these typically generate fewer dependencies and HTTP requests. Additionally, implementing lazy loading for calendar components can improve initial page load times by only loading scripts upon user interaction. As always, ensure thorough testing to maintain compatibility with your existing codebase.

yo, those ajax toolkit requests can be a pain. i’ve dealt with that too. have u tried bundling ur scripts? it can help cut down on those pesky http calls. also, maybe look into jquery ui for datepickers - it’s pretty solid and less bloated. just my 2 cents

Man, I feel your pain with those AjaxControlToolkit issues. Been there, done that. Here’s what worked for me:

I ditched the toolkit altogether and went with pure JavaScript. It’s a bit more work upfront, but the payoff is huge. I built a simple datepicker using vanilla JS and CSS. No extra HTTP requests, just one file.

For AJAX calls, I switched to using the Fetch API. It’s built into modern browsers and doesn’t need any extra libraries. Plus, it’s way more flexible than the old toolkit stuff.

The best part? My page load times dropped dramatically. Users were much happier, and I had way more control over the UI. It took some time to refactor, but it was totally worth it.

If you’re not ready to go full vanilla JS, maybe look into React or Vue for your components. They’re pretty lightweight and give you a lot of power without the bloat.