FREE Website Monitoring & Monitoring Software from Monitor.Us Here's what our monitoring tools can do for IT Consultants, ISPs, ISVs, Web Developers and Web Designers Imagine how much you could grow your business if you weren't chained to your desk. Monitor.Us makes this possible. Because Monitor.Us is Cloud-based it not only lets you keep an eagle eye on everything, from anywhere; it also takes complex set-ups, installs, updates, reinstalls and server monitoring... and drops them from a very large height. And, here's what our monitoring tools can do for Sys Admins, DevOps, and IT Managers Monitor.Us system and all-in-one dashboard gives you such unrivalled insight that you can get a sense that something's wrong before it even happens. Oh, and because we're Cloud-based, you can be doing your super-sensing 24/7/365 and you can be doing it from anywhere - home, office or at 3,000 feet!
The DOM isn’t slow, you are. | Wat, blogged Edited post-HN: Wow, big response! WARNING: May contain traces of opinion, and naughty words like ‘shit’ and ‘internet explorer’. Use jQuery for what it is meant for, not everything.If you do stupid shit with the DOM, it will perform poorly.If your web-app is slow, it’s because of your code, not the DOM. Whenever the native versus web argument arises, the biggest issue people usually have with web is performance. They quote figures like ‘60fps‘ and ‘scroll speed’, and, back when browsers were just getting good, i would say “OK, there’s work to be done, but they will get there”, which was met with anything from “Yeah maybe” to “No it will never happen!”. Really? But really, this point is redundant anyway, because when you get down to it, even C is an abstraction on assembly, and if you are an Android developer, you’re coding against Dalvik… which is just as much of an abstraction as JavaScript is anyway! But again, this isn’t the topic of the post. On filter change: I blame jQuery. What now?
Research | Projects | Page Detailer Page Detailer provides instrumentation and visualization of the performance of web page downloads, showing decomposition of the web page into its component parts (e.g., HTML, GIFs, Applets) and the activities involved in retrieving them. By understanding the retrieval schedule for Web page components, page designers can dramatically improve performance by reorganizing content. By decomposing response time, site architects can understand how to tune their servers and/or configure their applications to provide optimum performance. Page Detailer relies heavily on IBM Research's patented Web Detailer (aka ETE: End-to-End performance monitoring, US#06108700) technology developed in Hawthorne to provide instrumentation of browsers and other HTTP-based applications and to correlate discrete events into a hierarchy of timelines. To view PDF version click here
Accelerated Rendering in Chrome: The Layer Model Introduction For most web developers the fundamental model of a web page is the DOM. Rendering is the often obscure process of turning this representation of a page into a picture on the screen. Modern browsers have changed the way rendering works in recent years to take advantage of graphics cards: this is often vaguely referred to as “hardware acceleration”. Big, Fatty Caveats We’re talking about WebKit here, and more specifically we’re talking about the Chromium port of WebKit. Also, note that this entire article is discussing a core piece of Chrome’s rendering architecture that’s changing very fast. It’s important to understand that Chrome has had two different rendering paths for a while now: the hardware-accelerated path and the older software path. Lastly, we’re peeking under the hood of the rendering engine and looking at features of it that have a big impact on performance. From the DOM to the Screen Introducing Layers Quick aside on GPU terminology: what’s a texture? Invalid!
Pylot | Open Source Web Performance Tool The Browsers Performance in Dependence of HTML Coding Everyday dealing with creating and animating web sites I began to notice a very unpleasant peculiarity — one at the same JavaScript code works with the different speed on different sites. The cause of such strange behavior was found very promptly: speed of a script execution depended directly on the way the site was HTML coded. Searching of solutions of the arised problems was quite exciting but unfortunately I couldn't share the results of my investigations because of the local character of all the solutions. For example a certain site was working slowly but it was enough to change one construction to another for it to work twice quicker. Getting such an explanation the only thing a reader can do is to be happy for me as there is very little practical benefit from the offered solutions. This fact became the first reason of my researching of the up-to-date browsers general problem places. The second reason is buzz around a new versions of browsers. Let's look at an example. Results
Wbox HTTP testing tool HTTP testing tool Wbox aims to help you having fun while testing HTTP related stuff. You can use it to perform many tasks, including the following. Benchmarking how much time it takes to generate content for your web application.Web server and web application stressing.Testing virtual domains configuration without the need to alter your local resolver.Check if your redirects are working correctly emitting the right HTTP code.Test if the HTTP compression is working and if it is actually serving pages faster.Use it as a configuration-less HTTP server to share files! Download 10 Dec 2009 - wbox version 5 is out. Don't miss the next release, use the In order to compile wbox you need a working ANSI C compiler and a POSIX system like Linux. Windows binaries If you want to use WBox under Windows but don't know how to compile it you can download this precompiled binary of Wbox version 3 for Windows (Thanks to Zaim Bakar). HTTP client mode The following is a short tutorial. Basic usage Dumping data
Performance of jQuery selector with context SiteTimer About SiteTimer Web Monitor allows you to monitor how long it takes for a user to download one or more of your web site pages. It visits the page that your request and downloads all content that's directly linked from that page; Images Frames IFrames Script files It follows redirects As the pages are downloaded, SiteTimer stores statistics on how long time each item takes to download, and how much data they contained. Web Monitor correctly handles http compressed material (see OctaGate Switch), and it also honors keep-alive requests to give an accurate indication of the times a real browser would spend downloading the content. Optimizing your site Your page shouldn't take too long to load, slow load speeds will lead to users leaving your pages even though they're interested in the material. The size of the page is the main deciding factor for download times, coupled with bandwidth. Decrease the size of your images: Use JPG instead of GIF or BMP. Reasons for slow load speeds
Bitwise Gems and other optimizations One of my favorite posts in the last few years was Bitwise Gems in AS3 by Polygonal Labs, an article inspired by Bitwise Operations in C on Gamedev. This article is a summery of what I’ve learned, applied to Javascript, plus a few other tricks. What’s the wisdom in using bitwise? Bitwise operations can be moderately faster than conventional methods. When processing a lot of data, even a 5% increase in speed can become noticeable. Standard operation on the (left) === (right) is bitwise or an alternative method such as replacing Math.max(a, b) with (a > b ? Minimize calls to new Object() and new Array();+/- 50% faster using flat-variables, not bitwise, but still wise. [2-23-2012] Updated as per Closure Compiler group discussion.Rounding, flooring, and ceiling with bit-shifting;+/- 20% faster using bitwise operations. Or, if you’re certain the number will be positive (for example dealing with pixel values): Fast modulo operation using bitwise AND (&);+/- 15% faster using bitwise operations.
Web Page Analyzer - free website optimization tool website speed test check website performance report from web site optimization Free Website Performance Tool and Web Page Speed Analysis Try our free web site speed test to improve website performance. Enter a URL below to calculate page size, composition, and download time. The script calculates the size of individual elements and sums up each type of web page component. Help Speed Up the Web Tired of waiting for slow web sites? <a href=" Page Analyzer</a> - Free web page analysis tool calculates page size, composition, and download time. Consider optimizing your site - with our Website Optimization Secrets book, contacting us about our optimization services, or our Speed Tweak tutorials. Related Website Optimization Services Try our targeted services to optimize your web site's ROI. Version History See the version history for all revisions.
Optimizing your JavaScript game for Firefox OS When developing on a quad core processor with 16 gigabytes of RAM you can easily forget to consider how it will perform on a mobile device. This article will detail some best practices and things to consider for moving a game to Firefox OS or any similar hardware target. Making the best of 256 Mb RAM/800 Mhz CPU There are many areas of focus to keep in mind while developing a game. Don’t over-optimize This might sound counter-intuitive in an article about game optimization but optimization is the last step; performed on complete, working code. Optimize Drawing Drawing on HTML5 2D canvas is the biggest bottleneck in most JavaScript games, as all other updates are usually just algebra without touching the DOM. Use whole-pixel rendering Sub-pixel rendering occurs when you render objects on a canvas without whole values. This causes the browser to do extra calculations to create the anti-aliasing effect. jsPerf – drawImage whole pixels. Cache drawing in an offscreen canvas or