images
6 years ago
javascript
5 years ago
stylesheet
5 years ago
admin.php
5 years ago
connect.php
5 years ago
dashboard.php
5 years ago
diag.php
5 years ago
help.php
6 years ago
help.php
103 lines
| 1 | <div> |
| 2 | <div class="row"> |
| 3 | <div class="col-md-12"> |
| 4 | <div class="card card-faq-item"> |
| 5 | <div class="card-header"> |
| 6 | Can I use another page caching plugin and NitroPack.io at the same time? |
| 7 | </div> |
| 8 | <div class="card-body"> |
| 9 | <p>WordPress is designed in a way that you can use only a single page cache solution at a time. Such is the case with other page cache solutions too. You can use other non-page cache optimization solutions perfectly well with NitroPack.io (example: ShortPixel).</p> |
| 10 | </div> |
| 11 | </div> |
| 12 | </div> |
| 13 | </div> |
| 14 | <div class="row"> |
| 15 | <div class="col-md-12"> |
| 16 | <div class="card card-faq-item"> |
| 17 | <div class="card-header"> |
| 18 | What is an optimization? |
| 19 | </div> |
| 20 | <div class="card-body"> |
| 21 | <p>An 'optimization' is when our service optimizes a single version of one of your site URLs. The result is then cached on your website and it is served to all visitors until the cache is deleted or becomes invalid. After that, a second optimization is required for the same URL.</p> |
| 22 | </div> |
| 23 | </div> |
| 24 | </div> |
| 25 | </div> |
| 26 | <div class="row"> |
| 27 | <div class="col-md-12"> |
| 28 | <div class="card card-faq-item"> |
| 29 | <div class="card-header"> |
| 30 | What is the difference between Invalidate and Purge? |
| 31 | </div> |
| 32 | <div class="card-body"> |
| 33 | <p>When our service optimizes the content for a specific page, this content is cached on your site, and it is subsequently served to future visitors. There are two ways to refresh this content - Invalidate and Purge.</p> |
| 34 | |
| 35 | <p>Invalidate only marks the cached content as "stale", but keeps serving it until newly optimized content is available. As a result, your visitors always see optimized content, even though it may be outdated for a short while.</p> |
| 36 | |
| 37 | <p>Purge deletes the cached file from your site, meaning your site visitors will see the updated content immediately, but it will not be optimized for a few requests until NitroPack prepares the newly optimized content. Usually, this takes between a few seconds to a few minutes.</p> |
| 38 | </div> |
| 39 | </div> |
| 40 | </div> |
| 41 | </div> |
| 42 | <div class="row"> |
| 43 | <div class="col-md-12"> |
| 44 | <div class="card card-faq-item"> |
| 45 | <div class="card-header"> |
| 46 | How often should I purge / invalidate the cache? |
| 47 | </div> |
| 48 | <div class="card-body"> |
| 49 | <p>Typically, you should not need to do a cache purge / invalidate manually. You can take these actions in case you want to force NitroPack.io to re-cache the updated site content immediately. In most cases, NitroPack.io takes care of updating the content automatically.</p> |
| 50 | </div> |
| 51 | </div> |
| 52 | </div> |
| 53 | </div> |
| 54 | <div class="row"> |
| 55 | <div class="col-md-12"> |
| 56 | <div class="card card-faq-item"> |
| 57 | <div class="card-header"> |
| 58 | If I modify an image/CSS/JS file on my site, why is it not updated in the NitroPack.io CDN? |
| 59 | </div> |
| 60 | <div class="card-body"> |
| 61 | <p>To avoid excessive traffic to your site, we need to cache your image/CSS/JS files on our servers. If you modify the file contents on your end, this will not update it on our end. This expected behavior is a common practice on many other caching solutions (CDN, browser caching, etc.)</p> |
| 62 | |
| 63 | <p>To force NitroPack to download the new file, you can either:</p> |
| 64 | |
| 65 | <p>Option 1) Save the file with a different name, and update your site content to use the new name. After that, please make sure to invalidate all NitroPack cache. Doing this is the best way to ensure the updated content will be re-cached while avoiding excessive traffic to your server.</p> |
| 66 | |
| 67 | <p>Option 2) Do a complete purge of your NitroPack cache, forcing our service to re-download all resources.</p> |
| 68 | </div> |
| 69 | </div> |
| 70 | </div> |
| 71 | </div> |
| 72 | <div class="row"> |
| 73 | <div class="col-md-12"> |
| 74 | <div class="card card-faq-item"> |
| 75 | <div class="card-header"> |
| 76 | What are the advantages and disadvantages of Medium, Strong, and Ludicrous? |
| 77 | </div> |
| 78 | <div class="card-body"> |
| 79 | <p>Ludicrous mode ensures you receive the highest possible PageSpeed score, as it uses a resource loader script which alters the way your CSS and JS resources are loaded/rendered (in some cases, some resources are delayed). The resource loader is generally stable, but on some themes, it may cause unexpected behavior.</p> |
| 80 | |
| 81 | <p>Strong mode also has a resource loader, but it is loading your resources without delaying them - this produces better stability, but also gives lower PageSpeed scores compared to Ludicrous mode.</p> |
| 82 | |
| 83 | <p>Finally, Medium does not have the resource loader enabled, ensuring better stability, but it does not give the best PageSpeed scores.</p> |
| 84 | |
| 85 | <p>Which option is best for you depends on the way your theme is coded, and the 3rd party CSS and JS resources it utilizes. As a rule of thumb, the best mode is the one which produces the highest scores with the least user experience issues.</p> |
| 86 | </div> |
| 87 | </div> |
| 88 | </div> |
| 89 | </div> |
| 90 | <div class="row"> |
| 91 | <div class="col-md-12"> |
| 92 | <div class="card card-faq-item"> |
| 93 | <div class="card-header"> |
| 94 | Which optimization mode would you recommend me to use? |
| 95 | </div> |
| 96 | <div class="card-body"> |
| 97 | <p>We recommend you to use the Strong mode. If your score is below 80 points on it, we recommend trying the Ludicrous mode. If Ludicrous mode seems too aggressive (as it is delaying the loading of most of the resources), you can stick to using Strong mode.</p> |
| 98 | </div> |
| 99 | </div> |
| 100 | </div> |
| 101 | </div> |
| 102 | </div> |
| 103 |