Page MenuHomePhabricator

Improving page load
Closed, ResolvedPublic

Description

Hello,

When editing a page, it seems that the image is loaded 3 times: first when reading the page, second when editing it, third when displaying after editing.
This renders editing very difficult unless on a very fast connection.
I think that improving page load is a priority for increasing the numbers of edits.


Version: unspecified
Severity: enhancement

Details

Reference
bz24149

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 11:05 PM
bzimport added a project: ProofreadPage.
bzimport set Reference to bz24149.

Bug in MediaWiki itself, not in ProofreadPage.

What is being requested here? That we don't load the page three times like you describe? That those 3 loads be faster? Please provide a concrete suggestion for improvement.

thomasV1 wrote:

The image shown when a page is read is a reduced size version. This is why a new image is loaded during proofreading; if it was the same image, then your browser would use its cache. And when the image is displayed after editing, the image is supposed to be in your cache, so there shoud be no third download.

Part of the perceived slowness comes from the fact that you cannot edit a page until the full image is loaded. This bug was caused by the last code update ; I have fixed it two months ago, but the code has not been deployed yet (see r65014).

Maybe we should keep this bug open until the fix goes live.

(In reply to comment #2)

The image shown when a page is read is a reduced size version. This is why a
new image is loaded during proofreading; if it was the same image, then your
browser would use its cache. And when the image is displayed after editing, the
image is supposed to be in your cache, so there shoud be no third download.

Part of the perceived slowness comes from the fact that you cannot edit a page
until the full image is loaded. This bug was caused by the last code update ; I
have fixed it two months ago, but the code has not been deployed yet (see
r65014).

Maybe we should keep this bug open until the fix goes live.

We generally close bugs in such cases. Putting this back into the ProofReadPage component and closing as FIXED.