Optimize WordPress site for speed

I will paste the requirements from ySlow below: ySlow is the site speed testing solution I used, you can find it here: [login to view URL] 1. Grade F on Make fewer HTTP requests This page has 8 external Javascript scripts. Try combining them into one. This page has 13 external stylesheets. Try combining them into one. This page has 7 external background images. Try combining them with CSS sprites. Decreasing the number of components on a page reduces the number of HTTP requests required to render the page, resulting in faster page loads. Some ways to reduce the number of components include: combine files, combine multiple scripts into one script, combine multiple CSS files into one style sheet, and use CSS Sprites and image maps. The requirement is to get this to a grade A-B. 2. Grade D on Put JavaScript at bottom There are 8 Javacript scripts found in the head of the document * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] JavaScript scripts block parallel downloads; that is, when a script is downloading, the browser will not start any other downloads. To help the page load faster, move scripts to the bottom of the page if they are deferrable. The requirement is to bring that up to B or better. 3. Grade F on Use a Content Delivery Network (CDN) There are 58 static components that are not on CDN. You can specify CDN hostnames in your preferences. See YSlow FAQ for details. * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] * [login to view URL] User proximity to web servers impacts response times. Deploying content across multiple geographically dispersed servers helps users perceive that pages are loading faster. The requirement is to bring this up to a C or better.