This repository has been archived by the owner on Feb 8, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 308
Full performance report #4262
Labels
Comments
#4234 is part of 8, but all projects are still being loaded. |
This was referenced Dec 27, 2016
Closed
Closed
Are the italics portions our current times/metrics? How did you set those targets? Are they standard? |
https://gratipay.slackarchive.io/gratipay/page-55/ts-1486065489005059 |
We can't do this for dynamic pages, since Heroku doesn't support HTTP/2 yet. However, we can do this for assets served via the CDN (where it is definitely important, given the number of small requests) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Introduction
The following is a report on the overall performance of https://gratipay.com/. I hope by sharing this we can get more people involved in improving the performance of the website and keep track of what is done and needs doing.
Note: Target values may not be attainable. They are simply there to demonstrate that there is room for improvement.
Table of Contents
1. Page load performance is fast
Users notice if sites and apps don't perform well. These top-level metrics capture the most important perceived performance concerns.
First meaningful paint: 9689.3ms
First meaningful paint measures when the primary content of a page is visible.
Perceptual Speed Index: 5186
Speed Index shows how quickly the contents of a page are visibly populated.
First Visual Change: 916ms
Last Visual Change: 14079ms
Estimated Input Latency: 1706ms
The score above is an estimate of how long Gratipay takes to respond to user input, in milliseconds. There is a 90% probability that a user encounters this amount of latency, or less. 10% of the time a user can expect additional latency.
Time To Interactive: 14186.8ms
Time to Interactive identifies the time at which Gratipay appears to be ready enough to interact with.
Critical Request Chains: 27
The Critical Request Chains below show you what resources are required for first render of this page.
Longest request chain (shorter is better): 3
Longest chain duration (shorter is better): 8296.49ms
Longest chain transfer size (smaller is better): 449.78KB
Other:
2 resources delayed first paint by 703ms:
2. Site is progressively enhanced
Progressive enhancement means that everyone can access the basic content and functionality of a page in any browser, and those without certain browser features may receive a reduced but still functional experience.
3. Network connection is secure
Security is an important part of the web for both developers and users. Moving forward, Transport Layer Security (TLS) support will be required for many APIs.
4. Mobile-friendly
Users increasingly experience Gratipay on mobile devices, so it's important to ensure that the experience can adapt to smaller screens.
theme-color
meta tag.5. Modern protocols
6. CSS
The following elements do not have sufficient colour contrast:
7. JavaScript
8. Best practices
Projects
page into individual pages. Currently it's one big page. (Add a "Featured" tab on the homepage #4234)The text was updated successfully, but these errors were encountered: