the blog post part 1

This commit is contained in:
soulgalore 2016-10-19 13:53:20 +02:00
parent ada68a9ddc
commit 1a0d7bb5d1
2 changed files with 42 additions and 15 deletions

View File

@ -1,15 +0,0 @@
---
layout: default
title: Welcome sitespeed.io 4.0 beta
description: Finally sitespeed.io 4.0 is here!
author: Peter Hedenskog
authorimage: /img/aboutus/peter.jpg
intro: We have released the first beta version of 4.0 of sitespeed.io. Finally!
keywords: sitespeed.io, sitespeed, site, speed, webperf, performance, web, wpo
nav: blog
---
# Sitespeed.io 4.0 beta
Yes finally we have released the first beta of 4.0. We plan to do at least one beta before final.
We have a have some great changes in 4.0 but let pause those for the 4.0 final post and let me go through what missing this release and what's coming in 4.0 final.

View File

@ -0,0 +1,42 @@
---
layout: default
title: Welcome sitespeed.io 4.0
description: Finally sitespeed.io 4.0 is here!
author: Peter Hedenskog
authorimage: /img/aboutus/peter.jpg
intro: Yes finally we have released the 4.0. We (Peter/Tobias/Jonathan and contributors) have been working really hard the last year to make this happen.
keywords: sitespeed.io, sitespeed, site, speed, webperf, performance, web, wpo
nav: blog
---
# Sitespeed.io 4.0
Yes finally we have released the 4.0. We (Peter/Tobias/Jonathan and contributors) have been working extremely hard the last year to make this happen.
## Background
When we started 4.0 there was a couple of things that we wanted to fix:
* We wanted to get rid of YSlow. Yes we know that many people love/uses Yslow and we have been using a modified version with our own rules (because some of the original rules did't get updated over time). We wanted something new and modern that could stand the test of time.
* We wanna move to only test in real browsers to be able to support HTTP/2. In 3.x we used PhantomJS to run the YSlow tests and that made us suffer so we had the same limits as PhantomJS (no HTTP/2, incorrect assets sisez etc). To make one thing clear: I love PhantomJS and what Ariya and contributors have done with it. But to make sitespeed.io even better, we needed to move only use real browsers.
* We wanted a better HAR. We used to use BrowserMobProxy and it doesn't support HTTP/2 and also modifies responses.
* We want more contributors. 3.X was the first thing we built in NodeJS and we could surely make the code more readable and easier to understand. We also want a structure to build upon.
* Test a page as a logged in user. The number one feature that users wanted in sitespeed.io was to be able to login a user and test the performance as a logged in user.
* Don't overload Graphite with metrics. One of all the things I did wrong in 3.x was send all the metrics we collected to Graphite. Graphite got overloaded. Instead we should pick the most important one and make it possible for the user to add the ones she needs.
I think that was the list. The most important things at least. We have more things on the list that didn't make it to 4.0 but is coming soon (like InfluxDB support, server for showing the result).
# What we have accomplished the last year
We released four new Open Source performance tools. Yep four. Lets talk about them and then g into what we've done with sitespeed.io.
## The coach
<img src="/img/logos/coach.png" class="pull-right img-big" alt="I'm the coach" width="188" height="219">
YSlow is dead, long live the Coach! The coach helps you find performance problems on your page and gives you advice of what you can do better. We use the coach in sitespeed.io but what's extra cool is that it can be used by any tool.
## PageXray
## Browsertime