Anything But Easy

Hi @flyfisher842 ,

That’s strange! Can you please open up a support ticket in our support center so that we can take a close look at your issue?

for whatever reason, the check box to display on elementor canvas did not work for awhile. I finally did get it to work but it uses a page each for the header and footer which imcreases load times. So I made a template with the header and footer embedded into the template which should decrease http requests some.

Building pages with blocks whether it is gutenberg, beaver builder or elementor is a lot slower than doing them with the classic editor with the tinymce plugin from Ozz enabled. The big advantage is creative license with blocks which the classic editor is more constrained.

I have classic editor home pages that were in the sub 1 second load times before my host started customer dumps on my server. Now those load times are about 3.5 seconds and with similar elementor pages about 6 to 8 seconds.

I will be spemding some time load testing elementor templates to see how they do.

As you can see I not a big block building fan yet. That may happen but word processors are easier to run then block builders.

Go ahead and close out this ticket

• This reply was modified 5 years, 9 months ago by flyfisher842.

Hello @flyfisher842,

May I know which theme are you using?

If you are using one of the supported themes then only the header and footer will work automatically on all pages. If you are not using one of the supported themes you will be warned after activating the plugin and will be notified about this.

Since you are using the plugin only on Elementor Canvas templates, for the header and footer to work you will need to set the elementor canvas template on the pages else the header not work.

I think this is the confusion that you faced when trying this plugin out.

About the speed comparisons –

You are right, The code generated by the classic editor will load faster than generated with Gutenberg/Elementor, as you are getting more freedom with the layout that can be built using these plugins.

On a side note though. This plugin is a third-party add-on for the Elementor page builder, So speed comparisons for Elementor VS other solutions would be more appropriate on the Elementor’s support forums as even if there is anything that can be improved in this aspect it can be fixed by their development team.

I was using the Astra Child theme.
I looked at the header and footer pages. Each is on its own page which makes sense when saved as a template.
When checked to work with Elementor canvas, the code shows that the header and footer are rendered as separate pages. Probably with an include or a require once php or similar in JS. So this makes one http request to get each page then whatever http requests are on the pages have to be done to render the page.

To speed this up I made an elementor template that embed the header and footer into the canvas template which avoids some of the http requests round trips. on webpagetest.org, this template with embeded headers and footers and a lot of information inbetween got .512 and .535 first byte times. Doing it with the function calls was about 3 seconds due to server response time which I can’t control. Does this make sense to you.

There was something to be said for html pages which IMO will still beat performance on any wordpress site period. Just not very flexable for creative.

Can you explain with maybe screenshots how you have setup this?

>I made an elementor template that embed the header and footer into the canvas template

For loading the templates –
> When checked to work with Elementor canvas, the code shows that the header and footer are rendered as separate pages. Probably with an include or a require once php or similar in JS

This plugin calls elementor’s functions to render the layout and does not do anything custom to render the page.