I bring you a tutorial on BunnyCDN, for me the best CDN today that you can use on your WordPress website.
And eye, that in the last weeks I have tried a lot of CDNs.
By the way, you should know the importance of using a CDN in WordPress and see if you need it.
Get ready because you will learn everything.
What is BunnyCDN?
BunnyCDN is a CDN that has great technology and also at the best price.
It has 37 data centers spread across 6 countries, where it has many technologies.
In terms of optimization, it has GZIP, HTTP / 2, HTTP streaming, video streaming, cloud storage and many more.
Then insecurity we have many functions such as free SSL Let’s Encrypt or you can upload yours, Hotlinking protection, user blocking, and others.
If there is something important to see in a CDN is the price, because depending on what your website consumes, you will pay.
BunnyCDN has normal and high volume rates if you consume more than normal.
To give you an idea, in Ragose I spent 7.64 this month and I will pay only 0.21 Euros.
Even if you don’t worry, because you can try it for 14 days for free without any commitment.
Storage prices are also more than affordable, costing 0.01 per GB per month.
Then you recharge the balance you need, something that does not happen with others that you pay month to month, consume what you consume.
BunnyCDN VS Cloudflare
I guess you’ll have doubts about whether you use BunnyCDN or Cloudflare.
Personally I prefer to use the first one, since Cloudflare usually has a much higher TTFB, to provide all the security systems it has.
This slows the web down a lot.
BunnyCDN VS KeyCDN
If we compare BunnyCDN with KeyCDN, the prices of the former are much lower.
You can save more than 80% on CDN expenses.
BunnyCDN tutorial step by step
Registration in BunnyCDN
To register go to the BunnyCDN page and click on the Try BunnyCDN button .
Fill in username and password, accept the terms and voila.
What you will have to do is verify your email using an email that arrives.
Once verified, you will reach the main panel where you can see everything.
Although it sends you to a special panel, within this you will see:
- Overview: What is the summary panel of everything.
- Pull Zones: The CDN zones that we will create. I recommend one per web.
- Storage: The storage areas that we will create.
- Statistics: Here you can see what you consume.
- Purge: To purge your CDN.
- Logs: A log in real-time.
- Monitoring: a real-time monitor.
Create a pull zone in BunnyCDN
A pull zone or extraction zone is where the static files of your website are going to be stored and from where they will be served.
- Give your pull a name: For example ragose.
- Enter the URL of your website: included if it has SSL.
- Choose the type of pull zone: Standard for small sites or high volume tier for large or streaming video sites.
Once you have it, within manage pull zones you can edit each one and be careful, there is a lot to customize here.
In the general section, you can see the hostname that has been created and which in my case is ragose.b-cdn.net.
But you can add a custom cname to the cdn.ragose.com style so that the content is part of your website.
Within the caching section you can make some changes:
- File Cache Expiration Time: If you want to respect the expiration time that some plugins like WP Rocket insert or put yours. I prefer Rocket to manage it.
- Disable cookies: If we activate, the pull zone will not put cookies, which fixes the GTMetrix warning of using a cookie-free domain.
- Vary cache: In Vary Cache or variable cache, certain parameters such as user location will be used to display custom content.
In pricing you can simply change one billing system to the other.
Within security we can configure certain security parameters:
- Block Root Path Access: if you want to block the main URL of the CDN that will give an error 403. I do not recommend it, because it gives you an idea of whether it works well.
- Enable Logging: Activate or deactivate the log of this pull zone.
- Anonymize Log IPs: anonymize the log IPs, which is recommended at the GDPR level.
- Blocked Referrers: in case you want to block access to the pull zone and avoid hotlinking.
- Allowed Referrers: better than the previous one, because only the only ones active here will have access to the pull zone. Beware of social networks and similar, that the linked images will give 404 error.
- Blocked IPs: in case you want to block specific IPs.
- Enable AWS S3 Authentication: In case you use Amazon S3 storage and want to give access.
In Authentication it allows you to create URLs that expire after a certain time and are accessible by means of a token or secret key.
I’m not going to get into this, because if you don’t know what it is, you don’t need it and if you know it, you don’t need an explanation.
In Traffic Manager we can manage where we want our files to be served through the pull zone.
As simple as selecting with the mouse and choosing if that country will be redirected (yellow) to another area or blocked (red).
Within Headers we can add certain parameters to the headers, some of them very important.
- Add CORS Headers: Add the Cross-Origin Resource Sharing headers, which guarantees that those files are original for security.
- Add Canonical Headers: Add canonical headers, interesting topic for SEO.
- Forward Host Header: This redirects the request to the source server. It should not be enabled.
The Optimize section is one of the most interesting, since it allows you to configure certain settings that improve speed, although I have my opinion and prefer to do it differently.
In addition, it is paid, so if you want to enjoy it, you will have to take out your wallet.
- WebP Compression: Convert images to WebP and serve them to customers that are compatible. I prefer to do this with WordPress.
- Manipulation Engine: This manipulates the images live, being able to change the width, height, crop and others.
- Minify CSS files: Compress the CSS. I prefer to do it with plugin.
- Automattic Image Optimization: Optimizes images. I prefer to do it with plugin.
- Watermark images: In case you want to put a watermark, without altering the original images.
In Edge Rules you can configure certain rules of how the CDN can behave.
For example, you can create certain redirection rules, depending on the characteristics of the visitor.
In the Network Limits section you can assign certain limits to your pull zone.
From the connection speed, the requests per second, the maximum number of connections or the maximum band consumption that the pull zone can consume.
In the Storage section we can create a storage area, to serve files hosted from the CDN.
Once created, we can access as if it were an online FTP and upload what we want.
Or connect one of our pull zones to serve files from it.
Within Statistics we can see all the statistics of our pull zones, being able to filter by date, zone and data center.
I love to see how we can know which servers serve the most data in our extraction area.
By the way we can know how many errors 400 or 500 our website has.
In Purge we will be able to purge or empty our extraction area, either doing only with a URL, if for example we are editing a CSS or the whole area.
In the Logs section we can see the latest movements in our pull zone, to see what is served, from where and to whom.
We can see the correct requests, redirects, errors 400 and 500 and filter by these.
I recommend anonymizing the IPs , although I have left them in this test so you can see them.
In the Monitoring tool we can see in real time how our BunnyCDN account works, although in general, since we cannot filter for anything.
Once you decide to pay for BunnyCDN, which I recommend, you can recharge your credits by clicking on the Billing section .
Above all in the green box you will see at all times the credit you have left.
I have recharged 10 USD and as you can see, in the whole month for having consumed 34 GB , it only cost me $ 0.54 .
It also has a system of recommendations, in which they give you $ 20 for each referral that registers and makes its first recharge.