# ClientTimingHelper.InitClientTimings for WebForms?

**URL:** <https://community.miniprofiler.com/t/clienttiminghelper-initclienttimings-for-webforms/118>\
**Category:** uncategorized\
**Created:** [June 15, 2012, 7:08am UTC](https://community.miniprofiler.com/t/clienttiminghelper-initclienttimings-for-webforms/118 "2012-06-15T07:08:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kent\_Fehribach](https://avatars.discourse-cdn.com/v4/letter/k/a9a28c/32.png) [@Kent\_Fehribach](https://community.miniprofiler.com/u/Kent_Fehribach)\
**Post date:** [June 15, 2012, 7:08am UTC](https://community.miniprofiler.com/t/clienttiminghelper-initclienttimings-for-webforms/118/1 "2012-06-15T07:08:33Z")

</div>

It looks like the only reason that InitClientTimings expects a WebBasePage is because it is an extension method. It seems like this limits the ClientTimings to only Razor based pages and excludes WebForms. Are there other implications to this or if we add a WebForm (System.Web.UI.Control) implementation would that be enough to support client timings in WebForms?

---

<div class="post-metadata">

**Author:** ![sam](https://sea2.discourse-cdn.com/flex016/user_avatar/community.miniprofiler.com/sam/32/377_2.png) [@sam](https://community.miniprofiler.com/u/sam)\
**Post date:** [June 21, 2012, 2:45pm UTC](https://community.miniprofiler.com/t/clienttiminghelper-initclienttimings-for-webforms/118/2 "2012-06-21T14:45:30Z")

</div>

This would be a bug then, changing it to one. There should be no arbitrary restrictions here for web forms