Want access to MageReport Premium? MageReport Premium is developed for our optimized Magento hosting platform: Hypernode. Check out Hypernode.com for more information.
Table of contents
- 1 Hypernode customers get even more
- 2 Alerting
- 3 Security level
- 4 Performance checks
- 5 Stability
- 6 Charts
Hypernode customers get even more
Anyone can scan their Magento shop with MageReport.com to check whether there are any security issues. However, when logged on with their Byte account, Hypernode customers can access additional data such as Performance checks and charts. MageReport Premium offers a checklist with a complete overview of all your shops and the status per check. MageReport (Premium) offers:
- Security level checks (MageReport & MageReport Premium)
- Performance checks (MageReport Premium only)
- Charts (MageReport Premium only)
The Performance checks and Charts offer specific information about your shop’s performance and help you optimize your Hypernode. That’s why MageReport for Hypernode users is called MageReport Premium.
Accessing MageReport Premium is easy by logging on to MageReport.com with your Byte customer account. Choose ‘Sign in with Byte’ on your top right.
MageReport Premium doesn’t have alerting. If you’re interested in setting up your own alerting, based on serverdata MageReport Premium is also using, please contact email@example.com and we’ll discuss the possibilities with you.
The Security level checks are accessible for any Magento shop owner (Hypernode or not) and show you the safety of your Magento shop. If a check comes out red, navigate to the given knowledgebase How-to and find out how to fix the vulnerability. All Security level how-to’s can be found in the Security category.
The Performance checks in MageReport Premium tell you how to make your shop even faster, by showing the bottlenecks in your Magento.
Number of active caches
This feature shows you how many caching options in your Cache Management (System –> Cache Management) have been enabled. The higher the number of active caches, the better. Caching stores data, so that future requests can be served faster. Read Magento cache management for more information.
Var/log directory size
This check tells you how big your var/log directory has gotten. We recommend keeping your var/log directory below 100 MB. To keep your Magento shop optimized and fast, you’ll need to clean these logs. Cleaning your logs can be done automatically or manually. We recommend your to do it manually, since it’s more efficient. Read Magento log cleaning for more information on how to clean up these logs.
A full disk slows your Hypernode down. You can always upgrade to a bigger node, but in most cases cleaning up your disk is sufficient. More information about cleaning up your disk is explained in How to free up disk space.
When your shop has at least 1600 PHP requests in one day and 30% of those are bots, the bot traffic check in MageReport comes out red. Search engines indexing your webshop are very welcome, though too many bots can quickly consume your shop’s resources. Bots and crawlers often get stuck in the layered navigation of your Magento shop, causing them to crawl every combination of your products and parameters, creating millions of URLs to index and causing bad performance. Read how to optimize your shop by controlling these bots and crawlers in Fixing bad performance caused by search engines.
This check shows you your average PHP response time in seconds. Keeping your load time below 1 second is preferable to keep your shop fast. The faster the webshop, the higher the conversion. A good tool to further analyze performance bottlenecks, and improve your response time, is New Relic. Read all about New Relic in Find your performance bottleneck with New Relic.
We recommend you to keep at least 20% free to speed up file access and to make sure your Hypernode doesn’t slow down, or worse, stop working. If your shop is using more than 80%, consider upgrading to a bigger Hypernode to guarantee the continuity of your shop. Optimizing your Hypernode with caching tools such as Varnish and Redis helps reduce the memory usage. Use New Relic to pinpoint which pages are slurping memory and find the cause.
I/O operations stands for Input/Output operations and shows how much information is transferred between programs, and devices, such as Magento, and your Hypernode’s hard drives. The chart shows you the number of I/O operations per minute. To keep your Hypernode optimized we recommend you to keep the average below 100 (Warning) or 300 (Critical), or your site may slow down significantly. See our knowledgebase for more information about optimizing your Hypernode.
Not optimizing images properly results in extremely slow loading time. Quick loading images is important and a quick loading website keeps visitors engaged. Resizing images can take up a lot of time, so we took care of this for you. We developed a tool that’ll optimize all your images for you. You just need to take a few steps, explained in this Magento image optimization howto, and you’re all set!
NB: MageReport.com checks for a cronjob that optimizes your images periodically. If you optimized your images only once, the check will come out red.
Storefronts configured correctly?
Hypernode is cloud-based hosting, which means your IP can change. To make sure your visitors can still reach your Magento shop after a configuration change, you’ll need to redirect your storefronts using a CNAME. With
n98-magerun you can find which storefronts are configured in in your webshop:
This tool shows the storefronts configured in your shop and the storecode. In MageReport Premium you can check whether your DNS is configured correctly. See our manual on configuring DNS for more information.
If you’re using Cloudflare the check will say your storefronts aren’t configured correctly and your shop is not live. Right now MageReport can’t detect if a shop is using Cloudflare, so you can ignore this.
Most charts give you more specific information about a Performance check.
PHP requests per minute
This chart shows the average number of PHP requests per minute. It includes visitors and bots requesting webpages. The orange line indicates requests done by bots. Bots and crawlers take up a lot of resources, especially in Magento, and can cause your shop to slow down. Read how to optimize your shop by controlling these bots and crawlers in Fixing bad performance caused by search engines.
Average PHP response time (seconds)
The faster a page loads, the longer visitors will stay on your shop. Like the performance check ‘Response time’, the average PHP response time chart shows you (in seconds) how long it takes for pages to load. A well optimized Magento shop should be able to keep the response time below one second.
A good tool to further analyze performance bottlenecks, and improve response time, is New Relic. Read all about New Relic in Find your performance bottleneck with New Relic.
Long running processes
This chart shows you the duration of long running processes. We recommend you to keep FPM processes running under 5 to 10 minutes, SQL processes no longer than 60 minutes and SSH processes no longer than 24 hours. If the proces duration is longer than the given criteria, you should consider them stuck and fix them. Long running processes or stuck processes are often the result of errors in your PHP code, a missing index (in SQL) or a deadlock. Read more about how to stop long running processes in Identifying and stopping long running processes.
A line of 50% or higher in this chart indicates your Hypernode is very busy. If your Hypernode uses a lot of resources, check for an increase of web requests (chart: PHP requests per minute). A periodic cronjob can also cause an increase in CPU usage. Optimizing your Hypernode with caching tools such as Varnish and Redis helps reduce the CPU usage. Consider upgrading to a bigger node if your shops consistently use more than 50% of the available CPU.
Redis memory in use
This chart shows you the percentage of memory in use by Redis and the hitratio (percentage of requests served out of Redis cache). The more data is cached, the more the memory usage increases. The memory usage decreases when expired cache items are removed. Red vertical lines (not always showing), mean your cache was full and Redis deleted the least requested (LRU) items. You’ll notice this can happen when less then 100% is used according to the graph. This is because the graph shows you the average usage (in %) per week.
We recommend you to upgrade to a bigger node if your using more memory than your Hypernode offers. If all available memory is in use, Redis will delete cache items to free up memory, which could lead to a reduced hit ratio depending on your configuration. Every Hypernode has access to Redis, starting from 64 MB, depending on the plan. Please check our website for an overview of the Hypernode plans and their specs.