How to interpret these test results??

mecanto · September 7, 2015, 10:49pm

Hi there. I’m new to the forum, but I’m not new to wanting to reduce the number of requests on my web pages. The problem is, whenever I run an analysis of my web pages using a website such as webpagetest.org, it identifies a LOT of problems with my web page and I want to address them, but I don’t UNDERSTAND the issues in the first place.

I’ve made a habit of lowering the quality of my images to optimize them for the web (that’s easy enough to do) but as far as anything beyond that, I’m clueless.

If there’s a thread that serves as a resource for these newbie questions, I assure you that I made an effort to find it before posting this thread, but I could not find anything, so I apologize for that.

I’m hoping that by sharing my test results here, someone would be kind enough to give me some pointers so I can take action against what seems to be an excessive amount of requests on my website (at least more than my competitors have)

F - First Byte Time
A - Keep-alive Enabled
A - Compress Transfer
A - Compress Images
F - Cache static content
X - Effective use of CDN

Details:
First Byte Time (back-end processing): 19/100
945 ms First Byte Time
135 ms Target First Byte Time

Use persistent connections (keep alive): 100/100

Use gzip compression for transferring compressable responses: 100/100
502.9 KB total in compressible text, target size = 502.9 KB - potential savings = 0.0 KB

Compress Images: 91/100
358.7 KB total in images, target size = 329.7 KB - potential savings = 29.0 KB

Use Progressive JPEGs: 90/100
303.1 KB of a possible 335.3 KB (90%) were from progressive JPEG images

CDN’s Used:
assets.pinterest.com : Akamai
fonts.googleapis.com : Google
s.gravatar.com : Edgecast
s0.wp.com : WordPress Jetpack
app.videoleadbox.net : Cloudflare
stats.wp.com : WordPress Jetpack
1.gravatar.com : Edgecast
images.dmca.com : NetDNA
www.google-analytics.com : Google
www.youtube.com : Google
pixel.wp.com : WordPress Jetpack
fonts.gstatic.com : Google
s.ytimg.com : Google
s-passets.pinimg.com : Edgecast
yt3.ggpht.com : Google
widgets.pinterest.com : Fastly
www.google.com : Google
static.doubleclick.net : Google
i.ytimg.com : Google
apis.google.com : Google
connect.facebook.net : Facebook
ajax.googleapis.com : Google
static.ak.facebook.com : Facebook
accounts.google.com : Google
syndication.twitter.com : Twitter
s-static.ak.facebook.com : Facebook
cdn.syndication.twitter.com : Fastly
www.facebook.com : Facebook
ssl.gstatic.com : Google
oauth.googleusercontent.com : Google
fbstatic-a.akamaihd.net : Akamai

GreenGecko · September 8, 2015, 10:13pm

There are 2 avenues that need to be addressed.

First off, the 1 second TTFB. That’s down to your infrastructure, and how well it’s working. Reconfiguration of the constituent parts - Mysql, PHP, web server - and efficient use of caching at all levels will help to reduce that ( well, until the time where only more processing power is the only way forward ).

The second part is the files that your html want to download. Improving performance here is down to:

reducing the number of files
reducing the size of the payload
adding expiry headers to the files

There is a latency overhead involved with downloading a file which is just lost time to the site. Reducing the number of files reduces that wasted time.

Less volume to download, the faster it it. Stands to reason, your pipe is only so big.

An expiry header associated with a file allows it to be stored in the client’s browser for a set period of time, so that it doesn’t need downloading next time. No difference for the first visit to a site, but a huge improvement afterwards.

Obviously you only have control over the files that you are delivering, so for those coming from all those other source, you’re at the mercy of their Admins. In addition, if you’re out in the 'wops like we are, delivering from mainland USA is not necessarily a good idea.

This is a start… there are loads of other things you can do on top of this ( WP level caching, CDNs, SPDY/HTTP2 when it becomes available, lazy loading of images for example ), but get your site as efficient as possible before you go down that route…

Topic		Replies	Views
How to interpret these test results?? Discuss Test Results	0	125	September 7, 2015
test results Discuss Test Results	1	104	August 8, 2013
Test Results not looking good. Need some help please. Discuss Test Results	23	142	December 8, 2013
Problems detection of webpage tests, any suggestions? Newbie Discuss Test Results	5	119	January 3, 2012
Understand the webpagetest results after some changes on a website Discuss Test Results	2	112	November 2, 2015

How to interpret these test results??

Related Topics