Update README.md with performance information

Title's self explanatory. I timed paleofetch and neofetch, and though it is a good idea to put that in the readme.
このコミットが含まれているのは:
Simon Gardling 2020-05-01 18:56:03 -04:00 committed by GitHub
コミット af6f3a7430
この署名に対応する既知のキーがデータベースに存在しません
GPGキーID: 4AEE18F83AFDEB23
1個のファイルの変更8行の追加0行の削除

ファイルの表示

@ -4,6 +4,14 @@ paleofetch
A rewrite of [neofetch](https://github.com/dylanaraps/neofetch) in C.
Currently only supports Linux and Xorg.
Why use paleofetch over neofetch?
-----------------------------------------
One major reason is the performance improvement. For example: neofetch finishes running after about 222 milliseconds where as paleofetch can finish running in a blazing fast 3 milliseconds.
Note: this testing occured on only 1 computer, it's not a good representation on the performance benefit you may gain.
Example output:
![example output](example.png)