Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Fri, 22 Dec 2017 18:36:01 +0000 (UTC)
From: "Denis Magda (JIRA)" <jira@apache.org>
To: dev@ignite.apache.org
Message-ID: <JIRA.13126871.1513967728000.521467.1513967761018@Atlassian.JIRA>
In-Reply-To: <JIRA.13126871.1513967728000@Atlassian.JIRA>
References: <JIRA.13126871.1513967728000@Atlassian.JIRA> <JIRA.13126871.1513967728299@jira-lw-us.apache.org>
Subject: [jira] [Created] (IGNITE-7292) Optimize Ignite main page load
 performance
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 22 Dec 2017 18:36:05 -0000

Denis Magda created IGNITE-7292:
-----------------------------------

             Summary: Optimize Ignite main page load performance
                 Key: IGNITE-7292
                 URL: https://issues.apache.org/jira/browse/IGNITE-7292
             Project: Ignite
          Issue Type: Task
            Reporter: Denis Magda
            Assignee: Prachi Garg
            Priority: Blocker
             Fix For: 2.4
         Attachments: Screen Shot 2017-12-22 at 9.49.02 AM.png

Ignite main page load performance is poor - takes from 3 to 5 seconds to load in completely. That might affect the SEO optimizations we've done so far. These are immediate actions to alleviate the situation: 
# Reduce banner and all the images size to 72 ppi resolution and save in the JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of screencasts were already changed, just need to regenerate the CSS and merge the patch.
# The next fierce contributors to the poor performance are screencasts youtube video. It takes 700ms for each screencast to make a roundtrip to YouTube. See the screenshot attached where 3 base.js calls are triggered by the video links. This has to be done asynchronously.
# Preload GitHub, Twitter butter and feed asynchronously too.

The overall goal of this optimization is to speed up the loading to 2.5 seconds (no more).


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)