2.86 score from hupso.pl for:
blakecrosby.com



HTML Content


Titleblake crosby

Length: 12, Words: 2
Description pusty

Length: 0, Words: 0
Keywords pusty
Robots
Charset UTF-8
Og Meta - Title exist
Og Meta - Description exist
Og Meta - Site name exist
Tytuł powinien zawierać pomiędzy 10 a 70 znaków (ze spacjami), a mniej niż 12 słów w długości.
Meta opis powinien zawierać pomiędzy 50 a 160 znaków (łącznie ze spacjami), a mniej niż 24 słów w długości.
Kodowanie znaków powinny być określone , UTF-8 jest chyba najlepszy zestaw znaków, aby przejść z powodu UTF-8 jest bardziej międzynarodowy kodowaniem.
Otwarte obiekty wykresu powinny być obecne w stronie internetowej (więcej informacji na temat protokołu OpenGraph: http://ogp.me/)

SEO Content

Words/Characters 3638
Text/HTML 28.57 %
Headings H1 11
H2 4
H3 9
H4 10
H5 0
H6 0
H1
blake crosbypilot and nerd
humboldt distillery spiced rum
velocity new york
why i love working at fastly
an introduction to hpack: compressing headers in http 2
top “non-browser” user agents
the cdn manifesto
pagespeed and spdy slides
toronto web performance meetup
getting lost in 302s
ipv6 and web performance
H2
methodology
assumptions
results
conclusion
H3
routing
dns requests
tcp handshake
http get
conclusion
blake crosby
social media
upcoming & previous talks
latest tweets
H4 share story
share story
share story
share story
share story
share story
share story
share story
share story
share story
H5
H6
strong
http 1.1
http 2
[
]
toronto web performance group (july 2014) toronto on, canada
surge 2013 (sept. 2013) national harbour md, united states
o’reilly velocity (june 2013) santa clara ca, united states
fitc (march 2013) toronto on, canada
more...
b
i
http 1.1
http 2
[
]
toronto web performance group (july 2014) toronto on, canada
surge 2013 (sept. 2013) national harbour md, united states
o’reilly velocity (june 2013) santa clara ca, united states
fitc (march 2013) toronto on, canada
more...
em http 1.1
http 2
[
]
toronto web performance group (july 2014) toronto on, canada
surge 2013 (sept. 2013) national harbour md, united states
o’reilly velocity (june 2013) santa clara ca, united states
fitc (march 2013) toronto on, canada
more...
Bolds strong 9
b 0
i 9
em 9
Zawartość strony internetowej powinno zawierać więcej niż 250 słów, z stopa tekst / kod jest wyższy niż 20%.
Pozycji używać znaczników (h1, h2, h3, ...), aby określić temat sekcji lub ustępów na stronie, ale zwykle, użyj mniej niż 6 dla każdego tagu pozycje zachować swoją stronę zwięzły.
Styl używać silnych i kursywy znaczniki podkreślić swoje słowa kluczowe swojej stronie, ale nie nadużywać (mniej niż 16 silnych tagi i 16 znaczników kursywy)

Statystyki strony

twitter:title pusty
twitter:description pusty
google+ itemprop=name pusty
Pliki zewnętrzne 10
Pliki CSS 3
Pliki javascript 7
Plik należy zmniejszyć całkowite odwołanie plików (CSS + JavaScript) do 7-8 maksymalnie.

Linki wewnętrzne i zewnętrzne

Linki 153
Linki wewnętrzne 89
Linki zewnętrzne 64
Linki bez atrybutu Title 131
Linki z atrybutem NOFOLLOW 0
Linki - Użyj atrybutu tytuł dla każdego łącza. Nofollow link jest link, który nie pozwala wyszukiwarkom boty zrealizują są odnośniki no follow. Należy zwracać uwagę na ich użytkowania

Linki wewnętrzne

#
home /
speaking engagements #
speaking engagements
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
- /wp-content/uploads/2014/06/redirects.png
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
rtt javascript:void(0)
rtt javascript:void(0)
rtt javascript:void(0)
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
javascript:void(0);
more... ./previous-talks/

Linki zewnętrzne

blake crosbypilot and nerd

http://www.blakecrosby.com
contact http://www.blakecrosby.com/contact/
previous talks http://www.blakecrosby.com/previous-talks/
speaker profile http://www.blakecrosby.com/speaker-profile/
humboldt distillery spiced rum http://www.blakecrosby.com/2014/09/29/humboldt-distillery-spiced-rum/
food http://www.blakecrosby.com/category/food/
no comments http://www.blakecrosby.com/2014/09/29/humboldt-distillery-spiced-rum/#comments
- http://www.blakecrosby.com/wp-content/uploads/2014/09/1472933_10152807145378793_9142179495725529995_n.jpg
velocity new york http://www.blakecrosby.com/2014/09/09/velocity-new-york/
nerd http://www.blakecrosby.com/category/nerd/
no comments http://www.blakecrosby.com/2014/09/09/velocity-new-york/#comments
velocity conference http://velocityconf.com/velocityny2014
barbara bermes’ talk http://velocityconf.com/velocityny2014/public/schedule/detail/35489
why i love working at fastly http://www.blakecrosby.com/2014/09/05/why-i-love-working-at-fastly/
work http://www.blakecrosby.com/category/work/
no comments http://www.blakecrosby.com/2014/09/05/why-i-love-working-at-fastly/#comments
- http://www.blakecrosby.com/wp-content/uploads/2014/09/bwo7nwbcyaagw__.jpg
an introduction to hpack: compressing headers in http 2 http://www.blakecrosby.com/2014/08/13/an-introduction-to-hpack-compressing-headers-in-http-2-0/
nerd http://www.blakecrosby.com/category/nerd/
no comments http://www.blakecrosby.com/2014/08/13/an-introduction-to-hpack-compressing-headers-in-http-2-0/#comments
top “non-browser” user agents http://www.blakecrosby.com/2014/07/29/top-non-browser-user-agents/
nerd http://www.blakecrosby.com/category/nerd/
no comments http://www.blakecrosby.com/2014/07/29/top-non-browser-user-agents/#comments
direct correlation http://www.akamai.com/html/io/io_dataset.html#stat=browser&top=5&type=line&start=20140626&end=20140726&net=both&hide=android%20webkit+others+mobile safari+chrome+firefox
fastly http://www.fastly.com/
service http://www.foxtel.com.au/about-foxtel/what-we-do/default.htm
browser war https://en.wikipedia.org/wiki/browser_wars
the cdn manifesto http://www.blakecrosby.com/2014/07/18/the-cdn-manifesto/
work http://www.blakecrosby.com/category/work/
no comments http://www.blakecrosby.com/2014/07/18/the-cdn-manifesto/#comments
velocity conference http://velocityconf.com/velocity2014
pagespeed and spdy slides http://www.blakecrosby.com/2014/07/08/pagespeed-and-spdy-slides/
nerd http://www.blakecrosby.com/category/nerd/
work http://www.blakecrosby.com/category/work/
1 comment http://www.blakecrosby.com/2014/07/08/pagespeed-and-spdy-slides/#comments
slideshare http://www.slideshare.net/blakecrosby/pagespeed-and-spdy
toronto web performance meetup http://www.blakecrosby.com/2014/07/02/toronto-web-performance-meetup/
nerd http://www.blakecrosby.com/category/nerd/
work http://www.blakecrosby.com/category/work/
no comments http://www.blakecrosby.com/2014/07/02/toronto-web-performance-meetup/#comments
july toronto web performance group http://www.meetup.com/toronto-web-performance-group/events/184662142/
eventmobi http://www.eventmobi.com/
getting lost in 302s http://www.blakecrosby.com/2014/06/18/getting-lost-in-302s/
nerd http://www.blakecrosby.com/category/nerd/
no comments http://www.blakecrosby.com/2014/06/18/getting-lost-in-302s/#comments
ipv6 and web performance http://www.blakecrosby.com/2014/06/15/ipv6-and-web-performance/
nerd http://www.blakecrosby.com/category/nerd/
work http://www.blakecrosby.com/category/work/
1 comment http://www.blakecrosby.com/2014/06/15/ipv6-and-web-performance/#comments
ilya’s excellent book http://shop.oreilly.com/product/0636920028048.do
linode http://www.linode.com/
http://ipv4.blakecrosby.com/test.txt http://ipv4.blakecrosby.com/test.txt
http://ipv6.blakecrosby.com/test.txt http://ipv6.blakecrosby.com/test.txt
ipv4 conversation https://www.cloudshark.org/captures/b84a5db37d98
ipv6 conversation https://www.cloudshark.org/captures/4f222c877a40
@jpaulellis https://twitter.com/jpaulellis
winmtr.net http://winmtr.net/
2 http://www.blakecrosby.com/page/2/
next page http://www.blakecrosby.com/page/2/
https://www.facebook.com/blakecrosby
https://www.twitter.com/blakecrosby
https://www.linkedin.com/in/crosbyblake
toronto web performance group (july 2014) http://www.meetup.com/toronto-web-performance-group/events/184662142/
tweets by @blakecrosby https://twitter.com/blakecrosby

Zdjęcia

Zdjęcia 5
Zdjęcia bez atrybutu ALT 2
Zdjęcia bez atrybutu TITLE 5
Korzystanie Obraz ALT i TITLE atrybutu dla każdego obrazu.

Zdjęcia bez atrybutu TITLE

http://www.blakecrosby.com/wp-content/uploads/2014/09/1472933_10152807145378793_9142179495725529995_n-170x300.jpg
http://www.blakecrosby.com/wp-content/uploads/2014/09/bwo7nwbcyaagw__-168x300.jpg
/wp-content/uploads/2014/06/redirects-1024x758.png
http://www.blakecrosby.com/wp-content/uploads/2014/05/18-x-96-windsocks1.jpg
http://www.blakecrosby.com/wp-content/uploads/2015/11/11942100_10153635024488793_6446544134664089311_o1.jpg

Zdjęcia bez atrybutu ALT

http://www.blakecrosby.com/wp-content/uploads/2014/05/18-x-96-windsocks1.jpg
http://www.blakecrosby.com/wp-content/uploads/2015/11/11942100_10153635024488793_6446544134664089311_o1.jpg

Ranking:


Alexa Traffic
Daily Global Rank Trend
Daily Reach (Percent)









Majestic SEO











Text on page:

toggle navigation blake crosbypilot and nerd home contact speaking engagements speaking engagements previous talks speaker profile --> humboldt distillery spiced rum september 29, 2014 / food / no comments sara and i check in to a hotel in the sleepy town of eureka, california. the carter house inn in the old town neighborhood, to be exact. the concierge let us know that a free glass of wine is waiting for us at the bar. we freshen up and bee-line it to the bar to enjoy our free libations. matthew, our bartender, was awesome. he tended to us nicely, especially when i asked: “can i take a look at that bottle of spiced rum you have?” humboldt distillery spiced rum the bottle had clean lines, clear glass with a honey coloured liquor inside. i opened the wood stopper and took a whiff. wow! hints of vanilla and, is that? yes. cloves. i normally shy away from spiced rums. i feel that the spice always overpowers the base notes of the rum itself. but, i could tell that this rum was different. the bartender explained that it was distilled in a local distillery just south of the city. this was the distillery’s first batch of rum. they also make a vodka as well. i ordered a glass to sample the beverage. the colour was light. not a true white rum, but not dark enough to be a dark rum. i suspect that the colouring is mainly from the vanilla and spices. while sipping the generous pour, i came to two conclusions: firstly, this is the best tasting spiced rum i’ve ever had and i need to share this with others. second, and most importantly: this will be the first rum to officially enter my new rum collection. i’ve decided to start collecting rum. these bottles will represent the various places i’ve visited around the world. if i ever needed a reminder of a feeling or place i’ve been to, i will have the luxury of sampling a rum from my travels to take me back. this rum will always remind me of the best oysters i’ve ever had and my visit to portland for our 34th and 32nd birthdays. share story --> velocity new york september 9, 2014 / nerd / no comments in one week, i’ll be in new york city for the latest instalment of the velocity conference. this time around i will be working the fastly booth! come by, talk nerdy to us, and we can give you a first hand demo of our awesome cdn. i’ll also have the opportunity to see barbara bermes’ talk on evaluating the performance of third party scripts. barbara and i worked together at cbc back in the day and highly recommend that you see her talk if you’re going to be at the conference. if you’re going to be at velocity, drop me a line and we can get together. share story --> why i love working at fastly september 5, 2014 / work / no comments i’m lucky that i get to work with a lot of great people at fastly. i was reminded of this during an “emergency ops” issue that occurred yesterday. we use irc for internal communications between all of our remote workers and teams. a message came into the ops channel: < edmund> hey ops, i broke the coffee machine. the stack trace is "internal error in file qa_fifo, line 81" i stared at the screen in disbelief. i had to double check that this was no joke: < bcrosby> edmund: is the coffee machine really showing that error? if so... omg < edmund> yes, it is. sure enough, the machine was reporting an error on line 81 of ‘qa_fifo’. in typical it fashion, the jokes and quips started flying: < bcrosby> i just took a pic.. omg < docwilco> a pic of what? < edmund> the coffee machine, i assume, kernel panicking < brendan> did you run chef on it? < brendan> should have run barista instead... * brendan finds coat < mbyerly> roll to the coffee maker failed, roll her back < bcrosby> barista-client ? < aspires_> fifo? < aspires_> is our coffee maker on a stack language? < mmay> did you try turning it off and on again? < bcrosby> i didn't.. cause i figured the coffee ops guys would want to preserve the logs ;) < edmund> i held down a button because i thought it was the right thing to do < edmund> maybe i overfilled a buffer somewhere with inputs < edmund> coffee instructions unclear; broke machine. < bcrosby> hehe < mmay> it's probably written with windows embedded lol < bcrosby> the fact that the file has "qa" in it.. scares me < bcrosby> this entire time we were brewing coffee on a qa version of the code!!!! < mmay> lol < mmay> or their process is that once a file is qa'ed, prepend filename with qa_* < bcrosby> maybe there is a dip switch we need to change from qa to production? then the bomb dropped. a co-worker found the exact bit of code that had caused the machine to crash: < edmund> hmmm http://www.state-machine.com/qp/qpc/qa__fifo_8c.html < bcrosby> true. < mmay> lolz < bcrosby> edmund: rofl < mmay> lets send debug info to them < edmund> http://gitorious.digitalstrom.org/ds485-stack/ds485-core/blobs/df6acce3f736e2731177748f2965361c642f05c2/src/qpc/qf/source/qa_fifo.c#line69 maybe this was it < mmay> i bet we can hook up jtag to it < edmund> asserts on overflow, should use a ring buffer. noobs in the end, the machine was fixed by turning it off and then on again. share story --> an introduction to hpack: compressing headers in http 2 august 13, 2014 / nerd / no comments one of the problems with http 1.1 is header overhead. http headers are not compressed, even though your content may be. this results in situations where the http headers can actually be larger than the body of the request! (small side note: i’ve encountered a website whereby the developer decided to store html in a cookie. the header ended up being over 5kb in size!) http 2 solves this problem by compressing the headers using a specification called hpack. hpack compresses headers using two main methods: headers are now stored as explicit key value pairs. on the first request, a full compliment of headers are sent. on subsequent requests, only the difference from the headers in the first request are sent. take a look at an example: let’s say you need to fetch two objects: /index.html and /logo.jpg. here are an example of what the request headers would look like: http 1.1 http 2 # 1 get /index.html http/1.1 host: www.foo.com referer:http://www.example.com/ accept-encoding:gzip :method: get :scheme: http :host: www.foo.com :path: /index.html referer: http://www.example.com/ accept-encoding: gzip # 2 get /logo.jpg http/1.1 host: www.foo.com referer:http://www.foo.com/index.html accept-encoding:gzip :path: /logo.jpg referer: http://www.foo.com/index.html a few things you will notice: http 2 has a new header value called “scheme”. this will be either http or https. instead of sending all of the same headers again in the second request, the client only sends the new ones. the method (get), scheme (http), and host (www.foo.com) didn’t change. this is known as differential encoding — where only the differences are sent along. the second method that is used to reduce the size of headers is using a compression algorithm called huffman coding. this will futher compress the binary data. both request and response headers are compressed this way. this means that traditionally large headers, such as cookies, are compressed both from the client (when a cookie has already been set) or from the server (when you want to set a cookie). this vastly reduces the chances of header overhead exceeding the size of object body. not only will this improve the speed of browsing the web, it also means that companies will pay less to deliver their content! share story --> top “non-browser” user agents july 29, 2014 / nerd / no comments a simple question came to mind the other day: “what are the top http libraries or applications that are used to access web content?” what i mean by that is: what are the top user agents that are not browsers (ie, firefox, chrome, etc..) that web developers use to access content via http. a few come to mind: libwww for perl, libcurl for php, and cfnetwork for ios. is this information useful to anyone? usually these libraries are used by applications to fetch content to be handed off to another layer for presentation. developers do no need to worry about which “non-browser” user agent to tailor their output for, like they do for ie vs. chrome for example. i decided to take a small sample of traffic to see if there were any interesting patterns to be found. methodology i took a sampling of approximately one million hits from four different geographical locations: los angeles, new york, amsterdam, and sydney. for a total of 3,147,379 samples. all hits were filtered for user-agents that started with “mozilla” (using the regular expression: ^user-agent: mozilla.*) at capture time. i later realized this didn’t filter out requests from the opera browser, which i did in post processing. assumptions the user agent field is a free text field. this means that any value can be used in this field by the application or web developer. i’m assuming that most libraries do not try to pretend to be a user agent it is not by spoofing the header. data was captured at the same time across all geographic locations, regardless of local time. there is a direct correlation between time of day or day of week and user agent usage. i’m assuming that is not the case for “non-browser” user agents. there may be a bias as the data was sampled from fastly customers. results there is no surprise that the top to user agents are cfnetwork and dalvik. these are the agents that are used for ios and android applications respectively. does this count as a “non-browser” user agent? i would argue yes. however, there is no way to determine if the requests were from the app or from an in-app browser. btwebclient comes in third place. this user agent is used by bit torrent clients to download torrent files from websites as well as updating trackers using http. libwww-perl comes in fourth place, followed by java. facebook external hit is the next most popular user agent. whenever a user shares a link on facebook, the site goes out and fetches a copy of that link to display on the users wall. rank user agent 1 cfnetwork 2 dalvik 3 btwebclient 4 libwww-perl 5 java 6 facebookexternalhit 7 apache-httpclient 8 httpcomponents 9 parsoid 10 python-urllib i’m surprised that curl didn’t make the top ten. conclusion there was a signifigant location bias. for example: the sydney data contained a lot of requests from the “foxtel guide” user agent. however, that agent was not found in any of the us sample data. this makes sense as users in the us do not care about a service that isn’t available in that country. although this information is interesting, i can’t see any useful need to generate recurring reports or analysis over time. it’s certainly not as interesting as the ongoing browser war. share story --> the cdn manifesto july 18, 2014 / work / no comments i wasn’t able to attend this years velocity conference. so i’m catching up now by watching videos that are available online. a lot of people ask me: “why did you want to work at fastly?”. it’s an innocent, but complex question. my answer usually varies based on the audience. the explanation i give non-technical people is most likely: “because i want to make the internet faster”. however, fastly is doing much more than just making websites faster. they are much more than a cdn, they are an extension of your application or website. no longer is the cdn a black box that you just place between your origin and your audience. a friend asked me the other day: “give me the 10 second elevator pitch on why fastly is better than any other cdn”. i thought for a split second and answered with: “there are three main differentiating factors that sets fastly apart from the rest of cdn field: real time log delivery instant purging / invalidation full programmatic api interface other cdns don’t have all three capabilities”. these three items are very powerful to web developers. it’s allows you to fully control your content and gain visibility into what your users are doing. an excellent talk by my co-worker, hooman beheshti, touches on these very points. his entertaining and informative talk at velocity is a manifesto of what every cdn should be moving forward. don’t let the fact that this is a sponsored talk turn you off. it’s not a sales pitch at all. share story --> pagespeed and spdy slides july 8, 2014 / nerd work / 1 comment slides from my toronto web performance talk are now available on slideshare. or, you can view them here: share story --> toronto web performance meetup july 2, 2014 / nerd work / no comments i’m going to be talking about page speed and spdy (with a little http/2 thrown in) at the july toronto web performance group, on july 8th. it’s free! drinks and snacks will be provided by our host, eventmobi. share story --> getting lost in 302s june 18, 2014 / nerd / no comments web properties that have been around for a while probably have a lot of old links, dead ends, and redirects. there is a fear amongst content owners that users are not going to be able to find their site if a url changes. “what about everyone’s bookmarks?!” cries the content owner. the bookmark is something from the 90s web (web 1.0 if you will). nobody uses them anymore. this was a challenge i was up against at my previous job. it wasn’t until i illustrated the complexities and unscalability of keeping every url around forever, did change happen. the mobile landscape changes quickly. this shaped the url structure and was the main cause of the many redirects for the cbc’s mobile website. over the course of a week and after digging through apache configurations, akamai config files, and “meta refresh” html files, the following flow chart was born. click for larger thankfully there were no redirect loops! however, there were some pretty serious issues. for example: cbc.ca/mobile -> m.cbc.ca -> cbc.ca/m -> cbc.ca/m/rich yes. you would be redirected three times to the final url! not ideal, especially if you are on a mobile device! a lot of these have since been removed. however, it wasn’t until this diagram was presented to the web developers and management did everyone realize the gravity of the situation. it’s true what they say: a picture speaks a thousand words. in this case: a visio diagram improved web performance! share story --> ipv6 and web performance june 15, 2014 / nerd work / 1 comment after reading the first 60 or so pages of ilya’s excellent book, my mind started racing. how does ipv6 (v6) affect packet size, round trip times, and overall web performance versus ipv4 (v4)? i decided to set up a simple test from my windows desktop and my personal webserver hosted by linode. both have native ipv6 connectivity. no tunneling. the setup: client: windows 7 & chrome 35.0.1916.114 server: centos 6.5 linux (kernel: 2.13.7) & apache 2.2.15 i wanted to keep things as simple as possible to better understand the low level effects of ipv6 on the typical http transaction. as such, i made sure to try to keep the conditions the same for both v6 and v4 requests. my test urls were: http://ipv4.blakecrosby.com/test.txt http://ipv6.blakecrosby.com/test.txt the hostname is the same number of characters and the fetched object is exactly the same. in order to ensure that only v6 and v4 packets were being sent, i disabled support for each one in windows before doing the test. you can follow along the packet streams if you like at cloudshark: ipv4 conversation ipv6 conversation routing my v6 packets take a different route versus my v4 packets. this results in a lower latency for v4 traffic over the v6 traffic (average over twenty packets is 82.1ms vs. 87.4ms repsectively). windows doesn’t have mtr, so i used my macbook pro on the same network instead. [edit: thanks to @jpaulellis for pointing me to: winmtr.net] v6 routing: blakes-mbp:~ bcrosby$ sudo /usr/local/sbin/mtr -n -c 20 -r ipv6.blakecrosby.com host: blakes-mbp loss% snt last avg best wrst stdev 1.|-- 2601:9:8480:1196:76d0:2bf 0.0% 20 1.1 1.2 1.0 1.9 0.2 2.|-- ??? 100.0 20 0.0 0.0 0.0 0.0 0.0 3.|-- 2001:558:82:213b::1 0.0% 20 9.7 18.6 8.9 184.2 39.0 4.|-- 2001:558:80:14a::1 0.0% 20 12.7 12.2 10.2 14.3 1.1 5.|-- 2001:558:80:cf::2 0.0% 20 15.7 12.9 10.4 20.6 2.5 6.|-- 2001:558:0:f6cb::1 0.0% 20 14.4 14.4 11.8 23.3 2.3 7.|-- 2001:558:0:f5e8::2 0.0% 20 18.1 17.1 15.4 18.2 0.8 8.|-- 2001:559::502 0.0% 20 20.3 17.0 14.7 21.8 1.9 9.|-- 2001:590::4516:8f75 0.0% 20 14.2 15.7 13.9 40.4 5.8 10.|-- 2001:590::4516:8fa6 0.0% 20 14.7 15.1 14.4 16.3 0.4 11.|-- 2001:590::4516:8e00 0.0% 20 33.0 45.6 31.5 185.6 40.2 12.|-- 2001:590::4516:8e3b 0.0% 20 34.6 36.4 31.0 66.4 9.6 13.|-- 2001:590::4516:8e65 0.0% 20 64.5 66.8 64.3 99.9 7.8 14.|-- 2001:590::4516:8e4b 0.0% 20 85.5 85.0 82.0 109.0 5.9 15.|-- 2001:590::451f:22b2 0.0% 20 84.5 87.1 82.7 95.8 4.1 16.|-- 2001:518:1001:1::2 0.0% 20 93.5 88.0 82.9 94.5 4.5 17.|-- 2001:518:2800:3::2 0.0% 20 84.2 84.2 82.8 86.5 1.0 18.|-- 2600:3c03::f03c:91ff:fe6e 5.0% 20 83.0 87.4 82.8 121.1 9.7 v4 routing: blakes-mbp:~ bcrosby$ sudo /usr/local/sbin/mtr -n -c 20 -r ipv6.blakecrosby.com host: blakes-mbp loss% snt last avg best wrst stdev 1.|-- 192.168.1.1 0.0% 20 0.7 1.3 0.7 2.5 0.6 2.|-- 50.185.86.1 0.0% 20 9.2 9.3 8.3 10.5 0.8 3.|-- 162.151.1.229 0.0% 20 10.8 10.0 8.7 14.2 1.5 4.|-- 68.85.154.74 0.0% 20 12.2 13.5 10.3 38.0 6.0 5.|-- 68.85.155.14 0.0% 20 11.3 12.7 9.7 20.7 2.6 6.|-- 68.86.90.157 0.0% 20 14.2 14.1 11.0 25.9 3.1 7.|-- 68.86.89.122 55.0% 20 38.6 57.6 36.8 203.4 54.8 8.|-- 68.86.86.205 0.0% 20 39.9 43.9 38.2 102.2 13.8 9.|-- 68.86.86.181 0.0% 20 64.9 64.2 61.9 69.4 1.8 10.|-- 68.86.88.149 0.0% 20 90.9 83.2 79.9 90.9 2.4 11.|-- 173.167.58.26 0.0% 20 80.6 81.8 80.5 88.4 1.9 12.|-- 209.123.10.118 0.0% 20 84.7 85.9 81.7 93.6 4.2 13.|-- 207.99.53.42 0.0% 20 82.4 82.8 81.0 91.6 2.3 14.|-- 97.107.139.208 5.0% 20 83.0 82.1 80.9 84.0 0.9 dns requests the main difference betwen looking up a v4 ip address versus a v6 address is the record name. v4 addresses use an “a” record, while v6 addresses use a “aaaa” record. v6 addresses are also much larger at 16 bytes (versus 4), so the response will always be larger than a standard v4 response. in this particular test, both v4 and v6 responses fit into a single packet. so the number of round trips are the same. the client is going to my router to do the dns resolution using udp. so there is no tcp handshake overhead. version # of packets total size rtt v4 2 176 bytes 0.092ms v6 2 228 bytes 0.089ms the v6 request is ~30% larger than the v4 request. however, round trip time will be the same (under my test conditions) tcp handshake all v6 packets will be larger due to the increase in size of ip headers. v6 headers have a 40 byte size, while v4 headers only have a 20 byte header. one thing i did notice was that the mss size was different in the initial syn packet from the client to the server. the v4 mss was set to 1260 bytes, while the v6 one was set to 1460 bytes. the v4 syn/ack response from the server reset the mss to 1460 and the same v6 syn/ack response reset it to 1420. version # of packets total size rtt v4 3 186 bytes 0.081ms v6 3 246 bytes 0.085ms http get there is no difference between v4 and v6 when fetching the object. http header and body sizes are exactly the same. conclusion ipv6 is a new version of the internet protocol. it doesn’t change the way tcp or http behaves. your packets (although a little larger with v6) are routed the same way. this means that it’s latency and not available bandwidth that affects v6 performance, just like with v4. overall you will be pushing more bits over the wire, however the number of round trips made to the server to make a simple http request with v6 is the same as with v4. version # of packets total size rtt v4 12 2236 bytes 0.337ms v6 15 2848 bytes 0.342ms what’s this? 3 extra packets with the v6 conversation? yes. for some reason the server decided to change the mss to 1420 from 1460 before returning the http response. after the response was sent, another mss change from 1420 back to 1460 was made. i have no idea why. but this accounts for the 3 extra packets. [edit: my coworker pointed out that this additional tcp handshake was chrome being proactive with setting up a new tcp session. the browser does this exepecting to download more data when you click on a link or perform another action] v6 will eventually be the de facto ip version used on the internet. the good news is that all of the advancements in web performance such as front end optimization and http/2 won’t have to change when v6 becomes ubiquitous. v6 should result in better web performance overall. mainly due to the fact that: v6 routers don’t perform packet fragmentation. routers don’t need to perform checksums on v6 packets (like they do on v4) routers aren’t required to compute packet time in queues the above points may be moot now with today’s fast routers and specialized cpus. however, when it comes to web performance, every little bit counts. share story 12next page blake crosbya canadian living in san francisco. likes to drink beer, socialize, travel, and solve complex problems using computers. flies airplanes, rides bikes, and runs marathons. social media upcoming & previous talks toronto web performance group (july 2014) toronto on, canada page speed & spdy surge 2013 (sept. 2013) national harbour md, united states how do you scale for both predictable and unpredictable events on such a large scale? o’reilly velocity (june 2013) santa clara ca, united states the canadian public broadcaster on a diet: slimming down for a whole nation fitc (march 2013) toronto on, canada the canadian public broadcaster on a diet: slimming down for a whole nation more... latest tweets tweets by @blakecrosby copyright 2016 · blake crosby


Here you find all texts from your page as Google (googlebot) and others search engines seen it.

Words density analysis:

Numbers of all words: 3774

One word

Two words phrases

Three words phrases

the - 6.2% (234)
and - 1.8% (68)
for - 1.4% (53)
are - 1.22% (46)
that - 1.22% (46)
his - 1.11% (42)
use - 1.11% (42)
this - 1.09% (41)
0.0 - 1.03% (39)
http - 0.93% (35)
her - 0.87% (33)
was - 0.79% (30)
you - 0.79% (30)
all - 0.77% (29)
0.0% - 0.74% (28)
web - 0.72% (27)
header - 0.61% (23)
our - 0.61% (23)
not - 0.58% (22)
from - 0.58% (22)
user - 0.53% (20)
crosby - 0.53% (20)
out - 0.5% (19)
here - 0.5% (19)
ever - 0.5% (19)
end - 0.48% (18)
packet - 0.48% (18)
work - 0.48% (18)
pro - 0.48% (18)
will - 0.45% (17)
agent - 0.45% (17)
with - 0.45% (17)
headers - 0.42% (16)
rum - 0.4% (15)
have - 0.4% (15)
request - 0.4% (15)
perform - 0.4% (15)
over - 0.4% (15)
can - 0.37% (14)
share - 0.34% (13)
may - 0.34% (13)
there - 0.34% (13)
off - 0.34% (13)
performance - 0.32% (12)
pic - 0.32% (12)
same - 0.32% (12)
time - 0.32% (12)
blake - 0.32% (12)
packets - 0.32% (12)
one - 0.32% (12)
size - 0.29% (11)
fast - 0.29% (11)
how - 0.29% (11)
did - 0.29% (11)
2014 - 0.29% (11)
byte - 0.29% (11)
talk - 0.26% (10)
bar - 0.26% (10)
set - 0.26% (10)
client - 0.26% (10)
--> - 0.26% (10)
what - 0.26% (10)
bcrosby> - 0.26% (10)
get - 0.26% (10)
comment - 0.26% (10)
story - 0.26% (10)
new - 0.24% (9)
app - 0.24% (9)
ipv6 - 0.24% (9)
bytes - 0.24% (9)
1.1 - 0.24% (9)
browser - 0.24% (9)
able - 0.24% (9)
used - 0.24% (9)
edmund> - 0.24% (9)
were - 0.24% (9)
change - 0.24% (9)
nerd - 0.24% (9)
large - 0.24% (9)
bet - 0.24% (9)
host - 0.24% (9)
test - 0.24% (9)
url - 0.21% (8)
than - 0.21% (8)
however - 0.21% (8)
content - 0.21% (8)
machine - 0.21% (8)
file - 0.21% (8)
very - 0.21% (8)
coffee - 0.21% (8)
site - 0.21% (8)
html - 0.21% (8)
cdn - 0.21% (8)
fastly - 0.21% (8)
day - 0.21% (8)
sent - 0.21% (8)
response - 0.21% (8)
round - 0.21% (8)
other - 0.21% (8)
when - 0.21% (8)
way - 0.21% (8)
comments - 0.21% (8)
compress - 0.21% (8)
low - 0.21% (8)
4.2 - 0.21% (8)
city - 0.21% (8)
any - 0.21% (8)
hey - 0.19% (7)
your - 0.19% (7)
larger - 0.19% (7)
need - 0.19% (7)
using - 0.19% (7)
server - 0.19% (7)
spice - 0.19% (7)
first - 0.19% (7)
two - 0.19% (7)
mmay> - 0.19% (7)
make - 0.19% (7)
however, - 0.19% (7)
like - 0.19% (7)
example - 0.19% (7)
route - 0.19% (7)
it’s - 0.19% (7)
july - 0.19% (7)
line - 0.19% (7)
top - 0.19% (7)
mind - 0.16% (6)
different - 0.16% (6)
more - 0.16% (6)
version - 0.16% (6)
data - 0.16% (6)
agents - 0.16% (6)
log - 0.16% (6)
they - 0.16% (6)
requests - 0.16% (6)
1.0 - 0.16% (6)
toronto - 0.16% (6)
going - 0.16% (6)
these - 0.16% (6)
only - 0.16% (6)
both - 0.16% (6)
now - 0.16% (6)
cbc - 0.16% (6)
i’m - 0.16% (6)
lot - 0.16% (6)
main - 0.16% (6)
velocity - 0.16% (6)
i’ve - 0.16% (6)
some - 0.16% (6)
www.foo.com - 0.16% (6)
developer - 0.16% (6)
come - 0.16% (6)
/index.html - 0.13% (5)
fetch - 0.13% (5)
mean - 0.13% (5)
address - 0.13% (5)
direct - 0.13% (5)
router - 0.13% (5)
count - 0.13% (5)
does - 0.13% (5)
tcp - 0.13% (5)
second - 0.13% (5)
application - 0.13% (5)
though - 0.13% (5)
hit - 0.13% (5)
method - 0.13% (5)
host: - 0.13% (5)
website - 0.13% (5)
fact - 0.13% (5)
thing - 0.13% (5)
windows - 0.13% (5)
cause - 0.13% (5)
hand - 0.13% (5)
mss - 0.13% (5)
place - 0.13% (5)
spiced - 0.13% (5)
ops - 0.13% (5)
every - 0.13% (5)
gain - 0.13% (5)
decided - 0.13% (5)
while - 0.13% (5)
but - 0.13% (5)
sample - 0.13% (5)
just - 0.13% (5)
page - 0.13% (5)
had - 0.13% (5)
take - 0.13% (5)
down - 0.13% (5)
want - 0.13% (5)
comes - 0.11% (4)
developers - 0.11% (4)
again - 0.11% (4)
see - 0.11% (4)
4.5 - 0.11% (4)
nation - 0.11% (4)
free - 0.11% (4)
start - 0.11% (4)
1.8 - 0.11% (4)
network - 0.11% (4)
around - 0.11% (4)
2013 - 0.11% (4)
been - 0.11% (4)
referer: - 0.11% (4)
0.9 - 0.11% (4)
chrome - 0.11% (4)
old - 0.11% (4)
most - 0.11% (4)
“non-browser” - 0.11% (4)
local - 0.11% (4)
versus - 0.11% (4)
speed - 0.11% (4)
field - 0.11% (4)
object - 0.11% (4)
simple - 0.11% (4)
yes. - 0.11% (4)
trip - 0.11% (4)
cookie - 0.11% (4)
best - 0.11% (4)
look - 0.11% (4)
such - 0.11% (4)
back - 0.11% (4)
means - 0.11% (4)
total - 0.11% (4)
los - 0.11% (4)
redirect - 0.11% (4)
encoding - 0.11% (4)
also - 0.11% (4)
mobile - 0.11% (4)
difference - 0.11% (4)
ring - 0.11% (4)
rest - 0.11% (4)
where - 0.11% (4)
users - 0.11% (4)
three - 0.11% (4)
even - 0.11% (4)
blakes-mbp - 0.11% (4)
2.|-- - 0.11% (4)
try - 0.11% (4)
distillery - 0.11% (4)
would - 0.11% (4)
body - 0.11% (4)
1.9 - 0.11% (4)
info - 0.11% (4)
bit - 0.11% (4)
exact - 0.11% (4)
available - 0.11% (4)
1.|-- - 0.11% (4)
their - 0.11% (4)
1460 - 0.11% (4)
let - 0.11% (4)
real - 0.11% (4)
should - 0.11% (4)
don’t - 0.11% (4)
result - 0.11% (4)
why - 0.11% (4)
full - 0.11% (4)
4.|-- - 0.11% (4)
turn - 0.11% (4)
routers - 0.11% (4)
about - 0.11% (4)
3.|-- - 0.11% (4)
between - 0.11% (4)
link - 0.11% (4)
keep - 0.08% (3)
same. - 0.08% (3)
location - 0.08% (3)
time. - 0.08% (3)
facebook - 0.08% (3)
june - 0.08% (3)
5.8 - 0.08% (3)
little - 0.08% (3)
complex - 0.08% (3)
14.2 - 0.08% (3)
0.4 - 0.08% (3)
ask - 0.08% (3)
5.|-- - 0.08% (3)
interesting - 0.08% (3)
14.4 - 0.08% (3)
traffic - 0.08% (3)
example. - 0.08% (3)
files - 0.08% (3)
made - 0.08% (3)
wasn’t - 0.08% (3)
conclusion - 0.08% (3)
7.|-- - 0.08% (3)
better - 0.08% (3)
apache - 0.08% (3)
week - 0.08% (3)
cbc.ca/m - 0.08% (3)
conversation - 0.08% (3)
ipv6.blakecrosby.com - 0.08% (3)
follow - 0.08% (3)
test. - 0.08% (3)
slides - 0.08% (3)
8.|-- - 0.08% (3)
routing - 0.08% (3)
after - 0.08% (3)
ipv4 - 0.08% (3)
much - 0.08% (3)
doing - 0.08% (3)
9.7 - 0.08% (3)
internet - 0.08% (3)
6.|-- - 0.08% (3)
0.2 - 0.08% (3)
0.8 - 0.08% (3)
overall - 0.08% (3)
spdy - 0.08% (3)
all. - 0.08% (3)
dns - 0.08% (3)
another - 0.08% (3)
handshake - 0.08% (3)
has - 0.08% (3)
remind - 0.08% (3)
found - 0.08% (3)
came - 0.08% (3)
rtt - 0.08% (3)
send - 0.08% (3)
them - 0.08% (3)
2013) - 0.08% (3)
on, - 0.08% (3)
results - 0.08% (3)
being - 0.08% (3)
problem - 0.08% (3)
hpack - 0.08% (3)
value - 0.08% (3)
addresses - 0.08% (3)
true - 0.08% (3)
lol - 0.08% (3)
syn - 0.08% (3)
example: - 0.08% (3)
sure - 0.08% (3)
people - 0.08% (3)
into - 0.08% (3)
machine. - 0.08% (3)
canadian - 0.08% (3)
stack - 0.08% (3)
san - 0.08% (3)
error - 0.08% (3)
started - 0.08% (3)
maybe - 0.08% (3)
1420 - 0.08% (3)
run - 0.08% (3)
brendan - 0.08% (3)
give - 0.08% (3)
v4. - 0.08% (3)
turning - 0.08% (3)
conference. - 0.08% (3)
york - 0.08% (3)
record - 0.08% (3)
called - 0.08% (3)
september - 0.08% (3)
5.0% - 0.08% (3)
took - 0.08% (3)
84.2 - 0.08% (3)
libraries - 0.08% (3)
0.7 - 0.08% (3)
colour - 0.08% (3)
overhead - 0.08% (3)
applications - 0.08% (3)
check - 0.08% (3)
always - 0.08% (3)
0.6 - 0.08% (3)
previous - 0.08% (3)
compressed - 0.08% (3)
bottle - 0.08% (3)
3.1 - 0.08% (3)
didn’t - 0.08% (3)
scheme - 0.08% (3)
number - 0.08% (3)
glass - 0.08% (3)
accept-encoding: - 0.08% (3)
gzip - 0.08% (3)
5.9 - 0.08% (3)
/logo.jpg - 0.08% (3)
82.8 - 0.08% (3)
cfnetwork - 0.08% (3)
rum. - 0.08% (3)
instead - 0.08% (3)
libwww - 0.08% (3)
whole - 0.05% (2)
drink - 0.05% (2)
[edit: - 0.05% (2)
tweets - 0.05% (2)
routing: - 0.05% (2)
blakes-mbp:~ - 0.05% (2)
scale - 0.05% (2)
instead. - 0.05% (2)
public - 0.05% (2)
along - 0.05% (2)
before - 0.05% (2)
points - 0.05% (2)
sent, - 0.05% (2)
states - 0.05% (2)
united - 0.05% (2)
predictable - 0.05% (2)
canada - 0.05% (2)
solve - 0.05% (2)
order - 0.05% (2)
packets. - 0.05% (2)
latency - 0.05% (2)
broadcaster - 0.05% (2)
doesn’t - 0.05% (2)
group - 0.05% (2)
social - 0.05% (2)
slimming - 0.05% (2)
diet: - 0.05% (2)
reset - 0.05% (2)
compute - 0.05% (2)
9.2 - 0.05% (2)
12.2 - 0.05% (2)
15.7 - 0.05% (2)
2.5 - 0.05% (2)
82.1 - 0.05% (2)
2.4 - 0.05% (2)
90.9 - 0.05% (2)
2.3 - 0.05% (2)
1.5 - 0.05% (2)
14.7 - 0.05% (2)
response. - 0.05% (2)
9.|-- - 0.05% (2)
1.3 - 0.05% (2)
87.4 - 0.05% (2)
83.0 - 0.05% (2)
10.|-- - 0.05% (2)
4.1 - 0.05% (2)
11.|-- - 0.05% (2)
14.|-- - 0.05% (2)
12.|-- - 0.05% (2)
12.7 - 0.05% (2)
fit - 0.05% (2)
v4) - 0.05% (2)
snt - 0.05% (2)
bcrosby$ - 0.05% (2)
sudo - 0.05% (2)
/usr/local/sbin/mtr - 0.05% (2)
facto - 0.05% (2)
idea - 0.05% (2)
extra - 0.05% (2)
loss% - 0.05% (2)
performance, - 0.05% (2)
v6) - 0.05% (2)
last - 0.05% (2)
trips - 0.05% (2)
13.|-- - 0.05% (2)
avg - 0.05% (2)
syn/ack - 0.05% (2)
wrst - 0.05% (2)
stdev - 0.05% (2)
notice - 0.05% (2)
due - 0.05% (2)
speaking - 0.05% (2)
1.2 - 0.05% (2)
exactly - 0.05% (2)
know - 0.05% (2)
conditions - 0.05% (2)
side - 0.05% (2)
aspires_> - 0.05% (2)
because - 0.05% (2)
thought - 0.05% (2)
right - 0.05% (2)
buffer - 0.05% (2)
probably - 0.05% (2)
process - 0.05% (2)
then - 0.05% (2)
co-worker - 0.05% (2)
code - 0.05% (2)
compressing - 0.05% (2)
problems - 0.05% (2)
humboldt - 0.05% (2)
overhead. - 0.05% (2)
store - 0.05% (2)
roll - 0.05% (2)
http://www.foo.com/index.html - 0.05% (2)
(when - 0.05% (2)
way. - 0.05% (2)
data. - 0.05% (2)
reduce - 0.05% (2)
things - 0.05% (2)
few - 0.05% (2)
http://www.example.com/ - 0.05% (2)
ended - 0.05% (2)
:path: - 0.05% (2)
accept-encoding:gzip - 0.05% (2)
http/1.1 - 0.05% (2)
say - 0.05% (2)
sent. - 0.05% (2)
request, - 0.05% (2)
maker - 0.05% (2)
barista - 0.05% (2)
less - 0.05% (2)
bartender - 0.05% (2)
sampling - 0.05% (2)
enter - 0.05% (2)
mainly - 0.05% (2)
enough - 0.05% (2)
dark - 0.05% (2)
29, - 0.05% (2)
base - 0.05% (2)
i’ll - 0.05% (2)
feel - 0.05% (2)
vanilla - 0.05% (2)
clear - 0.05% (2)
especially - 0.05% (2)
town - 0.05% (2)
inn - 0.05% (2)
visit - 0.05% (2)
latest - 0.05% (2)
brendan> - 0.05% (2)
issue - 0.05% (2)
kernel - 0.05% (2)
typical - 0.05% (2)
omg - 0.05% (2)
edmund: - 0.05% (2)
broke - 0.05% (2)
internal - 0.05% (2)
love - 0.05% (2)
working - 0.05% (2)
drop - 0.05% (2)
you’re - 0.05% (2)
together - 0.05% (2)
third - 0.05% (2)
barbara - 0.05% (2)
awesome - 0.05% (2)
improve - 0.05% (2)
deliver - 0.05% (2)
6.5 - 0.05% (2)
find - 0.05% (2)
although - 0.05% (2)
manifesto - 0.05% (2)
18, - 0.05% (2)
me: - 0.05% (2)
answer - 0.05% (2)
audience. - 0.05% (2)
website. - 0.05% (2)
asked - 0.05% (2)
pitch - 0.05% (2)
fully - 0.05% (2)
excellent - 0.05% (2)
engagements - 0.05% (2)
or, - 0.05% (2)
http/2 - 0.05% (2)
bookmark - 0.05% (2)
sydney - 0.05% (2)
diagram - 0.05% (2)
size, - 0.05% (2)
affect - 0.05% (2)
book, - 0.05% (2)
pages - 0.05% (2)
realize - 0.05% (2)
everyone - 0.05% (2)
times - 0.05% (2)
until - 0.05% (2)
click - 0.05% (2)
flow - 0.05% (2)
files, - 0.05% (2)
config - 0.05% (2)
redirects - 0.05% (2)
changes - 0.05% (2)
care - 0.05% (2)
curl - 0.05% (2)
talks - 0.05% (2)
usually - 0.05% (2)
filter - 0.05% (2)
capture - 0.05% (2)
four - 0.05% (2)
hits - 0.05% (2)
small - 0.05% (2)
vs. - 0.05% (2)
useful - 0.05% (2)
header. - 0.05% (2)
information - 0.05% (2)
http. - 0.05% (2)
access - 0.05% (2)
“what - 0.05% (2)
day: - 0.05% (2)
question - 0.05% (2)
assuming - 0.05% (2)
geographic - 0.05% (2)
java - 0.05% (2)
well - 0.05% (2)
dalvik - 0.05% (2)
copy - 0.05% (2)
agent. - 0.05% (2)
next - 0.05% (2)
external - 0.05% (2)
libwww-perl - 0.05% (2)
websites - 0.05% (2)
case - 0.05% (2)
download - 0.05% (2)
torrent - 0.05% (2)
btwebclient - 0.05% (2)
ios - 0.05% (2)
surprise - 0.05% (2)
bias - 0.05% (2)
which - 0.05% (2)
0.0% 20 - 0.74% (28)
of the - 0.37% (14)
user agent - 0.34% (13)
at the - 0.32% (12)
the same - 0.32% (12)
from the - 0.29% (11)
share story - 0.26% (10)
web performance - 0.26% (10)
< bcrosby> - 0.26% (10)
to the - 0.26% (10)
2014 / - 0.26% (10)
on the - 0.24% (9)
< edmund> - 0.24% (9)
story --> - 0.24% (9)
no comments - 0.21% (8)
in the - 0.21% (8)
/ nerd - 0.19% (7)
< mmay> - 0.19% (7)
is the - 0.19% (7)
there is - 0.19% (7)
will be - 0.19% (7)
to web - 0.16% (6)
need to - 0.16% (6)
decided to - 0.13% (5)
going to - 0.13% (5)
the coffee - 0.13% (5)
the server - 0.13% (5)
lot of - 0.13% (5)
work / - 0.13% (5)
as the - 0.13% (5)
if you - 0.13% (5)
spiced rum - 0.13% (5)
that the - 0.13% (5)
the v6 - 0.11% (4)
larger than - 0.11% (4)
want to - 0.11% (4)
and the - 0.11% (4)
http 2 - 0.11% (4)
take a - 0.11% (4)
be the - 0.11% (4)
means that - 0.11% (4)
“non-browser” user - 0.11% (4)
round trip - 0.11% (4)
the top - 0.11% (4)
that this - 0.11% (4)
the header - 0.11% (4)
it was - 0.11% (4)
the us - 0.11% (4)
nerd / - 0.11% (4)
the client - 0.11% (4)
user agents - 0.11% (4)
the first - 0.11% (4)
headers are - 0.11% (4)
are the - 0.11% (4)
have a - 0.11% (4)
comments i - 0.11% (4)
that are - 0.11% (4)
8, 2014 - 0.08% (3)
size of - 0.08% (3)
than a - 0.08% (3)
of what - 0.08% (3)
the request - 0.08% (3)
the v4 - 0.08% (3)
rtt v4 - 0.08% (3)
total size - 0.08% (3)
v6 address - 0.08% (3)
host: www.foo.com - 0.08% (3)
of header - 0.08% (3)
number of - 0.08% (3)
in this - 0.08% (3)
are used - 0.08% (3)
web developers - 0.08% (3)
from my - 0.08% (3)
the internet - 0.08% (3)
nerd work - 0.08% (3)
of packets - 0.08% (3)
v6 packets - 0.08% (3)
a cookie - 0.08% (3)
this means - 0.08% (3)
so the - 0.08% (3)
this will - 0.08% (3)
version # - 0.08% (3)
this is - 0.08% (3)
agents that - 0.08% (3)
blake crosby - 0.08% (3)
and we - 0.08% (3)
you will - 0.08% (3)
such a - 0.08% (3)
we can - 0.08% (3)
was the - 0.08% (3)
took a - 0.08% (3)
all of - 0.08% (3)
size rtt - 0.08% (3)
packets total - 0.08% (3)
coffee machine - 0.08% (3)
for the - 0.08% (3)
with a - 0.08% (3)
did you - 0.08% (3)
over the - 0.08% (3)
the machine - 0.08% (3)
new york - 0.08% (3)
to change - 0.08% (3)
cause i - 0.08% (3)
are not - 0.08% (3)
to 1460 - 0.08% (3)
the fact - 0.08% (3)
the mss - 0.08% (3)
the same. - 0.08% (3)
page speed - 0.05% (2)
slimming down - 0.05% (2)
a diet: - 0.05% (2)
canadian public - 0.05% (2)
broadcaster on - 0.05% (2)
exactly the - 0.05% (2)
a whole - 0.05% (2)
you can - 0.05% (2)
on, canada - 0.05% (2)
this results - 0.05% (2)
whole nation - 0.05% (2)
-> cbc.ca/m - 0.05% (2)
and v4 - 0.05% (2)
and my - 0.05% (2)
the canadian - 0.05% (2)
it wasn’t - 0.05% (2)
around for - 0.05% (2)
i decided - 0.05% (2)
down for - 0.05% (2)
public broadcaster - 0.05% (2)
wasn’t until - 0.05% (2)
the web - 0.05% (2)
diet: slimming - 0.05% (2)
however, there - 0.05% (2)
to set - 0.05% (2)
was set - 0.05% (2)
blakes-mbp:~ bcrosby$ - 0.05% (2)
20 14.2 - 0.05% (2)
syn/ack response - 0.05% (2)
my test - 0.05% (2)
v4 and - 0.05% (2)
change the - 0.05% (2)
or http - 0.05% (2)
round trips - 0.05% (2)
and v6 - 0.05% (2)
a little - 0.05% (2)
addresses use - 0.05% (2)
the number - 0.05% (2)
of round - 0.05% (2)
make a - 0.05% (2)
the main - 0.05% (2)
3 extra - 0.05% (2)
sudo /usr/local/sbin/mtr - 0.05% (2)
to 1420 - 0.05% (2)
the response - 0.05% (2)
20 83.0 - 0.05% (2)
change from - 0.05% (2)
0.0 0.0 - 0.05% (2)
does this - 0.05% (2)
due to - 0.05% (2)
set to - 0.05% (2)
wrst stdev - 0.05% (2)
avg best - 0.05% (2)
snt last - 0.05% (2)
blakes-mbp loss% - 0.05% (2)
routers don’t - 0.05% (2)
ipv6.blakecrosby.com host: - 0.05% (2)
was different - 0.05% (2)
speaking engagements - 0.05% (2)
1 comment - 0.05% (2)
it off - 0.05% (2)
< brendan> - 0.05% (2)
coffee maker - 0.05% (2)
< aspires_> - 0.05% (2)
turning it - 0.05% (2)
off and - 0.05% (2)
i thought - 0.05% (2)
mmay> lol - 0.05% (2)
or their - 0.05% (2)
headers in - 0.05% (2)
bcrosby> edmund: - 0.05% (2)
http headers - 0.05% (2)
results in - 0.05% (2)
the http - 0.05% (2)
the headers - 0.05% (2)
using a - 0.05% (2)
of headers - 0.05% (2)
are sent. - 0.05% (2)
the difference - 0.05% (2)
bcrosby> i - 0.05% (2)
was no - 0.05% (2)
here are - 0.05% (2)
had and - 0.05% (2)
distillery spiced - 0.05% (2)
29, 2014 - 0.05% (2)
a free - 0.05% (2)
look at - 0.05% (2)
this rum - 0.05% (2)
the colour - 0.05% (2)
came to - 0.05% (2)
i’ve ever - 0.05% (2)
i will - 0.05% (2)
to work - 0.05% (2)
have the - 0.05% (2)
to take - 0.05% (2)
will always - 0.05% (2)
velocity conference. - 0.05% (2)
to see - 0.05% (2)
if you’re - 0.05% (2)
5, 2014 - 0.05% (2)
/ work - 0.05% (2)
comments i’m - 0.05% (2)
a look - 0.05% (2)
an example - 0.05% (2)
and spdy - 0.05% (2)
to make - 0.05% (2)
comes in - 0.05% (2)
a user - 0.05% (2)
make the - 0.05% (2)
requests from - 0.05% (2)
the cdn - 0.05% (2)
18, 2014 - 0.05% (2)
you want - 0.05% (2)
i want - 0.05% (2)
fastly is - 0.05% (2)
to download - 0.05% (2)
more than - 0.05% (2)
they are - 0.05% (2)
much more - 0.05% (2)
are an - 0.05% (2)
that you - 0.05% (2)
the other - 0.05% (2)
me the - 0.05% (2)
your content - 0.05% (2)
users are - 0.05% (2)
as well - 0.05% (2)
if the - 0.05% (2)
http 1.1 - 0.05% (2)
or from - 0.05% (2)
http/1.1 host: - 0.05% (2)
http://www.example.com/ accept-encoding: - 0.05% (2)
the second - 0.05% (2)
only the - 0.05% (2)
is used - 0.05% (2)
the size - 0.05% (2)
are compressed - 0.05% (2)
such as - 0.05% (2)
other day: - 0.05% (2)
is not - 0.05% (2)
used to - 0.05% (2)
this information - 0.05% (2)
to fetch - 0.05% (2)
like they - 0.05% (2)
or web - 0.05% (2)
assuming that - 0.05% (2)
previous talks - 0.05% (2)
try to - 0.05% (2)
week and - 0.05% (2)
do not - 0.05% (2)
share story --> - 0.24% (9)
/ no comments - 0.21% (8)
2014 / nerd - 0.19% (7)
there is no - 0.11% (4)
going to be - 0.11% (4)
/ nerd work - 0.08% (3)
this means that - 0.08% (3)
size rtt v4 - 0.08% (3)
work / no - 0.08% (3)
8, 2014 / - 0.08% (3)
nerd work / - 0.08% (3)
there is a - 0.08% (3)
total size rtt - 0.08% (3)
of packets total - 0.08% (3)
# of packets - 0.08% (3)
the coffee machine - 0.08% (3)
the number of - 0.05% (2)
larger than the - 0.05% (2)
5.0% 20 83.0 - 0.05% (2)
0.0% 20 14.2 - 0.05% (2)
avg best wrst - 0.05% (2)
distillery spiced rum - 0.05% (2)
way. this means - 0.05% (2)
round trip time - 0.05% (2)
ipv6.blakecrosby.com host: blakes-mbp - 0.05% (2)
number of round - 0.05% (2)
the mss to - 0.05% (2)
canadian public broadcaster - 0.05% (2)
on a diet: - 0.05% (2)
slimming down for - 0.05% (2)
a whole nation - 0.05% (2)
toronto on, canada - 0.05% (2)
the canadian public - 0.05% (2)
broadcaster on a - 0.05% (2)
diet: slimming down - 0.05% (2)
loss% snt last - 0.05% (2)
bcrosby$ sudo /usr/local/sbin/mtr - 0.05% (2)
sudo /usr/local/sbin/mtr -n - 0.05% (2)
what are the - 0.05% (2)
ever had and - 0.05% (2)
will be the - 0.05% (2)
if you’re going - 0.05% (2)
2014 / work - 0.05% (2)
it off and - 0.05% (2)
< bcrosby> edmund: - 0.05% (2)
turning it off - 0.05% (2)
this results in - 0.05% (2)
all of the - 0.05% (2)
the other day: - 0.05% (2)
requests from the - 0.05% (2)
routing: blakes-mbp:~ bcrosby$ - 0.05% (2)
that are used - 0.05% (2)
18, 2014 / - 0.05% (2)
you want to - 0.05% (2)
exactly the same. - 0.05% (2)
v6 and v4 - 0.05% (2)
a look at - 0.05% (2)
-r ipv6.blakecrosby.com host: - 0.05% (2)
blakes-mbp loss% snt - 0.05% (2)
last avg best - 0.05% (2)
wrst stdev 1.|-- - 0.05% (2)
for a whole - 0.05% (2)

Here you can find chart of all your popular one, two and three word phrases. Google and others search engines means your page is about words you use frequently.

Copyright © 2015-2016 hupso.pl. All rights reserved. FB | +G | Twitter

Hupso.pl jest serwisem internetowym, w którym jednym kliknieciem możesz szybko i łatwo sprawdź stronę www pod kątem SEO. Oferujemy darmowe pozycjonowanie stron internetowych oraz wycena domen i stron internetowych. Prowadzimy ranking polskich stron internetowych oraz ranking stron alexa.