Website with Varnish Cache
Squixa and section. io
Why you need a fast website
Problems making websites fast
How to make your website fast using Varnish
Demo — View of Varnish from section. io
SQUIXA AND SECT| ON. |O
We do web performance
Web optimisation platform (CDN, Site specific
optimisations and metrics)
section. io — New Varnish as a service platform
WHY YOU NEED A FAST SITE
Google study — 0.5 seconds slower = 20% less
Amazon study — 100ms faster = 10/0 revenue
0 SEO and Siteseed
I Organic search
I Adwords (PPC performance — landing pages)
THE PROBLEM - WHY SITES
0 2 broad areas that make up page load
(Frontend/ Backend time)
I What is a page load
I A click through to completed page
I A number of events happen end to end
I Identifying which events are causing issues
PAGE LOAD TECHNICAL VIEW
6.0 6.5 1 0 7 3.0 8.5 9.0
éééciénd (Origin) time
. uw lar) uh er
. uuw. c1ar) ubber.
mm . c 1 arkrubber‘
. IJI-IM. C1ar‘kl‘uI)I: I
ui-II-I . C 1 arkrubber
HOW TO SOLVE BACKEND
I HTML document performance issues are hard
0 HTML document generation is important to
I Seeing nothing is ugly
I Most of your hosting cost is spent making
HTML documents Server CPU
I Caching HTML documents in Varnish eliminates
I Varnish — Introduction
A caching HTTP reverse proxy
Must be a GET request, not a POST.
I No cookies in the request.
I Response Cache—ControI header allows caching.
I No cookies in the response.
. Identify which resources are user—specific.
. Strip cookies from non—user specific requests and
. Tune the Cache—Control response headers.
. Conditionally strip cookies by user workflow.