README.rdoc in watir-performance-0.9.1 vs README.rdoc in watir-performance-0.9.2

- old
+ new

@@ -1,8 +1,9 @@ = watir-performance {<img src="https://badge.fury.io/rb/watir-performance.svg" alt="Gem Version" />}[https://badge.fury.io/rb/watir-performance] {<img src="https://api.codeclimate.com/v1/badges/ce9c9de5e6146dedab27/maintainability" />}[https://codeclimate.com/github/MacCracken/watir-performance/maintainability] +{<img src="https://api.codacy.com/project/badge/Grade/fc700f21a3f446fc8f3b3c2aca400430" alt="Codacy code quality" />}[https://www.codacy.com/manual/MacCracken/watir-performance?utm_source=github.com&utm_medium=referral&utm_content=MacCracken/watir-performance&utm_campaign=Badge_Grade] {<img src="https://travis-ci.org/MacCracken/watir-performance.svg?branch=master" alt="Build Status" />}[https://travis-ci.org/MacCracken/watir-performance] Successor to 90kts:watir-webdriver-performance[https://github.com/90kts/watir-webdriver-performance] for Watir as opposed to watir-webdriver. The Watir-Performance aims to provide a set of navigation timing metrics for Watir[https://github.com/watir/watir] actions using a {W3C page performance standard}[https://w3c-test.org/navigation-timing/]. This is a perfect solution to capture response time metrics, and it’s very straightforward to do. Works for Chrome, Firefox, Edge and IE9 and up. Currently no Safari support.