FirstInteractive Scorecard
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

Comment only
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAEAF
1
This spreadsheet accompanies https://goo.gl/KgZcFN
2
VerdictReasonable RegionsRaw numbers
3
SiteSite URLAnnotated TraceFMP based TTINetwork Reverse SearchAbsolute Reverse Search CommentsMetric Improvement ideasReasonable StartReasonable EndNetRevOriginalForward-FMP-5s WindowForward-FMP-1s Window
4
58 picshttp://58pic.com
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=https://deepanjan.me/tti-benchmark-traces/58pic.json.gz
Too earlyReasonableReasonableSite loaded some non-critical images after firstInteractive. Interesting that most things on the site were usable 4 seconds before firstInteractive in the sense that they would respond to user clicks, but there were too many pictures missing for the site to look usable.990016486.7116486.719908.8259908.825
5
Amazon product listing
https://www.amazon.com/Google-Wifi-system-single-point/dp/B01MDJ0HVG/
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=https://deepanjan.me/tti-benchmark-traces/amazon.json.gz
Too earlyReasonableReasonableTough case. The site incrementally makes different parts interactive, and does prioritize more common user actions to load quicker. However there is a 100ms jank to laod the video player (and the site is very clearly still loading various components up until this point), so I think it's reasonable to define firstInteractive after this point.512520018.89620018.8962969.3652969.365
6
Booking.comhttp://booking.com
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=https://deepanjan.me/tti-benchmark-traces/booking.json.gz
ReasonableReasonableReasonable47706335.0236335.0236335.0234150.439
7
Crunchbase
https://www.crunchbase.com/#/home/index
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=https://deepanjan.me/tti-benchmark-traces/crunchbase.json.gz
Maybe too lateMaybe too lateMaybe too lateSite feels ready to use at 14,820, but there are some really long javascript tasks (one is a >500ms task full of layout thrashing) later that pushes back the metric.There is a 500ms task in there somewhere - I don't know if having variable leniency for long tasks would help here.1480422395.90622395.90622395.90614804.418
8
Dawn.comhttp://dawn.com
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=https://deepanjan.me/tti-benchmark-traces/dawn-4g.json.gz
Maybe too lateMaybe too lateMaybe too lateThis is a tricky and contentious case. The main site content is interactive and usable blazingly fast. I suspect this is because the site strives to be simple with very little fancy javascript going on, but even the things that require javascript (e.g. menu button) are interactive in less than two seconds. The only reason firstInteractive gets pushed back to after 10 seconds is a few long scripts late in the page loading phase, which I suspect are for loading ads.The long running JS tasks are 100 - 140ms long, and there are ~3 of these tasks. If we become more lenient the further we are from FMP we might be able to forgive these cases. We must first answer where we want our real firstInteractive to be.1333.15110694.46610694.46610694.4661333.151
9
Doubleclick landing page
https://www.doubleclickbygoogle.com/
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/doubleclick.json.gz
ReasonableReasonableReasonableSite is usable for most use cases before the firstInteractive point, but all of the interface of the site becomes usable at the calculated firstInteractive point so the timestamp looks totally reasonable. 645013757.97913757.97913757.9797201.801
10
Ebaywww.ebay.com
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/ebay.json.gz
Maybe too lateMaybe too lateMaybe too lateSite is completely usable around 7.5s, but some longish running ads/tracking scripts pushes our metric back to 10s340010072.76810072.76810072.7683203.156
11
EBShttps://www.ebs.in/IPS/
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/ebs.json.gz
ReasonableReasonableReasonableIt feels like this worked by luck.836519809.04119809.04119809.0418030.941
12
Flipkarthttps://www.flipkart.com/
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/flipkart.json.gz
ReasonableReasonableReasonableIt's hard to pinpoint the exact moment the site became interactive, but it feels like firstInteractive fired at a great time.69007513.3257513.3257513.3257513.325
13
France TV Infohttp://www.francetvinfo.fr/
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/francetvinfo.json.gz
Maybe too lateMaybe too lateMaybe too lateSite was totally interactive at 4.2 seconds but then ads/analytics scripts pushed it back to 7.5s.Being more lenient about long tasks the further we are from FMP may fix this.42877536.0397536.0397536.0392898.499
14
Housing
https://housing.com/in/buy/real-estate-hyderabad
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/housing.json.gz
ReasonableReasonableReasonablefirstInteractive fires when search box starts behaving properly.25304088.0184088.0184088.0182455.537
15
Inbox (logged in)https://inbox.google.com
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/inbox.json.gz
Maybe too lateMaybe too lateMaybe too lateThis is the inbox website we use everyday, and it certainly does not take 18 second to become interactive. Everything on the page, including the chat sidebar, is usable by around 6s, but there is a ~200ms long task around 18s from an XHR callback that pushs back our firstInteractive. Being more lenient about long tasks the further we are from FMP may fix this.323018400.67718400.67718400.67710494.933
16
Live nationhttp://www.livenation.com/
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/livenation.json.gz
ReasonableReasonableReasonableSite is actually interactive around 7s, but the jank at 10 second is big enough (330ms + more >50ms tasks) that pushing back firstInteractive until that point feels reasonable. 460011043.02511043.02511043.0254605.953
17
Nasahttps://www.nasa.gov/
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/nasa.json.gz
Too earlyReasonableReasonableSite is usable for most tasks around 11s, but there the search and share buttons load around 17s and feels like a better time point to declare firstInteractive.1034517477.63317477.63310347.36310347.363
18
NPRhttp://www.npr.org/
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/npr.json.gz
ReasonableMaybe too lateMaybe too lateSite is totally usable about 10s, but there is some long task around 17 second that pushed back reverseSearch firstInteractive. Not sure what that task is doing. Being more lenient about long tasks the further we are from FMP may fix this.534817431.4917431.4910877.7525347.742
19
TEDhttp://www.ted.com
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/ted.json.gz
ReasonableReasonableReasonablePerfect firstInteractive detection. All the user interface starts responding to user input aorund 11s, and that's exactly when we declare firstInteractive.630011588.52311588.52311588.5236301.371
20
TheStarhttp://www.thestar.com.my/
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/thestar.json.gz
ReasonableMaybe too lateMaybe too lateThe site became completely usable at 28s, but at 36s some onLoad handler fires that has a single 110ms task, which pushes back the reverseSearch firstInteractives to 36s. That onLoad handler doesn't really change the site experience in any tangible way for me except for a very brief jank, so pushing it so far out feels unfair. Being more lenient about long tasks the further we are from FMP may fix this.2403836777.82236777.82228161.17623943.07
21
Travis branch page
https://travis-ci.org/GoogleChrome/lighthouse/branches
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/travis.json.gz
ReasonableReasonableReasonablefirstInteractive fired at a great time here, but it feels like we were luck to detect the large paint/layout task on the main thread. I'm scared that if the site was structured a little bit differently to avoid this large paint task we would fire firstInteractive prematurely.Perhaps we can not fire firstInteractive if there are too many small javascript tasks with almost no delay between them.1195012464.19112464.19112464.19112464.191
22
Twitter (Logged in)https://twitter.com
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/twitter.json.gz
Maybe too lateMaybe too lateMaybe too lateSite is completely usable at 4s, but a small 60ms task later pushes firstInteractive to 6.5sBeing more lenient about long tasks the further we are from FMP may fix this.41406395.4766395.4766395.4764112.523
23
Vevohttps://www.vevo.com
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/vevo.json.gz
Too earlyReasonableReasonablefirstInteractive fires when search and share becomes active, and app install banner shows up.537019323.98619323.9865331.0195331.019
24
Vinehttps://vine.co
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/vine.json.gz
ReasonableReasonableReasonableIt might have been better if firstInteractive fired after the thumbails were loaded becase the thumbnails are part of the core site experience, but since firstInteractive fires after the thumbnails start responding to user tap this is still reasonable. 936010565.77710565.77710565.7778791.034
25
Weatherhttp://weather.com
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/weather.json.gz
ReasonableReasonableReasonableThe interface was responsive sooner, but the thumbnails on the page took a while to load and the page did not look usable until that time. 12.8 seconds was a perfectly reasonable time to fire firstInteractive. 736512869.88612869.88612869.8866318.171
26
Wikipedia article
https://en.m.wikipedia.org/wiki/Solo_Foods
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/wikipedia.json.gz
ReasonableReasonableReasonableStraightforward case. FirstInteractive is declared when menu button starts working. 23424481.4314481.4314481.4311819.866
27
Yahoohttp://www.yahoo.com
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/yahoo.json.gz
Too earlyMaybe too lateMaybe too lateThe ideal time to fire firstInteractive would be around 15 seconds, but then a script that preloads some left bar menu item takes 55ms and pushes back firstInteractive to 17.2s. Being more lenient about long tasks the further we are from FMP may fix this.513817237.36317237.3635140.8745140.874
28
Yahoo news post
https://www.yahoo.com/news/were-top-10-most-visited-us-national-parks-105323727.html?ref=gs
http://deepanjan.me/timeline-viewer/?loadTimelineFromURL=http://deepanjan.me/tti-benchmark-traces/yahoo-news.json.gz
ReasonableReasonableReasonableThe site is fully usable at 6.2 seconds, but the 192ms task shortly after introduces a big enough jank that pushing firstInteractive to 7.4 seconds seems fair.27657470.5417470.5417470.5414066.655
29
30
31
32
Total Reasonable141616
33
Total Maybe too late699
34
Total Too early500
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...