CSS file not being handled by caching plugin

  • Resolved Per Olsson

    (@styrketrappan)


    5 years, 3 months ago

    Hi,

    When analyzing my page with GTMetrix or other pagespeed services, I get a warning about a frontend.css file not being delivered through a CDN. I do use Litespeed plugin where all CSS file is minified, delivered by CDN and what not but the Wordproof one seem not to be handled properly. Is it a Litespeed problem that I should report to them or is it something that Wordproof can/should handle?

    This is the info I get in GTMetrix results (I changed the domain name manually so you have to image what the domain name is 🙂 ):
    CDNs can give an equally fast web experience to your users across the globe.

    Learn how to improve this
    URL
    https://xxxxxxxxxxxxxxx.xx/wp-content/plugins/wordproof-timestamp/assets/css/frontend.css

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author WordProof

    (@wordproof)

    5 years, 3 months ago

    Hi Per,

    The stylesheet we include is not loaded in the usual WordPress way, so that is probably the reason Litespeed did not find it. We are will be refactoring the certificate in the coming weeks which will solve this issue for you.

    Marijn

    Robert Lang

    (@robertlang)

    5 years, 2 months ago

    What’s the status on this issue? 6 weeks is plenty of time isn’t it? I just bought your service and I won’t allow any scripts to run from servers I do not control. This is why we created API’s. So only data is sent, not files.

    Does your script pull files from a third party server on pages loaded in a visitor’s browser?

    So far review tests show a 30ms page load. That’s acceptable, but need answer on the above please.

    • This reply was modified 5 years, 2 months ago by Robert Lang. Reason: Additional Information Added
    Plugin Author WordProof

    (@wordproof)

    5 years, 2 months ago

    Hi Robert,

    It has to do with the way the script is loaded, not with a third party server. This will be fixed with the new certificate, but that has not been rolled out to the WordPress-plugin yet. This will take place in April and will also greatly reduce the size of the script. Hope this helps, sorry it hasn’t happened yet!

    Jelle

    Robert Lang

    (@robertlang)

    5 years, 1 month ago

    No worries. I can wait another month to see what you guys come up with? I bought the plugin anyways. And since the script is localized, I have no issues with that. Besides, I use cache servers in my builds. So unless the cert is dynamically pulled from within your script, it won’t even matter. Thanks for responding.

    This is a great improvement in security. It took me nineteen years to wake up Google to https. Now I would like to run your plugin over this year and then provide the results to Google and suggest we get onboard with crypto time stamped certs as well. It’s the only way to be sure.

    Plugin Author WordProof

    (@wordproof)

    5 years ago

    Hey Robert,

    Quick update: the new certificate is almost finished and will reduce the loading time significantly. We expect to roll it out in June. I’ll close this topic for now, feel free to open a new topic / send us an email ([email protected]) in case you have any other questions or remarks!

    Jelle from WordProof

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

The topic ‘CSS file not being handled by caching plugin’ is closed to new replies.

Tags