Google Web Toolkit

Speed Tracer Hints

Speed Tracer analyzes your application and reports hints when it finds a potential performance problems that can degrade the user experience. Each hint is generated by a JavaScript rule definition and is flagged with one of three priority values, which depend on the severity of the issue.

Informational
Warning
Critical

Built in Rules

Long Duration Event

hintlet_long_duration.js
A top level event blocked the browser UI for an excessive amount of time.
(INFO) Event took 100 milliseconds or longer.
(WARNING) Event took 2 seconds or longer.

Excessive Layout

hintlet_excessive_layout.js
Frequent layout is adding up to a non-trivial amount of time.
(WARNING) At least 3 layout sub-events totaling 70 milliseconds or greater.

Total Bytes Downloaded

hintlet_total_bytes.js
A large amount of data was downloaded to load the current page. The thresholds are reset after a page transition.
(INFO) Cumulative download size is 500kB or greater.
(WARNING) Cumulative download size is 1MB or greater.
(CRITICAL) Cumulative download size is 2MB or greater.

Google Web Toolkit (GWT) Detection

hintlet_gwt_detect.js
Warns of inappropriate cache settings for a GWT selection script. The selection script should be served with no-caching enabled so that, when the application is upgraded, stale pages are not served from client side cache.
(CRITICAL) GWT selection script served with no-caching disabled.

Rules from Page Speed

The following rules are derived from the Page Speed tool. Please consult the Page Speed documentation for more information about these recommendations.

Caching rules

hintlet_cache_control.js
These hints have to do with optimizing client side caching.

Compressed Content

hintlet_not_gz.js
Advises you to compress content to save download time.

Cookies

hintlet_static_no_cookie.js
Advises you to serve static data from cookieless domains.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 3.0 License.

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.