WebPerf Cloudflare PageSpeed Cloudflare Speed Week

eva2000 · May 14, 2019

This week is Cloudflare Speed Week - this is it's first time launch where the whole week is dedicated to showcasing what Cloudflare is doing to speed up the internet and it's customers' web sites Cloudflare web acceleration has already shown to benefit alot of Centmin Mod Nginx users, so these new feature announcements are welcomed

All things Speed
Want a sneak peek at what we’re announcing this week? I’m really excited to see this week’s announcements unfold. Each day we’ll post a new blog where we’ll share product announcements and customer stories that demonstrate how we’re making life better for our customers.

Monday: An inside view of how we’re making faster, smarter routing decisions

Tuesday: HTTP/2 can be faster, we’ll show you how

Wednesday: Simplify image management and speed up load times on any device

Thursday: How we’re improving our network for faster video streaming

Friday: How we’re helping make JavaScript faster

For bonus points, sign up for a live stream webinar where Kornel Lesinksi and I will be hosted by Dennis Publishing to discuss the many challenges of the modern web “Stronger, Better, Faster: Solving the performance challenges of the modern web.” The event will be held on Monday, May 13th at 11:00 am BST and you can either register for the live event or sign up for one of the on-demand sessions later in the week.
Click to expand...

First up is Cloudflare blog post showcasing Cloudflare Argo and the new Cloudflare Global Private Backbone.

Today, we’re introducing the Cloudflare Global Private Backbone. It’s been in operation for a while now and links Cloudflare locations with private fiber connections.

This private backbone benefits all Cloudflare customers, and it shines in combination with Argo. Argo can select the best available link across the Internet on a per data center-basis, and takes full advantage of the Cloudflare Global Private Backbone automatically.

Let’s open the hood on Argo and explain how our backbone network further improves performance for our customers.

What’s Argo?
Argo is like Waze for the Internet. Every day, Cloudflare carries hundreds of billions of requests across our network and the Internet. Because our network, our customers, and their end-users are well distributed globally, all of these requests flowing across our infrastructure paint a great picture of how different parts of the Internet are performing at any given time.
Click to expand...

eva2000 · May 14, 2019

As a pagespeed addict, couldn't help myself so enabled Cloudflare Argo for centminmod.com and all domains i.e. this forum

Yes there's additional costs for Cloudflare Argo Smart Routing though https://support.cloudflare.com/hc/en-us/articles/115000224192

Guess I need to wait 48+ hrs before Cloudflare Argo Analytic statistics show up - querying Cloudflare Argo API

Code (Text):

curl -sX GET "https://api.cloudflare.com/client/v4/zones/${zid}/analytics/latency/colos" -H "Authorization: Bearer $cfkey" -H "Content-Type: application/json"
{
  "result": null,
  "success": true,
  "errors": null,
  "messages": [
    {
      "code": 1234,
      "message": "Argo Smart Routing is optimizing 87.0% of requests to your origin. There have not been enough requests to your origin in the last 48 hours to display detailed performance data."
    }
  ]
}

Cloudflare Argo Analytics starting to show up. From my custom cf-analytics.sh script querying both CF Zone and Argo Analaytics for a domain

this is Argo Analytics part

Code (Text):

./cf-analytics.sh 24hrs                                                 
------------------------------------------------------------------
  Cloudflare Argo Analytics
------------------------------------------------------------------
  since: 2019-05-13T21:53:00Z
  until: 2019-05-15T07:55:00Z
------------------------------------------------------------------
  Argo Response Time:
------------------------------------------------------------------
  request-without-argo: 6282
  request-with-argo: 56404
  argo-smarted-routed: 86.2%
  argo-improvement: 60.0600%
  without-argo: 383 (milliseconds)
  with-argo 153 (milliseconds)
------------------------------------------------------------------
  Argo Cloudflare Datacenter Response Times
------------------------------------------------------------------
  ATL  14584  0.6288817279605762   330.5444305381727   122.67107789358201
  LHR  1604   0.6415915970039859   472.99723756906076  169.52618453865335
  DME  1250   0.6375640659208469   726.6608391608391   263.368
  HAM  597    0.3539220653522123   333.6392405063291   215.5569514237856
  ORD  761    0.5590327372450438   207.5609756097561   91.52759526938239
  ARN  1276   0.538852376849302    475.388198757764    219.22413793103448
  FRA  3405   0.6163214864285327   533.5953608247422   204.72907488986783
  AMS  1822   0.6683572200088377   582.8351955307263   193.29308452250274
  AKL  772    0.4643016303689894   698.7755102040817   374.33290155440415
  NRT  1487   0.560084374861064    367.3787878787879   161.61566913248151
  SJC  429    0.5023774280374559   399.81481481481484  198.95687645687644
  EWR  997    0.6232081453363305   303.7109375         114.4358074222668
  SIN  2004   0.6172478683329683   639.2209302325581   244.6631736526946
  SEA  5231   0.3900570082855188   119.93859649122807  73.15570636589563
  IAD  13435  0.6250579033758243   327.0426829268293   122.62206922218087
  CDG  935    0.5750737863559962   512.445054945055    217.75133689839572
  YVR  965    0.4740699772952203   148.33333333333334  78.01295336787565
  BNE  543    0.44177230205679574  659.8015873015873   368.3195211786372
  HKG  1335   0.5311103779910232   474.05405405405406  222.27902621722848
  GRU  842    0.5846446654195169   706.1320754716982   293.2957244655582
  KBP  1549   0.6220275590440028   659.6005917159763   249.31084570690768
  MIA  637    0.6002104551734758   286.71875           114.62715855572998
  total-argo-reqs: 56460
  datacenter-calc-avg-resp-without: 382.6575
  datacenter-calc-avg-resp-with: 153.1784
  argo-improvement:
      min: 0.3539
      avg: 0.5571
      max: 0.6684
      stddev: 0.0863
  argo-resp-time-without-argo:
      min: 119.9386
      avg: 453.0086
      max: 726.6608
      stddev: 184.7685
  argo-resp-time-with-argo:
      min: 73.1557
      avg: 196.0579
      max: 374.3329
      stddev: 84.1581

eva2000 · May 15, 2019

Day 2 has Cloudflare reveal a new Enhanced HTTP/2 Priorization feature folks on Pro plan and above can enable https://blog.cloudflare.com/better-http-2-prioritization-for-a-faster-web/. Related background info on HTTP/2 Priorization in Pat's Youtube video talk at https://community.centminmod.com/th...resource-loading-prioritization-http-2.17478/

Already enabled Cloudflare's Enhanced HTTP/2 Priorization on centminmod.com site and this forum

eva2000 · May 15, 2019

Day 2 still related to HTTP/2 is new Cloudflare feature for parallel streaming of progressive images https://blog.cloudflare.com/parallel-streaming-of-progressive-images/ - currently is in beta so you need to sign up for beta testing.

Progressive image rendering and HTTP/2 multiplexing technologies have existed for a while, but now we've combined them in a new way that makes them much more powerful. With Cloudflare progressive streaming images appear to load in half of the time, and browsers can start rendering pages sooner.
Click to expand...

eva2000 · May 15, 2019

Day 3 of Cloudflare Speed Week for Image Resizing product for Business and higher plans - aka similar to ngx_pagespeed/mod_pagespeed https://blog.cloudflare.com/announcing-cloudflare-image-resizing-simplifying-optimal-image-delivery/

Today we are launching a new product, Image Resizing, to fix this problem once and for all.

Announcing Image Resizing
With Image Resizing, Cloudflare adds another important product to its suite of available image optimizations. This product allows customers to perform a rich set of the key actions on images.

Resize - The source image will be resized to the specified height and width. This action allows multiple different sized variants to be created for each specific use.

Crop - The source image will be resized to a new size that does not maintain the original aspect ratio and a portion of the image will be removed. This can be especially helpful for headshots and product images where different formats must be achieved by keeping only a portion of the image.

Compress - The source image will have its file size reduced by applying lossy compression. This should be used when slight quality reduction is an acceptable trade for file size reduction.

Convert to WebP - When the users browser supports it, the source image will be converted to WebP. Delivering a WebP image takes advantage of the modern, highly optimized image format.

By using a combination of these actions, customers store a single high quality image on their server, and Image Resizing can be leveraged to create specialized variants for each specific use case. Without any additional effort, each variant will also automatically benefit from Cloudflare’s global caching.
Click to expand...

Next Steps and Simple Pricing
Image Resizing is available today for Business and Enterprise Customers. To enable it, login to the Cloudflare Dashboard and navigate to the Speed Tab. There you’ll find the section for Image Resizing which you can enable with one click.

This product is included in the Business and Enterprise plans at no additional cost with generous usage limits. Business Customers have 100k requests per month limit and will be charged $10 for each additional 100k requests per month. Enterprise Customers have a 10M request per month limit with discounted tiers for higher usage. Requests are defined as a hit on a URI that contains Image Resizing or a call to Image Resizing from a Worker.

Now that you’ve enabled Image Resizing, it’s time to resize your first image.

Using your existing site, store an image here: https://yoursite.com/images/yourimage.jpg

Use this URL to resize that image:
https://yoursite.com/cdn-cgi/image/width=100,height=100,quality=75/images/yourimage.jpg

Experiment with changing width=, height=, and quality=.

The instructions above use the Default URL Format for Image Resizing. For details on options, uses cases, and compatibility, refer to our Developer Documentation.
Click to expand...

pamamolf · May 16, 2019

Damn this week will be for paid plans only?

eva2000 · May 17, 2019

Day 4, Cloudflare new Concurrent Video Streaming Acceleration for Enterprise account users https://blog.cloudflare.com/introducing-concurrent-streaming-acceleration/

Today we’re excited to introduce Concurrent Streaming Acceleration, a new technique for reducing the end-to-end latency of live video on the web when using Stream Delivery.
Click to expand...

The problem

To recap thus far:

Chunked encoding splits up video segments into smaller pieces

This can reduce end-to-end latency by allowing chunks to be fetched and decoded by players, even while segments are being produced at the origin server

Some CDNs neutralize the benefits of chunked encoding by buffering entire files inside the CDN before they can be delivered to clients

Click to expand...

The solution

Cloudflare’s solution: Concurrent Streaming Acceleration
As you may have guessed, we think we can do better. Put simply, we now have the ability to deliver un-cached files to multiple clients simultaneously while we pull the file once from the origin server.

This sounds like a simple change, but there’s a lot of subtlety to do this safely. Under the hood, we’ve made deep changes to our caching infrastructure to remove the cache lock and enable multiple clients to be able to safely read from a single file while it’s still being written.

The best part is – all of Cloudflare now works this way! There’s no need to opt-in, or even make a config change to get the benefit.

We rolled this feature out a couple months ago and have been really pleased with the results so far. We measure success by the “cache lock wait time,” i.e. how long a request must wait for other requests – a direct component of Time To First Byte. One OTT customer saw this metric drop from 1.5s at P99 to nearly 0, as expected:
Click to expand...

Conclusion
New techniques like chunked encoding have revolutionized live delivery, enabling publishers to deliver low-latency live video at scale. Concurrent Streaming Acceleration helps you unlock the power of this technique at your CDN, potentially shaving precious seconds of end-to-end latency.
Click to expand...

eva2000 · May 18, 2019

Day 5, Faster script loading with BinaryAST?

he performance of applications on the web platform is becoming increasingly bottlenecked by the startup (load) time. Large amounts of JavaScript code are required to create rich web experiences that we’ve become used to. When we look at the total size of JavaScript requested on mobile devices from HTTPArchive, we see that an average page loads 350KB of JavaScript, while 10% of pages go over the 1MB threshold. The rise of more complex applications can push these numbers even higher.

While caching helps, popular websites regularly release new code, which makes cold start (first load) times particularly important. With browsers moving to separate caches for different domains to prevent cross-site leaks, the importance of cold starts is growing even for popular subresources served from CDNs, as they can no longer be safely shared.

Usually, when talking about the cold start performance, the primary factor considered is a raw download speed. However, on modern interactive pages one of the other big contributors to cold starts is JavaScript parsing time. This might seem surprising at first, but makes sense - before starting to execute the code, the engine has to first parse the fetched JavaScript, make sure it doesn’t contain any syntax errors and then compile it to the initial bytecode. As networks become faster, parsing and compilation of JavaScript could become the dominant factor.
Click to expand...

deltahf · May 19, 2019

eva2000 said: ↑

As a pagespeed addict, couldn't help myself so enabled Cloudflare Argo for centminmod.com and all domains i.e. this forum

Yes there's additional costs for Cloudflare Argo Smart Routing though https://support.cloudflare.com/hc/en-us/articles/115000224192

Guess I need to wait 48+ hrs before Cloudflare Argo Analytic statistics show up - querying Cloudflare Argo API

Code (Text):

curl -sX GET "https://api.cloudflare.com/client/v4/zones/${zid}/analytics/latency/colos" -H "Authorization: Bearer $cfkey" -H "Content-Type: application/json"
{
  "result": null,
  "success": true,
  "errors": null,
  "messages": [
    {
      "code": 1234,
      "message": "Argo Smart Routing is optimizing 87.0% of requests to your origin. There have not been enough requests to your origin in the last 48 hours to display detailed performance data."
    }
  ]
}

Cloudflare Argo Analytics starting to show up. From my custom cf-analytics.sh script querying both CF Zone and Argo Analaytics for a domain

this is Argo Analytics part

Code (Text):

./cf-analytics.sh 24hrs                                               
------------------------------------------------------------------
  Cloudflare Argo Analytics
------------------------------------------------------------------
  since: 2019-05-13T21:53:00Z
  until: 2019-05-15T07:55:00Z
------------------------------------------------------------------
  Argo Response Time:
------------------------------------------------------------------
  request-without-argo: 6282
  request-with-argo: 56404
  argo-smarted-routed: 86.2%
  argo-improvement: 60.0600%
  without-argo: 383 (milliseconds)
  with-argo 153 (milliseconds)
------------------------------------------------------------------
  Argo Cloudflare Datacenter Response Times
------------------------------------------------------------------
  ATL  14584  0.6288817279605762   330.5444305381727   122.67107789358201
  LHR  1604   0.6415915970039859   472.99723756906076  169.52618453865335
  DME  1250   0.6375640659208469   726.6608391608391   263.368
  HAM  597    0.3539220653522123   333.6392405063291   215.5569514237856
  ORD  761    0.5590327372450438   207.5609756097561   91.52759526938239
  ARN  1276   0.538852376849302    475.388198757764    219.22413793103448
  FRA  3405   0.6163214864285327   533.5953608247422   204.72907488986783
  AMS  1822   0.6683572200088377   582.8351955307263   193.29308452250274
  AKL  772    0.4643016303689894   698.7755102040817   374.33290155440415
  NRT  1487   0.560084374861064    367.3787878787879   161.61566913248151
  SJC  429    0.5023774280374559   399.81481481481484  198.95687645687644
  EWR  997    0.6232081453363305   303.7109375         114.4358074222668
  SIN  2004   0.6172478683329683   639.2209302325581   244.6631736526946
  SEA  5231   0.3900570082855188   119.93859649122807  73.15570636589563
  IAD  13435  0.6250579033758243   327.0426829268293   122.62206922218087
  CDG  935    0.5750737863559962   512.445054945055    217.75133689839572
  YVR  965    0.4740699772952203   148.33333333333334  78.01295336787565
  BNE  543    0.44177230205679574  659.8015873015873   368.3195211786372
  HKG  1335   0.5311103779910232   474.05405405405406  222.27902621722848
  GRU  842    0.5846446654195169   706.1320754716982   293.2957244655582
  KBP  1549   0.6220275590440028   659.6005917159763   249.31084570690768
  MIA  637    0.6002104551734758   286.71875           114.62715855572998
  total-argo-reqs: 56460
  datacenter-calc-avg-resp-without: 382.6575
  datacenter-calc-avg-resp-with: 153.1784
  argo-improvement:
      min: 0.3539
      avg: 0.5571
      max: 0.6684
      stddev: 0.0863
  argo-resp-time-without-argo:
      min: 119.9386
      avg: 453.0086
      max: 726.6608
      stddev: 184.7685
  argo-resp-time-with-argo:
      min: 73.1557
      avg: 196.0579
      max: 374.3329
      stddev: 84.1581

Click to expand...

Really cool to see those statistics.

I would absolutely love to have it myself... I have a very international audience and I think a lot of my low cache rate is simply from the fact that people are accessing so many different edges. Unfortunately, it would take my Cloudflare bill from $25/month to $1k+/month.

eva2000 · May 19, 2019

Yeah Cloudflare Argo is costly if you're not a for-profit site earning revenues to cover the cost but it is showing good benefits since I enabled it, so Google Webmaster Tools's reported Crawl Statistics show Google bot's download time has improved noticeably from May 14th onwards - when I enabled Cloudflare Argo from ~304ms to 178-180ms ! Which potentially means you have increased your Google crawl rate and Google crawl budget by >41% !

eva2000 · May 20, 2019

pamamolf said: ↑

Damn this week will be for paid plans only?
Click to expand...

indeed alot of the new CF speed improvements seem to be for paid plans or paid options unfortunately

eva2000 · May 21, 2019

Final item for Cloudlfare Speed Week, new Speed page https://blog.cloudflare.com/new-speed-page/

This post will describe the exciting changes we have made to the Speed Page on the Cloudflare dashboard to give our customers a much clearer understanding of how their websites are performing and how they can be made even faster. The new Speed Page consists of :

A visual comparison of your website loading on Cloudflare, with caching enabled, compared to connecting directly to the origin.

The measured improvement expected if any performance feature is enabled.

A report describing how fast your website is on desktop and mobile.

We want to simplify the complexity of making web experiences fast and give our customers control. Take a look - We hope you like it.
Click to expand...

Nice Patrick Meenan's Webpagetest.org work reflected in this new Cloudflare Speed page - FYI Patrick has left Google to work for Cloudflare for folks who didn't know

and

As a bonus, we’re also rolling out one more new feature: “TCP Turbo” automatically chooses the TCP settings to further accelerate your website.
Click to expand...

eva2000 · May 23, 2019

Follow up from HTTP/2 Enhanced Prioritization work - https://blog.cloudflare.com/nginx-structural-enhancements-for-http-2-performance/ and work on improving Nginx internals in relation to HTTP/2 HTTPS.

My team: the Cloudflare PROTOCOLS team is responsible for termination of HTTP traffic at the edge of the Cloudflare network. We deal with features related to: TCP, QUIC, TLS and Secure Certificate management, HTTP/1 and HTTP/2. Over Q1, we were responsible for implementing the Enhanced HTTP/2 Prioritization product that Cloudflare announced during Speed Week.

This is a very exciting project to be part of, and doubly exciting to see the results of, but during the course of the project, we had a number of interesting realisations about NGINX: the HTTP oriented server onto which Cloudflare currently deploys its software infrastructure. We quickly became certain that our Enhanced HTTP/2 Prioritization project could not achieve even moderate success if the internal workings of NGINX were not changed.

Due to these realisations we embarked upon a number of significant changes to the internal structure of NGINX in parallel to the work on the core prioritization product. This blog post describes the motivation behind the structural changes, how we approached them, and what impact they had. We also identify additional changes that we plan to add to our roadmap, which we hope will improve performance further.
Click to expand...

The Enhanced HTTP/2 Prioritization project has the lofty goal of fundamentally re-shaping how we send traffic from the Cloudflare edge to clients, and as results of our testing and feedback from some of our customers shows, we have certainly achieved that! However, one of the most important aspects that we took away from the project was the critical role the internal data flow within our NGINX software infrastructure plays in the outlook of the traffic observed by our end users. We found that changing a few lines of (albeit critical) code, could have significant impacts on the effectiveness and performance of our prioritization algorithms. Another positive outcome is that in addition to improving HTTP/2, we are looking forward to carrying our newfound skills and lessons learned and apply them to HTTP/3 over QUIC.

We are eager to share our modifications to NGINX with the community, so we have opened this ticket, through which we will discuss upstreaming the event re-ordering change and the buffer partial re-use change with the NGINX team.

As Cloudflare continues to grow, our requirements on our software infrastructure also shift. Cloudflare has already moved beyond proxying of HTTP/1 over TCP to support termination and Layer 3 and 4 protection for any UDP and TCP traffic. Now we are moving on to other technologies and protocols such as QUIC and HTTP/3, and full proxying of a wide range of other protocols such as messaging and streaming media.
Click to expand...

Log in / Register

Forums

Learn about Centmin Mod LEMP Stack today

WebPerf Cloudflare PageSpeed Cloudflare Speed Week

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

deltahf Premium Member Premium Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

.

Log in / Register

Useful Searches

Learn about Centmin Mod LEMP Stack today

WebPerf Cloudflare PageSpeed Cloudflare Speed Week

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

deltahf Premium Member Premium Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

.