macksq's Replies | ww.wp.xz.cn

Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)

Forum: Plugins
In reply to: [AMP] Site slow

macksq
(@macksq)

6 years, 8 months ago

My apologies to @gustavors if my follow up question hi-jacks the thread at all!
The reference to a server-side AMP protocol in my previous question is based off mention of the AMP Optimizer found on the AMP.dev site under the server-side rendering tutorial.
Below is a snippet from the tutorial:

Server-side-rendering is a technique that AMP caches use to even further speed up loading time. With server-side-rendering it’s possible to remove the AMP boilerplate so that the AMP document can be painted without running the AMP runtime JavaScript. For example, the server-side rendered version of the AMP Boilerplate Generator renders twice as fast as the normal AMP version!

I would assume this suggestion is exactly what the WP AMP plugin accomplishes! Although there are calls to the needed javascript by the plugin.

Forum: Plugins
In reply to: [AMP] Site slow
macksq
(@macksq)

6 years, 8 months ago
Heya Weston,
I am having the same issue as @gustavors, with a long TTFB/server-pause before webpage rendering starts. (In my case it’s a 2.5 second TTFB and non-amp pages have a 400ms to TTFB.)
We have WProcket to assist with caching and the AMP plugin is in Transitional mode. This has helped with then troubleshooting of any given page when searching slow elements.

Would use of the serverside-rendering AMP protocol help @gustavors and I with speeding up any uncached elements?

On that note, shouldn’t our AMP pages already be cached by the AMP cache system and the slowdown potentially related to the building/sanitizing of the AMP page by the plugin?

Thank you again for your awesome work and insight to this project.
- This reply was modified 6 years, 8 months ago by macksq.
Forum: Plugins
In reply to: [AMP] Sanitizing of amp-sidebar

Thread Starter macksq
(@macksq)

6 years, 9 months ago

Hi Westin,
Thank you so much for the insight on this.
Just for clarification, I was under the impression that the toolbar element removed the need for a direct descendant of body. That placement of the element could have a few wrappers in this case. This is the way I interpreted the description in the AMP library.

If no editing of the AMP plugin can be done on my end, any estimate for the V1.3 release?

Thank you again for your insight and tolerance for some of our less informed questions.

Forum: Plugins
In reply to: [AMP] Sanitizing of amp-sidebar
Thread Starter macksq
(@macksq)

6 years, 9 months ago
<header
```
<div class="Header-Nav-Menu-Inner">
<?php if ( is_amp_endpoint() && wp_is_mobile()): ?>
<div>
  <amp-sidebar id="sidebar-right"
                  class="sidebar"
               layout="nodisplay"
                     side="right">
        <button on="tap:sidebar-right.close">(x)</button>
        <nav toolbar="(max-width: 760px)" toolbar-target="target-element-right">
                                                              <ul>
                                                                <li>Nav item 1</li>
                                                                <li>Nav item 2</li>
                                                              </ul>
                                                            </nav>
                                                            <ul>
                                                              <li>Nav item 3</li>
                                                              <li>Nav item 4</li>
                                                            </ul>
                                                          </amp-sidebar>
                                                        <span class="Header-Nav-Menu-Icon"><i class="fa fa-bars" role="button" tabindex="0" on="tap:sidebar-right.open"></i></span>
<div id="target-element-right">
</div>
</div>
   <?php else: ?>
<span class="Header-Nav-Menu-Icon"><i class="fa fa-bars"></i></span>
<?php endif; ?>
</div>
```
Plugin version is 1.2.2 and set to transitional mode.

Viewing 4 replies - 1 through 4 (of 4 total)