Luhnar Site Accelerator FAQ

Accelerator FAQ

Getting Started

What does it take to get started?

Setup is easy and only takes a few minutes:

  1. Create an account and enter the domain name for your site. You will then get to preview the accelerated version of the site to make sure everything looks OK.
  2. When you're ready to go live, you can either let us automatically set up HTTPS for the site with a free SSL certificate, or provide your own if you already have one you would like to use.
  3. Then, simply log in to your DNS provider's control panel and change your domain to point to Luhnar.

How can I test how fast my site will load on a mobile device?
One way to get a feel for how quickly your site loads on mobile is to use the Google Chrome web browser and open Developer Tools (Under "More Tools" in the Chrome menu). From there, click on the mobile device icon (second from the left on the Developer Tools menu bar). This will display the device toolbar. Finally, on the right side of the device toolbar (just below the Chrome address bar), click on the drop-down where it says "online" and choose "Mid-tier mobile" to simulate a mobile network connection. It's also a good idea to clear your cache in order to test the load time for new visitors (check the "Disable cache" setting in Developer Tools under "Network").

How much does Luhnar Site Accelerator cost?
It depends on how much bandwidth you will need, but plans start at just $10/mo. Bandwidth is calculated per accelerated website and includes both incoming and outgoing data. We provide a 30-day free trial period for every site, during which time you will be able to visit our control panel to see a report of how much bandwidth your site is using. You can expect Luhnar to reduce your current bandwidth usage by at least 20% due to our advanced compression techniques. Check out our pricing page to learn more.

How do I log in to my CMS admin panel after enabling Luhnar?
For many content management systems, your admin panel will continue to function normally using Luhnar's default settings. However, if you are using a custom system or have modified the default admin URL for your CMS, you may need to add a URL prefix for the admin portion of your site to the "Never cache" site setting under "Advanced Settings" in the Luhnar control panel. This will prevent Luhnar from caching any admin pages, as they may contain sensitive information. If your CMS login page simply refreshes after you attempt to log in, your CMS may be trying to associate your login session with a particular client IP address. To work around this, configure your web server to use the X-Forwarded-For header, set by Luhnar, to pass on the correct IP address to the CMS. Alternatively, you can log into your CMS directly, using the origin domain name you created when setting up Luhnar for the site.

After enabling Luhnar, will I still have access to other things running on my server, such as FTP and cPanel?
Absolutely. However, it is important to note that Luhnar only forwards HTTPS traffic on the standard port (443). Therefore, to access additional services that may be running on your server on different ports, such as FTP, SSH, cPanel, WHM, or email (POP/IMAP), you will need to use the origin domain name that you created when adding the site to Luhnar.

How does Luhnar Site Accelerator compare to a CDN?
While a CDN can help your site load faster by offloading static assets—typically CSS, JS, and images—from your web server, they only solve one piece of the puzzle. In contrast, Luhnar Site Accelerator provides an all-in-one solution for site performance issues, with advanced asset optimization bots, full-site caching, transport acceleration, site health monitoring, and more. Unlike a CDN, Luhnar doesn't require changing up your URLs or tweaking a bunch of CMS settings. With Luhnar all of your images continue to be served from your primary domain name, so you don't lose out on SEO bonuses for inbound links and image searches like you would with a CDN.


What happens if I go over my bandwidth allowance?
Nothing scary. Your site remains online and you are automatically bumped up to the next billing tier. Each month we check the amount of bandwidth you have used, and then simply bill you based on the tier that matches your current usage.

How does Luhnar handle forms and other POST requests?
Luhnar simply forwards POST and PUT requests to the origin server that hosts the site. This means that form submissions, AJAX requests, and REST API calls will continue to work as expected. Note, however, that all request bodies are limited to 250 MB.

Does Luhnar offer a service level agreement (SLA)?
While we strive to always be up and running, we currently do not offer a blanket SLA. If you have a large site that requires an SLA, please contact us and we would be happy to discuss your needs.

I'm Worried

Will Luhnar work for my site?
Luhnar is designed to work well for most sites, but may not be a good fit for interactive content and web applications. Luhnar may also not be a good fit for sites that use a site builder platform, such as Squarespace, since some of the optimization techniques those platforms use may conflict with Luhnar's. That being said, it doesn't cost anything to try Luhnar on a site with our free 30-day trial. You can preview the accelerated version of a site without having to change anything about the way the site is hosted or configured.

Can using Luhnar Site Accelerator hurt my site?
While Luhnar's defaults work well for many sites, in some cases you may need to adjust a few settings in the Luhnar control panel. For this reason, we always recommend thoroughly testing newly-added sites via our test domain, before going live and switching over the primary domain. This gives you a chance to identify any potential issues and adjust site settings accordingly.

What if I have an image, JS file, or other asset that I don't want optimized?
By default, Luhnar optimizes all CSS, JS, and image files. If you have an image that you need to provide at studio quality to your visitors (e.g., for professional editing or printing), simply add "x-original=yes" to the query string in the image URL to disable optimizations. Similarly, in the rare case that a particular JavaScript or CSS file is not working correctly after being minified, simply add "x-original=yes" to the query string for the asset's URL. Adding this parameter will disable Luhnar's minifier.

I've spent a fair amount of time improving my performance—what can you do for me?
While there are occasionally sites that don't see a useful performance boost from Luhnar, they are the exception. Almost every site has some optimizations left undone. For example, Luhnar Site Accelerator uses cutting-edge image compression technologies that most developers and designers haven't adopted yet. Give it a try with our free 30-day trial to see how well it works for you.

I've spent a lot of time optimizing SEO, why should I care about Luhnar? Will this really help?
Yes—most typical SEO work isn't performance or security related, but Google's site speed and HTTPS bonuses can give you the edge you need. Plus, if you serve your images through Luhnar instead of a static asset CDN, all your URLs will then use your primary domain name, so that you no longer lose out on SEO bonuses for inbound links to your images or image searches.


What does Luhnar do for security?

We do what we can, but not everything about your site is under our control. Here's what we handle:

  • Automatic HTTPS with support for TLS 1.3 and protection against common SSL/TLS attacks
  • A free SSL/TLS certificate for your domain, or reuse a cert you already own
  • Distributed denial-of-service (DDoS) protection

Check out our features page to learn more.

I don't really need HTTPS, do I?
Your site will function without HTTPS, but it is highly recommended that you serve all of your content over an HTTPS connection. Doing so not only helps prevent hackers from hijacking your JavaScript libraries and other sensitive assets, but also improves your SEO and site speed.

Do I need to pay for another SSL certificate?
If you already have a certificate that you would like to reuse, you can configure it for your site in the Luhnar control panel. Otherwise, we will issue a free SSL/TLS certificate for your domain. Unless you have already invested in an Extended Validation (EV) certificate, we recommend simply keeping your existing certificate in place on your origin server, and letting us issue a free additional certificate for the accelerated version of the site.

Do I need to change the certificate on my server?
If you have already configured HTTPS on the origin server with your own certificate, you can simply leave everything as-is. As mentioned above, Luhnar can either re-use your certificate for the accelerated version of the site, or provide a new one free of charge. On the other hand, if the origin server only speaks HTTP, Luhnar can be configured not to use HTTPS when forwarding requests.

Does Luhnar offer DDoS protection?
Yes, Luhnar Site Accelerator has built-in DDoS protection that is enabled by default for every accelerated site.

Is Luhnar PCI compliant?
At Luhnar we take security seriously and work hard to protect the privacy of site visitors. We provide everything you need to complete PCI-DSS SAQ A. However, we do not currently offer comprehensive PCI-DSS compliance for passing card holder data through our systems, as this is not needed by most sites. If you need to accept credit cards on your site, we recommend using your payment service provider's hosted or iframe solution. In this way, you can avoid passing card holder data though your server, which would then require full PCI-DSS compliance for your site. That being said, Luhnar does not store submitted form data and only passes sensitive data through to your site over a secured HTTPS connection (when supported by your web server).


What are POPs?
POPs are Points of Presence—in Internet terms, this means a server or cloud node in a particular location. Luhnar has a number of POPs, located strategically across North America and around the world, helping to move your content closer to site visitors. This approach shortens the commute time between the browser and the server.

How does Luhnar handle user agent sniffing?
Luhnar Site Accelerator will forward the User-Agent string from the browser when requesting pages, but we recommend not configuring your origin server to return different content based on that string, as doing so may result in sub-optimal caching.

How does Luhnar determine how long to cache a page or asset?
For cacheable pages and assets, Luhnar first checks for any cache-control headers returned by the origin server that hosts the site. If the origin server specifies a cache duration of at least a few hours, Luhnar will cache the item for that same duration. Otherwise, Luhnar uses a default duration that is tuned to balance site performance with content freshness. Note that you can always manually refresh Luhnar's cache from the site settings page in the Luhnar control panel.

How does Luhnar determine whether something is cacheable?
Luhnar automatically optimizes and caches static assets, such as CSS, JavaScript, PDFs, and fonts. When it comes to pages, Luhnar will only consider them cacheable if they match one of the path prefixes or full paths listed under "Always cache" in the site settings. Also, if "HTML Auto Cache" in the settings is enabled, a page will be considered cacheable if it appears to be static (the HTML is not personalized for different visitors). Luhnar will always disable caching for "view cart", "checkout", and "control panel" pages for common CMS and site builder platforms. Luhnar will also detect and disable caching for any requests that set cookies.

Does Luhnar pass on the client IP address for site visitors?
Luhnar sets both the X-Forwarded-For and Forwarded headers for requests that are passed on to the origin server.

What types of traffic will Luhnar forward?
In order to prevent abuse and ensure quality-of-service, Luhnar only forwards HTTPS traffic on the standard port (443) to the origin server. Therefore, to access additional services that may be running on your server on different ports, such as FTP, SSH, cPanel, WHM, or email (POP/IMAP), you will need to use the origin domain name or IP address for the site.

Didn't See Your Question?

No worries. Just contact us and we’ll be happy to help.

Try It Free for 30 Days

There's no risk to trying Luhnar. You'll see the speed improvement in minutes and you'll be able to prove it boosts sales in a week or two.

Sign Up Now