The same happens in Firefox, and it's definitely the page author's responsibility.
This is the page code that scrolls the window incorrectly:

    window.scrollTo(this._scrollPosition.x, this._scrollPosition.y);

You can use a userscript to fix the site bug:
1. install Tampermonkey
   https://chrome.google.com/webstore/detail/tampermonkey/dhdgffkkebhmkfjojejmpbldmpobfkfo
2. click the Tampermonkey icon
   click Dashboard
   click the icon to the left of "Installed userscripts"
3. paste the following code and save it (Ctrl-S key or the toolbar icon)

// ==UserScript==
// @name     Block programmatic scrolling
// @match    http://www.pulifourswim.tw/*
// @license  MIT License
// @run-at   document-start
// @grant    none
// ==/UserScript==
window.scrollTo = null;

Thanks but I have a radical new idea:
We are all familiar with
https://en.wikipedia.org/wiki/Software_flow_control
when we are using a terminal.
Well it would be a step backwards if something similar is not available
in the browser.
In the browser one has ESC, that stops loading.
But one also usually wants to stop all the other singing and dancing
happening on a page too. To allow the user to just scroll around without
having to fight a page, just like when one does CTRL+S and then types
SHIFT+PgUp SHIFT+PgDown in e.g., xterm, before letting things resume
with CTRL+Q.
In our analogy with a terminal, one would have to reload the page to get
things going again.
So therefore a new functionality is required: freeze page / thaw page.
This is more that just a javascript on/off toggle. It would toggle all active
rendering operations, movies playing, etc. on a page.

Anyway, the user, without needing to install anything extra, should be able to freeze all singing and dancing on a page, without needing to throw his hands up and hit CTRL+W.

Able to reproduce the issue using #59.0.3071.115 on Mac 10.12.5, Win 10, Linux Ubuntu 14.04 as well. Observed the jerking behavior on page scrolling.

Observing the same behavior since M45. Hence considering this issue as Non-Regression issue and untriaging to get input's from dev.

Note:
1. Same behavior is seen in M61 as well.
2. Removing Bisect label as this is a Non-Regression issue.
3. Same behavior is seen in Firefox and Safari as well.

Thanks!!

I doubt there are more than 0.001% of Chrome users who need to freeze/thaw pages. Firefox users may need it a lot more though as FF is often used by those who can't live without the rare advanced features.

As for a realistic solution, many browsers have a reader mode to fight incorrectly designed/programmed pages such as the reported one. It'd be nice if Chrome would follow the suit by exposing a reader mode button in the address bar. 

I'm not sure if there's anything Chrome would want to do here, but passing off to the scrolling team to decide.

No longer reproduces in Chrome 63.0.3239.84. Closing.