Author Archives: Mark Reyes

About Mark Reyes

Web Developer based out of Southern California.

PageSpeed: here.ashford.edu

Page speed seems to be one of the bigger priorities as of late and I was designated with the RND task in making one of our subdomains, here.ashford.edu a bit…faster. In summary, this is a single-page design intended to support our Marketing campaigns during the 2014 Winter Olympics.

In one sprint (2 weeks in my case), we were able to set some benchmarks and reduce our network requests, optimize our images, minify our CSS, minify our JavaScript, compress and cache our assets by tweaking our server-side configurations.

The before benchmarks are listed below for 03/19/2014 unless otherwise stated:

  1. Google PageSpeed – Mobile: 55/100
  2. Google PageSpeed – Desktop: 71/100
  3. Y-SLOW: 67/100
  4. Network Requests: 112 (03/21/2014)

The after benchmarks are listed below for 03/27/2014:

  1. Google PageSpeed – Mobile: 64/100
  2. Google PageSpeed – Desktop: 83/100
  3. Y-SLOW: 79/100
  4. Network Requests: 87

Tools and methods I used to compliment our page speed via server-side:

Tools and methods I used to compliment our page speed via client-side,:

I still have some items to solve—Youtube iframes ultimately being the culprit. Getting into a 1-second threshold with mobile is another instigator. I’m suspecting a JavaScript solution is on the horizon but we shall see.

WTF HTML and CSS

Common HTML and CSS miscues as explained by WTF, HTML and CSS?.

Thanks to, CSS Weekly #103 and WTF, HTML and CSS?.

How to keep up to date on FRONT-END TECHNOLOGIES

The web is a rapidly evolving universe. An important part of our job as front-end developers is keeping up to date and staying close to new tools, trends and workflows. Hundreds of blog posts and articles are published every day, but there is no way you can read all of them. We think you should have a strategy to keep up to date, so we have created this recipe.

Visit, How to keep up to date on FRONT-END TECHNOLOGIES.

Thanks to an old friend and the curators of this document, @jonycheung and @frontendrescue.