Eliminate render-blocking JavaScript and CSS
in above-the-fold content
Your page has 7 blocking script resources and
9 blocking CSS resources. This causes a delay in rendering your page.
§ None of the above-the-fold content on your
page could be rendered without waiting for the following resources to load. Try
to defer or asynchronously load blocking resources, or inline the critical
portions of those resources directly in the HTML.
§ http://appstore-24.com/wp-includes/js/jquery/jquery.js?ver=1.10.2
§ http://appstore-24.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
§ http://appstore-24.com/wp-content/plugins/wiziapp-create-your-own-native-iphone-app/themes/webapp/scripts/wiziapp.js?ver=2.0.9
§ http://appstore-24.com/wp-content/themes/cache/js/tie-scripts.js?ver=3.6.1
§ http://dtym7iokkjlif.cloudfront.net/media/js/jquery.shareaholic-publishers-sb.min.js?ver=6.1.5.1
§ http://appstore-24.com/wp-content/plugins/wp-favorite-posts/wpfp.js?ver=3.6.1
§ http://appstore-24.com/wp-content/plugins/follow-me/js/bubble.js
§ http://appstore-24.com/wp-content/themes/cache/style.css
§ http://fonts.googleapis.com/css?family=Droid+Sans:regular,bold
§ http://appstore-24.com/wp-content/plugins/wp-favorite-posts/wpfp.css
§ http://appstore-24.com/wp-includes/js/thickbox/thickbox.css?ver=20121105
§ http://appstore-24.com/wp-content/plugins/download-manager/css/front.css?ver=3.6.1
§ http://appstore-24.com/wp-content/plugins/follow-me/css/style.css
§ http://fonts.googleapis.com/css?family=Oswald
§ http://appstore-24.com/wp-content/plugins/paid-downloads/css/style.css?ver=3.15
§ http://appstore-24.com/wp-content/themes/cache/css/style-blue.css
Reduce server response time
§ In our test, your server responded in 0.90
seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where
your server is spending the most time.
Improve
Server Response Time
This rule triggers when PageSpeed Insights detects that your
server response time is above 200 ms.
Overview
Server response time measures how long it takes to load the
necessary HTML to begin rendering the page from your server, subtracting out
the network latency between Google and your server. There may be variance from
one run to the next, but the differences should not be too large. In fact,
highly variable server response time may indicate an underlying performance
issue.
Recommendations
You should reduce your server response time under 200ms. There
are dozens of potential factors which may slow down the response of your
server: slow application logic, slow database queries, slow routing,
frameworks, libraries, resource CPU starvation, or memory starvation. You need
to consider all of these factors to improve your server's response time. The
first step to uncovering why server response time is high is to measure. Then,
with data in hand, consult the appropriate guides for how to address the
problem. Once the issues are resolved, you must continue measuring your server
response times and address any future performance bottlenecks.
1.
Gather and inspect existing performance and data. If none is
available, evaluate using an automated web application monitoring solution
(there are hosted and open source versions available for most platforms), or
add custom instrumentation.
2.
Identify and fix top performance bottlenecks. If you are using
a popular web framework, or content management platform, consult the
documentation for performance optimization best practices.
3.
Monitor and alert for any future performance regressions!
Optimize images
Properly formatting and compressing images can
save many bytes of data.
§ Losslessly compressing
http://appstore-24.com/wp-content/uploads/app-store-android-logo-copy1.jpg
could save 16.8KiB (77% reduction).
§ Losslessly compressing
http://appstore-24.com/wp-content/themes/cache/images/patterns/body-bg7.png
could save 7.1KiB (26% reduction).
§ Losslessly compressing
http://2.bp.blogspot.com/-INo7IsiQ0xU/UjLS4-TJOlI/AAAAAAAAABo/eY9nW61iRfA/s1600/728x90.gif
could save 2.6KiB (31% reduction).
§ Losslessly compressing
http://appstore-24.com/wp-content/plugins/follow-me/images/us/followme_top.gif
could save 1.6KiB (18% reduction).
§ Losslessly compressing
http://appstore-24.com/wp-content/themes/cache/timthumb.php?src=/wp-content/uploads/Flipster-for-Facebook-logo.png&h=125&w=272&a=c
could save 1.2KiB (7% reduction).
§ Losslessly compressing http://appstore-24.com/wp-content/themes/cache/timthumb.php?src=/wp-content/uploads/Modern-combat-4-zero-hour-app-store.jpg&h=125&w=272&a=c
could save 850B (6% reduction).
§ Losslessly compressing
http://appstore-24.com/wp-content/themes/cache/timthumb.php?src=/wp-content/uploads/IM-pro.jpg&h=125&w=272&a=c
could save 745B (7% reduction).
§ Losslessly compressing
http://appstore-24.com/wp-content/themes/cache/timthumb.php?src=/wp-content/uploads/Adobe-Reader.jpg&h=125&w=272&a=c
could save 686B (10% reduction).
