Title: Preload website?
Last modified: April 12, 2022
---
# Preload website?
* [pkiula](https://wordpress.org/support/users/pkiula/)
* (@pkiula)
* [4 years, 1 month ago](https://wordpress.org/support/topic/preload-website/)
* Having tried so many bloated and complicated cache plugins, I absolutely love
the simple effective plugin that this is.
* One request – is there any way I can re-preload the page or post or custom post
type that was just updated? Including the home page? This is one feature that
will make this a 100% cache plugin for us.
* Thanks!
Viewing 3 replies - 1 through 3 (of 3 total)
* Thread Starter [pkiula](https://wordpress.org/support/users/pkiula/)
* (@pkiula)
* [4 years, 1 month ago](https://wordpress.org/support/topic/preload-website/#post-15560266)
* Ah, i notice this was asked and answered. A plugin called “Warm Loader”. But
we’d like to do this on our own, without yet another plugin.
* So we wrote a script that “curl”s the website every hour or so.
* I found that this doesn’t do anything. In fact it slows down the website further.
What am I missing? Does Cache Enabler deal with curl requests differently? In
the dashboard I can see the cache size is increasing when our cron script runs.
But the website is slow and in an incognito window (non logged in user) the pages
loading are NOT the ones from the cache.
* Any tips? Are we overwriting and confusing the Cache Enabler functionality somehow?
What could we do to ‘check’ that the cache for a page exists, and access it via
curl only if the cache does NOT exist?
* Thanks.
* Thread Starter [pkiula](https://wordpress.org/support/users/pkiula/)
* (@pkiula)
* [4 years, 1 month ago](https://wordpress.org/support/topic/preload-website/#post-15565483)
* Is there anyone here? We have fairly sophisticated
“warm preloader” on our own.
It goes through our sitemap and “curl’s them, so Cache Enabler is already writing
the requisite files in the `/cache/cache-enbaler/[domain.com]` folder.
* Secondly, we have Apache rules in our `.htaccess`, and importantly, this is ABOVE
the wordpress block:
* ```
#===========================================================
# BEGIN Cache Enabler
RewriteEngine On
RewriteBase /
# cache directory
SetEnvIf Host ^ CE_CACHE_DIR=/wp-content/cache/cache-enabler
# default cache keys
SetEnvIf Host ^ CE_CACHE_KEY_SCHEME http-
SetEnvIf Host ^ CE_CACHE_KEY_DEVICE
SetEnvIf Host ^ CE_CACHE_KEY_WEBP
SetEnvIf Host ^ CE_CACHE_KEY_COMPRESSION
# scheme cache key
RewriteCond %{HTTPS} ^(on|1)$ [OR]
RewriteCond %{SERVER_PORT} =443 [OR]
RewriteCond %{HTTP:X-Forwarded-Proto} =https [OR]
RewriteCond %{HTTP:X-Forwarded-Scheme} =https
RewriteRule ^ - [E=CE_CACHE_KEY_SCHEME:https-]
# device cache key
# SetEnvIf User-Agent "(Mobile|Android|Silk/|Kindle|BlackBerry|Opera Mini|Opera Mobi)" CE_CACHE_KEY_DEVICE=-mobile
# webp cache key
# SetEnvIf Accept image/webp CE_CACHE_KEY_WEBP=-webp
# compression cache key
#
# SetEnvIf Accept-Encoding gzip CE_CACHE_KEY_COMPRESSION=.gz
# AddType text/html .gz
# AddEncoding gzip .gz
#
# get cache file
SetEnvIf Host ^ CE_CACHE_FILE_DIR=%{ENV:CE_CACHE_DIR}/%{HTTP_HOST}%{REQUEST_URI}
SetEnvIf Host ^ CE_CACHE_FILE_NAME=%{ENV:CE_CACHE_KEY_SCHEME}index%{ENV:CE_CACHE_KEY_DEVICE}%{ENV:CE_CACHE_KEY_WEBP}.html%{ENV:CE_CACHE_KEY_COMPRESSION}
SetEnvIf Host ^ CE_CACHE_FILE=%{ENV:CE_CACHE_FILE_DIR}/%{ENV:CE_CACHE_FILE_NAME}
# check if cache file exists
RewriteCond %{DOCUMENT_ROOT}%{ENV:CE_CACHE_FILE} -f
# check request method
RewriteCond %{REQUEST_METHOD} =GET
# check permalink structure has trailing slash
RewriteCond %{REQUEST_URI} /[^\./\?]+(\?.*)?$
# check permalink structure has no trailing slash
# RewriteCond %{REQUEST_URI} /[^\./\?]+/(\?.*)?$
# check excluded query strings
RewriteCond %{QUERY_STRING} !^(?!(fbclid|ref|mc_(cid|eid)|utm_(source|medium|campaign|term|content|expid)|gclid|fb_(action_ids|action_types|source)|age-verified|usqp|cn-reloaded|_ga|_ke)).+$
# check excluded cookies
RewriteCond %{HTTP_COOKIE} !(wp-postpass|wordpress_logged_in|comment_author)_
# deliver cache file
RewriteRule ^ %{ENV:CE_CACHE_FILE} [L]
# END Cache Enabler
#===========================================================
#===========================================================
# BEGIN WordPress
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress
#===========================================================
```
* But:
* 1. Cache Enabler is often not finding its own cached files. In totally new Incognito
window, so no user logged in. It should be serving cached files.
* 2. The Apache logic above seems never to be met… so CE is always going to wordpress.
* Any thoughts?
* [albie2011](https://wordpress.org/support/users/albie2011/)
* (@albie2011)
* [3 years, 10 months ago](https://wordpress.org/support/topic/preload-website/#post-15882774)
* We use cache-warmer.com – not expensive and works well.
Viewing 3 replies - 1 through 3 (of 3 total)
The topic ‘Preload website?’ is closed to new replies.
* 
* [Cache Enabler](https://wordpress.org/plugins/cache-enabler/)
* [Support Threads](https://wordpress.org/support/plugin/cache-enabler/)
* [Active Topics](https://wordpress.org/support/plugin/cache-enabler/active/)
* [Unresolved Topics](https://wordpress.org/support/plugin/cache-enabler/unresolved/)
* [Reviews](https://wordpress.org/support/plugin/cache-enabler/reviews/)
* 3 replies
* 2 participants
* Last reply from: [albie2011](https://wordpress.org/support/users/albie2011/)
* Last activity: [3 years, 10 months ago](https://wordpress.org/support/topic/preload-website/#post-15882774)
* Status: not resolved