-
Notifications
You must be signed in to change notification settings - Fork 76
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add separate about.html and instructions.html (#359)
Move the about section and the newly created instruction section into a standalone html file to simplify the in-page navigation for the runner.
- Loading branch information
1 parent
7b1b81e
commit 9837ccc
Showing
5 changed files
with
149 additions
and
81 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,88 @@ | ||
<!DOCTYPE html> | ||
<html> | ||
<head> | ||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> | ||
<meta name="viewport" content="width=850" /> | ||
<title>Speedometer 3.0 About</title> | ||
<link rel="stylesheet" href="resources/main.css" /> | ||
<link rel="icon" href="resources/favicon.png" /> | ||
</head> | ||
<body> | ||
<main> | ||
<section id="about" class="visible" data-title="About"> | ||
<a href="./" class="logo"> | ||
<img srcset="resources/[email protected] 2x" src="resources/logo.png" alt="Speedometer" /> | ||
<div class="version">3.0</div> | ||
</a> | ||
<div class="section-grid"> | ||
<h1 class="section-header">About Speedometer 3</h1> | ||
<div class="section-content"> | ||
<p>Speedometer 3 is a benchmark for web browsers that measures Web application responsiveness by timing simulated user interactions on various workloads.</p> | ||
<p> | ||
The following high level user journeys are implemented in the current version. Each of these journeys has one or more workloads which test important aspects of it - for example commonly used patterns, frameworks, or | ||
technologies. | ||
</p> | ||
<ul> | ||
<li>Working with a todo list</li> | ||
<ul> | ||
<li>Measures the time to add, complete, and remove 100 todo items in a basic list.</li> | ||
<li>Each example implements the same todo application (TodoMVC) using different techniques and frameworks.</li> | ||
<li> | ||
Workloads: <a href="resources/todomvc/vanilla-examples/javascript-es5/readme.md" target="_blank">TodoMVC-JavaScript-ES5</a>, | ||
<a href="resources/todomvc/vanilla-examples/javascript-web-components/readme.md" target="_blank">TodoMVC-WebComponents</a>, | ||
<a href="resources/todomvc/architecture-examples/react-complex/readme.md" target="_blank">TodoMVC-React-Complex-DOM</a>, | ||
<a href="resources/todomvc/architecture-examples/backbone/readme.md" target="_blank">TodoMVC-Backbone</a>, <a href="resources/todomvc/architecture-examples/angular/readme.md" target="_blank">TodoMVC-Angular</a>, | ||
<a href="resources/todomvc/architecture-examples/vue/readme.md" target="_blank">TodoMVC-Vue</a>, <a href="resources/todomvc/architecture-examples/jquery/readme.md" target="_blank">TodoMVC-jQuery</a>, | ||
<a href="resources/todomvc/architecture-examples/preact/readme.md" target="_blank">TodoMVC-Preact</a>, <a href="resources/todomvc/architecture-examples/svelte/readme.md" target="_blank">TodoMVC-Svelte</a>, | ||
<a href="resources/todomvc/architecture-examples/lit/readme.md" target="_blank">TodoMVC-Lit</a> | ||
</li> | ||
</ul> | ||
<li>Editing rich text</li> | ||
<ul> | ||
<li>Loading and styling text inside WYSIWYG and code editors.</li> | ||
<li>Workloads: <a href="resources/editors/readme.md" target="_blank">Editor-CodeMirror</a>, <a href="resources/editors/readme.md" target="_blank">Editor-TipTap</a></li> | ||
</ul> | ||
<li>Rendering charts</li> | ||
<ul> | ||
<li>Loading and interacting with SVG and canvas charts.</li> | ||
<li> | ||
Workloads: <a href="resources/charts/readme.md" target="_blank">Charts-observable-plot</a>, <a href="resources/charts/readme.md" target="_blank">Charts-chartjs</a>, | ||
<a href="resources/react-stockcharts/readme.md" target="_blank">React-Stockcharts-SVG</a>, <a href="resources/perf.webkit.org/readme.md" target="_blank">Perf-Dashboard</a> | ||
</li> | ||
</ul> | ||
<li>Reading a news site</li> | ||
<ul> | ||
<li>Navigating across pages and interacting with a typical looking news site.</li> | ||
<li>Workloads: <a href="resources/newssite/news-next/readme.md" target="_blank">NewsSite-Next</a>, <a href="resources/newssite/news-nuxt/readme.md" target="_blank">NewsSite-Nuxt</a></li> | ||
</ul> | ||
</ul> | ||
|
||
<p class="note"><strong>Notes about methodology</strong></p> | ||
<ul> | ||
<li>Although user-driven actions like mouse movements and keyboard input cannot be fully emulated in JavaScript, Speedometer does its best to faithfully replay a typical workload within the demo applications.</li> | ||
<li>To make the run time long enough to measure with the limited precision, we synchronously execute a large number of the operations, such as adding one hundred to-do items.</li> | ||
<li> | ||
Modern browser engines execute some work asynchronously as an optimization strategy to reduce the run time of synchronous operations. While returning control back to JavaScript execution as soon as possible is worth | ||
pursuing, the run time cost of such an asynchronous work should still be taken into a holistic measurement of web application performance. In addition, some JavaScript frameworks call into DOM APIs asynchronously as an | ||
optimization technique. Speedometer approximates the run time of this asynchronous work in the UI thread with a zero-second timer that is scheduled immediately after each execution of synchronous operations. | ||
</li> | ||
<li>Speedometer does not attempt to measure concurrent asynchronous work (e.g. in Web Workers).</li> | ||
<li>Speedometer should not be used as a way to compare the performance of different JavaScript frameworks.</li> | ||
<li> | ||
The goal of all workloads is to represent a scenario that could be found on the Web. Although all workloads strive to use patterns that are commonly used, some implementation details are Speedometer specific and should | ||
not be used as a guideline on how to implement and deploy a standalone app. For example, due to constraints within the test harness, workloads must not depend on a server infrastructure to function properly and are | ||
built as static files ahead of time. | ||
</li> | ||
</ul> | ||
</div> | ||
<div class="buttons section-footer"> | ||
<div class="button-row"> | ||
<a class="button" href="./" title="Show main section.">Home</a> | ||
<a class="button" href="instructions.html" title="Show test instructions.">Test Instructions</a> | ||
</div> | ||
</div> | ||
</div> | ||
</section> | ||
</main> | ||
</body> | ||
</html> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -29,7 +29,8 @@ | |
<button class="start-tests-button">Start Test</button> | ||
</div> | ||
<div class="button-row"> | ||
<a href="#about">About Speedometer</a> | ||
<a href="about.html">About Speedometer</a> | ||
<a href="instructions.html">Test Instructions</a> | ||
</div> | ||
</div> | ||
</section> | ||
|
@@ -100,80 +101,6 @@ <h2>Detailed Metrics</h2> | |
</div> | ||
</div> | ||
</section> | ||
|
||
<section id="about" data-title="About"> | ||
<a href="#home" class="logo"> | ||
<img srcset="resources/[email protected] 2x" src="resources/logo.png" alt="Speedometer" /> | ||
<div class="version">3.0</div> | ||
</a> | ||
<div class="section-grid"> | ||
<h1 class="section-header">About Speedometer 3</h1> | ||
<div class="section-content"> | ||
<p>Speedometer 3 is a benchmark for web browsers that measures Web application responsiveness by timing simulated user interactions on various workloads.</p> | ||
<p> | ||
The following high level user journeys are implemented in the current version. Each of these journeys has one or more workloads which test important aspects of it - for example commonly used patterns, frameworks, or | ||
technologies. | ||
</p> | ||
<ul> | ||
<li>Working with a todo list</li> | ||
<ul> | ||
<li>Measures the time to add, complete, and remove 100 todo items in a basic list.</li> | ||
<li>Each example implements the same todo application (TodoMVC) using different techniques and frameworks.</li> | ||
<li> | ||
Workloads: <a href="resources/todomvc/vanilla-examples/javascript-es5/readme.md" target="_blank">TodoMVC-JavaScript-ES5</a>, | ||
<a href="resources/todomvc/vanilla-examples/javascript-web-components/readme.md" target="_blank">TodoMVC-WebComponents</a>, | ||
<a href="resources/todomvc/architecture-examples/react-complex/readme.md" target="_blank">TodoMVC-React-Complex-DOM</a>, | ||
<a href="resources/todomvc/architecture-examples/backbone/readme.md" target="_blank">TodoMVC-Backbone</a>, <a href="resources/todomvc/architecture-examples/angular/readme.md" target="_blank">TodoMVC-Angular</a>, | ||
<a href="resources/todomvc/architecture-examples/vue/readme.md" target="_blank">TodoMVC-Vue</a>, <a href="resources/todomvc/architecture-examples/jquery/readme.md" target="_blank">TodoMVC-jQuery</a>, | ||
<a href="resources/todomvc/architecture-examples/preact/readme.md" target="_blank">TodoMVC-Preact</a>, <a href="resources/todomvc/architecture-examples/svelte/readme.md" target="_blank">TodoMVC-Svelte</a>, | ||
<a href="resources/todomvc/architecture-examples/lit/readme.md" target="_blank">TodoMVC-Lit</a> | ||
</li> | ||
</ul> | ||
<li>Editing rich text</li> | ||
<ul> | ||
<li>Loading and styling text inside WYSIWYG and code editors.</li> | ||
<li>Workloads: <a href="resources/editors/readme.md" target="_blank">Editor-CodeMirror</a>, <a href="resources/editors/readme.md" target="_blank">Editor-TipTap</a></li> | ||
</ul> | ||
<li>Rendering charts</li> | ||
<ul> | ||
<li>Loading and interacting with SVG and canvas charts.</li> | ||
<li> | ||
Workloads: <a href="resources/charts/readme.md" target="_blank">Charts-observable-plot</a>, <a href="resources/charts/readme.md" target="_blank">Charts-chartjs</a>, | ||
<a href="resources/react-stockcharts/readme.md" target="_blank">React-Stockcharts-SVG</a>, <a href="resources/perf.webkit.org/readme.md" target="_blank">Perf-Dashboard</a> | ||
</li> | ||
</ul> | ||
<li>Reading a news site</li> | ||
<ul> | ||
<li>Navigating across pages and interacting with a typical looking news site.</li> | ||
<li>Workloads: <a href="resources/newssite/news-next/readme.md" target="_blank">NewsSite-Next</a>, <a href="resources/newssite/news-nuxt/readme.md" target="_blank">NewsSite-Nuxt</a></li> | ||
</ul> | ||
</ul> | ||
|
||
<p class="note"><strong>Notes about methodology</strong></p> | ||
<ul> | ||
<li>Although user-driven actions like mouse movements and keyboard input cannot be fully emulated in JavaScript, Speedometer does its best to faithfully replay a typical workload within the demo applications.</li> | ||
<li>To make the run time long enough to measure with the limited precision, we synchronously execute a large number of the operations, such as adding one hundred to-do items.</li> | ||
<li> | ||
Modern browser engines execute some work asynchronously as an optimization strategy to reduce the run time of synchronous operations. While returning control back to JavaScript execution as soon as possible is worth | ||
pursuing, the run time cost of such an asynchronous work should still be taken into a holistic measurement of web application performance. In addition, some JavaScript frameworks call into DOM APIs asynchronously as an | ||
optimization technique. Speedometer approximates the run time of this asynchronous work in the UI thread with a zero-second timer that is scheduled immediately after each execution of synchronous operations. | ||
</li> | ||
<li>Speedometer does not attempt to measure concurrent asynchronous work (e.g. in Web Workers).</li> | ||
<li>Speedometer should not be used as a way to compare the performance of different JavaScript frameworks.</li> | ||
<li> | ||
The goal of all workloads is to represent a scenario that could be found on the Web. Although all workloads strive to use patterns that are commonly used, some implementation details are Speedometer specific and should | ||
not be used as a guideline on how to implement and deploy a standalone app. For example, due to constraints within the test harness, workloads must not depend on a server infrastructure to function properly and are | ||
built as static files ahead of time. | ||
</li> | ||
</ul> | ||
</div> | ||
<div class="buttons section-footer"> | ||
<div class="button-row"> | ||
<a class="button" href="#home" title="Show main section.">Home</a> | ||
</div> | ||
</div> | ||
</div> | ||
</section> | ||
</main> | ||
</body> | ||
</html> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
<!DOCTYPE html> | ||
<html> | ||
<head> | ||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> | ||
<meta name="viewport" content="width=850" /> | ||
<title>Speedometer 3.0 Test Instructions</title> | ||
<link rel="stylesheet" href="resources/main.css" /> | ||
<link rel="icon" href="resources/favicon.png" /> | ||
</head> | ||
<body> | ||
<main> | ||
<section id="instructions" class="visible" data-title="Test Instructions"> | ||
<a href="./" class="logo"> | ||
<img srcset="resources/[email protected] 2x" src="resources/logo.png" alt="Speedometer" /> | ||
<div class="version">3.0</div> | ||
</a> | ||
<div class="section-grid"> | ||
<h1 class="section-header">Speedometer 3 Test Instructions</h1> | ||
<div class="section-content"> | ||
<h2>General Instructions</h2> | ||
<ol> | ||
<li>Before running Speedometer:</li> | ||
<ul> | ||
<li>Close all other applications.</li> | ||
<li>Close other browser windows and tabs.</li> | ||
<li>Use a fresh browser profile and a single window.</li> | ||
</ul> | ||
<li>While running Speedometer:</li> | ||
<ul> | ||
<li>Keep the browser window in the foreground.</li> | ||
<li>Do not use any other applications while Speedometer runs.</li> | ||
</ul> | ||
</ol> | ||
|
||
<!-- TODO: fill in detailed instructions | ||
<h2>Detailed browser-specific instructions</h2> | ||
<h3>Chrome</h3> | ||
<h3>Edge</h3> | ||
<h3>Firefox</h3> | ||
<h3>Safari</h3> | ||
--></div> | ||
<div class="buttons section-footer"> | ||
<div class="button-row"> | ||
<a class="button" href="./" title="Show main section.">Home</a> | ||
<a class="button" href="about.html" title="Show about section.">About</a> | ||
</div> | ||
</div> | ||
</div> | ||
</section> | ||
</main> | ||
</body> | ||
</html> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters