Your Github respository is not a fork of www-sugarlabs repository; whyis that? Was there some advantage in making a new repository?

Are you still planning to target the laptops that run Sugar? I askbecause your design has gone backwards two orders of magnitude interms of performance and load time. Your design on 14th March was 6MBover 35 requests from one domain, but your design now is 12MB over153 requests across many domains.

Without a test harness for evaluating the impact of each change, andcontinuous integration, my guess is that you've allowed changes thatwill make it even harder for you to target the laptops that run Sugar.

So I do not think it will be possible for you to target the laptopsthat run Sugar, and it will be best to have the Browse activity inSugar not link directly to the main page. If you agree, please make asubpage for use by Browse and make a pull request against Browse, filedata/index.html which we can hold until the site goes live.

On the other hand, if you would like to target the laptops that arerunning Sugar now, you might do these things;

- install a Fedora 18 virtual machine and use the Epiphany webbrowser, which is based on WebKit,

- install an Ubuntu 16.04 virtual machine and use the Epiphany webbrowser, which is based on WebKit2,

- use the virtual machine configuration to restrict the resourcesavailable; such as the VirtualBox Settings System -> Processor ->Execution Cap value,

- use a virtual machine API to record CPU usage during tests,

- set up continuous integration test harness that will wait for agit commit, load the page in fresh browser, and measure CPU timeused.