Google pagespeed insights headache.

Failed to add items

Sorry, we are unable to add the item because your shopping basket is already at capacity.

Add to cart failed.

Please try again later

Add to wishlist failed.

Please try again later

Remove from wishlist failed.

Please try again later

Follow podcast failed

Unfollow podcast failed

Google pagespeed insights headache.

Listen for free

View show details

About this listen

Today on Episode 24, Web Hosting Podcast. Are you obsessed with page speed ranking? Speed is always a great thing to have but the realization is, getting that perfect score is almost impossible with a website. Megan joins me to discuss some things that may cause your site to be slow. We also dive into pagespeed insights and discuss some surprising and shocking results we got. What can make your website slow? Slow hosting environmentImages too largeNo caching setup on website, expireslong database queriesRunning old versions of software, PHP, Apache, CMS software (WordPress, Drupal, Joomla, etc..) If you use google pagespeed insights or pingdom website speed test, you may have got a low score for your website. A low score would be something in the 60-70 range. Anything above a 80 would be considered a pretty good score. I just want to point out that you should not obsess about getting a perfect score. google pagespeed insights Pingdom website speed test Both of the pagespeed tests use a score from A (great) to F (fail). Of course you want to try and get all A in your grade score. But sometimes it is just not possible. For a base line, I installed a default version of wordpress (4.9.8) on a domain I own. Right after installing, I ran both google pagespeed and pingdom website speed tests. The site is being served over SSL using the default free cPanel SSL certificate. Google – Mobile = 70 Google – Desktop = 92 Pingdom = Overall 88 (B) When you first run the test, you will get a list of currently applied optimizations as well as improvement recommendations. My list of currently applied optimizations on a default install are as follows. NOTE: these may be different depending on your hosting providers setup and environment. Avoid landing page redirects Enable compression Minify HTML Optimize images Prioritize visible content From the list, you can see that I do not have redirects for the landing page, I have gzip compression enabled, my html is minified, my images are optimized, and I have content that is visible that is prioritized. But what does this all mean? Landing Page Redirects : This occurs when you redirect the main site the user is going to, to another page. Google provides some great examples. Here are some examples of redirect patterns: example.com uses responsive web design, no redirects are needed – fast and optimal! example.com → m.example.com/home – multi-roundtrip penalty for mobile users. example.com → www.example.com → m.example.com – very slow mobile experience. Enable Compression : We actually discussed this in the very first episode and it is worth noting again. Compression will shrink down elements before sending them to the browser. This saves bandwidth and can improve site speed by sending smaller elements through the internet. You can enable gzip compression in cPanel by going to “optimize website” and click on compress all content. Minify HTML : According to google here is what they mean by Minify HTML: Minification refers to the process of removing unnecessary or redundant data without affecting how the resource is processed by the browser – e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. You should minify your HTML, CSS, and JavaScript resources: To minify HTML, try HTMLMinifier To minify CSS, try CSSNano and csso. To minify JavaScript, try UglifyJS. The Closure Compiler is also very effective. You can create a build process that uses these tools to minify and rename the development files and save them to a production directory. Optimize Images : This rule triggers when PageSpeed Insights detects that the images on the page can be optimized to reduce their filesize without significantly impacting their visual quality. This means that I do not have a image that is to large and scaled to fit the area. Do not scale images in your web framework. Always scale the image before uploading. My initial run of items that needed improvement. Reduce server response time In our test, your server responded in 0.64 seconds. There is not much to be done here. That is almost 1/2 a second for a response time. It could certainly be better, but this value will shift up and down depending on a lot of factors. If this value is higher than 1 second, then you may have a overloaded server. Eliminate render-blocking JavaScript and CSS in above-the-fold content Your page has 1 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. Leverage browser caching Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network. This is simply setting a...

No reviews yet