Improving your WordPress website on-page SEO – Improving Google page speed score

What is Google Page Speed Score?

Google Page Speed Score helps you to find out your website performance both for mobile and desktop. It gives you a score ranging from 0 to 100

The more score you have got, your website is going to rank better as in on-page SEO.

There are so many factors that affect this score as listed below –

  • Static resources caching policy
  • Static resources minification, CSS/JS minification
  • Image Optimization
  • Avoid multiple redirects
  • Render-blocking resources
  • Text compression
  • Serve images in next-gen formats 
  • Minimal Javascript execution time
  • Time To First Byte

Getting these optimization right can help you bring you to score above 90 ( good ) We will discuss how you can make these optimizations in this blog post. If you are running a WordPress site it is as simple as installing a few plugins.

This blog post, we will discuss how you can work on these issues to get to your onsite SEO sorted.

  • Static resources caching policy – Your webserver needs to return the static resource with a big cache TTL ( time to live ) so they can be delivered faster to clients. You can also go with Cloudflare as a reverse proxy and they can handle the caching policy for you.
  • Static resources minification, CSS/JS minification – The JS/CSS minification helps you to save overall bytes server sends to the client. Below are the available options if you are using WordPress

    Autoptimize – Autoptimize makes optimizing your site really easy. It can aggregate, minify and cache scripts and styles, inject CSS in the page head by default but can also inline critical CSS and defer the aggregated full CSS, moves and defers scripts to the footer and minifies HTML. 

    Upon activation, you need to visit the Settings » Autoptimize page to configure the plugin settings.

    autoptimize wordpress plugin

    You can also go with W3 Total Cache or any other plugin that serves the purpose.
  • Image Optimization – Images need to be optimized for the right size to reduce the extra bytes you might be sending along with server response.

    The Autooptimize WordPress Plugin can help you serve images in WEBP format.

WebP is Google’s open-source image format. They utilize the file extension .webp

There are several variations of WebP images, one uses lossy compression and is comparable to JPEG images, but with a 25-34% smaller file size. Lossy WebP images also support transparency, which is something JPEGs can’t do.

  • Avoid multiple redirects – its important to avoid multiple redirects to avoid document loading multiple times and increasing overall delay for displaying the content to the end-users.
  • Render-blocking resources – Avoiding any static resource which is going to block the document rendering is important to display the page to the end-users as soon as possible. The JS/CSS should be added below the fold to avoid extra bytes adding into page load time.
  • Text compression – If you are using a reverse proxy like Cloudflare, they do this out of the box. Text compression often significantly reduces the size of transmitted data and may add extra overhead along with the response.
  • Minimal Javascript execution time – Having a WordPress theme with a lot of Javascript may increase the overall page rendering time.
  • Time To First Byte – TTFB is the number of milliseconds it takes for a browser to receive the first byte of the response from your web server. More clearly TTFB is also called “waiting” by Google: Time spent waiting for the initial response, also known as the Time To First Byte.

    TTFB depends on a lot of factors again and it can be improved by introducing caching servers, CDN or improving the overall execution time for response returned by the server. Also if you are running over a shared hosting you may get higher TTFB compared to running a website over dedicated hosting.

    What is your website score? Do let us know in the comment section.

Write a Comment

Your email address will not be published. Required fields are marked *