This week I have been doing some technical SEO investigations, to understand why so few of my pages within a site designed with Oxygen for WordPress are being fully cached by Google.
By using “inspect URL” in Google’s Search console, then more info, it will show if all the page resources of a web page are being cached. This can be very important with SEO, especially if critical components of a page are missing, such as CSS and frameworks.
Google Crawl Quotas, for A Single Page
In my case, several pages were not being fully cached. Google was only caching about the first 25 – 30 or so page resources, before deciding not to load the rest. A bit of investigation and the critical term “Crawl Quota” appeared yet again.
I had always believed crawl quotas related to how often Google came to a website, or how many pages it would cache in a particular period, based on the quality of the site. I am not more educated and can say, it is also about how many resources per page, it will cache, before stopping.
Oxygen From Elementor
I have recently been getting to grip with Oxygen, after being disappointed with load times from Elementor template designs. Oxygen has been a saviour on my opinion of WordPress websites, as load speed is much faster.
I had assumed it was because it used much less resources to achieve this faster speed. But no, even with faster speeds, the page resource count is about the same than with the page builder Elementor of the designs and projects I have been putting together.
But what also confused me was that some pages even in a second site with only 15 page resources, were still not being fully cached by Google. However, eventually I figured I could easily fix this by “Regenerating the CSS” within Oxygen within the settings menu. After doing this, every inspect page, produced a cache of 100% of the page.
It does worry me that I must log in regularly regenerate CSS to ensure pages can be cached by Google. This will be on my Oxygen check list. If it only needs doing after a change or added content, then this will bearable.
But back to the first website, with page resources well above 25-30, there were issues. Especially one with 40 page resources. Well I found a solution by not using the CSS in Oxygen and replacing it with a plugin called Autoptimize. It brings many of the CSS and JSS resources into much fewer, in this case 40 down to 9.
I started using this on Elementor sites also, to see if this make a difference with SEO rankings, improving the quality score of a website.
If you are having ranking issues with a WordPress site and your page load speed is good, and you know you have a good link profile and content. Take a few minutes to check how much of each page is being cached by Google? You may be surprised at what you find.