Closed Bug 1583521 Opened 5 months ago Closed 5 months ago

[Translate.Next] Compare performance view current Translate app

Categories

(Webtools :: Pontoon, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: adrian, Assigned: adrian)

Details

(Whiteboard: tn-release)

It is important to know how our new Translate.Next app compares to the current one in terms of performance. We do not want to ship a degraded experience to our users.

This bug covers collecting basic web performance data about Translate.Current and Translate.Next, and comparing that data, then using that to drive decisions on things to improve, if any.

Here's a first, basic test using webpagetest.org, running on Firefox Desktop from the USA.

Translate Current

Full report: https://www.webpagetest.org/result/190924_JQ_ecc07edee2514e77327a3c4955d02038/

Translate Next

Full report: https://www.webpagetest.org/result/190924_Y3_c4af9e06acdff24bcca517fe24e854ce/

Comparison

Measure Current Next
Load Time 2.407s 2.618s
First Byte 0.684s 0.334s
Start Render 1.100s 0.700s
Full Loading Time 3.563s 3.560s
Total Bytes 784 KB 897 KB
Total Requests 35 31

Analysis

Quick analysis based on this simple test: overall performance don't seem to change much. Next is a bit slower to load overall, but starts rendering much earlier (as is expected, since the rendering happens on the client side). Byte size goes up a little, and we might want to look into that and make the JS bundles smaller.

This is a pretty reassuring test as it shows that there is nothing to be concerned about in the major data points: time to load, requests and bytes for Translate.Next are all within acceptable range from Current.

I'll still perform more advanced testing later on.

Status: NEW → ASSIGNED
Whiteboard: tn-release

I'm actually going to be satisfied with just this result. We will conduct more analysis performance later on, and make optimizations as we go. The new translate page is fast enough compared to the old one.

Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.