Programming

You are currently browsing the archive for the Programming category.

I particularly like the regexp benchmark in google’s new revision of V8.

I will do more comparisons with different benchmarks but here is a quick update on the state of alpha browsers regarding the V8 benchmark on windows.

Test system: Mac Pro Early 2006: 2x Dual Core Xeon 5150 (2.66GHz), 3GB RAM, Vista x64 SP1.

Benchies!

IE8 RC1 64-bit on Google's V8 benchmark Revision 3

IE8 RC1 64-bit on Google's V8 benchmark Revision 3

Firefox 3.2a1 32bit 200907033501 on V8 benchmark revision 3

Firefox 3.2a1 32bit 200907033501 on V8 benchmark revision 3

Webkit rev. 40730 on V8 Benchmark revision 3

Webkit rev. 40730 on V8 Benchmark revision 3

Chromium 32bit rev9376 on Google's V8 Benchmark Revision 3

Chromium 32bit rev9376 on Google's V8 Benchmark Revision 3

  • Share/Bookmark

Tags: , , , , , ,

When you’re using various tools to get information on what exactly is making your website slow, the most common method to display detailed information is a waterfall graph.

In this article, I will show you some tools that provide waterfall graphs and also give an explanation of how to read a simple waterfall graph.

Read the rest of this entry »

  • Share/Bookmark

Services and tools such as AOL WebPageTest will provide you with graphs and punchlists of things you need to fix.

Here is how you read them!

Load time is the time that it took to transfer ALL of the page, and for it to stop transferring.

First byte is “how long it took for the beginning of the page to be sent to the browser”

“Start render” is “When the user begins to see a page form.”

Document complete is when the document is usable.

Fully loaded includes anything that loads after Document Complete, such as AJAX calls.

“Requests” are the number of items that had to be sent individually to the browser.

“Bytes in” is the total size of items that had to be sent to the browser.

  Load Time First Byte Start Render Document Complete Fully Loaded Requests Bytes In
First View 4.752s 0.301s 2.558s 4.752s 4.752s 16 590 KB
Repeat View 0.674s 0.425s 0.238s 0.674s 0.920s 6 1 KB

So now that you know what these things mean, you ask, what should I be seeing that I need to improve?

Without a waterfall graph to give you more detail, this graph says that you need to decrease the number of requests and the total bytes in.

  • Share/Bookmark

I am working on a plugin (originally started by DD32) that combines all external CSS and JavaScript that passes through WP_Scripts.

This will provide an order of magnitude page load time decrease for nearly all WordPress blogs.

Unfortunately, in order for this to work enough to close the open ticket, several things are going to have to be figured out:

  • Themes and Plugins need to use wp_enqueue_script() and wp_enqueue_style()
  • Most javascript will need to be rewritten, preferably to be exeecuted after the DOM is ready.
  • LTR (left-to-right) styles
  • A framework for minification and gzipping of the resulting scripts and styles.

I will be posting more about this in the future as I work out the details.

  • Share/Bookmark

Tags: , , , , , , ,

Bad Behavior has blocked 252 access attempts in the last 7 days.

Load time improved by PHP Speedy Load time improved by PHP Speedy