# If the graphics won't be changing size, you can even make them bitmaps. That way, they barely require any processing, no matter how detailed they are.
# This is because vector graphics are calculated and drawn in real-time every frame. Every line, fill, gradient, and layer needs to be figured out. Bitmap images are simply copied from memory.
# Note: Always put your images into symbols. Never use images directly in an animation. They won't tween anyway.
# When slow-down IS caused by code, it's usually because of loops. Such as when checking for collisions or searching for something.
# The key is to figure out ways to reduce the size of "for" loops, or even look for some alternative ways that don't use looping at all. For instance, the collision-checking example below doesn't require any searching or hitTest() functions to find the walls. Instead it uses a 2-dimensional array and simply checks a location within it. This is useful for colliding with stationary blocks in a level.
# If you're checking for collision with every character, figure out ways to exclude movieClips you're not looking for. Check only the things you need to check.
# One way to do this is to make an array of references to each movieClip you wish to check, and simply loop through that array. The first step in collision checking is usually figuring out what to ignore.
# Or find ways to reduce the number of collision checks. For example, have characters check for blocks, instead of having blocks check for characters. Since there are fewer characters than blocks, it'll use fewer collision checks.
# When possible, animate things with image sequences or tweens. It's easier for Flash to process built-in features, than it is to process Actionscript.