1107980 - (mozorg-opt) [TRACKING] mozilla.org optimizations from MOZPDX work week

Status: NEW

(www.mozilla.org :: Project Tracking, defect)

Description

[Steven Garrity [:sgarrity]]

Some smart and classy folks that work on mozilla.org got together at the Portland work week in Dec 2014. This is a tracking bug for the tasks from that meeting.

We came up with the following list of possible optimizations for mozilla.org:

https://etherpad.mozilla.org/mozorg-optimization

MozWeb optimization task list
Getting started
 * Measure and log page weight of all pages for post-optimization comparison

Metrics:
 * Page weight
 * HTTP requests
 * Time to render

Key pages to track:
 * mozilla.org/
 * /firefox/new
 * /contribute

Fira font switch
 * WOFF2
 * rem
 * tidy up font size variables
 * check for local fonts

LESS cleanup
 * rename responsive LESS files
 * remove @imports in favor of settings.py
 * lightweight sandstone variant
 * audit lib.less and sandstone(-resp).less

JavaScript cleanup
 * make optimizely opt-in (not included on all pages by default)
 * research pages that may not need jQuery
 * tabzilla without jQuery?
 * minify tabzilla.js

General
 * SVG (maybe start with home page)
 * rebuild JS powered mobile nav to be CSS only
 * enable CSP
 * avoid unnecessary redirects (bug 715192)

Comment 1

[Jennifer Bertsch [:jbertsch]]

Just confirming for myself:  We need to leave this one open until we have the old style nav off pages like release notes and dev edition, correct?

Comment 2

[Jonathan Petto [:jpetto]]

I think there are still a few tasks listed in comment #0 that are yet to be done (including the old style drop-down header nav).

These would make good "own group" priorities (like Jascha talked about at today's all-hands).