PageSpeed Plus Blog

#1 PageSpeed Insights Blog. Learn how to improve your score

  • How To Score 90+ On PageSpeed Insights

    Posted on Oct 02, 2019

    Trying to Score 90+ on PageSpeed Insights is a process that consumes a lot of developer patience and energy. This guide shortcuts those problems and shows you exactly what steps you need to take.

    Read More
  • Why Google PageSpeed Matters

    Posted on Jul 23, 2019

    PageSpeed is the score Google awards a site after assessing it through its own PageSpeed Insights service. The metric is based on their view of how a web page should be constructed to load fast, offer a pleasant user experience with good code quality underneath.

    Read More
  • Serve static assets with an efficient cache policy on Laravel Forge

    Posted on Jul 15, 2019

    If you're managing a VPS with Laravel Forge and trying to optimize the PageSpeed Insights score, you’ve probably received the ‘Serve static assets with an efficient cache policy’ warning from Google. Fortunately, there is a quick and easy fix that only takes a five minutes to complete.

    Read More
  • Automating Google PageSpeed Tests

    Posted on Jun 22, 2019

    PagespeedPlus.com automatically scans your URLs daily or weekly and notifies you with the results.

    Read More
  • Bulk Testing Google PageSpeed Insights

    Posted on May 31, 2019

    PageSpeed Plus enables full site PageSpeed Insights scans so you can see the score of every page. Automated and on demand with multiple URLs in parallel

    Read More
  • How To Eliminate render-blocking resources

    Posted on Aug 10, 2018

    This quick guide will show you how to Eliminate render blocking resources, improving your PageSpeed grade by a significant margin as a result.

    Read More
  • How To Enable GZIP Compression on Laravel Forge

    Posted on May 01, 2018

    If you are using Laravel Forge and trying to optimize your website performance, you’ve probably received the Enable Compression warning from Google Pagespeed. This guide gives you precise instructions on how you can solve this with a simple change to your NGINX configuration.

    Read More