Fix (Chrome) speed issues for www.Easy.Auction

Fix (Chrome) speed issues for Easy.Auction. [login to view URL] can still optimize a bit more and i am mainly interested in Chrome speed improvement. I want to improve these pages: [login to view URL] [login to view URL] [login to view URL] [login to view URL] This is what google advices to do: Sources block the first view (FP) for your page. Consider providing critical JS / css inline and deferring all non-critical JS / styles. URL …css/[login to view URL] 32 KB 230 ms …css/[login to view URL] 27 KB 270 ms …javascript/[login to view URL] 158 KB 390 ms …css/[login to view URL] 12 KB 190 ms …css/[login to view URL] 3 KB 150 ms …css/[login to view URL] 1 KB 150 ms …css/[login to view URL] 1 KB 70 ms Remove redundant lines from stylesheets and defer loading of unused css for above-the-fold content to reduce unnecessary bytes by network activity. URL …css/[login to view URL] 32 KB …css/[login to view URL] 27 KB …css/[login to view URL] 12 KB Make use of the css 'font display' feature to ensure that text is visible to users while web fonts are loading. …fonts/[login to view URL] 500 ms …fonts/[login to view URL] 190 ms Cache TTL 7 days: …fonts/[login to view URL] 52 KB …fonts/[login to view URL] 52 KB [login to view URL] ([login to view URL]): Leverage browser caching for the following cacheable resources: [login to view URL] (15 minutes) [login to view URL] (15 minutes) [login to view URL] (30 minutes) [login to view URL] (1 hour) [login to view URL] (1 hour) [login to view URL] (1 hour) [login to view URL] (1 hour) [login to view URL] (1 hour) [login to view URL] (1 hour) [login to view URL] (1 hour) [login to view URL] (1 hour) [login to view URL] (2 hours Defer parsing of JavaScript: 400.8KiB of JavaScript is parsed during initial page load. Defer parsing JavaScript to reduce blocking of page rendering. [login to view URL] (399.5KiB) [login to view URL] (1.2KiB of inline JavaScript)