Objects already stop rendering as soon as they're off-screen. If anything, I think the "Object is on-screen" condtions could actually be slowing it down. Every time that condition is checked, Construct has to loop through each instance of the object to determine if it's on screen. If there were 1000 tiles, that would be 1000 loops each time the "Object is on-screen" condition was checked.
I don't know if that's actually you're problem or not, but I'd suggest having only one event with the "Object is on screen" condition and then placing all the events that currently use the condition as subevents to said event.