Tag Info

Hot answers tagged

51

The short answer is "Because HTTP wasn't designed for it". Tim Berners-Lee did not design an efficient and extensible network protocol. His one design goal was simplicity. (The professor of my networking class in college said that he should have left the job to the professionals.) The problem that you outline is just one of the many problems with the ...


31

Yes, there is almost no reason I can think of to not use GZIP at all times. It's like getting free bandwidth, and it is universally supported. Always have it on! The only possible downsides are If you are on a shared host with very limited CPU resources, as the compression is done on the server and it does take a tiny bit of server CPU. The server would ...


30

Document.ready waits for the DOM to load before running any JavaScript (http://www.learningjquery.com/2006/09/introducing-document-ready). The idea of putting it at the bottom, means that if your JS is having issues or the person has a slow connection, the rest of the page still loads first, and doesn't "hang". The JS still runs when everything has loaded, ...


25

There are 4 things you can do. Minify your JS File. This removes all comments and Whitespace to reduce its size. Combine your JS Files on each page so that there is only 1 file. Use a package to gzip your files when you send them. This will make them even smaller Put Javascript that isn't required immediately at the bottom of the page so that it loads at ...


23

It's built in. Page [paper] -> Developer -> Developer tools (in Chrome v5 and under). It is likely to be different in v6 since the Page button appears to be disappearing in that version.


21

FireFox Throttle is a FireFox extension that should do it. Sloppy is a proxy which slows down your connection so it should work across browsers. Source: http://www.devcurry.com/2010/07/simulate-slow-internet-connections.html MODERATOR EDIT 2013-02-02 This extension is no longer available.


21

Fiddler Web Debugger is an excellent HTTP proxy debugging tool for Windows that includes a modem speed simulation feature (Main menu > Rules > Performance > simulate modem speed). Fiddler is freeware. I also like Charles Web Debugging Proxy, a similar tool. Charles can also throttle the connection speed. Charles is commercial software, but has a free ...


21

If you are using common libraries (such as jQuery, Prototype or Dojo), you can offload the file to Google and make them serve it, this gives you several advantages: You don't have to worry about minifying and zipping etc It's not your bandwidth These files come from a different domain, so you can (at least partially) workaround the limit of 2 parallel ...


19

Try out http://www.webpagetest.org/test. You can run a test from any of their remote servers around the world and see how fast you page loads from those location. It will even let you use a dial-up speed or other slow speeds for most locations.


19

Google wants to provide its user base with the best experience possible when browsing the web - this is what retains their customers. A poor page load speed can have a serious effect on user experience, that is arguably the main reason Google sometimes ranks these sites less favorably. It is also an indication that the site isn't perhaps maintained to a ...


18

Someone is going to say that the markup should be Gzipped, so I might as well be the one. Here's a lengthy explanation of what Gzip is with links on how to set it up on Apache and IIS. An article on WebReference states that you'll find the following performance gains when using the mod_gzip Apache module. Webmasters typically see a 150-160% increase ...


17

#BestQuestionEver =) I'm the developer of the site so I should be able to answer most of these questions You brought up some interesting points. In terms of backend (Backend is rarely the source of bottle-necks in page loading, it's mostly loading but it's still worth going over the tech), the site runs on 2 dedicated servers from LiquidWeb (Both with ...


17

Per the official guidance http://www.google.com/support/webmasters/bin/answer.py?answer=158541 Site Performance is an experimental Webmaster Tools Labs feature that shows you latency information about your site. (To see Site Performance data, you must add and verify your site in Webmaster Tools.) Page load time is the total time from the moment ...


16

Yahoo's tips for improving page sped Google's tips for improving page speed If you're using PHP, Google's tips for making PHP faster Here's a basic list as comprised from Google's Page Speed addon (here's Yahoo's YSlow): Leverage browser caching Specify image dimensions Avoid CSS @import Avoid bad requests Combine images into CSS sprites ...


15

Right-Click -> Inspect Element


14

There are a few things you can do: Load the HTML and CSS before the javascript. This gives the browser everything it needs to lay out the page and render it. This gives the user the impression that the page is snappy. Place script tags or blocks as close to the closing body tag as possible. Consider using a CDN. If you are using any of the popular ...


12

Firebug Lite for Google Chrome.


12

Yes. 120KB for HTML alone(!) can be compressed greatly. Together with the CSS and JavaScript files. This will speed up the browsing experience for your users and save you bandwidth on your server. You could implement the compression using your server-side script and cache the compressed files, thus easing the pressure on the CPU on busy servers.


11

Jakob Nielsen has an excellent article, Website Response Times (June 21, 2010) in which he explains why website response times still matter. 0.1 seconds gives the feeling of instantaneous response — that is, the outcome feels like it was caused by the user, not the computer. This level of responsiveness is essential to support the feeling of direct ...


11

The Net tab of the Firebug console (remember to disable browser cache). Resources view of the Web Developer Tools in Chrome/Opera. Fiddler. HTTP Watch. WebPageTest. Gomez. We use WebPageTest and Gomez for server tuning, Fiddler if there are any hard to diagnose problems, then the rest for front-end experience testing. Once you have the level of ...


11

Your best solution is probably http://www.coralcdn.org or using Google's App Engine. It also depends on how much content you think will be downloaded from your site. I know Amazon Cloud Front isn't free but it does only cost $.12 per GB per month in the US. See pricing here, http://aws.amazon.com/cloudfront/#pricing.


10

It probably isn't worth it. I've played with removing whitespace in HTML a little bit, and saw only a 10% size reduction in payload after gzipping. Realistically, whitespace and linefeed removal is doing work that the compression would be doing for us. We're just adding a dab of human-assisted efficiency: Raw Compressed ...


10

It doesn't have to be unique. But if it's not it makes your life more difficult. Having a unique username means there is only one possible password for that username. If it's wrong, you don't have to go looking for another user with the same username to compare it to. It's gets really complicated when someone requests a missing password. How do you know who ...


10

CloudFlare, in most cases, does not cache HTML. This is because we don't want to show stale dynamic content. That said, the system can help the performance of even dynamic content in four primary ways: CloudFlare can route traffic over preferred network routes that are often more efficient than what a request would normally take. For sites that get a lot ...


10

WordPress is likely not the issue. It can easily handle that much traffic (1,000,000 visits a month is less than one every two seconds) and that many posts. You need to figure out what's actually causing slowdowns. It might be your host, your database, a misconfiguration, a bad plugin, etc.


10

Like the others said, Wordpress can handle this amount of traffic just fine. I would suggest one of the two caching plugins. These plugins write database-heavy pages to disk, which saves load on the database server. The difference is remarkable. WP Super Cache W3 Total Cache Both are well-maintained, the latter has more features, but can be intimidating. ...


10

There's a great tool at http://www.webpagetest.org/ which allows you to measure the loading speed of a site. You can choose from a list of locations to test from and there are a few in the UK.


10

Google will penalize sites that are very slow (greater than 7-10 seconds for the page to become usable). They do this because they state that users are usually not willing to wait that long when they click and usually return to the serps. Google wants to make their users happy. In addition to the direct penalties applied by Google, there are indirect ...


10

The technical term for waiting is refereed to as time to first byte and determines the responsiveness of a web server or other network resources. Some common reasons you might see an high time to first byte: Overloaded network (normally shared hosting) Misconfiguration servers Distance from you and the server (geo location plays a minor role) Server ...


10

Because they do not know what those resources are. The assets a web page requires are coded into the HTML. Only after a parser determines what those assets are can the y be requested by the user-agent. Additionally, once those assets are known, they need to be served individually so the proper headers (i.e. content-type) can be served so the user-agent ...



Only top voted, non community-wiki answers of a minimum length are eligible