It just saves the page as a static page

  • It just saves the page as a static page. No optimizations are done.
    The only benefit is that there won’t be any page building process (running shortcodes, functions, connecting to the database).
    It has a weird way to do it though… there is a JSON code injected at the top of each cache generated, which mean there is some post processing when a page is served. Probably to control the expires headers.
    There shouldn’t be any noticeable scores improvement. It will mainly impact the TTFB. It still will be slightly slower to plugins using server redirections to serve cache (most of them do on Apache/LiteSpeed environments).
    That’s why you will likely get less score-wise when comparing it to other performance plugins that handle cache + optimize things a bit.
    Testing it gave me a blank page. It might not be working on all stacks properly.

Viewing 1 replies (of 1 total)
  • Plugin Author Konstantin Kovshenin

    (@kovshenin)

    Looks like you gave it too much stars then ??

    I’d be curious to know what were the underlying errors behind that blank page. Indeed, the plugin is very new, and hasn’t yet been tested across the many different environments and configurations.

    Regarding the optimizations, images, JavaScript, CSS and everything else, you are correct. Those things are outside of the scope of this plugin. Surge does only one thing, and that’s page caching. If you’re looking for an all-in-one optimization suite, then unfortunately it won’t fit the bill.

    You are also correct about serving the cached content. It does so by reading files, and cache metadata is stored in the same file along with some PHP code that makes sure the (potentially sensitive) content is not exposed in case an attacker guesses or enumerates the cache key.

    Finally, serving cache directly from Apache, Nginx or LiteSpeed is of course going to be faster, so if you can avoid hitting PHP at all that’s great. With Surge we do recommend adding a fastcgi_cache or proxy_cache layer on top of WordPress, which doubles the throughput with Surge, even with a very low TTL.

    Thanks for the feedback, and hope you could reconsider trying out Surge when it’s slightly more mature.

    ~ Konstantin

Viewing 1 replies (of 1 total)
  • The topic ‘It just saves the page as a static page’ is closed to new replies.