Thanks everyone for another great #WPOchat Twitter chat!
This month’s #WPOChat was moderated by Alois Reitbauer @AloisReitbauer from http://blog.dynatrace.com
Stay tuned for next months chat topic and moderator announcement.
Here is a copy/past of the #WPOchat Twitter chat.
This archive is a simple copy/paste/ from Tweet Report’s HTML interface.
Thank you again to @AloisReitbauer for moderating and @jonathanklein of CSNStores @utollwi of Yottaa for organizing this chat. Organizers, Moderators, Topics and Suggestions are appreciated. This is a community chat!
|
@sajal: #WPOchat in 20 mins…
|
|
@wpo_chat: Rescheduled: Tomorrow (Wednesday 3/21) 1pm ET Web Performance experts join #WPOchat @AloisReitbauermoderates http://t.co/R9MYzORc #WebPerf
|
|
@cweekly: RT @wpo_chat: Rescheduled: Tomorrow (Wednesday 3/21) 1pm ET Web Performance experts join #WPOchat@AloisReitbauer moderates http://t.co/R9MYzORc #WebPerf
|
|
@AloisReitbauer: RT @wpo_chat: Rescheduled: Tomorrow (Wednesday 3/21) 1pm ET Web Performance experts join #WPOchat@AloisReitbauer moderates…
|
|
@cgnwebperf: RT @wpo_chat: Rescheduled: Tomorrow (Wednesday 3/21) 1pm ET Web Performance experts join #WPOchat@AloisReitbauer moderates http://t.co/R9MYzORc #WebPerf
|
|
@perfplanet: RT @wpo_chat: Rescheduled: Tomorrow (Wednesday 3/21) 1pm ET Web Performance experts join #WPOchat@AloisReitbauer moderates http://t.co/R9MYzORc #WebPerf
|
|
@scottprice_geek: RT @wpo_chat: Rescheduled: Tomorrow (Wednesday 3/21) 1pm ET Web Performance experts join #WPOchat@AloisReitbauer moderates http://t.co/R9MYzORc #WebPerf
|
|
@JagReehal: RT @wpo_chat: Rescheduled: Tomorrow (Wednesday 3/21) 1pm ET Web Performance experts join #WPOchat@AloisReitbauer moderates http://t.co/R9MYzORc #WebPerf
|
|
@dynaTrace: RT @AloisReitbauer: RT @wpo_chat: Rescheduled: Tomorrow (Wednesday 3/21) 1pm ET Web Performance experts join#WPOchat @AloisReitbauer moderates…
|
|
@perf_testing: RT @AloisReitbauer: RT @wpo_chat: Rescheduled: Tomorrow (Wednesday 3/21) 1pm ET Web Performance experts join #WPOchat @AloisReitbauer moderates…
|
|
@yottaa: RT @wpo_chat Tomorrow (Wednesday 3/21) 1pm ET Web Performance experts join #WPOchat @AloisReitbauermoderates http://t.co/2YQKDfaJ #WebPerf
|
|
@LoadStorm: RT @yottaa: RT @wpo_chat Tomorrow (Wednesday 3/21) 1pm ET Web Performance experts join #WPOchat@AloisReitbauer moderates http://t.co/2YQKDfaJ #WebPerf
|
|
@perf_testing: RT @yottaa: RT @wpo_chat Tomorrow (Wednesday 3/21) 1pm ET Web Performance experts join #WPOchat@AloisReitbauer moderates http://t.co/2YQKDfaJ #WebPerf
|
|
@scottprice_geek: RT @yottaa: RT @wpo_chat Tomorrow (Wednesday 3/21) 1pm ET Web Performance experts join #WPOchat@AloisReitbauer moderates http://t.co/2YQKDfaJ #WebPerf
|
|
@jonathanklein: RT @wpo_chat: Rescheduled: Tomorrow (Wednesday 3/21) 1pm ET Web Performance experts join #WPOchat@AloisReitbauer moderates http://t.co/R9MYzORc #WebPerf
|
|
@bluesmoon: RT @wpo_chat: Rescheduled: Tomorrow (Wednesday 3/21) 1pm ET Web Performance experts join #WPOchat@AloisReitbauer moderates http://t.co/R9MYzORc #WebPerf
|
|
@wpo_chat: Today! 1PM ET Web Performance experts join #WPOchat @AloisReitbauer moderates More Info: http://t.co/R9MYzORc#WebPerf #Browser #W3C
|
|
@expertdan: RT @wpo_chat: Today! 1PM ET Web Performance experts join #WPOchat @AloisReitbauer moderates More Info:http://t.co/R9MYzORc #WebPerf #Browser #W3C
|
|
@yottaa: RT @wpo_chat Today! 1PM ET Web Performance experts join #WPOchat @AloisReitbauer moderates More Info:http://t.co/2YQKDfaJ #WebDev #Browser
|
|
@LoadStorm: RT @yottaa: RT @wpo_chat Today! 1PM ET Web Performance experts join #WPOchat @AloisReitbauer moderates More Info: http://t.co/2YQKDfaJ #WebDev #Browser
|
|
@scottprice_geek: RT @yottaa: RT @wpo_chat Today! 1PM ET Web Performance experts join #WPOchat @AloisReitbauermoderates More Info: http://t.co/2YQKDfaJ #WebDev #Browser
|
|
@jonathanklein: RT @yottaa: RT @wpo_chat Today! 1PM ET Web Performance experts join #WPOchat @AloisReitbauer moderates More Info: http://t.co/2YQKDfaJ #WebDev #Browser
|
|
@cweekly: RT @wpo_chat: Today! 1PM ET Web Performance experts join #WPOchat @AloisReitbauer moderates More Info:http://t.co/R9MYzORc #WebPerf #Browser #W3C
|
|
@wpo_chat: #WPOchat starts in 10 minutes. Remember to Tweet and tell your followers you are participating in a Twitter Chat today! #WebPerf
|
|
@wpo_chat: To make chatting easier we recommend the following web client:nhttp://t.co/fc7MK9qd #WPOchat
|
|
@jonathanklein: RT @wpo_chat: #WPOchat starts in 10 minutes. Remember to Tweet and tell your followers you are participating in a Twitter Chat today! #WebPerf
|
|
@AloisReitbauer: #wpochat getting ready to start.n #wpochat
|
|
@cweekly: Web performance twitter chat about to start: http://t.co/JaKF8tIy #webperf #pardonmyverbositythishour #wpochat
|
|
@AloisReitbauer: We will talk about end user monitoring and specifically Navigation Timing and other W3C specs #wpochat
|
|
@AloisReitbauer: We have some questions prepared for today #wpochat
|
|
@wpo_chat: Welcome to #WPOchat! Over the next 60 minutes @AloisReitbauer will guide our conversation. #WPOchat
|
|
@Catchpoint: Join #wpochat live at at http://t.co/4YHisr32 talk about Real User Monitoring and the W3C specs
|
|
@wpo_chat: Today’s Moderator is Alois Reitbauer @AloisReitbauer http://t.co/Hd8NdrMW #wpochatn #WPOchat
|
|
@wpo_chat: Let’s take a few minutes – please introduce yourself – what you do, what industry you are in etc.n #WPOchat
|
|
@AloisReitbauer: Question A: Is Navigation Timing ready for use in production monitoring. Some people (incl. me) had issues specifically in Firefox #wpochat
|
|
@wpo_chat: Remember Topics and Moderators are needed for the next chat! Leave a comment on http://t.co/cDXlL7ny Question 1 coming up. #WPOchat
|
|
@dritans: Is there a predefined list of questions for today’s chat? #wpochat
|
|
@jonathanklein: Jonathan Klein here – joining #WPOChat from Wayfair in Boston
|
|
@AloisReitbauer: Will also tweet them heren #wpochat
|
|
@cweekly: Hi folks, Chris Weekly here (wearing various hats for Yottaa in Boston)n #wpochat
|
|
@AloisReitbauer: Question A: Is Navigation Timing ready for use in production monitoring. #wpochat
|
|
@jonathanklein: #wpochat A1: We use it in production, but take the data with a grain of salt (and ignore older versions of Firefox)
|
|
@AloisReitbauer: Question B: Which problems are you solving with real user monitoring? #wpochat
|
|
@AloisReitbauer: What about the lack of support in Safari. Doesn’t that hurt you guys?n #wpochat
|
|
@AloisReitbauer: Q3: What does your real user monitoring portfolio look like (Nav. Timing, Synthetic Monitoring, Network Sniffing)?#wpochat
|
|
@dritans: A1 the data has been a little iffy. Even in the browsers that support it sometime the numbers make no sense. #wpochat
|
|
@jonathanklein: @AloisReitbauer yeah the data isn’t complete, but it’s another data point #wpochat
|
|
@log_normal: hey, philip here from Log-Normal, Buddy’s here too #wpochat
|
|
@jonathanklein: RT @AloisReitbauer Q2: Which problems are you solving with real user monitoring? #wpochat
|
|
@AloisReitbauer: A1: Did you know that there is a test suite of W3C. Maybe worth reporting problems to the WG #wpochat
|
|
@log_normal: we use the NavTiming API, but we have a few fallbacks for where it’s not supported, (Safari, IE <= 8, Opera, iOS, Android) #wpochat
|
|
@jonathanklein: #wpochat A2: I think RUM is the best way to correlate performance and engagement (bounce rate, conversion rate, etc.)
|
|
@dritans: Can we slow down a little with the questions. I think there is like 4-5 open ones as of right now. #wpochat
|
|
@log_normal: Answer A2: we’ve also solved the Firefox problem by using alternate start times #wpochat
|
|
@jonathanklein: @dritans yeah that was a mistake, should be on question 2 at the moment. Question 3 will be retweeted in a few minutes #wpochat
|
|
@AloisReitbauer: A1: Do you think the problems are for specific sites or the implementation is instable? #wpochat
|
|
@dritans: RT @jonathanklein: #wpochat A2: I think RUM is the best way to correlate performance and engagement (bounce rate, conversion rate, etc.)
|
|
@Catchpoint: RT @jonathanklein: #wpochat A2: I think RUM is the best way to correlate performance and engagement (bounce rate, conversion rate, etc.)
|
|
@sajal: A3: nav timing. Always facinated with network sniffing, but never implemented it #wpochat
|
|
@jonathanklein: @scottprice_geek you should join #wpochat - going on now! Info here: http://t.co/AnSsQ1kL
|
|
@jonathanklein: @dritans Got it, yeah in the past we have, this time Alois just picked the questions. We might go back to group ones in next chat #wpochat
|
|
@AloisReitbauer: A1: @log_normal do you feel that the values get better with newer browsers? #wpochat
|
|
@wpo_chat: Q3: What does your real user monitoring portfolio look like (Nav. Timing, Synthetic Monitoring, Network Sniffing)?#WPOchat
|
|
@cweekly: A1 Yes, “ready” w/ caveats about its fragility (i.e. take care to account for FF bug etc). GA has been using it for a long time… #wpochat
|
|
@log_normal: @AloisReitbauer other than the one big firefox bug, we haven’t seen any other issues, but we’re also not dependent on navtiming #wpochat
|
|
@cweekly: @log_normal have you documented your “alt start times” approach for FF? #wpochat
|
|
@log_normal: We’ve been using NavTiming in boomerang since the day IE9 added it #wpochat
|
|
@jonathanklein: #wpochat A3 We use Boomerang (via @log_normal) and a network tap for server side RUM
|
|
@jonathanklein: #wpochat A3 We also have synthetic monitoring through @Catchpoint
|
|
@AloisReitbauer: Q3: What does your real user monitoring portfolio look like #wpochat
|
|
@AloisReitbauer: I think boomerang is a great source of wisdom here
|
|
@AloisReitbauer: A3: Where do you see the cut btw. synthetic and RUM? #wpochat
|
|
@AloisReitbauer: A1: I wonder how widely Nav Timing is used today. We are using it as well. Specially like the support in new mobile browsers #wpochat
|
|
@jonathanklein: #wpochat A3: We like having both synthetic and RUM – the former for availability/change tracking and the latter for engagement and outliers
|
|
@AloisReitbauer: A3: There were some discussion on synthetic to die b/c of RUM. What’s your take on this? #wpochat
|
|
@andydavies: @AloisReitbauer I see synthetic as being about how your servers are performing and RUM about the users experience #wpochat #wpochat
|
|
@AloisReitbauer: @bluesmoon you will be talking about Q3 at Velocity – right?n #wpochat
|
|
@log_normal: Synthetic monitoring is great to analyze object level metrics and break down requests by different network components #wpochat
|
|
@sajal: @AloisReitbauer synthetic will never die, there is always a need for it . esp for debugging. #wpochat
|
|
@jonathanklein: @AloisReitbauer RUM is a little too noisy to use on its own. Good response to Pat’s post here: http://t.co/Q56KEDiZ#wpochat
|
|
@AloisReitbauer: @andydavies so you do not need browser driven synthetics?n #wpochat
|
|
@bluesmoon: @AloisReitbauer yes, will be doing a talk with @bbrewer and Carlos Bueno from Facebook. #wpochat
|
|
@mrPerezMarc: has any one used new relic to monitor users speed experience?n #wpochat
|
|
@AloisReitbauer: @jonathanklein Agree, also RUM can never provide availability #wpochat
|
|
@cweekly: A3 I see them as complementary. On-demand tests and scheduled monitoring and benchmarking… real browsers + control FTW #wpochat
|
|
@sajal: @mrPerezMarc i find end user report on new relic to be too noisy. Its awesome for app performance #wpochat
|
|
@bluesmoon: @AloisReitbauer not entirely true, it’s tricky, but you can tell downtime by a significant drop in beacons (we did that at yahoo) #wpochat
|
|
@andydavies: @AloisReitbauer The synthetic tools I use at the moment (SiteConfidence, private WPT) are browser based.#wpochat
|
|
@cweekly: RT @jonathanklein: @AloisReitbauer RUM too noisy to use on its own. Good response to Pats post here:http://t.co/LuLEDHGK #wpochat
|
|
@AloisReitbauer: A3: I also see every big performance vendor today having both – synthetic and RUM #wpochat
|
|
@rockstarapps: @mrPerezMarc - we use rewrelic for server monitoring and i find our ops guys gravitate to the RUM graphs. they’re nicely integrated #wpochat
|
|
@AloisReitbauer: Q4: Do we need more. If yes – which additional information do we need?. Are you happy with Resource Timing + User Timing? #wpochat
|
|
@jonathanklein: A4: I think resource timing will be great once it is widely supported – we need more granular timings in the browser#wpochat
|
|
@mrPerezMarc: What is this boomerang everyone is mentioning? #wpochat
|
|
@wpo_chat: Q4: Do we need more. If yes – which additional information do we need?. Are you happy with Resource Timing + User Timing? #WPOchat
|
|
@jonathanklein: A4: I also want really robust application level tracing for PHP *cough* dynatrace *cough* #wpochat
|
|
@andydavies: @jonathanklein One of the biggest problems I have with current RUM tools is the way the data is rolled up – hard to ask “what if” #wpochat
|
|
@sajal: @mrPerezMarc I mean it doesnt give any indication of time to interact. Ad networks, widgets, etc push onload longer.#wpochat
|
|
@mrPerezMarc: A4 i think we need a general feel for how fast user loads pagesn #wpochat
|
|
@andydavies: @jonathanklein Using Oracle RUEI was able to distill the huge amounts of data down to meaningful stuff #wpochat
|
|
@mrPerezMarc: A4: i found on CNN and other sites that they mesure bandwith and deliver content based on that speedn #wpochat
|
|
@AloisReitbauer: What do you think about the adoption of the CORS header by Third Parties?n #wpochat
|
|
@dritans: Has any of the browsers has resource timing in their roadmap? #wpochat
|
|
@AloisReitbauer: @mrPerezMarc What should this metric look like? Isn’t that always depending on the page? #wpochat
|
|
@andydavies: A4 Happyish with Resource Timing there are some limitations I don’t like but understand why they are there…#wpochat
|
|
@cweekly: RT @AloisReitbauer: What do you think about the adoption of the CORS header by Third Parties? Is this Q5? #wpochat
|
|
@andydavies: @AloisReitbauer I we’re going to have to educate third parties on the CORS stuff #wpochat
|
|
@AloisReitbauer: @andydavies most of them are security/privacy relatedn #wpochat
|
|
@AloisReitbauer: @cweekly Part of Q4 and Resource Timing. As this would help to understand Third Parties better. #wpochat
|
|
@bluesmoon: @mrPerezMarc you can use boomerang to measure bandwidth. #wpochat
|
|
@sajal: How long would it take for resource timing to get to the point where nav timing is? wrt browser implementation.. 2 yrs?#wpochat
|
|
@AloisReitbauer: I mean we already get third party data today. @bluesmoon does bommerang time resources as well #wpochat
|
|
@andydavies: @AloisReitbauer Yeh went and read @tonygentilcore’s post to the security list asking questions about it. #wpochat
|
|
@mrPerezMarc: I think with all tips and tricks from @souders books, a great deal of speed modification we’ve applied proved fruitful#wpochat
|
|
@dritans: 3rd party providers like adserving are already doing osmething similar to CORS for flash and they do have the capabilities to do it #wpochat
|
|
@bluesmoon: @AloisReitbauer kinda. boomerang lets you add timers to any part of your page #wpochat
|
|
@AloisReitbauer: Chrome will one of the early adopters as well I think #wpochat
|
|
@jonathanklein: @sajal I think Chrome and Firefox will be there much more quickly with the fast release cycle. IE…maybe in IE11?#wpochat
|
|
@mrPerezMarc: @cweekly, that’s the way it should be, to many people are patching up jobs and releasing site that are under constant change #wpochat
|
|
@jonathanklein: @ie any plans to support the resource timing spec in future browser versions? #wpochat
|
|
@mrPerezMarc: @sajal, could be quicker if we all submitted our ideas to w3cn #wpochat
|
|
@log_normal: @wpo_chat the tough part with RUM is to be able to measure and report numbers without affecting load time#wpochat
|
|
@AloisReitbauer: Resouce Timing Adoption – Maybe a question for this years browser panel at Velocity //cc @souders #wpochat
|
|
@andydavies: @jonathanklein MS are in the relevant W3C working group #wpochat
|
|
@dritans: RT @log_normal: @wpo_chat the tough part with RUM is to be able to measure and report numbers without affecting load time #wpochat
|
|
@mrPerezMarc: i find that the w3c gets a lot of collaboration from the industry #wpochat
|
|
@sajal: RT @AloisReitbauer: Resouce Timing Adoption – Maybe a question for this years browser panel at Velocity //cc @souders#wpochat
|
|
@AloisReitbauer: However browser vendors have a lot to do with the whole HTML5 thinkg
|
|
@andydavies: @log_normal That’s sort of where network taps help but obviously they don’t measure the browser experiencen#wpochat
|
|
@AloisReitbauer: All browser vendors are in except Apple #wpochat
|
|
@mrPerezMarc: why would they need to adot this, there are nifty Js code that does all this fir us #wpochat
|
|
@jonathanklein: RT @AloisReitbauer: Resouce Timing Adoption – Maybe a question for this years browser panel at Velocity //cc@souders #wpochat
|
|
@dritans: IE10 does not mention Resource Timing – so best case IE11 http://t.co/nQwfF1lJ #wpochat
|
|
@AloisReitbauer: Q5: What do you think about User Timing? Is manual code instrumentation the right way? #wpochat
|
|
@jonathanklein: @mrPerezMarc yeah but the JS has overhead and is less accurate – getting it directly from the browser is best#wpochat
|
|
@AloisReitbauer: A4: I think noise and meaning is a general problem in the monitoring space #wpochat
|
|
@andydavies: @AloisReitbauer First RUM tool I used was network tap based, you can still get a large amount of useful performance data out #wpochat
|
|
@cweekly: RT @andydavies: Mobile is where we really need resource timing api to be supported // TRUE #wpochat
|
|
@AloisReitbauer: @andydavies agree. We today managed to get Resource Timings on mobile. Custom built for sure
|
|
@mrPerezMarc: @jonathanklein A few millisecond of inaccuracy wont hurt, u will always have a margin of error #wpochat
|
|
@log_normal: @wpo_chat we sort of solve the noise problem by having a very large sample set (100K+) and looking at percentiles instead of amean #wpochat
|
|
@dritans: @andydavies afraid pple will misuse it on mobile,start posting large amnt of data for the sake of tracking #webperf making it worst #wpochat
|
|
@wpo_chat: Q5: What do you think about User Timing? Is manual code instrumentation the right way? #WPOchat
|
|
@jonathanklein: RT @andydavies: Mobile is where we really need resource timing api to be supported #wpochat
|
|
@mrPerezMarc: @dritans tracking should be on a small scale to get a glimpse of where ythere is room from improvementn#wpochat
|
|
@jonathanklein: A5: I’d much rather have the data in the browser – easier to implement, more accurate, and less overhead. Every ms counts. #wpochat
|
|
@AloisReitbauer: We for example send back only hotspot data. Sending beacons for every resource on mobile would kill you#wpochat
|
|
@dritans: @mrPerezMarc totally agree, thats why our RUM solution is called Glimpse. #wpochat
|
|
@AloisReitbauer: @jonathanklein did you ever use a lib like User Timing? I know some people who built similar stuff. It is not really rocket science #wpochat
|
|
@andydavies: @mrPerezMarc But how do you know who to sample? Been thinking about a beacon for Resource Timing that you can have predicates on #wpochat
|
|
@AloisReitbauer: Q6: What do you think the next standard should deal with? What are we still lacking? #wpochat
|
|
@cweekly: RT @AloisReitbauer: … Sending beacons for every resource on mobile would kill you // Yeah, observer effect 4 mobile cld b massiv #wpochat
|
|
@jonathanklein: @AloisReitbauer haven’t tried it, I’m sure it’s not hard but once the data is in the browser people do a lot of great stuff with it #wpochat
|
|
@mrPerezMarc: @andydavies you sample who your target is, if you have clients from the us, then you sample them, or create buckets #wpochat
|
|
@dritans: Q6 performance of JS code. Often is not the network wire time – but badly written code that impacts end users. #wpochat
|
|
@AloisReitbauer: @holydevil @lognormal in RUM I feel averages have very little value. I always work with percentiles #wpochat
|
|
@mrPerezMarc: A6: everything & everything #wpochat
|
|
@jonathanklein: A6: That’s a tough one…perhaps a better way to sandbox third parties? Better native ways to async JS that has no dependencies? #wpochat
|
|
@mrPerezMarc: @dritans Js will always be a problem bcause everyone does it differently. have you ever used JsLink?n #wpochat
|
|
@jonathanklein: @AloisReitbauer haha, fine. Maybe I’m just lazy (busy?) #wpochat
|
|
@AloisReitbauer: @jonathanklein. I think the performance sandboxing is a great idea. You should post that to the WG #wpochat
|
|
@andydavies: Q6 – media queries for more things e.g. SVG, better way of determining the browser characteristics on the server#wpochat
|
|
@dritans: @AloisReitbauer RUM or not, when measuring web performance averages will lie. Too many factors intertwined #wpochat
|
|
@wpo_chat: Q6: What do you think the next standard should deal with? What are we still lacking? #WPOchat
|
|
@cweekly: @jonathanklein @AloisReitbauer … also User Timing has better precision (so it’s not just a convenience for implementation) #wpochat
|
|
@AloisReitbauer: Q7: Which timings to you look at? Is onLoad still relevant. What timings do you track? #wpochat
|
|
@bluesmoon: @wpo_chat I’d really like to see measurements for rendering time, CSS, layout, etc. #wpochat
|
|
@mrPerezMarc: @AloisReitbauer Ok fine… including the kitchen sink. the big problem i find is that their are great ressources on how to speed #wpochat
|
|
@mrPerezMarc: @AloisReitbauer speed up sites, but 90% of ppl dont do it. #wpochat
|
|
@AloisReitbauer: @cweekly agreed. Just as performance.now() will have #wpochat
|
|
@jonathanklein: @dritans @AloisReitbauer yeah but those people at the 95th percentile make your site look SLOW </sarcasm>#wpochat
|
|
@wpo_chat: RT @AloisReitbauer: Q7: Which timings to you look at? Is onLoad still relevant. What timings do you track? #WPOchat
|
|
@andydavies: Sorry got to jump out will read back through the thread later #wpochat
|
|
@jonathanklein: RT @bluesmoon: @wpo_chat I’d really like to see measurements for rendering time, CSS, layout, etc. #wpochat
|
|
@mrPerezMarc: @AloisReitbauer A7, mainly everything before onLoad, because until then, most users can’t do anything, and post is all extra stuff #wpochat
|
|
@AloisReitbauer: @bluesmoon good point. How deep should that go. We are still in prod monitoring here …. #wpochat
|
|
@dritans: Q6 Onload is still relevant for most sites. On newer sites relying on AJAX/HTML5 it can be useless #wpochat
|
|
@jonathanklein: A7: TTFB is always a good one, onLoad still matters but you can game it. #wpochat
|
|
@bluesmoon: RT @jonathanklein: @dritans @AloisReitbauer yeah but those people at the 95th percentile make your site look SLOW </sarcasm> #wpochat
|
|
@AloisReitbauer: What about above the fold? #wpochat
|
|
@AloisReitbauer: RT @bluesmoon: yeah but those people at the 95th percentile make your site look SLOW </sarcasm> #wpochat
|
|
@bluesmoon: @jonathanklein if you’re gaming your own performance numbers, then performance is not your problem
|
|
@dritans: @jonathanklein the question abt 95% is are they there because of crappy router, downloading lots of torrents,or ur site hated them #wpochat
|
|
@jonathanklein: @AloisReitbauer Yeah could be nice, but hard to measure and fold is different for all. When the browser provides it natively…
|
|
@dritans: RT @bluesmoon: if youre gaming your own performance numbers, then performance is not your problem
|
|
@holydevil: @aloisreitbauer onLoad – yes. To be precise, it’s ‘time to interact’ that’s important. There’s no standard way to measure this. #wpochat
|
|
@AloisReitbauer: Q8: What do you think about the missing ability to measure bandwitdh? #wpochat
|
|
@wpo_chat: RT @AloisReitbauer: Q8: What do you think about the missing ability to measure bandwitdh? #WPOchat
|
|
@jonathanklein: A8: Well it’s not missing in Boomerang, but a native way is. It’s hard to do without making people download a series of files #wpochat
|
|
@jonathanklein: RT @AloisReitbauer: Q8: What do you think about the missing ability to measure bandwitdh? #wpochat
|
|
@dritans: A8. Not sure if we need bandwidth, or something else. We need an indicator if the user is having network issues across the board. #wpochat
|
|
@AloisReitbauer: Shouldn’t browsers just provide this info. They have it. #wpochat
|
|
@jonathanklein: A8: So I doubt browsers will add that functionality #wpochat
|
|
@bluesmoon: @AloisReitbauer so you can already get mobile connection type from Android devices #wpochat
|
|
@AloisReitbauer: I hate to do that image thing on mobile. Especially in Europe with all the costly roaming plans
|
|
@jonathanklein: @AloisReitbauer Do the browsers have it? How? They can estimate it…but it’s not super precise if resources are small #wpochat
|
|
@AloisReitbauer: You can kind of estimate it with Nav Timing as well #wpochat
|
|
@log_normal: We also record information from the Network Information API: http://t.co/De7FzKOc #wpochat
|
|
@dritans: At home my connection could say cable, but at 9PM its the equivalent of a modem. What consumers purchase is not what they get. #wpochat
|
|
@mrPerezMarc: @dritans what if an issue with 1-5% of ur visitors, should u spend that much time effort money 2 make sure they are well servered?n #wpochat
|
|
@AloisReitbauer: @bluesmoon agreed. Unfortunately that does not tell us what it really is. I now some 3G connections that are faster than WiFi
|
|
@bluesmoon: You can also buy a bandwidth database from MaxMind or Quova to tell (sort of) Bandwidth based on IP #wpochat
|
|
@dritans: @mrPerezMarc depends on who that 5% is, what if it is the one that bring 80% of your revenue? #wpochat
|
|
@AloisReitbauer: @mrPerezMarc What if they buy your stuff? Isn’t this why we all do it? #wpochat
|
|
@jonathanklein: @bluesmoon Is that based on purchased bandwidth or actual bandwidth? #wpochat
|
|
@mrPerezMarc: @AloisReitbauer if the 5% are the ones buying my stuff, then their really isn’t a problem with my site is there?#wpochat
|
|
@dritans: FCC study clearly shows there is problems with consumer networks. They do degrade way below what is promisedhttp://t.co/LDSiJxdV #wpochat
|
|
@bluesmoon: @jonathanklein it’s based on advertised bandwidth, which may not even be the same as purchased bandwidth#wpochat
|
|
@wpo_chat: You are welcome to keep chatting as we come to a close. Great conversation going here with the #WebPerf community. #WPOchat
|
|
@mrPerezMarc: @dritans then for them, they accept my site the way it is and gladly spend their money #wpochat
|
|
@wpo_chat: Did you enjoy this chat? Do you have any suggestions? #wpochatn #WPOchat
|
|
@cweekly: I’ve gotta bail. Great chat guys, see you all next time! n #wpochat
|
|
@wpo_chat: Remember – Topics, Moderators, Guests, Wanted – If that’s you leave a comment on http://t.co/cDXlL7ny #WPOchat
|
|
@AloisReitbauer: In Europe they now slow you down when over your data limit. Also a point #wpochat
|
|
@mrPerezMarc: @AloisReitbauer @dritans users have multiple devices, pc, ipads, phones, so if the site is fast enough on one they know it’s them #wpochat
|
|
@log_normal: @wpo_chat BTW, 54% of you who visited our site today have a network speed between 2-6Mbps #wpochat
|
|
@rockstarapps: #bandwidth is important but you can always measure known bandwidth performance… then simulate the rest.#wpochat
|
|
@wpo_chat: Thank You - @AloisReitbauer and the #webperf community. A great chat! Look for an archive soon athttp://t.co/cDXlL7ny #WPOchat
|
|
@sajal: RT @log_normal: @wpo_chat BTW, 54% of you who visited our site today have a network speed between 2-6Mbps#wpochat
|
|
@AloisReitbauer: Thanks everyone for joining! #wpochat
|
|
@holydevil: @AloisReitbauer That’s true for most providers in India too. Once you hit the FUP limit, your speed drops. #wpochat
|
|
@mrPerezMarc: Thank you everyone! This was, as always is a great discussion! #wpochat
|
|
@AloisReitbauer: Good #wpochat today about real user monitoring and Nav Timing #webperf #wpochat
|
|
@mrPerezMarc: where can i catch up on what i missed earlier?n #wpochat
|
|
@stubbornella: RT @jonathanklein: @dritans @AloisReitbauer yeah but those people at the 95th percentile make your site look SLOW </sarcasm> #wpochat
|
|
@AloisReitbauer: It will be posted on the wpochat pagen #wpochat
|



