Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
1
Proprietary + Confidential
“
As users migrate to mobile,
page load time is perhaps
the most important metric
we have. If you can’t
load pages fast enough,
% We should aim to make
53 your site usable in2
you can’t compete.
Consumer expectations
in a mobile-led world
of visitors will abandon
3 seconds are extreme.
a site that takes >3s to load1
”
Howard Mittman,
Condé Nast
1. Statistic from Think With Google Research Study: “The Need for Mobile Speed: How Mobile Latency Impacts Publisher Revenue”
2. Usable on Mobile 3G (1.6Mbps/768 Kbps 300ms RTT) in 3 seconds.
2
Proprietary + Confidential
They won’t engage and convert if your site load time is slow
3
Proprietary + Confidential
$450,000.00 $450,000.00
25 10
$440,000.00 $400,000.00
$430,000.00
20
Faster load $350,000.00
8
$420,000.00
$410,000.00 15
time = more $300,000.00
$250,000.00 6
$380,000.00 $100,000.00
5 2
$370,000.00 $50,000.00
$360,000.00 0 $ 0
June July August June July August
2013 Revenue 2013 Avg Page Load Time 2014 Revenue 2014 Avg Page Load Time
*Source: "Site Speed & PPC Performance: Why You Can’t Ignore A Slow Site Anymore"
**Revenue uplift is not guaranteed. The purpose of sharing this case study is to show the potential impact that mobile speed load times has on revenue.
4
Proprietary + Confidential
Use these two tools to assess your mobile site speed performance
PageSpeed Insights WebPage Test
Page Speed Insights indicates whether your site page’s code WebPageTest helps you deepdive into issues affecting load
reflects standard best practices. It fetches the url with time. You can simulate many device types, see a waterfall
a mobile user-agent and identifies issues such as large of when resources load, and create slow-motion filmstrips
images, render-blocking JS, and lack of browser caching. of your site loading.
The PageSpeed Score ranges from 0 to 100 points. One metric to monitor from WebPageTest is the Speed
A higher score is better and a score of 85 or above indicates Index. It is the average time in milliseconds at which visible
that the page adheres well to best practices. parts of the page are displayed and is good for comparing
pages against each other (either competitor pages
or before/after).
Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
5
Framework for Faster Mobile Sites IT’S LIKE... moving into a new apartment.
It’s a much faster process if:
Give a Good First Impression 1. You can unpack the most essential items first
Goal: <3 seconds so the new place quickly feels like home.
Customers want to see visible content that is
“above-the-fold” as soon as possible. 2. You require fewer trips between the moving
Load important content first and make site
usable in 3 seconds. van and the apartment.
Reduce Number of Requests 3. The boxes are all light and therefore
Goal: <80 requests easy to move.
Requests = Number of resources the browser
needs to request from the server.
Fewer requests = faster load time.
ConfidentialConfidential 6
+ Proprietary+ Proprietary
Proprietary + Confidential
Note: Specific recommendations are suggestions for achieving “First Impressions,” “Number of Requests,” and “Page Weight” goals.
If your site is achieving the overall goal, the recommendations may further improve site speed. 7
Proprietary + Confidential
8
Proprietary + Confidential
CSS in Above-the-Fold In the case of an external CSS script the parser is also forced
to wait for the resource to download, which may incur one or
Content more network roundtrips and delay the time to first render of
the page. We need to avoid and minimize the use of blocking
CSS script, particularly external CSS scripts that must be
fetched before they can be executed.
Background
High Level Overview of the Solution
The browser builds the DOM tree before rendering a page by
parsing the HTML markup. Whenever the parser encounters a 1. Identify all the CSS files which causes render
CSS script it has to stop and execute it before it can continue blocking using PageSpeed Insights tool.
parsing the HTML. 2. Properly call your css files
a. Do not use @import to call css files
b. Properly label conditional css
3. Lessen the amount of css files in the critical path
a. Combine CSS
b. Inline CSS
4. Use less css overall
Step-by-step Guide
9
Proprietary + Confidential
We recommend that you set the cache time as long as possible, Step-by-step Guide
pushing out updates using cache-busting query strings.
Please refer to the PDF attached for step-by-step instructions!
10
Proprietary + Confidential
Appendix
Proprietary + Confidential
11
Proprietary + Confidential
12
Thank you!
Mobile
Speed
Optimisation
Session
13