FAQs
Runtime Page Optimizer FAQs
- What is the Runtime Page Optimizer?
-
The Runtime Page Optimiser (RPO) is a server component that reduces the page load time for web browsers
accessing website pages on the server. It works by automatically processing the HTML page just before it
is sent to the client and combining similar resource files, reducing the number of requests to render a
page. This approach significantly improves the performance of the website.
Back to top
- Where did the Runtime Page Optimizer come from?
-
RPO has been developed by ActionThis to enable the company to deliver a highly responsive web application –
located at www.actionthis.com – to a global
market from New Zealand. The team behind ActionThis recognized that for a web application, fast performance is
the key to success, and has decided to commercialize its investment so that other companies can benefit.
Back to top
- What types of web servers are supported in this beta release?
-
The current version supports ASP.NET 2.0, with Microsoft Internet Information Services (IIS) version 6 and 7.
Back to top
- What browsers are supported in this beta release?
-
This beta release will support Microsoft Internet Explorer 6 and 7, Mozilla Firefox 2 and 3 and Apple Safari 3.
All other browsers will simply receive the original site content.
Back to top
- How can I tell if installing the Runtime Page Optimizer works?
-
We provide a checklist of things to check within the ReadMe file which accompanies the beta version of the
Runtime Page Optimizer software.
Back to top
- How come this technique works so well?
-
We tried a number of optimisation techniques when developing actionthis.com, and found that reducing requests
has the most dramatic effect on performance. Part of the reason is because many browsers load CSS files and JS
files sequentially rather than in parallel amplifying any latency effect.
Back to top
- How does this work with images?
-
We automatically “tile” images – assemble many small images into a single large mosaic image then refer to
this single image on the client. This technique is also known as creating CSS sprites.
Back to top
- Can’t I manually combine scripts and CSS files myself?
-
Yes, it is possible to combine scripts manually, and rework them anytime you change the site. Most people
haven’t got the patience; and prefer to leave source assets in the best structure for reuse and
maintainability.
Back to top
- Don’t client web browsers cache CSS and JS files already?
-
Client web browsers cache images and scripts locally, but often make requests to the server to check the
version in cache. The combined resources work more effectively than client-side caching – everything is
versioned, and automatically updated when the site changes.
Back to top
- Is the Runtime Page Optimizer difficult to install?
-
The install is low impact – copying a DLL and modifying a configuration file. In most cases, no other changes
to pages or the site need to be made.
Back to top
- Is the Runtime Page Optimizer protected by patents?
-
Yes – there is a significant amount of intellectual property utilized in the Runtime Page Optimizer, and we
have registered patents where necessary.
Back to top
- When will the Runtime Page Optimizer be released?
-
When you sign up now, you will be provided access to the beta release of the Runtime Page Optimizer. We have
an aggressive schedule in place, targeting a beta release in the next 4-6 weeks. This release will comprise a
number of additional features, including additional web browser support. Release of the 1.0 version will
follow the successful completion of the beta program.
Back to top
- What is the cost of the RPO?
-
Pricing is currently being confirmed. Contact us for details.
Back to top
