582866 - Improve our YSlow! score (currently, B, 85)

Status: VERIFIED FIXED

(Input :: General, defect, P3)

Description

[Stephen Donner [:stephend] Not actively reading bugmail]

We get a YSlow! score of "C" using ruleset 2 on http://input.stage.mozilla.com/en-US/.

Some quick takeaways:

* we should probably gzip-compress our static files (JS, CSS)
* it recommends we add expires headers

Comment 1

[Fred Wenzel [:wenzel]]

Yes, we're not minifying our assets yet, but I agree we should. Thanks for this bug.

Comment 2

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

Stephen, I don't have a working YSlow, do you mind updating this with the new score (the site has changed a bit)?

Comment 3

[Stephen Donner [:stephend] Not actively reading bugmail]

(In reply to comment #2)
> Stephen, I don't have a working YSlow, do you mind updating this with the new
> score (the site has changed a bit)?

I hear Firefox 3.6 is still a great browser.  The latest score is still a C, 70.

Comment 4

[Fred Wenzel [:wenzel]]

I'll minimize our JS and CSS files.

Comment 5

[Fred Wenzel [:wenzel]]

Done. We're up to a 77 score.

It also suggests long expires headers as well as gzip, which unless I am mistaken are both an Apache configuration question?

Davedash, care to chime in?

Comment 6

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

Yeah, I believe so - CCing oremj, who'd know.

Comment 7

[Jeremy Orem [:oremj]]

I can gzip by mime type via Zeus. Expires can be set to whatever you'd like.

Comment 8

[Aakash Desai [:aakashd]]

Is this bug fixed now?

Comment 9

[Stephen Donner [:stephend] Not actively reading bugmail]

(In reply to comment #8)
> Is this bug fixed now?

What's the criteria for "fixed"?

Comment 10

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

(In reply to comment #9)
> (In reply to comment #8)
> > Is this bug fixed now?
> 
> What's the criteria for "fixed"?

I told Aakash, to not ask if bugs are finished in bugzilla as it just adds to the noise.

But to clarify, a developer will mark this closed once they've done enough to make this score get to A or reasonably justify why it has to be a B.

Comment 11

[Fred Wenzel [:wenzel]]

We need to come up with criteria for the gzipping (<- use what AMO and SUMO do, I'd suggest) as well as expires header (<- actually I'd suggest the same here).

I think once those are in place (on prod is more important than on stage even, though the latter makes for better testing if it matches prod), we are good.

I'd call it "fixed" if the only thing remaining is "use a CDN" which I don't see us doing for Input any time soon.

Comment 12

[Fred Wenzel [:wenzel]]

Status: Gzipping was added for CSS and JS files in Zeus. We are up to a grade B, 85, in production.

Comment 13

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

http://github.com/fwenzel/reporter/commit/111172c

I sprited a few images, I'm calling this fixed if we drop to C again we can take a look again.

Comment 14

[Stephen Donner [:stephend] Not actively reading bugmail]

It's now complaining about the number of DOM elements and the lack of cookie-free domains; our score is an 83 on staging -- can we investigate and see if the latter is a config issue?

Comment 15

[Fred Wenzel [:wenzel]]

I don't think we have enough pics to warrant a cookie-free subdomain just for static assets... Also, most visitors of the dashboard are not going to have a cookie, I think.

Comment 16

[Stephen Donner [:stephend] Not actively reading bugmail]

Verified; we haven't regressed, and I think our setup is different (read: better) on prod, which makes our score higher, there.