Skip to content
Tests to see bad code's effect of page load time
Find file
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
c1 Adding initial tests and baseline
c2
c3
c4 Adding initial tests and baseline
c5 Adding initial tests and baseline
c6 Adding initial tests and baseline
c7 Adding initial tests and baseline
h1 Adding initial tests and baseline
h2
h3
h4
i1 Adding initial tests and baseline
i10 Adding initial tests and baseline
i2
i3
i4 Adding initial tests and baseline
i5 Adding initial tests and baseline
i6
i7 Adding initial tests and baseline
i8 Adding initial tests and baseline
i9
js1 Adding initial tests and baseline
js2
js3
js4 Adding initial tests and baseline
js5
README Edited README via GitHub
baseline.html Adding initial tests and baseline
dyn.jpg
efficient-html.png Adding initial tests and baseline
favicon.ico
inefficient-html.png
semantic-css.png
social.png Adding initial tests and baseline
star.jpg
styles.css

README

Created by Lara Swanson at Dyn Inc
http://www.dyn.com
@laraswanson

Initial test results: http://www.writegoodcode.com

Writing code that is efficient, semantic, and easily edited later makes sense for a lot of reasons. Your code will be able to be read and easily modified by other developers. It will be easy for browsers to understand and show to a user. It will even make it easy for you to repurpose your code on other areas of your site.

There are some developers, however, that may need more convincing - or perhaps there are non-developers that want you to just code fast and ignore good coding methods just to get the job done. This experiment's goal was to demonstrate the business value of coding well. Page speed is directly proportional to revenue, and coding well greatly impacts your page speed.
Something went wrong with that request. Please try again.