Forum Replies Created

Viewing 15 replies - 1 through 15 (of 847 total)
  • What’s you site URL?

    yes, that’s why there is foreground and background setting for CCSS generation.

    Consider a situation when the CCSS cache was cleared and a visitor comes before the background job was processed. In this case, CCSS should be generated in the foreground with a higher priority, so that it completes faster.

    Background jobs can wait, but visitors shouldn’t.

    In fact, I’m not sure why the plugin even offers foreground regeneration. Background should be the only method, with a high-priority foreground fallback for the rare occasions when that’s needed.

    This will make the first visitor after a CCSS clear wait a little bit, and prevent the flicker for every subsequent visitor.

    The excluding CSS is only excluding it from being combined or minified , but user still see that CSS content , so does the generator, that’s why it ignores your exclude setting.

    Actually, this depends on the width of the browser window, and it’s incorrect to assume that the user will always see the effects of this CSS.

    That file is included with media="min-width: 768px" and should be wrapped in a media query when combined.

    This is a problem with file combination, and excluding the file was a workaround, but apparently, that’s still not enough.

    Not handling the media attribute of included stylesheets is a fundamental problem with the plugin and needs to be fixed.

    It appears that CCSS generation is ignoring my stylesheet exclusion

    I’ve excluded “woocommerce-smallscreen.css” to “CSS Excludes” on the Tuning page, and this stylesheet is being loaded separately.

    However, the critical path CSS includes the following style, which only appears in that file:

    
    .woocommerce ul.products[class*=columns-] li.product, .woocommerce-page ul.products[class*=columns-] li.product {
        width: 48%;
        float: left;
        clear: both;
        margin: 0 0 2.992em;
    }
    

    If you compare https://dev.get-business-online.com/behappyinlife/books-products/ to the same URL with “?nocache”, you will see that the cached/optimised page has no right margins on the first and second product blocks due to the inline inclusion of this style.

    In the meantime, I’ve found and fixed the error(s) and gotten valid CCSS in the page.

    This just happened after 3 days of no access (it’s a dev site that only I use). How long does the block last?

    Oh, and why is this not done locally? It’s posting to https://as.wp.api.litespeedtech.com/ccss, which may or may not be available when the site is.

    According to the Optimize page, it takes 15 seconds for the API server to return the CCSS, which seems like a LONG time. This also means that the load on the API sever may become an issue for websites (small issue, but still).

    You have given zero useful information.

    What did you try to do?

    What did you expect?

    What did you see?

    Are there any relevant messages in error_log, wp-admin/error_log or your browser console?

    Take a look at your error_log and wp-admin/error_log files for relevant messages.

    Hi Daan,

    After 2 days in Stealth Mode, I’m getting around 10.5% more traffic, compared to last week. This is good, but seems to be about 30% short, according to this survey.

    If you look at this page, you can get all the lists used by AdBlock, and likely other browser extensions. A quick look at EasyList shows MANY patterns containing “analytics”, including some that may be included in the tracking script.

    If it’s not asking too much, it’ll be great if you could somehow get the script to pass through these filters by making it mismatch all the patterns.

    Thanks again,
    Gal

    After finding and fixing the error, I got this:

    
    02/20/20 08:50:49.323 [61.68.187.13:58317 1 leL] [CSS] Generating:  --- array (
      'home_url' => 'https://dev.get-business-online.com/behappyinlife',
      'url' => 'https://dev.get-business-online.com/behappyinlife',
      'ccss_type' => 'front',
      'user_agent' => 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.106 Safari/537.36',
      'is_mobile' => 0,
    )
    02/20/20 08:50:49.323 [61.68.187.13:58317 1 leL] [IAPI] posting to : https://as.wp.api.litespeedtech.com/ccss
    02/20/20 08:50:49.743 [61.68.187.13:58317 1 leL] [IAPI] failed to decode post json: Too many frequent errors
    02/20/20 08:50:49.749 [61.68.187.13:58317 1 leL] [CSS] empty ccss 
    

    Have you tried clearing your browser cache?

    Anything in error_log or wp-admin/error_log?

    Is this resolved?

    Check your error_log and wp-admin/error_log file for any relevant issues and post them here.

    Keep reading my previous note. There is no error anymore.

    First, I saw this:

    /*CssSyntaxError: /behappyinlife/min/95588.css:1:49734: Unexpected }*/

    However, I couldn’t find a “min” directory anywhere.

    After finding and fixing the error, I got this:

    
    02/20/20 08:50:49.323 [61.68.187.13:58317 1 leL] [CSS] Generating:  --- array (
      'home_url' => 'https://dev.get-business-online.com/behappyinlife',
      'url' => 'https://dev.get-business-online.com/behappyinlife',
      'ccss_type' => 'front',
      'user_agent' => 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.106 Safari/537.36',
      'is_mobile' => 0,
    )
    02/20/20 08:50:49.323 [61.68.187.13:58317 1 leL] [IAPI] posting to : https://as.wp.api.litespeedtech.com/ccss
    02/20/20 08:50:49.743 [61.68.187.13:58317 1 leL] [IAPI] failed to decode post json: Too many frequent errors
    02/20/20 08:50:49.749 [61.68.187.13:58317 1 leL] [CSS] empty ccss 
    

    Hello Damian,

    Reducing the site of an image from 100×100 (typical woocommerce_gallery_thumbnail) to 64×64 really doesn’t save much. In my particular case, the list image would be 64×134 (8,576 pixels), which is even closer to 10,000.

    So I still think the smaller size is unnecessary.

    Your suggestions are great, and thank you for thinking about it. There’s also another option, which is to use the core WordPress function wp_get_attachment_image(), which creates responsive image markup. This way, it will give the browser a few options, and the browser will choose the best one for the space available, while considering screen resolution, for example.

    You see, on a double-density display, 64×134 is not the right size. The right size is 128×268, because the screen density is double. 100×100 would actually look better.

    My thinking is this: if the sizes are good enough for WooCommerce, they should be good enough for WooCommerce addons, and developers should be able to handle this type of setup with best image size settings and optimal CSS.

    You actually don’t have to do this work at all 🙂

    Cheers,
    Gal

Viewing 15 replies - 1 through 15 (of 847 total)