What’s this about?
A few webmasters are getting a bit het up about Page Speed and showing off their technical chops in doing so.
PageSpeed is important, no doubt, but anything you do needs to be scalable and there are no awards for having the quickest page on the internet.
Read more in this exciting extract from TWIS SEO News & Updates 1st December 2017.
Stop Getting Over-Excited About PageSpeed
Key Issues Summary:
- Webmasters are getting over-excited about PageSpeed.
- There have been a couple of examples where people have been wondering if Time To First Byte (TTFB) and others bits are critical for ranking.
- Time to First Byte is not used for ranking, and the critical moment for Google is when a user can interact with the page (which is very tricky for Google to determine).
- They need to remember that Google is (and always has been) a relevancy engine. PageSpeed is assessed post-relevancy.
Key Actions To Take:
- Use Google’s Page Speed Insights, but remember it is at an individual page level, not at a site level.
- Remember that speed, or lack thereof, can be transitory, as servers get busy, as do routes.
- Also, remember that speed can be illusory, meaning that you can give the impression of speed without actually always being quick (eg, get the first screen painted double-quick-smart, even if your page take a while to load as a whole).
- Make sure your server and hosting package are up to the job. They will make more difference than code-fiddling, unless you have really, really, bad code.
- Finally, remember that Google’s PageSpeed is a fresh load of everything each time. If you are using cached resources, then their speed report is absolute rather than relative.
- Click here to contact me to discuss how to speed up your website properly.
Insights & Discussion:
Techie webmasters are generally foaming at the mouth over Page Speed, they can craft arcane code which shaves nanoseconds of the initial load of a cached resource. That kind of work is pointless, unless you are failing to cache things properly.
Instead of trying to make websites load more quickly, the heavy-duty coders of this world should be focusing their efforts on streamlining any code which is used dynamically, and dumping any dynamic code which could be served statically. Fat chance of that however.
In the meantime, however, we’ll have to put up with over-excited posts about how someone spent hours, days, weeks, to shave code which will never be repaid in revenue, and which would have been better spent producing something revenue-generating.
To some extent, this is just webmaster chest-beating, but it can have real-world consequences as other webmasters spend hours chasing down minimal incremental gains when they should be working on creating more revenue-generating content.
As a small additional side note, remember Google doesn’t even want to send traffic to websites. If it can show the data with no click, it will.
- Code Cutting To Improve Page Speed
- Google: PageSpeed Is Difficult
- Googlebot Doesn’t Crawl HTTP/2
- John Mueller Replies to Over-Enthusiastic Webmaster No 1
- And No 2.
Mobile First is NOT Mobile Friendly
I recently wrote about how Google’s Mobile First is Not Mobile Friendly. Read it now.
- Oooh look at me! I have the quickest page on the internet – can I have a biscuit?
- The PageSpeed tool is like using a hammer to bang in a screw. It works, kind of, but it’s not great.
- You need to work out if your time is better spent quickening up your site to the point of diminishing returns, or creating more delicious content for users to enjoy.
- Read The State of SEO in mid-2017.
- Read about how Google’s Mobile First Index is not Mobile Friendly.
- Finally, get your content ranking well on Google by starting to understand Find Crawl Index.
Thanks for reading. If you would like to discuss what these changes mean for your web property, or would like to know how to implement them, please feel free to contact me.