Gzip and the leverage cache (browsers cache) are best addressed at the server side.
Keep in mind that you can get an “A+” rating from most of these tools and still have a very slow site. They aren’t comparing to other competitors just looking at technical issues and making suggestions to improve load speed.
Depending on your hosting company and plan how you turn on gzip and browsers caching.
You also might want to consider adding a CloudFlare account to your site. Even the free account will address both of these two issues and a lot more.
Honestly, I didn’t look at your screenshots, I’m on an iPad and didn’t want deal with opening another window.
So the last item you mentioned was Renderblocking JS:
Since you’re using foundation, there’s an option in the SEO stack that addresses that.
CloudFlare also has a rocket option that addresses this as well, just don’t use both, and test test test, as both do change the source order being loaded into the browsers.
@Massimo From many years on these forums, by far the greatest problem appears to be the size of graphics. The aim should be to get all jpegs etc to about 100kb at 72dpi.
Hi @teefers, you mentioned above that Joe’s SEO stack addresses render blocking. Im looking but cant find, or don’t know what to look for! Could you be more specific?
On the SEO helper stack, in the drop down you’ll see an option called “page speed”, I think it’s the last option, same spot you pick Facebook or Twitter card.
My question about page speed and Rapidweaver is to do with displaying the content of one page on another page.
Lets say I have a page with six optimised warehoused images - set up in my case with Foundry’s Card Deck.
I want that same stack to appear on another page.
Is it better from a page load speed point of view to simply copy the stack and paste it into the other page (or create a partial); or should I use an “import” stack (I have JW’s Global Content/Import Stacks)?
If your using the same image on more than one page, warehousing is your best bet. Once the image is loaded once (assuming you’re using the same URL for the image), it will be in the user’s browsers cache. So it won’t have to load again from the server but instead would load from the local computer’s memory or harddrive.
Now that I have said that, Foundry’s image stacks don’t support warehousing.
As for partial vs. a copy of the stack, from a page load speed don’t think it matters.
Sorry, seems like I’ve caused some confusion with my post.
When I referred to “page speed”, I meant time taken to load a RW page (which is what I took the original post to be about), not a page speed stack.
Trying to clarify -
On Page One I have a stack containing ten warehoused images (a total of 400KB).
I want to have that same stack appear on Page Two.
If I want to optimize page load speed, do I simply copy the stack from Page One and paste it into Page Two, or should I import the stack from Page One into Page Two?
Importing would of course be easier because changes to the “original” would appear automatically on the “destination” page.
I had thought of Pluskit, but I believe it imports a whole page.
With JWs Global/Import stack you import only what’s in the Global Content stack.
Using partials can help the “copy and paste” procedure, but I have so many different pieces of content I want to process in this way, it would get very cumbersome.
(I use warehoused images in Foundry’s Card Stacks by having Yuzool Themes warehouse stack in the Card Slice element.)
If the images are warehoused, and you use The same URL to access them then from a page load time it doesn’t matter how you got them on the page.
If you access an image by direct URL
https://example.com/assets/myimage.jpg
Then once that URL is loaded, it will be in the browser’s cache, so any other page that uses that same URL will get the image from the cache and not return to the server.
As for the best way to repeat stacks of any kind partials would be the way to go.
No pluskit or importing should be used.
With 10 images adding up to 400kb on the same page, warehousing these images is a perfect example of how warehousing can speed up your site.
In this case, your 10 images will load into the browser cache when a visitor visits your first page. When they go to the second page, because the images have the same name and are already loaded, they are available for an instant display. If they were not warehoused, they would have to be loaded again and the user would have to wait for a further 400k be downloaded.
Avoiding an unnecessary 400kb download is a significant contribution to speeding up your site.
(here the screenshot of the test result)
