Denzi Monitor Features2018-11-08T16:47:09+00:00

Denzi Monitor Features

Uptime Monitoring

Demo

Powerful monitoring tools that are quick and easy to set up. Receive instant alerts that you can trust to notify you the moment your site goes down. Gain valuable insights into how your website’s performance is impacting your customers’ experiences.

Get the average response time of your website from different parts of the world.

Sales Monitoring

Access a concise, comprehensive visual review of your shops’ recent performance. Filter through daily, weekly, or monthly sales statistics from the dashboard on the DenZi WordPress Monitoring iOS or Android app.

Vulnerabilities Scanner

Demo

We use the latest technology in vulnerability scanning that uses deep scan technology and can provide instant reports. We keep track of all known bugs in WordPress and have a reliable database to query them. If there is a bug or security issue with your WordPress site, it will most likely show up in our scans. Our scanning technology relies on deep scans and can provides instant reports.

Detailed Analysis of Load Speed and SEO

Demo
  • Page speed tests
    • Metrics
      • First Contentful Paint
      • First Meaningful Paint
      • Speed Index
      • Time to Interactive
      • First CPU Idle
      • Estimated Input Latency
    • Opportunities
      • Properly size images
      • Minify CSS
      • Minify JavaScript
      • Enable text compression
      • Keep server response times low (TTFB)
      • Avoid multiple page redirects
      • Preload key requests
      • Use video formats for animated content
      • Eliminate render-blocking resources
      • Defer offscreen images
      • Defer unused CSS
      • Efficiently encode images
      • Serve images in next-gen formats
      • Avoid multiple, costly round trips to any origin
    • Diagnostics
      • Avoids enormous network payloads
      • User Timing marks and measures
      • Uses inefficient cache policy on static assets
      • Avoids an excessive DOM size
      • Critical Request Chains
      • JavaScript boot-up time is too high
      • Has significant main thread work
      • Text is invisible while webfonts are loading
  • Progressive Web App tests
    • Uses HTTPS
    • Redirects HTTP traffic to HTTPS
    • Has a <meta name="viewport"> tag with width or initial-scale
    • Contains some content when JavaScript is not available
    • Content is sized correctly for the viewport
    • The short_name won't be truncated on the homescreen
    • Page load is not fast enough on 3G
    • Does not respond with a 200 when offline
    • User will not be prompted to Install the Web App
    • Does not register a service worker
    • Is not configured for a custom splash screen
    • Address bar does not match brand colors
  • Accessibility tests
    • Elements Use Attributes Correctly
      • [accesskey] values are unique
      • <audio> elements contain a <track> element with [kind="captions"]
      • <input type="image"> elements have [alt] text
      • No element has a [tabindex] value greater than 0
      • Cells in a <table> element that use the [headers] attribute only refer to other cells of that same table.
      • <th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
      • Image elements do not have [alt] attributes
    • ARIA Attributes Follow Best Practices
      • [aria-*] attributes match their roles
      • [role]s have all required [aria-*] attributes
      • Elements with [role] that require specific children [role]s, are present
      • [role]s are contained by their required parent element
      • [role] values are valid
      • [aria-*] attributes have valid values
      • [aria-*] attributes are valid and not misspelled
    • Elements Have Discernible Names
      • Buttons have an accessible name
      • Links do not have a discernible name
    • Elements Describe Contents Well
      • The page contains a heading, skip link, or landmark region
      • Document has a <title> element
      • Presentational <table> elements avoid using <th>, <caption> or the [summary] attribute.
      • <object> elements have [alt] text
      • <video> elements contain a <track> element with [kind="captions"]
      • <video> elements contain a <track> element with [kind="description"]
      • <frame> or <iframe> elements do not have a title
      • Form elements do not have associated labels
    • Color Contrast Is Satisfactory
      • Background and foreground colors do not have a sufficient contrast ratio.
    • Elements Are Well Structured
      • <dl>'s contain only properly-ordered <dt> and <dd> groups, <script> or <template> elements.
      • Definition list items are wrapped in <dl> elements
      • [id] attributes on the page are unique
      • Lists contain only <li> elements and script supporting elements (<script> and <template>).
      • List items (<li>) are contained within <ul> or <ol> parent elements
    • Page Specifies Valid Language
      • <html> element has a valid value for its [lang] attribute
      • [lang] attributes have a valid value
      • <html> element does not have a [lang] attribute
    • Meta Tags Used Properly
      • The document does not use <meta http-equiv="refresh">
      • [user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
  • Best Practices tests
    • Avoids Application Cache
    • Avoids WebSQL DB
    • Uses HTTPS
    • Uses HTTP/2 for its own resources
    • Uses passive listeners to improve scrolling performance
    • Avoids requesting the geolocation permission on page load
    • Page has the HTML doctype
    • Avoids requesting the notification permission on page load
    • Allows users to paste into password fields
    • No browser errors logged to the console
    • Displays images with correct aspect ratio
    • Uses document.write()
    • Links to cross-origin destinations are unsafe
    • Includes front-end JavaScript libraries with known security vulnerabilities
    • Uses deprecated API's
  • SEO tests
    • Mobile Friendly
      • Has a <meta name="viewport"> tag with width or initial-scale
      • Document uses legible font sizes
    • Content Best Practices
      • Document has a <title> element
      • Links have descriptive text
      • Document has a valid hreflang
      • Document has a valid rel=canonical
      • Document avoids plugins
      • Document does not have a meta description
    • Crawling and Indexing
      • Page has successful HTTP status code
      • Page isn’t blocked from indexing
      • robots.txt is not valid