LightSpeed

Obligatory disclaimer as you visit these sites: Lightspeed impacts the initial HTML load time, so while the HTML response is in the .1-.3 second range, some of these sites are heavy with images, javascript, css and content which extend the total page load. redmarblesteaks.com, danner.com, betabrand.com, sweetcandy.com, or tinybrick.com.

If you install it right, Lightspeed will produce the results indicated in published benchmarks. We also offer a 15-day full-refund policy. However, we cannot offer a guarantee, as there are too many 'developer-induced' variables outside our control.

Since this is a cached page solution, the answer is yes. After a page set to cache is primed (loaded once), it shouldn't ever need to talk to PHP, Magento, or the Database ever again when loading that page.

The first time a new product page is requested, Magento renders the content. The second time the page is called, Lightspeed serves the content. If you edit and save a product, Lightspeed will drop all references to that product out of cache, and cache the updated results the next time it is requested.

As page caching requires a page load to cache, without intervention, the first page load will be uncached and slower than the following pages loads. If you're truly concerned about a single page load not running as fast as the rest, you'll need to find a way to pre-load the page, like a crawler script, by hand, building your own script, etc... (If you're a linux guru, a simple curl request to each of the affected pages would do great)

No. All changes on the server are only to your application and those are easily done (even if you're not technical) with a few lines added to a couple of files. For those techie among you, as with all our magento modules, enhancements to your application are done in the standard magento modular fashion with class extensions/rewrites (and not by editing app/code/core files).

For a developer, modifying the core usually involves modifying any code inside the app/code/core folder of the Magento application. Magento is meant to be extended/overwritten...not altered. If a developer is making changes to your application by editing code app/code/core, they don't understand this difference and their changes will be erased if Magento is ever upgraded. That said, routine layout changes or extending core functions, rather than altering, should not cause conflicts. Also, even if core modifications are made, the module will likely work, unless the modified code influences caching. So, instead of trying to say which part of the stove isn't going to burn you, it's just typically better to say not to touch the stove at all. If you do, we'd like to not be responsible for any pain that came as a result.

Unfortunately, we don't offer a free trial. Once we've released the code for implementation, we can't recall it, and prefer to avoid the possible issues surrounding that circumstance. In some cases we can issue you a development license for lightspeed, but it is subject to a few restrictions on the base URL of your development environment. Other products aren't available on a trial basis, but if you'd like to see the modules in action we do have demo servers. As always we do offer a 15-day grace period for returns. If things don't work out for any reason in that first 15 days, we'll give you a full refund. Note: You may be asked to allow access to your admin to ensure TinyBrick products have been completely removed.

Ongoing updates are FREE for the life of the product, unless a major upgrade revision requires a major re-architecture of the module. To date, only True Edit Orders has required this once.

Currently, we only accept PayPal, although you can checkout using a credit cart without actually creating a PayPal account.

Modules are sold per domain, and are registered to 1 domain. We offer bulk discounts for the following volumes:

• 2 = 20% off
• 3 = 30% off
• 4 = 40% off
• 5+ = 50% off
The TinyBrick shopping cart will automatically apply these discounts. If you end up purchasing your licenses at separate times, please contact a representative to arrange the promotional discount. You may also want to check out our policy on development licenses.

Yes! Please use the demo servers to test out any scenarios you're curious about. Log in credentials are on the admin log in screen.

• Lightspeed
• True Order Edit
• PromoBot (front-end)
• PromoBot (back-end)
• No PO Box Shipping (front-end)

We strongly encourage dev environments, so we try to do everything we can to accommodate them while still protecting our licenses. So when you are purchasing your original license, purchase it for your ultimate live domain. Then for your dev domain, here are some options: Subdomains: Your domain license will automatically include unlimited sub-domains. (e.g. test.domain.com, beta.domain.com, etc.) Local Domains: Your domain license will automatically include local domains. (e.g. localhost, 127.0.0.1) Dev Domains: If needed, you can request a dev license for a domain or IP that is clearly for development. (e.g. testdomain.com, betadomain.com, devdomain.com, test.domain.com, 67.23.44.251, etc.) We suggest purchasing your initial license for your live domain, then emailing sales@tinybrick.com with your request for a dev domain. 98% of the time we can accommodate your development domain request free of charge.

While there are only a couple of performance products out there for magento, it's important to know the differences so that you can make the performance product choice that best suits your situation. Note: If you have a working install of another product, it probably needs to be uninstalled before using Lightspeed/Speedbooster to prevent conflicts. Aitoc Magento Booster: Lightspeed replaces Aitoc Magento Booster. View published benchmarks on each site to compare response times and concurrent users (dramatic differences). Fooman Speedster: Lightspeed doesn't replace Fooman Speedster so there really is no comparison. This product compresses front-end CSS/JS. Lightspeed uses whole-page caching on the back-end. We have had conflicting reports of issues with conflicts in the .htaccess settings, so you may have to troubleshoot or uninstall Speedster to properly install Lightspeed. Magento Enterprise Edition - Full Page Caching: Lightspeed replaces the full-page caching utility that comes with Magento Enterprise Edition. While fairly comparable in speed, the price tag ($13K/annually per server vs. $500 once per domain - unlimited servers) and some advanced tagging features make Lightspeed the obvious choice. Find another product you think is a better value? Let us know.

Before Lightspeed, Magento generally return results in 2-4 seconds, serving 3 - 20 pages per second. After Lightspeed, you should expect to see HTML response times from 0.1 to 0.4 seconds, serving approximately 300 pages per second, almost independent of server size or traffic, as long as your developer has followed the install documentation and has not modified Magento's core code. We also recommend that you check these results using a tool such as firebug to be able to accurately measure results. More information on measuring the performance of your site can be found in our Speed Testing doc. Note: To further decrease page loads, make sure you've enabled gzip compression, compressed javascript and css, use image sprites, and when possible, a content delivery network.

Lightspeed doesn't directly speed up the admin (Lightspeed focuses on non-committal storefront browsing). It may, however, indirectly free up server resources, allowing the admin to run faster. However, if you're dealing with a slow admin, you might want to check first to see if your server meets the minimum requirements set for Magento to run properly. Sometimes shared hosting servers will NOT provide necessary resources to run Magento, even with Lightspeed installed.

Indirectly, yes. However, you may want to consider other areas of a performance issue if your admin and checkout are both slow. (like Hardware, Server Configuration, etc…).

If used with CE 1.4, the display for the Admin Panel Caching Page shows a 1.3 display (with all the functionality of the 1.4 version), and Widgets do not work currently with this module.

You can potentially run Lightspeed along with other products as long as they don't replicate the function (rewrite the same classes). Aitoc Magento Booster and Magento Enterprise Edition are two such products. Other products like Fooman Speedster have potential to work along side Lightspeed, but you should be careful and it might not hurt to lookup your uninstall procedures for other "speed/booster" modules before purchasing.

"Hole Punching", or tagging to allow dynamic session-related data to be served in the middle of a fully cached page, requires more involved configuration. This includes functions like logged in status or items in cart. You can find more information on this here.

This is a very common bug in how Magento refreshes the admin view. After installing a new module you may be required to force a refresh the admin. Let's walk through how to do that:

• In the admin panel, browse to System -> Configuration -> Advanced (In the advanced section at the bottom left)
• On the left there should be an expandable panel. If not already expanded, expand it.
• It should show a long list of modules. Near the end of the list, you should see one or more of modules labeled "TinyBrick_ModuleName". If you do not, then browse back to the top and click "Save Config".
• After saving, browse to System -> Permissions -> Roles. Open the Administrator role (Since most people are logged in an administrator anyway.)
• Don't edit anything in the role, and click "Save Role".
• After save is complete, you may have to log out and back in, but most likely if you browse back to the long list of modules mentioned earlier, you should see the installed module.
There are a few other possible things to do to get the installed module to start showing up (like clearing all caches in System -> Cache Management, logging out and back in, or disabling and re-enabling the output of a module in that long list while saving in between changing state), but if these steps do not produce an output like you're looking for, then there is probably a larger issue like a module conflict or a step you missed during installation.